ipv6 global address remains while route item disappears after this interface is restared in 2.6.34.x
With two directly connected targets running kernel 2.6.34.x. TargetA - TargetB 3000::1/643000::2/64 TargetA - bring the interface down by doing an "ifconfig eth1 down" - bring the interface back up by doing an "ifconfig eth1 up" TargetB - ping6 3000::1 ping6 succeeds the first time - after bringing the interface on TargetA down and then back up, ping6 to the interface fails. The root cause is: IPv6 address 3000::1/64 remains while the ipv6 route on eth1 disappears. Thus on TargetB, running "ping6 3000::1" can not succeed. Compared with 3.4.x, ipv6 address and ipv6 route item are removed when an interface is restarted in the. Best Regards! zhuyj -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
ipv6 global address remains while route item disappears after this interface is restared in 2.6.34.x
With two directly connected targets running kernel 2.6.34.x. TargetA - TargetB 3000::1/643000::2/64 TargetA - bring the interface down by doing an ifconfig eth1 down - bring the interface back up by doing an ifconfig eth1 up TargetB - ping6 3000::1 ping6 succeeds the first time - after bringing the interface on TargetA down and then back up, ping6 to the interface fails. The root cause is: IPv6 address 3000::1/64 remains while the ipv6 route on eth1 disappears. Thus on TargetB, running ping6 3000::1 can not succeed. Compared with 3.4.x, ipv6 address and ipv6 route item are removed when an interface is restarted in the. Best Regards! zhuyj -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
