IPv6 beta for Bigpipe

Forums › Spark New Zealand (including Skinny and BigPipe) › IPv6 beta for Bigpipe

1 | ... | 18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | ... | 29

7 posts

Wannabe Geek

#1833596 29-Jul-2017 23:52

Need some advice: UFB on Netgear D7000

Netgear D7000 - Wifi ADSL modem Firmware Version V1.0.1.48_1.0.1

Reboot
[ADVANCED] -> [Advanced Setup] -> [IPv6]
- [Internet Connection Type] -> [DHCP]
Reboot
See IPv6 under [ADVANCED] -> [Advanced Setup] -> [IPv6] -> [Internet Connection Type] = [DHCP]
It get a ip
- Router's IPv6 Address On WAN 2403:9800:C041:FFE0:42F4:405D:82FF:A553/64
- LAN Setup
  - Router's IPv6 Address On LAN 2403:9800:C048:0850:425D:82FF:FEFF:A552/60
  - IP Address Assignment = [Auto Config]

Linux pc on wifi behind the Netgear D7000

$ ip -6 route
2403:9800:c048:850::/64 dev wlp2s0 proto kernel metric 256 expires 1555sec pref medium
2403:9800:c048:850::/64 via fe80::425d:82ff:feff:a552 dev wlp2s0 proto ra metric 600 pref medium
fe80::/64 dev wlp2s0 proto kernel metric 256 pref medium
default via fe80::425d:82ff:feff:a552 dev wlp2s0 proto static metric 600 pref medium

$ ip -6 addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 state UNKNOWN qlen 1000
inet6 ::1/128 scope host
3: wlp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 state UP qlen 1000
inet6 2403:9800:c048:850:71b9:4ec3:c86f:4cfa/64 scope global temporary dynamic
inet6 2403:9800:c048:850:4665:bcea:b026:d719/64 scope global mngtmpaddr noprefixroute dynamic
inet6 fe80::fde5:3ee:b0ce:ee6b/64 scope link

$ ping6 fe80::425d:82ff:feff:a552%wlp2s0
PING fe80::425d:82ff:feff:a552%wlp2s0(fe80::425d:82ff:feff:a552) 56 data bytes
64 bytes from fe80::425d:82ff:feff:a552: icmp_seq=1 ttl=64 time=29.5 ms
64 bytes from fe80::425d:82ff:feff:a552: icmp_seq=2 ttl=64 time=1.72 ms
^C

$ ping6 2403:9800:C041:FFE0:42F4:405D:82FF:A553
PING 2403:9800:C041:FFE0:42F4:405D:82FF:A553(2403:9800:c041:ffe0:42f4:405d:82ff:a553) 56 data bytes
64 bytes from 2403:9800:c041:ffe0:42f4:405d:82ff:a553: icmp_seq=1 ttl=64 time=1.93 ms
64 bytes from 2403:9800:c041:ffe0:42f4:405d:82ff:a553: icmp_seq=2 ttl=64 time=1.68 ms
^C

$ ping6 -n www.google.com
PING www.google.com(2404:6800:4006:808::2004) 56 data bytes
From 2403:9800:c048:850:425d:82ff:feff:a552 icmp_seq=1 Destination unreachable: No route

$ ping6 www.geekzone.co.nz
PING www.geekzone.co.nz(2400:cb00:2048:1::6818:20e) 56 data bytes
From 2403:9800:c048:850:425d:82ff:feff:a552 icmp_seq=1 Destination unreachable: No route
From 2403:9800:c048:850:425d:82ff:feff:a552 icmp_seq=2 Destination unreachable: No route
^C

Questions

Is it normal for the Default route to point to a link-local addr ?
Is the Destination unreachable, my Netgear informing me it does not know how to route the traffic ? What could be the reason ?

michaelmurfy

meow
13260 posts

Uber Geek

Moderator

ID Verified

Trusted

Lifetime subscriber

#1833604 30-Jul-2017 00:27

It really looks like IPv6 is broken on your Netgear. Also, your Linux box shouldn't have 2 Global addresses like that. You updated its firmware?

Michael Murphy | https://murfy.nz
Referral Links: Quic Broadband (use R122101E7CV7Q for free setup)

Are you happy with what you get from Geekzone? Please consider supporting us by subscribing.
Opinions are my own and not the views of my employer.

fe31nz

1232 posts

Uber Geek

#1833967 31-Jul-2017 01:16

The extra global address on the Linux box is probably a "privacy" address. I turn off the option for privacy addresses whenever I set up a new Linux box. It seems to be on by default in most distros, and I find it very annoying that my boxes will then not use the static or semi-static (DHCPv6) IPv6 address I have gone to the trouble of setting up for them so that my DNS will work.

IPv6pipe

98 posts

Master Geek

Trusted

BigPipe

#1834356 31-Jul-2017 14:45

We've found that Netgear's implementation of IPv6 can be a bit problematic, at least on the R7000 and R8000. While it does work, there are a few quirks. We've gotten around it in the office by flashing to third party (non Netgear) firmware.

Disclaimer: I'm not suggesting you should try alternate firmware. If you try on your own accord and it works, great. If however you were to try it, and your router ended up bricked we won't be able to take responsibility for that happening.

diepes

7 posts

Wannabe Geek

#1839152 4-Aug-2017 13:26

1a. What is the standards implemented/followed for IPv6 ?

1b. Is this the standard that BigPipe implements

https://www.broadband-forum.org/technical/download/TR-187.pdf

2. DHCPv6 and DHCPv6 Prefix Delegation is used for the IP allocation

- Is this (on UFB) done over PPPoE or just plain ethernet ?

IPv6pipe

98 posts

Master Geek

Trusted

BigPipe

#1839204 4-Aug-2017 14:37

That document looks to be it, yep. Note that you cannot establish an IPv6 only session with us - your router must first establish an IPv4 PPP session, and from there request an IPv6 prefix over that same PPP session via DHCPv6-PD.

If your router tries to establish a separate PPP session for IPv6 this will not work. If it tries to only establish a PPP session and requests only an IPv6 address, this also will not work. Our core routers will only allow a single PPP session per given line. Any PADI packets sent from a line that already has an active PPP session will not receive PADO.

Our officially supported protocol on all of our plans is PPP. Over ATM on ADSL, or over Ethernet on VDSL and UFB. While we can enable IPoE on request (for v4 and v6 on UFB, and v4 only on xDSL), it is not something we officially support. PPPoE over VLAN 10 on an ADSL line should also work. :)

lucky015

743 posts

Ultimate Geek

ID Verified

Trusted

#1839285 4-Aug-2017 17:23

SirHumphreyAppleby:

Success! pfSense is now working with Bigpipe!

I am able to connect to IPv6 on Bigpipe and to have that connection persist after reboots.

I am using using latest development branch for pfSense and IPoE.

The critical setting appear to be Do not wait for a RA. This didn't resolve the issue with earlier versions of pfSense, but it's possible the relevant change has been merged in the 2.3 branch, and may also work with PPPoE. IPv6 is very much a moving target on pfSense and OPNsense, so I still have no idea which of the many issues that presented with similar symptoms has been resolved. 2.4 does contain additional IPv6 fixes that have not been merged in to the latest 2.3 releases, and reports suggest it's quite stable.

My settings are as follows:

WAN

IPv6 Configuration Type: DHCP6 (note, this requires Bigpipe to enable IPoE on your connection)

Use IPv4 connectivity as parent interface

Request only an IPv6 prefix

DHCPv6 Prefix Delegation size: 60

Do not wait for a RA

LAN

IPv6 Configuration Type: Track Interface

IPv6 Interface: WAN

No additional firewall rules are required, Block private networks and loopback addresses and Block bogon networks do not need to be deselected on the WAN interface as some pfSense forum posts suggest. Both settings should be off on the LAN interface.

Awesome, I've requested IPoE be enabled on my service so hopefully I should be able to confirm the same results.

Sharesies

Trade NZ and US shares and funds with Sharesies (affiliate link).

lucky015

743 posts

Ultimate Geek

ID Verified

Trusted

#1841909 9-Aug-2017 15:26

SirHumphreyAppleby:

Success! pfSense is now working with Bigpipe!

I am able to connect to IPv6 on Bigpipe and to have that connection persist after reboots.

I am using using latest development branch for pfSense and IPoE.

The critical setting appear to be Do not wait for a RA. This didn't resolve the issue with earlier versions of pfSense, but it's possible the relevant change has been merged in the 2.3 branch, and may also work with PPPoE. IPv6 is very much a moving target on pfSense and OPNsense, so I still have no idea which of the many issues that presented with similar symptoms has been resolved. 2.4 does contain additional IPv6 fixes that have not been merged in to the latest 2.3 releases, and reports suggest it's quite stable.

My settings are as follows:

WAN

IPv6 Configuration Type: DHCP6 (note, this requires Bigpipe to enable IPoE on your connection)

Use IPv4 connectivity as parent interface

Request only an IPv6 prefix

DHCPv6 Prefix Delegation size: 60

Do not wait for a RA

LAN

IPv6 Configuration Type: Track Interface

IPv6 Interface: WAN

No additional firewall rules are required, Block private networks and loopback addresses and Block bogon networks do not need to be deselected on the WAN interface as some pfSense forum posts suggest. Both settings should be off on the LAN interface.

Appears to be now working over IPoE however I'm not receiving a valid IPv6 address, Screenshots included below however I believe I've matched your config.

Edit:
I assumed I'd require some kind of IPv6 specific gateway so I've manually added this as I was going from IPv4 only to IPv6.

Next step will be to try 2.4 I suppose unless I've made any obvious mistakes.

SirHumphreyAppleby

2847 posts

Uber Geek

#1841911 9-Aug-2017 15:32

lucky015:

Appears to be now working over IPoE however I'm not receiving a valid IPv6 address, Screenshots included below however I believe I've matched your config.

The WAN interface will have a link-local address, so that looks correct.

Did you enable Track Interface on the LAN? If you do that, you should get a public IPv6 address assigned to the LAN interface, and everything else on your network should just work. If you don't get an address on the LAN interface, then the only option is probably to upgrade to the 2.4 branch.

Regarding your edit - no further settings should be required other than those I posted.

lucky015

743 posts

Ultimate Geek

ID Verified

Trusted

#1841913 9-Aug-2017 15:40

SirHumphreyAppleby:

lucky015:

Appears to be now working over IPoE however I'm not receiving a valid IPv6 address, Screenshots included below however I believe I've matched your config.

The WAN interface will have a link-local address, so that looks correct.

Did you enable Track Interface on the LAN? If you do that, you should get a public IPv6 address assigned to the LAN interface, and everything else on your network should just work. If you don't get an address on the LAN interface, then the only option is probably to upgrade to the 2.4 branch.

Regarding your edit - no further settings should be required other than those I posted.

Yep, Track Interface is enabled on the LAN interface.

Time to bite the bullet and upgrade to 2.4 I suspect, Based on what I've seen on the forums 2.4 is looking nearly ready anyway.

SirHumphreyAppleby

2847 posts

Uber Geek

#1841922 9-Aug-2017 15:50

lucky015:

Yep, Track Interface is enabled on the LAN interface.

Time to bite the bullet and upgrade to 2.4 I suspect, Based on what I've seen on the forums 2.4 is looking nearly ready anyway.

The only thing I can't see is the interface selected for tracking. If you've got WAN selected, then everything looks to be configured as it should be. The DHCP logs will likely show some odd entries that will lead you down the path of spending hours trying to track down the possible cause, getting you nowhere. Alternatively, you could spend 10 minutes upgrading to 2.4, and have everything just work (no guarantees).

lucky015

743 posts

Ultimate Geek

ID Verified

Trusted

#1841924 9-Aug-2017 15:55

SirHumphreyAppleby:

lucky015:

Yep, Track Interface is enabled on the LAN interface.

Time to bite the bullet and upgrade to 2.4 I suspect, Based on what I've seen on the forums 2.4 is looking nearly ready anyway.

The only thing I can't see is the interface selected for tracking. If you've got WAN selected, then everything looks to be configured as it should be. The DHCP logs will likely show some odd entries that will lead you down the path of spending hours trying to track down the possible cause, getting you nowhere. Alternatively, you could spend 10 minutes upgrading to 2.4, and have everything just work (no guarantees).

Yep, Logs below seem to indicate some form of permission denied so I'm assuming it's falling outside of some of the normal parameters but I'll upgrade anyway, Just been making the backups, etc

Aug 9 15:36:18

dhcp6c

29744

reset a timer on hn0, state=SOLICIT, timeo=335, retrans=121524

Aug 9 15:38:20

dhcp6c

29744

Sending Solicit

Aug 9 15:38:20

dhcp6c

29744

set client ID (len 14)

Aug 9 15:38:20

dhcp6c

29744

set elapsed time (len 2)

Aug 9 15:38:20

dhcp6c

29744

set option request (len 4)

Aug 9 15:38:20

dhcp6c

29744

set IA_PD

Aug 9 15:38:20

dhcp6c

29744

transmit failed: Permission denied

Aug 9 15:38:20

dhcp6c

29744

reset a timer on hn0, state=SOLICIT, timeo=336, retrans=121800

Aug 9 15:40:22

dhcp6c

29744

Sending Solicit

Aug 9 15:40:22

dhcp6c

29744

set client ID (len 14)

Aug 9 15:40:22

dhcp6c

29744

set elapsed time (len 2)

Aug 9 15:40:22

dhcp6c

29744

set option request (len 4)

Aug 9 15:40:22

dhcp6c

29744

set IA_PD

Aug 9 15:40:22

dhcp6c

29744

transmit failed: Permission denied

Aug 9 15:40:22

dhcp6c

29744

reset a timer on hn0, state=SOLICIT, timeo=337, retrans=131808

Aug 9 15:42:34

dhcp6c

29744

Sending Solicit

Aug 9 15:42:34

dhcp6c

29744

set client ID (len 14)

Aug 9 15:42:34

dhcp6c

29744

set elapsed time (len 2)

Aug 9 15:42:34

dhcp6c

29744

set option request (len 4)

Aug 9 15:42:34

dhcp6c

29744

set IA_PD

Aug 9 15:42:34

dhcp6c

29744

transmit failed: Permission denied

Aug 9 15:42:34

dhcp6c

29744

reset a timer on hn0, state=SOLICIT, timeo=338, retrans=115896

Aug 9 15:44:31

dhcp6c

29744

Sending Solicit

Aug 9 15:44:31

dhcp6c

29744

set client ID (len 14)

Aug 9 15:44:31

dhcp6c

29744

set elapsed time (len 2)

Aug 9 15:44:31

dhcp6c

29744

set option request (len 4)

Aug 9 15:44:31

dhcp6c

29744

set IA_PD

Aug 9 15:44:31

dhcp6c

29744

transmit failed: Permission denied

Aug 9 15:44:31

dhcp6c

29744

reset a timer on hn0, state=SOLICIT, timeo=339, retrans=131040

Aug 9 15:46:42

dhcp6c

29744

Sending Solicit

Aug 9 15:46:42

dhcp6c

29744

set client ID (len 14)

Aug 9 15:46:42

dhcp6c

29744

set elapsed time (len 2)

Aug 9 15:46:42

dhcp6c

29744

set option request (len 4)

Aug 9 15:46:42

dhcp6c

29744

set IA_PD

Aug 9 15:46:42

dhcp6c

29744

transmit failed: Permission denied

Aug 9 15:46:42

dhcp6c

29744

reset a timer on hn0, state=SOLICIT, timeo=340, retrans=122688

Aug 9 15:48:45

dhcp6c

29744

Sending Solicit

Aug 9 15:48:45

dhcp6c

29744

set client ID (len 14)

Aug 9 15:48:45

dhcp6c

29744

set elapsed time (len 2)

Aug 9 15:48:45

dhcp6c

29744

set option request (len 4)

Aug 9 15:48:45

dhcp6c

29744

set IA_PD

Aug 9 15:48:45

dhcp6c

29744

transmit failed: Permission denied

Aug 9 15:48:45

dhcp6c

29744

reset a timer on hn0, state=SOLICIT, timeo=341, retrans=113064

Aug 9 15:50:38

dhcp6c

29744

Sending Solicit

Aug 9 15:50:38

dhcp6c

29744

set client ID (len 14)

Aug 9 15:50:38

dhcp6c

29744

set elapsed time (len 2)

Aug 9 15:50:38

dhcp6c

29744

set option request (len 4)

Aug 9 15:50:38

dhcp6c

29744

set IA_PD

Aug 9 15:50:38

dhcp6c

29744

transmit failed: Permission denied

Aug 9 15:50:38

dhcp6c

29744

reset a timer on hn0, state=SOLICIT, timeo=342, retrans=123228

SirHumphreyAppleby

2847 posts

Uber Geek

#1843232 10-Aug-2017 09:17

lucky015:

Yep, Logs below seem to indicate some form of permission denied so I'm assuming it's falling outside of some of the normal parameters but I'll upgrade anyway, Just been making the backups, etc

How did your upgrade go? I've been updating in the 2.4 branch regularly, but after upgrading again this morning, my connection seems unreliable.

@Bigpipe - are there presently connectivity issues?

IPv6pipe

98 posts

Master Geek

Trusted

BigPipe

#1843236 10-Aug-2017 09:21

All smooth sailing on our end at the moment. The graphs all look normal. :)

pesticles

5 posts

Wannabe Geek

#1843309 10-Aug-2017 09:51

Ahh graphs, such pretty lies ;)

1 | ... | 18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | ... | 29