> From: Archie Cobbs [mailto:[EMAIL PROTECTED]] > Sent: November 21, 2002 16:54 > To: Don Bowman > Cc: 'Wes Peters'; Archie Cobbs; [EMAIL PROTECTED] > Subject: Re: Sockets and changing IP addresses > > > Don Bowman wrote: > > > > 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? > > > > > > Yes. The other end can't possibly reply to address X, so the > > > connection is broken at this point. > > > > I think the current behaviour is correct. Since the IP->MAC lookup > > will remain cached, the communication will continue to work > to the old > > IP. Changing the IP on the connected socket will make the connection > > drop. The best case is the the way it works. > > What you're saying doesn't make sense to me. First of all, this has > nothing to do with ARP tables (although you are right that > the router's > ARP entry for the old IP address will remain valid). Secondly, the > communiation will NOT work because the host will drop packets sent > to it with the (now) wrong IP address. > > The current behavior is bad because the application does not ever > receive any notification that the socket it's using is no longer > valid.
I guess I was thinking of the transparent proxy case (e.g. Squid) where I have a ipfw fwd rule, and the socket is terminated locally. Changing the IP address of the interface shouldn't drop my proxied connection. --don ([EMAIL PROTECTED] www.sandvine.com) To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-net" in the body of the message
