OpenWRT reporting upstream IPv6 address as "::"

Installing and Using OpenWrt
1

Interesting issue showed up today...

For reference, this is not my gateway device... This is a router I have sitting on the LAN only to offer local services and to just play with. Anyway, take a look below at this LuCi screenshot:

image
image1226×313 28.4 KB

If I go into the "Interfaces" tab, I see this on LAN:

image
image1208×233 18 KB

My LAN entry in /etc/config/network:

config interface 'lan'
        option type 'bridge'
        option ifname 'eth0'
        option proto 'static'
        option netmask '255.255.255.0'
        option dns 'fe80::164:32a1:3a46:611c'
        option ipaddr '192.168.10.4'
        option ip6addr '2605:xxxx:xxxx:xxxx::4/64'
        option ip6gw 'fe80::164:32a1:3a46:611c'
        option gateway '192.168.10.5'
        option ip6ifaceid 'eui64'

ifconfig output:

br-lan    Link encap:Ethernet  HWaddr 00:1C:C2:1B:51:EF
          inet addr:192.168.10.4  Bcast:192.168.10.255  Mask:255.255.255.0
          inet6 addr: fe80::21c:c2ff:fe1b:51ef/64 Scope:Link
          inet6 addr: 2605:xxxx:xxxx:xxxx::4/64 Scope:Global
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:2854 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2314 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:404741 (395.2 KiB)  TX bytes:472289 (461.2 KiB)

ping6 works fine:

root@HT-TM02:~# ping6 -c 4 ip6.me
PING ip6.me (2604:90:1:1::69): 56 data bytes
64 bytes from 2604:90:1:1::69: seq=0 ttl=50 time=46.497 ms
64 bytes from 2604:90:1:1::69: seq=1 ttl=50 time=46.583 ms
64 bytes from 2604:90:1:1::69: seq=2 ttl=50 time=45.876 ms
64 bytes from 2604:90:1:1::69: seq=3 ttl=50 time=45.446 ms

--- ip6.me ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 45.446/46.100/46.583 ms

I am scratching my head here... Maybe it was a bug in LuCi for the snapshot I installed, but I only have like 900KB of space left so I am hesitant to upgrade.

Thoughts anyone?

1 Like
2 
ubus call system board; ifstatus wan6
3

Output of ubus call system board; ifstatus wan6

root@HT-TM02:~# ubus call system board; ifstatus wan6
{
        "kernel": "4.14.63",
        "hostname": "HT-TM02",
        "system": "Ralink RT5350 id:1 rev:3",
        "model": "HooToo HT-TM02",
        "board_name": "ht-tm02",
        "release": {
                "distribution": "OpenWrt",
                "version": "18.06.1",
                "revision": "r7258-5eb055306f",
                "target": "ramips\/rt305x",
                "description": "OpenWrt 18.06.1 r7258-5eb055306f"
        }
}
Interface wan6 not found

But, as I said before:

So, I am thinking you meant for me to run ubus call system board; ifstatus lan

root@HT-TM02:~# ubus call system board; ifstatus lan
{
        "kernel": "4.14.63",
        "hostname": "HT-TM02",
        "system": "Ralink RT5350 id:1 rev:3",
        "model": "HooToo HT-TM02",
        "board_name": "ht-tm02",
        "release": {
                "distribution": "OpenWrt",
                "version": "18.06.1",
                "revision": "r7258-5eb055306f",
                "target": "ramips\/rt305x",
                "description": "OpenWrt 18.06.1 r7258-5eb055306f"
        }
}
{
        "up": true,
        "pending": false,
        "available": true,
        "autostart": true,
        "dynamic": false,
        "uptime": 2416,
        "l3_device": "br-lan",
        "proto": "static",
        "device": "br-lan",
        "updated": [
                "addresses",
                "routes"
        ],
        "metric": 0,
        "dns_metric": 0,
        "delegation": true,
        "ipv4-address": [
                {
                        "address": "192.168.10.4",
                        "mask": 24
                }
        ],
        "ipv6-address": [
                {
                        "address": "2605:xxxx:xxxx:xxx::4",
                        "mask": 64
                }
        ],
        "ipv6-prefix": [

        ],
        "ipv6-prefix-assignment": [

        ],
        "route": [
                {
                        "target": "68.232.0.14",
                        "mask": 32,
                        "nexthop": "192.168.10.5",
                        "source": "0.0.0.0\/0"
                },
                {
                        "target": "129.107.132.35",
                        "mask": 32,
                        "nexthop": "192.168.10.5",
                        "source": "0.0.0.0\/0"
                },
                {
                        "target": "0.0.0.0",
                        "mask": 0,
                        "nexthop": "192.168.10.5",
                        "metric": 1,
                        "source": "0.0.0.0\/0"
                },
                {
                        "target": "::",
                        "mask": 0,
                        "nexthop": "fe80::164:32a1:3a46:611c",
                        "source": "::\/0"
                },
                {
                        "target": "0.0.0.0",
                        "mask": 0,
                        "nexthop": "192.168.10.5",
                        "source": "0.0.0.0\/0"
                }
        ],
        "dns-server": [
                "fe80::164:32a1:3a46:611c"
        ],
        "dns-search": [

        ],
        "inactive": {
                "ipv4-address": [

                ],
                "ipv6-address": [

                ],
                "route": [

                ],
                "dns-server": [

                ],
                "dns-search": [

                ]
        },
        "data": {

        }
}

Maybe this is the issue? Maybe I should add WAN6 in LuCi? It doesn't come w/ one by default since it only has 2 interfaces: eth0 assigned to br-lan and wlan0 defaulted in AP mode w/ SSID OpenWRT.

4

It looks like the same bug.
You should upgrade to the latest stable supported release.
The issue has already been fixed.

You can also edit the file manually.

5

Yes, this seems likely to me... though in the previous case, wan6 existed, whereas for me it doesn't, I still think you're right.

I checked opkg -list-upgradable but didn't see anything LuCi related.

It's purely cosmetic, but.... if I get around to it I'll try to reflash firmware with latest.

1 Like
6

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.