Adding IPv6 address to vlan in UNKNOWN state results in routes that expire within 30 days.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Confirmed
|
Medium
|
Unassigned |
Bug Description
We noticed that after adding IPv6 address to vlan route to local network is added with expiration time. If after `ip link set vlanXXX up` up we wait until vlan's link state becomes UP then route get added without expiration time.
We are using Ubuntu LTS 10.04: Ubuntu 2.6.32-32.62-server 2.6.32.38+drm33.16.
To reproduce one can use following test script:
$ cat test.sh
ip addr del 2a02::1.1.1.1/64 dev vlan764 || :
vconfig rem vlan764 || :
vconfig set_name_type VLAN_PLUS_
vconfig add eth0 764
ip link set vlan764 up
#sleep 5
ip addr add 2a02::1.1.1.1/64 dev vlan764
sleep 2
ip -6 route show
$ sudo ./test.sh
2a02::/64 dev vlan764 proto kernel metric 256 expires 2591999sec mtu 8950 advmss 8890 hoplimit 4294967295
fe80::/64 dev eth0 proto kernel metric 256 mtu 8950 advmss 8890 hoplimit 4294967295
fe80::/64 dev vlan764 proto kernel metric 256 mtu 8950 advmss 8890 hoplimit 4294967295
default via fe80::226:
Notice `expires 2591999sec` in `2a02::/64 dev vlan764 ` route
Now uncomment `#sleep 5`
$ sudo ./test.sh
2a02::/64 dev vlan764 proto kernel metric 256 mtu 8950 advmss 8890 hoplimit 4294967295
fe80::/64 dev eth0 proto kernel metric 256 mtu 8950 advmss 8890 hoplimit 4294967295
fe80::/64 dev vlan764 proto kernel metric 256 mtu 8950 advmss 8890 hoplimit 4294967295
default via fe80::226:
Now `expire` is gone.
description: | updated |
Changed in linux (Ubuntu): | |
status: | Incomplete → Confirmed |
summary: |
- Adding address to vlan in UNKNOWN state results in routes that expire - within 30 days. + Adding IPv6 address to vlan in UNKNOWN state results in routes that + expire within 30 days. |
This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:
apport-collect 917643
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.