Sudden IPv6 issues with init7

Software SW help
1

Hello,

I’m experiencing issues with ipv6 connectivity with init7 (Switzerland) since yesterday. I’ve tried resetting the configuration and have now restored the router to factory defaults. The ISP provides a static delegated /48 ipv6 prefix. Clients get correctly assigned the static prefix, but for example ping -6 google.com fails (no response), directly from the router the same is working. The router obtains a dynamic /64 subnet and a /128 ipv6 address on the wan port (eth1), to which it is responding to pings from outside, while it is not responding to the delegated static prefix from outside, which is correctly assigned on the br-lan interface. Clients can reach the router via the static ipv6 address. The output of ifstatus lan and ifstatus wan6 is pasted below. For the moment, I’ve replaced turris with an old router running pfsense, on which I’m not facing the same problems.

Firmware Version:
OpenWrt omnia 15.05 r47055 / LuCI cc8b99aacec15490bb725fe53abefa1156cb5fe3 branch (git-18.123.42193-cc8b99a)

Kernel Version:
4.4.131-a2dbf3bef3d0c1f725e0a5f0801935a1-2

ifstatus lan 
{
	"up": true,
	"pending": false,
	"available": true,
	"autostart": true,
	"dynamic": false,
	"uptime": 857,
	"l3_device": "br-lan",
	"proto": "static",
	"device": "br-lan",
	"updated": [
		"addresses"
	],
	"metric": 0,
	"dns_metric": 0,
	"delegation": true,
	"ipv4-address": [
		{
			"address": "192.168.1.1",
			"mask": 24
		}
	],
	"ipv6-address": [

	],
	"ipv6-prefix": [

	],
	"ipv6-prefix-assignment": [
		{
			"address": "2a02:XXX:ZZZ::",
			"mask": 60,
			"preferred": 3227,
			"valid": 86027,
			"local-address": {
				"address": "2a02:XXX:ZZZ::1",
				"mask": 64
			}
		},
		{
			"address": "fd12:2d93:5d31::",
			"mask": 60,
			"local-address": {
				"address": "fd12:2d93:5d31::1",
				"mask": 64
			}
		}
	],
	"route": [

	],
	"dns-server": [

	],
	"dns-search": [

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

		],
		"ipv6-address": [

		],
		"route": [

		],
		"dns-server": [

		],
		"dns-search": [

		]
	},
	"data": {

	}
}
ifstatus wan6 
{
	"up": true,
	"pending": false,
	"available": true,
	"autostart": true,
	"dynamic": false,
	"uptime": 356,
	"l3_device": "eth1",
	"proto": "dhcpv6",
	"device": "eth1",
	"metric": 0,
	"dns_metric": 0,
	"delegation": true,
	"ipv4-address": [

	],
	"ipv6-address": [
		{
			"address": "2a02:168:2000:e:da58:d7ff:xxxx:tttt",
			"mask": 64,
			"preferred": 604663,
			"valid": 2591863
		},
		{
			"address": "2a02:168:2000:e:66da:280f:zzzz:uuuu",
			"mask": 128,
			"preferred": 3234,
			"valid": 86034
		}
	],
	"ipv6-prefix": [
		{
			"address": "2a02:XXX:YYYY::",
			"mask": 48,
			"preferred": 3234,
			"valid": 86034,
			"class": "wan6",
			"assigned": {
				"lan": {
					"address": "2a02:XXX:YYYY::",
					"mask": 60
				}
			}
		}
	],
	"ipv6-prefix-assignment": [

	],
	"route": [
		{
			"target": "2a02:168:2000:e::",
			"mask": 64,
			"nexthop": "::",
			"metric": 256,
			"valid": 2591863,
			"source": "::\/0"
		},
		{
			"target": "::",
			"mask": 0,
			"nexthop": "fe80::1edf:fff:XXXX:ZZZZ",
			"metric": 512,
			"valid": 1663,
			"source": "2a02:XXX:YYYY::\/48"
		},
		{
			"target": "::",
			"mask": 0,
			"nexthop": "fe80::1edf:fff:XXXX:ZZZZ",
			"metric": 512,
			"valid": 1663,
			"source": "2a02:168:2000:e:da58:d7ff:xxxx:tttt\/64"
		},
		{
			"target": "::",
			"mask": 0,
			"nexthop": "fe80::1edf:fff:XXXX:ZZZZ",
			"metric": 512,
			"valid": 1663,
			"source": "2a02:168:2000:e:66da:280f:zzzz:uuuu\/128"
		}
	],
	"dns-server": [
		"2001:1620:2777:1::10",
		"2001:1620:2777:2::20"
	],
	"dns-search": [

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

		],
		"ipv6-address": [

		],
		"route": [

		],
		"dns-server": [

		],
		"dns-search": [

		]
	},
	"data": {
		"passthru": "...."
	}
}
2

Hi Simon,

I have the same problem with init7 now. The problem is since three day. I find out, that after 30min the preferred lifetime of the prefix change to 0 like in this example:

“ipv6-prefix”: [
{
“address”: “2a02:168:xxxx::”,
“mask”: 48,
“preferred”: 0,
“valid”: 64914,
“class”: “wan6”,
“assigned”: {
“lan”: {
“address”: “2a02:168:xxxx:cafe::”,
“mask”: 64
}
}
}

Bests Dimitri

3

have u told your init7?

they seemed to be very aproachable

4

Hi Dimitri,

meantime, I’ve managed to obtain the public prefix again (see below for current contents of /etc/config/network). Although after approx 1-2h the public prefix on the lan adapter gets marked as deprecated (I don’t understand why, probably there is a lease time which has expired?) and the clients seem to loose ipv6 connection partially, while the router is still responding when pinged from outside to its public prefix. But I still don’t understand what the problem is. There were some updates last Thursday, after having received the notification I’ve rebooted the router and then the troubles begun. After having tried restoring the config, resetting the factory defaults, and because I’ve never had this issue before, I suspected that there might be something on the ISP side causing this problem. Also, I believe to have discovered, when connecting the turris after a factory reset (before having noticed that there is schnapps), it “automagically” obtains the public prefix and binds it to the lan interface. However, this wasn’t working neither, because afterwards the router was still not responding to pings made from the wan side to the public prefix. I’ve used pfsense today without any problems.

@hadc: I’ve already been in contact with init7, but we weren’t able to resolve the issue yet (was Friday afternoon).

/etc/config/network 
config interface 'lan'
	option ifname 'eth0 eth2'
	option force_link '1'
	option type 'bridge'
	option proto 'static'
	option netmask '255.255.255.0'
	option ipaddr '192.168.1.1'
	option ip6assign '48'

config interface 'wan'
	option ifname 'eth1'
	option proto 'dhcp'

config interface 'wan6'
	option ifname '@wan'
	option proto 'dhcpv6'
	option reqaddress 'try'
	option reqprefix 'auto'
	option ip6prefix '2a02:168:XXXX::/48'

Best,
Simon

5

Just to let you know that you are not alone @simon I have the same setup (Turris + init7) and it started failing on Friday.

I have done a factory reset but I still have the same problem.

6

Of course i informed init7 that i have a problem. I think init7 is working on it because normaly they are very fast

7

Hello !

Same for me, recently, when I reboot my turris, my wan connection is broken. Sometimes, the problem disappear by himself after hours (or even an entire day), i have tons of logs that I don’t understand totally. I have a Hybrid7 connection with Init7 via sfp fiber. I have try to disable IPv6, and for now it works. I have informed init7 too, but they told me that they can’t do much for me :man_shrugging:

I hope someone found a solution !

Manax

8

@manax, downgrading packages seems to help (apparently in contrast to what I’ve written in my previous posts about factory reset):

9

future generations might :wink:

10

@hadc, this post was from another guy, I do immediately notice when ipv6 is down; I’m relying on it heavily :wink:

11

Hello Simon,

Thanks for reply, I will follow the update of the IPv6 package, for now I don’t need it :wink: