Re: kernel/2278

[Darren Reed <darrenr@reed.wattle.id.au>]

Neither NetBSD or FreeBSD work this way - changing the interface address
automatically leads to the IP# in the route being changed.

Just as I do not manually create the host route, neither should I have
to flush the routing table manually.

If this is really being left like this and closed then changing IP
addresses for interfaces under OpenBSD does not work as it does elsewhere.
It might also lead to unexpected results (security problems, especially)
and people believing they need to reboot in order for an IP address change
to take effect.

I'm not sure why anyone would want to continue using an old IP address to
talk to a remote host once it has been discarded.  The host itself is not
going to respond to it and in a configuration where dynamic addresses are
being used for source address filtering in pf, will lead to blocked packets
when the user did not intend for such.

In some email I received from Jun-ichiro itojun Hagino, sie wrote:
> Synopsis: changing IP# with ifconfig results in old IP# still being used
> 
> State-Changed-From-To: open->closed
> State-Changed-By: itojun
> State-Changed-When: Sat Jun 8 23:56:35 MDT 2002
> State-Changed-Why: 
> this is not a bug but a feature.  you must nuke and reinstall route if you change interface address.
> 
> .