PSA - IPv6 issues on non-fritzbox? Try changing your Prefix Size requested on WAN to /56

Forums › 2degrees › PSA - IPv6 issues on non-fritzbox? Try changing your Prefix Size requested on WAN to /56

ripdog

415 posts

Ultimate Geek
+1 received by user: 214

Subscriber

Topic # 242523 2-Nov-2018 04:27

One person supports this post

In the past, customers not paying for a static IP were given a /48 IPv6 prefix, and those who were paying would get a /56. 2degrees is currently rolling out a config change which harmonises these configurations, giving everyone a /56.

I just got hit with this, my IPv6 breaking overnight. The fix was simply to change my requested prefix from /48 to /56. All hunky dory again!

Authoritative source: https://www.geekzone.co.nz/forums.asp?forumid=85&topicid=240157

For our dynamic subscribers we allocate a /48 or /56 address space depending on the version of code they are running (due to our currently upgrades in progress), for static customers we allocate a /56 address space. Upgrades are planned to be completed in the first week of November 2018 which will see us standardise on /56 for all subscribers.

1 | 2

1595 posts

Uber Geek
+1 received by user: 157

Trusted

Reply # 2118198 2-Nov-2018 06:07

Excellent exactly what the issue was

Thanks for the email 2degrees to let us know our config needed to be updated :S

for edgerouter lite (or can be done via the config gui which basically does this below)

delete interfaces ethernet eth0 vif 10 pppoe 0 dhcpv6-pd pd 0 prefix-length /48

set interfaces ethernet eth0 vif 10 pppoe 0 dhcpv6-pd pd 0 prefix-length /56

then a dhcp /renew on your device and you should be sorted again.

CPU: Intel 3770k| RAM: F3-2400C10D-16GTX G.Skill Trident X |MB: Gigabyte Z77X-UD5H-WB | GFX: GV-N660OC-2GD gv-n660oc-2gd GeForce GTX 660 | Monitor: Qnix 27" 2560x1440

michaelmurfy

Mr Snotty
8198 posts

Uber Geek
+1 received by user: 4193

Moderator

Trusted

Lifetime subscriber

Reply # 2118210 2-Nov-2018 08:57

That would explain why my IPv6 dropped out a few times over the last few days - I'm static already on a /56.

Thanks for sharing! I do see it as a good thing that 2degrees are making both Static and Dynamic prefixes the same to avoid confusion.

Michael Murphy | https://murfy.nz
A quick guide to picking the right ISP | The Router Guide | Community UniFi Cloud Controller | Ubiquiti Edgerouter Tutorial

NickMack

282 posts

Ultimate Geek
+1 received by user: 218

Trusted

2degrees

Reply # 2118269 2-Nov-2018 09:37

One person supports this post

michaelmurfy:

That would explain why my IPv6 dropped out a few times over the last few days - I'm static already on a /56.

Thanks for sharing! I do see it as a good thing that 2degrees are making both Static and Dynamic prefixes the same to avoid confusion.

Hiya,

We have 2 core devices left to be upgraded (One in Nelson, the other in Blenheim - it's been a journey) - so apart from those locations (depending on which device you're connected to as we have PE diversity), all Dynamic and static IP's should be /56.

This is one of the joys of moving away from 2degrees only supported/supplied devices (Fritzbox) and customers being able to supply their own. For most of the population this is a non-event, however I take the point re-notification. This would/could create confusion for most customers..... so there is a trade off.

Nick.

michaelmurfy

Mr Snotty
8198 posts

Uber Geek
+1 received by user: 4193

Moderator

Trusted

Lifetime subscriber

Reply # 2118272 2-Nov-2018 09:42

One person supports this post

NickMack:

This is one of the joys of moving away from 2degrees only supported/supplied devices (Fritzbox) and customers being able to supply their own. For most of the population this is a non-event, however I take the point re-notification. This would/could create confusion for most customers..... so there is a trade off.

Fully agree. Also, many people won't understand what IPv6 is. I think posting on forums like Geekzone is a good way of communicating more technical changes out.

On another note! See you tomorrow!

Michael Murphy | https://murfy.nz
A quick guide to picking the right ISP | The Router Guide | Community UniFi Cloud Controller | Ubiquiti Edgerouter Tutorial

NickMack

282 posts

Ultimate Geek
+1 received by user: 218

Trusted

2degrees

Reply # 2118318 2-Nov-2018 09:55

michaelmurfy:

NickMack:

This is one of the joys of moving away from 2degrees only supported/supplied devices (Fritzbox) and customers being able to supply their own. For most of the population this is a non-event, however I take the point re-notification. This would/could create confusion for most customers..... so there is a trade off.

Fully agree. Also, many people won't understand what IPv6 is. I think posting on forums like Geekzone is a good way of communicating more technical changes out.

On another note! See you tomorrow!

Hiya,

"Also, many people won't understand what IPv6 is. I think posting on forums like Geekzone is a good way of communicating more technical changes out." - Agree, hence why that was the option I chose, the people who are likely to hit an issue from a residential perspective who aren't using a Fritzbox know about GZ and are most likely on here :-)

And yes, look forward to it!

Nick

BlackHand

75 posts

Master Geek
+1 received by user: 6

Reply # 2121244 7-Nov-2018 08:23

Since these changes (could be coincidence) my IPv6 keeps dropping off after awhile, my prefix length is set correctly to /56, anything else I need to change (I have a stock standard Edgerouter setup)

NickMack

282 posts

Ultimate Geek
+1 received by user: 218

Trusted

2degrees

Reply # 2121704 7-Nov-2018 16:55

BlackHand:

Since these changes (could be coincidence) my IPv6 keeps dropping off after awhile, my prefix length is set correctly to /56, anything else I need to change (I have a stock standard Edgerouter setup)

Hiya,

Can't comment to your Edge router/configuration - Anyone else having issues as we haven't received any other related escalations?

Nick

BlackHand

75 posts

Master Geek
+1 received by user: 6

Reply # 2121826 7-Nov-2018 22:06

Looks like there is a seperate thread with lots Edgerouter users experiencing the same issue ... https://www.geekzone.co.nz/forums.asp?forumid=66&topicid=242645 will try to log it now with the customer care team (was just avoiding the pain of trying to explain this to them)

NickMack

282 posts

Ultimate Geek
+1 received by user: 218

Trusted

2degrees

Reply # 2121827 7-Nov-2018 22:10

@Michaelmurfy - thoughts? We aren't seeing this on other devices..

dfnt

defiant
748 posts

Ultimate Geek
+1 received by user: 368

Lifetime subscriber

Reply # 2121831 7-Nov-2018 22:19

Neither @michaelmurfy nor myself have the issue on our ER's, I assume we run off the same BNG in Wellington

NickMack

282 posts

Ultimate Geek
+1 received by user: 218

Trusted

2degrees

Reply # 2121837 7-Nov-2018 22:22

dfnt:
Neither @michaelmurfy nor myself have the issue on our ER's, I assume we run off the same BNG in Wellington

Cool - Can you share your firmware Version and you ipv6 configuration elements for younEdge router?

dfnt

defiant
748 posts

Ultimate Geek
+1 received by user: 368

Lifetime subscriber

Reply # 2121883 7-Nov-2018 23:31

I'm running 2.0b1, but the config is the same and pretty much the same as the EdgeRouter tutorial from @michaelmurfy


firewall {

ipv6-name WAN6_IN {
default-action drop
rule 10 {
action accept
description "allow established"
protocol all
state {
established enable
related enable
}
}
rule 20 {
action drop
description "drop invalid packets"
protocol all
state {
invalid enable
}
}
rule 30 {
action accept
description "allow ICMPv6"
protocol icmpv6
}
}
ipv6-name WAN6_LOCAL {
default-action drop
rule 10 {
action accept
description "allow established"
protocol all
state {
established enable
related enable
}
}
rule 20 {
action drop
description "drop invalid packets"
protocol all
state {
invalid enable
}
}
rule 30 {
action accept
description "allow ICMPv6"
protocol icmpv6
}
rule 40 {
action accept
description "allow DHCPv6 client/server"
destination {
port 546
}
protocol udp
source {
port 547
}
}
}
ipv6-receive-redirects disable
ipv6-src-route disable
}
 

interfaces {
ethernet eth0 {
duplex auto
mtu 1508
speed auto
vif 10 {
mtu 1508
pppoe 0 {
default-route auto
dhcpv6-pd {
pd 0 {
interface eth1 {
host-address ::1
no-dns
prefix-id :0
service slaac
}
prefix-length 56
}
prefix-only
rapid-commit enable
}
firewall {
in {
ipv6-name WAN6_IN
name WAN_IN
}
local {
ipv6-name WAN6_LOCAL
name WAN_LOCAL
}
}
ipv6 {
dup-addr-detect-transmits 1
enable {
}
}

NickMack

282 posts

Ultimate Geek
+1 received by user: 218

Trusted

2degrees

Reply # 2121886 7-Nov-2018 23:36

Thanks @Defiant .. hopefully that helps ;-)

evilonenz

22 posts

Geek
+1 received by user: 10

Reply # 2121920 8-Nov-2018 07:52

I've not seen any issues on my end either, running ERLite-3 on 1.10.7.

Edit: config snippet, seems the same as everyone else.

firewall {
ipv6-name WAN6_IN {
default-action drop
description "WAN6 to internal"
rule 10 {
action accept
description "Allow established/related"
state {
established enable
related enable
}
}
rule 20 {
action drop
description "Drop invalid packets"
state {
invalid enable
}
}
rule 30 {
action accept
description "Allow ICMPv6"
protocol icmpv6
}
}
ipv6-name WAN6_LOCAL {
default-action drop
description "WAN6 to router"
rule 10 {
action accept
description "Allow established/related"
state {
established enable
related enable
}
}
rule 20 {
action drop
description "Drop invalid packets"
state {
invalid enable
}
}
rule 30 {
action accept
description "Allow ICMPv6"
protocol icmpv6
}
rule 40 {
action accept
description "Allow DHCPv6 client/server"
destination {
port 546
}
protocol udp
source {
port 547
}
}
}
ipv6-receive-redirects disable
ipv6-src-route disable
interfaces {
ethernet eth0 {
duplex auto
mtu 1508
speed auto
vif 10 {
description "Internet (PPPoE)"
mtu 1508
pppoe 0 {
default-route auto
dhcpv6-pd {
pd 0 {
interface eth1 {
host-address ::1
prefix-id :0
service slaac
}
prefix-length 56
}
prefix-only
rapid-commit enable
}
firewall {
in {
ipv6-name WAN6_IN
name WAN_IN
}
local {
ipv6-name WAN6_LOCAL
name WAN_LOCAL
}
}
ipv6 {
dup-addr-detect-transmits 1
enable {
}

BlackHand

75 posts

Master Geek
+1 received by user: 6

Reply # 2121927 8-Nov-2018 08:20

I'm running a ER-4 on 1.10.7

firewall {

ipv6-name WAN6_IN {
default-action drop
rule 10 {
action accept
description "allow established"
protocol all
state {
established enable
related enable
}
}
rule 20 {
action drop
description "drop invalid packets"
protocol all
state {
invalid enable
}
}
rule 30 {
action accept
description "allow ICMPv6"
protocol icmpv6
}
}
ipv6-name WAN6_LOCAL {
default-action drop
rule 10 {
action accept
description "allow established"
protocol all
state {
established enable
related enable
}
}
rule 20 {
action drop
description "drop invalid packets"
protocol all
state {
invalid enable
}
}
rule 30 {
action accept
description "allow ICMPv6"
protocol icmpv6
}
rule 40 {
action accept
description "allow DHCPv6"
destination {
port 546
}
protocol udp
source {
port 547
}
}
}
ipv6-receive-redirects disable
ipv6-src-route disable
}

interfaces {
ethernet eth0 {
duplex auto
mtu 1508
speed auto
vif 10 {
mtu 1508
pppoe 0 {
default-route auto
dhcpv6-pd {
pd 0 {
interface eth1 {
host-address ::1
no-dns
prefix-id :0
service slaac
}
prefix-length /56
}
prefix-only
rapid-commit enable
}
firewall {
in {
ipv6-name WAN6_IN
name WAN_IN
}
local {
ipv6-name WAN6_LOCAL
name WAN_LOCAL
}
}
ipv6 {
dup-addr-detect-transmits 1
enable {
}
}

1 | 2