[DragonFlyBSD - Bug #2611] Change in IP address results in network not working

[bugtracker-admin at leaf.dragonflybsd.org]

Issue #2611 has been updated by phma.


Darner does not have the bug of sending an IPv4 packet with the old source address. It does have a default gateway beginning with fe80 after its address was changed on it, but that apparently does not cause a problem with only one network card.

----------------------------------------
Bug #2611: Change in IP address results in network not working
http://bugs.dragonflybsd.org/issues/2611#change-11666

* Author: phma
* Status: New
* Priority: Normal
* Assignee: 
* Category: 
* Target version: 
----------------------------------------
I'm on a satellite connection and am assigned a public IPv6 address and an IPv4 address in shared address space behind NAT. Occasionally the network goes down, and I get new addresses. This does not bother the Linux boxes (except that I have to edit /etc/hosts so that they know where each other are) but the DragonFly box is unable to reach any hosts except on the LAN, and that only on IPv6.

In IPv4, after the address change, a ping from 100.116.42.28 (Linux laptop) to 100.116.42.26 (DragonFly box) is answered by a pong from 100.116.27.42 (DFly's old address, which no longer appears in ifconfig) to 100.116.42.28.

In IPv6, after the address change, the default gateway begins with fe80 instead of 2001. The attached files are:
routebad: the routing table (netstat -rn) after a previous address change
routegood: the routing table after rebooting
routebadagain: the routing table after the most recent address change.
After rebooting, I had to find the gateway by asking the Linux box and set it manually; this may not be a bug, as normally zyxomma runs a tunnel, and the IPv6 gateway was pointing to an address in the tunnel.


-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account