You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Software versions of OpenWrt/LEDE release, packages, etc.
Steps to reproduce
With no client (NO-CARRIER) connected to the br-iface its ipv6 is not accessible whilst ipv4 is. Connecting a client to the br-iface and its ipv6 becomes accessible.
It would be expected that the br-iface is accessible not only via ipv4 but also ipv6 regardless of the Carrier state as long as the br-iface is up.
ip l show up | grep mgt
8: lan3@eth1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue master br-mgt state LOWERLAYERDOWN mode DEFAULT group default qlen 1000
18: br-mgt: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default qlen 1000
ip -o a show br-mgt
18: br-mgt inet 192.168.112.12/24 brd 192.168.112.255 scope global br-mgt\ valid_lft forever preferred_lft forever
18: br-mgt inet6 fd30:d64c:1eed:4c3a:17c8:d407:23a0:d524/64 scope global tentative noprefixroute \ valid_lft forever preferred_lft forever
18: br-mgt inet6 fd30:d64c:1eed:4c3a::12/128 scope global tentative \ valid_lft forever preferred_lft forever
ip routing tables of the br-iface with NO-CARRIER
ip route show table all dev br-mgt
192.168.112.0/24 proto kernel scope link src 192.168.112.12 linkdown
broadcast 192.168.112.0 table local proto kernel scope link src 192.168.112.12 linkdown
local 192.168.112.12 table local proto kernel scope host src 192.168.112.12
broadcast 192.168.112.255 table local proto kernel scope link src 192.168.112.12 linkdown
fd30:d64c:1eed:4c3a::12 proto kernel metric 256 linkdown pref medium
fd30:d64c:1eed:4c3a::/64 proto static metric 1024 linkdown pref medium
ff00::/8 table local metric 256 linkdown pref medium
ip routing tables of the br-iface with CARRIER
ip route show table all dev br-mgt
192.168.112.0/24 proto kernel scope link src 192.168.112.12
broadcast 192.168.112.0 table local proto kernel scope link src 192.168.112.12
local 192.168.112.12 table local proto kernel scope host src 192.168.112.12
broadcast 192.168.112.255 table local proto kernel scope link src 192.168.112.12
fd30:d64c:1eed:4c3a::12 proto kernel metric 256 pref medium
fd30:d64c:1eed:4c3a::/64 proto static metric 1024 pref medium
fe80::/64 proto kernel metric 256 pref medium
anycast fd30:d64c:1eed:4c3a:: table local proto kernel metric 0 pref medium
local fd30:d64c:1eed:4c3a::12 table local proto kernel metric 0 pref medium
local fd30:d64c:1eed:4c3a:17c8:d407:23a0:d524 table local proto kernel metric 0 pref medium
anycast fe80:: table local proto kernel metric 0 pref medium
local fe80::da58:d7ff:fe00:797a table local proto kernel metric 0 pref medium
ff00::/8 table local metric 256 pref medium
Comparing the ip routing tables of the different Carrier states it is apparent that NO-CARRIER state is short of a few routing entries pertaining to ipv6.
The text was updated successfully, but these errors were encountered:
n8v8R:
Supply the following if possible:
ubus -S call system board
{"kernel":"4.14.113","hostname":"to","system":"ARMv7 Processor rev 1 (v7l)","model":"Turris Omnia","board_name":"armada-385-turris-omnia","release":{"distribution":"TurrisOS","version":"4.0-beta1","revision":"0663455801","target":"mvebu/cortexa9","description":"TurrisOS 4.0-beta1 0663455801"}}
With no client (NO-CARRIER) connected to the br-iface its ipv6 is not accessible whilst ipv4 is. Connecting a client to the br-iface and its ipv6 becomes accessible.
It would be expected that the br-iface is accessible not only via ipv4 but also ipv6 regardless of the Carrier state as long as the br-iface is up.
config globals 'globals'
option ula_prefix 'fd30:d64c:1eed::/48'
config interface 'mgt'
option type 'bridge'
option bridge_empty '1'
option proto 'static'
option ipaddr '192.168.112.12'
option netmask '255.255.255.0'
list ip6addr 'fd30:d64c:1eed:4c3a::12'
option ip6assign '64'
option ip6hint '4c3a'
option ip6ifaceid 'random'
option ifname 'lan3'
ifstatus mgt
{
"up": true,
"pending": false,
"available": true,
"autostart": true,
"dynamic": false,
"uptime": 44703,
"l3_device": "br-mgt",
"proto": "static",
"device": "br-mgt",
"updated": [
"addresses"
],
"metric": 0,
"dns_metric": 0,
"delegation": true,
"ipv4-address": [
{
"address": "192.168.112.12",
"mask": 24
}
],
"ipv6-address": [
{
"address": "fd30:d64c:1eed:4c3a::12",
"mask": 128
}
],
"ipv6-prefix": [
}
ip l show up | grep mgt
8: lan3@eth1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue master br-mgt state LOWERLAYERDOWN mode DEFAULT group default qlen 1000
18: br-mgt: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default qlen 1000
ip -o a show br-mgt
18: br-mgt inet 192.168.112.12/24 brd 192.168.112.255 scope global br-mgt\ valid_lft forever preferred_lft forever
18: br-mgt inet6 fd30:d64c:1eed:4c3a:17c8:d407:23a0:d524/64 scope global tentative noprefixroute \ valid_lft forever preferred_lft forever
18: br-mgt inet6 fd30:d64c:1eed:4c3a::12/128 scope global tentative \ valid_lft forever preferred_lft forever
ip route show table all dev br-mgt
192.168.112.0/24 proto kernel scope link src 192.168.112.12 linkdown
broadcast 192.168.112.0 table local proto kernel scope link src 192.168.112.12 linkdown
local 192.168.112.12 table local proto kernel scope host src 192.168.112.12
broadcast 192.168.112.255 table local proto kernel scope link src 192.168.112.12 linkdown
fd30:d64c:1eed:4c3a::12 proto kernel metric 256 linkdown pref medium
fd30:d64c:1eed:4c3a::/64 proto static metric 1024 linkdown pref medium
ff00::/8 table local metric 256 linkdown pref medium
ip route show table all dev br-mgt
192.168.112.0/24 proto kernel scope link src 192.168.112.12
broadcast 192.168.112.0 table local proto kernel scope link src 192.168.112.12
local 192.168.112.12 table local proto kernel scope host src 192.168.112.12
broadcast 192.168.112.255 table local proto kernel scope link src 192.168.112.12
fd30:d64c:1eed:4c3a::12 proto kernel metric 256 pref medium
fd30:d64c:1eed:4c3a::/64 proto static metric 1024 pref medium
fe80::/64 proto kernel metric 256 pref medium
anycast fd30:d64c:1eed:4c3a:: table local proto kernel metric 0 pref medium
local fd30:d64c:1eed:4c3a::12 table local proto kernel metric 0 pref medium
local fd30:d64c:1eed:4c3a:17c8:d407:23a0:d524 table local proto kernel metric 0 pref medium
anycast fe80:: table local proto kernel metric 0 pref medium
local fe80::da58:d7ff:fe00:797a table local proto kernel metric 0 pref medium
ff00::/8 table local metric 256 pref medium
Comparing the ip routing tables of the different Carrier states it is apparent that NO-CARRIER state is short of a few routing entries pertaining to ipv6.
The text was updated successfully, but these errors were encountered: