devel:blueprints:pping-ipv6
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
|
devel:blueprints:pping-ipv6 [2011/04/03 09:44] morten [Pointers] |
devel:blueprints:pping-ipv6 [2011/06/14 12:58] (current) morten [Pointers] |
||
|---|---|---|---|
| Line 16: | Line 16: | ||
| A few places in the pping code makes assumptions about what an IP address string looks like, and currently, a single AF_INET socket is used for sending ICMPv4 packets. Probably the best way to go is to add an AF_INET6 socket as well, then select the sending socket based on the destination IP address family, and adding the new socket to the socket list of the select() call used to receive data. | A few places in the pping code makes assumptions about what an IP address string looks like, and currently, a single AF_INET socket is used for sending ICMPv4 packets. Probably the best way to go is to add an AF_INET6 socket as well, then select the sending socket based on the destination IP address family, and adding the new socket to the socket list of the select() call used to receive data. | ||
| + | |||
| + | This ICMP-packet manipulating code can probably be reused in NAV: http://code.activestate.com/recipes/409689-icmplib-library-for-creating-and-reading-icmp-pack/ (PSF license, which I believe is compatible with GPL) | ||
devel/blueprints/pping-ipv6.1301823853.txt.gz ยท Last modified: 2011/04/03 09:44 by morten
Page Tools
