Hi Rao,
On Wed, 12 Apr 2006, Rao Shoaib wrote:
Hullo,
IP_RECVPKTINFO Enable/disable receipt of the index of the
interface the packet arrived on, the local
address that was matched for reception, and of
the inbound packet's actual destination
address. Takes boolean as the
IP_PKTINFO Set the source address and/or interface out
which the packet(s) will be sent. Takes a
struct in4_pktinfo as the parameter.
struct in4_pktinfo {
This implementation is not compatible with the Linux implementation of
IP_PKTINFO.
Good to see this, but still: *Groan*. Are there good reasons to be
incompatible with Linux and, worse, /contrary/ to the established usage?
This just makes things very tedious for users and leads to much auto*
and ifdef ickyness (needlessly?).
IP_RECVPKTINFO:
It really ought to be made compatible with the existing IP_PKTINFO
implementation for the sanity of users.
IP_PKTINFO:
a) Call this something else (to avoid Linux IP_PKTINFO clash)
b) Remove the ifindex member from the struct to avoid clashing with
routing (raw + IP_HDRINCL remains an option for those wanting
such absolute control over outbound interface selection).
Alternatively document that ifindex is ignored for the option (if you
want to reuse the struct across both options) - might be mildly
confusing though.
regards,
--
Paul Jakma,
Network Approachability, KISS. http://quagga.ireland.sun.com/
Sun Microsystems, Dublin, Ireland. tel: EMEA x19190 / +353 1 819 9190
_______________________________________________
networking-discuss mailing list
[email protected]
