Date: Tue, 12 Nov 2002 15:16:52 -0800 (PST) From: Archie Cobbs <archie@dellroad.org> To: freebsd-net@freebsd.org Subject: Sockets and changing IP addresses Message-ID: <200211122316.gACNGqWC017440@arch20m.dellroad.org>
next in thread | raw e-mail | index | archive | help
I'm curious what -net's opinion is on PR kern/38544:
http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/38554
In summary: if you have a connected socket whose local IP address
is X, and then change the interface IP address from X to Y, then
packets written out by the socket will continue to be transmitted
with source IP address X.
Do people agree that this is a bug and should be fixed?
Do people agree that my suggestion of returning ENETDOWN is reasonable?
If so, what would be the most efficient way to implement this?
Obviously we'd like to avoid searching the entire IP address list
for every outgoing packet. Would it work to only do that search if
the socket's cached route is invalid? Etc.
Thanks,
-Archie
__________________________________________________________________________
Archie Cobbs * Packet Design * http://www.packetdesign.com
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-net" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200211122316.gACNGqWC017440>