https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=187203
--- Comment #7 from Xin LI <[email protected]> --- (In reply to andy zhang from comment #6) Hi, Is there a specific use case for the possible issue if SIOCGIFADDR is not handled there? Actually this is a follow up of changeset 277103 [1] which is review request D1508 [2] and you may find additional information there. My main reasoning is that the SIOCGIFADDR (get interface address) is used to "observe" the interface object, or a "get" accessor, and semantically it shouldn't bump the interface, like triggering an ARP broadcast, etc. like SIOCSIFADDR (set interface address) does. If we do it for SIOCGIFADDR too, there may be some undesired behavior (e.g. an 'ifconfig' would cause the interface to announce its IP address). We can indeed add it back if there is good reason to do so, but I haven't yet see one... [1] https://svnweb.freebsd.org/base/head/sys/dev/xen/netfront/netfront.c?r1=276750&r2=277103 [2] https://reviews.freebsd.org/D1508 -- You are receiving this mail because: You are the assignee for the bug. _______________________________________________ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-emulation To unsubscribe, send any mail to "[email protected]"
