ipv6 iface/address inaccessible wihen link state DOWN
TO | OS4.x beta 1 | router mode installation with medkit
Whilst ipv4 ifaces are reachable (ping
| traceroute
) their equivalent ipv6 addresses are not when the iface's link status is DOWN (no client connected). Once a client is connected to the iface and the link status changes to UP the iface's ipv6 address becomes reachable - tried this many times and it reproduced the same result eacht time.
Since running most services (e.g. sshd, resolver, lighttpd) on a management iface rather than lan this makes it impossible to bind those services to the respective ipv6 address of the management iface.
connected to the TO via lan iface
ip -o a show br-lan
22: br-lan: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP qlen 1000\ link/ether d8:58:d7:00:79:7a brd ff:ff:ff:ff:ff:ff
22: br-lan inet 192.168.84.23/24 brd 192.168.84.255 scope global br-lan\ valid_lft forever preferred_lft forever
22: br-lan inet6 xxxx:xxxx:6b29:c301:4fec:a3c8:3aac:8eb5/64 scope global dynamic \ valid_lft 78123sec preferred_lft 78123sec
22: br-lan inet6 fd30:d64c:1eed:9a9b:3f80:9f6b:48d:96f3/64 scope global \ valid_lft forever preferred_lft forever
22: br-lan inet6 fe80::da58:d7ff:fe00:797a/64 scope link \ valid_lft forever preferred_lft forever
and from there trying to reach the management iface
ip -o a show br-mgt
23: br-mgt: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN qlen 1000\ link/ether d8:58:d7:00:79:7a brd ff:ff:ff:ff:ff:ff
23: br-mgt inet 192.168.112.12/24 brd 192.168.112.255 scope global br-mgt\ valid_lft forever preferred_lft forever
23: br-mgt inet6 xxxx:xxxx:6b29:c302:fadb:150a:99c6:deed/64 scope global tentative dynamic \ valid_lft 77865sec preferred_lft 77865sec
23: br-mgt inet6 fd30:d64c:1eed:4c3a:db0e:5fb6:97d9:f9e5/64 scope global tentative \ valid_lft forever preferred_lft forever
23: br-mgt inet6 fd30:d64c:1eed:4c3a::12/128 scope global tentative \ valid_lft forever preferred_lft forever
which works with ipv4
traceroute 192.168.112.12
traceroute to 192.168.112.12 (192.168.112.12), 30 hops max, 38 byte packets
1 192.168.112.12 (192.168.112.12) 0.011 ms 0.009 ms 0.008 ms
but fails with ipv6
traceroute fd30:d64c:1eed:4c3a::12
traceroute to fd30:d64c:1eed:4c3a::12 (fd30:d64c:1eed:4c3a::12), 30 hops max, 64 byte packets
1 fd30:d64c:1eed:9a9b:3f80:9f6b:48d:96f3 (fd30:d64c:1eed:9a9b:3f80:9f6b:48d:96f3) 3138.885 ms !H 3129.493 ms !H 3109.975 ms !H
The management iface appaears to be UP, indicated by the reachability over ipv4 and also running ip l show up | grep mgt
or ifstatus mgt
or ubus list network.interface.*
.
However, dmesg | grep mgt
produces
[ 21.372098] IPv6: ADDRCONF(NETDEV_UP): br-mgt: link is not ready
[ 21.402853] br-mgt: port 1(lan3) entered blocking state
[ 21.408109] br-mgt: port 1(lan3) entered disabled state
This seems rather curious/odd, ipv4 netdev is reachable whilst ipv6 netdev is not, unless a client gets connected and the link state changes to UP.
The issue is not present in TOS3.11.4