Modify

Opened 3 years ago

Last modified 3 years ago

#17518 new defect

"IPv6 WAN Status" on Status page shows "Not connected", but system has IPv6 address

Reported by: anonymous Owned by:
Priority: low Milestone:
Component: luci Version: Barrier Breaker 14.07
Keywords: Cc:

Description

I am using BB RC3 on a WR703N. OpenWRT is configured as AP. I got a public IPv4 addr and a public IPv6 prefix from my provider and use IPv6 if possible.

ETH0 is attached to my LAN and gets v4 addr and v6 addr from router. ifconfig shows this addresses:
root@wr703n02:~# ifconfig
br-lan Link encap:Ethernet HWaddr 14:CF:92:6D:xx:xx

inet addr:192.168.178.67 Bcast:192.168.178.255 Mask:255.255.255.0
inet6 addr: 2a02:xxxx:xxxx:xxxx:xxxx:xxx:fe6d:xxxx/64 Scope:Global
inet6 addr: fe80::16cf:92ff:fe6d:xxxx/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:23251 errors:0 dropped:0 overruns:0 frame:0
TX packets:7630 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1839753 (1.7 MiB) TX bytes:1708722 (1.6 MiB)

eth0 Link encap:Ethernet HWaddr 14:CF:92:6D:xx:xx

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:30556 errors:0 dropped:3 overruns:0 frame:0
TX packets:7749 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:3944584 (3.7 MiB) TX bytes:1718762 (1.6 MiB)
Interrupt:4

lo Link encap:Local Loopback

inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:65 errors:0 dropped:0 overruns:0 frame:0
TX packets:65 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:4190 (4.0 KiB) TX bytes:4190 (4.0 KiB)

wlan0 Link encap:Ethernet HWaddr 14:CF:92:6D:xx:xx

inet6 addr: fe80::16cf:92ff:fe6d:xxxx/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:6 errors:0 dropped:0 overruns:0 frame:0
TX packets:16260 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:558 (558.0 B) TX bytes:1516815 (1.4 MiB)

Problem is with web interface. On the status page it got a "IPv4 WAN Status" vor v4, but says "not connected" for v6. Bug or "works as designed"? If "works as designed", it seems inconsistent with v4 behaviour.

IPv4 WAN Status

br-lan Type: dhcp
Address: 192.168.178.67
Netmask: 255.255.255.0
Gateway: 192.168.178.1
DNS 1: 192.168.178.1
Connected: 1h 9m 28s

IPv6 WAN Status

? Not connected

Attachments (0)

Change History (5)

comment:1 Changed 3 years ago by jow

Attach the output of "ubus call network.interface dump" here please.

comment:2 Changed 3 years ago by anonymous

Removed empty lines:

root@wr703n02:~# ubus call network.interface dump
{

"interface": [

{

"interface": "lan",
"up": true,
"pending": false,
"available": true,
"autostart": true,
"uptime": 490,
"l3_device": "br-lan",
"proto": "dhcp",
"device": "br-lan",
"metric": 0,
"delegation": true,
"ipv4-address": [

{

"address": "192.168.178.67",
"mask": 24

}

],
"ipv6-address": [
],
"ipv6-prefix": [
],
"ipv6-prefix-assignment": [
],
"route": [

{

"target": "0.0.0.0",
"mask": 0,
"nexthop": "192.168.178.1",
"source": "0.0.0.0\/0"

}

],
"dns-server": [

"192.168.178.1"

],
"dns-search": [

"fritz.box"

],
"inactive": {

"ipv4-address": [
],
"ipv6-address": [
],
"route": [
],
"dns-server": [
],
"dns-search": [
]

},
"data": {
}

},
{

"interface": "loopback",
"up": true,
"pending": false,
"available": true,
"autostart": true,
"uptime": 493,
"l3_device": "lo",
"proto": "static",
"device": "lo",
"updated": [

"addresses"

],
"metric": 0,
"delegation": true,
"ipv4-address": [

{

"address": "127.0.0.1",
"mask": 8

}

],
"ipv6-address": [
],
"ipv6-prefix": [
],
"ipv6-prefix-assignment": [
],
"route": [
],
"dns-server": [
],
"dns-search": [
],
"inactive": {

"ipv4-address": [
],
"ipv6-address": [
],
"route": [
],
"dns-server": [
],
"dns-search": [
]

},
"data": {
}

}

]

}

comment:3 Changed 3 years ago by jow

There is no IPv6 default route, thats why IPv6 *W*AN status says not connected. It usually shows the interface/address of the interface providing internet connectivity for the address family (IPv4 or IPv6)

Last edited 3 years ago by jow (previous) (diff)

comment:4 Changed 3 years ago by anonymous

netstat -rn also shows no route for IPv6. So the next question would be: How did BB got the Global IPv6 address? I assume it did by using SLAAC. If it did, wouldn't it also acquire a default route automatically? Wrong assumptions?

I didn't configured any IPv6 explicitly, but assumed BB did automatically get IPv6 up when I said "use DHCP", as modern hosts to today. Wrong assumptions?

If this turns out that it is me being to stupid using OpenWRT, please accept my apologies for wasting your time in advance.

comment:5 Changed 3 years ago by anonymous

Found it: http://wiki.openwrt.org/doc/uci/network6#upstream.configuration.for.wan-interfaces1

"Router Advertisements are not accepted by default anymore and thus OpenWrt will not configure itself with default routes and / or addresses. Also the interface-options accept_ra and send_rs have been removed. You should add an interface with proto dhcpv6 - also for receiving RAs only - as described in Native IPv6 Connection."

Sorry for the inconvenience. Just tought this looks odd and wanted to help improve BB before it ships. Please close this ticket.

Add Comment

Modify Ticket

Action
as new .
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.