stupid pet tricks (using ifconfig)
Wierdness in 4.2. Scenario: interface fxp0 has address 100.1.1.1. Use it with this address for awhile. decide to change it to 100.1.1.5. do: ifconfig fxp0 delete 100.1.1.1 ifconfig fxp0 100.1.1.5 netmask 255.255.255.0 viewing ifconfig shows the new address. HOWEVER, pinging 100.1.1.99, the freebsd machine sends out 100.1.1.1, the OLD address. Is this cached/saved somewhere and not getting cleaned up? Dennis To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message
Re: stupid pet tricks (using ifconfig)
viewing ifconfig shows the new address. HOWEVER, pinging 100.1.1.99, the freebsd machine sends out 100.1.1.1, the OLD address. Is this cached/saved somewhere and not getting cleaned up? in the routing table, apparently. If you do a "route -n get" for the destination address you see the old one. Manually flushing the relevant entries in the routing table does the job (yes it is a bug, it should happen automatically, and it is not 4.2 specific, it has been there forever) cheers luigi To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-hackers" in the body of the message