IPv6 beta for Bigpipe

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

1 | ... | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | ... | 29

50 posts

Geek

#1771001 27-Apr-2017 02:15

DataBitz:

haysking:

haysking:

IPv6pipe:

haysking:

hi so i trying to setup ipv6 on my asus rt-ac58u router and it get the ipv6 address but when i try load the bigpipe app or reach there web site it wont load and the app say network error.

Bbut when i disable ipv6 it will load both. when geekzone the wee green ipv6 logo comes up and ipv6 test say 10/10 your ipv6 ready.

i can not work as it not happening to any others websites

So other services (either v4 or v6) for you work as expected when you have v6 enabled, except for the Bigpipe app and www.bigpipe.co.nz? Is that correct?

Correct
I can't ping or tracert it

yes another services work but will but that router back confirm that

it not even getting address for ipv6 but it is working on FRITZ!BOX 7490

so not sure now

It's probably a long shot, but you don't have the LAN 'Domain Name' on your ASUS RT-AC58U router set to 'bigpipe.co.nz' by any chance do you? That may cause a problem like your seeing.

If it is set to bigpipe, empty the field which is the default I think, or setting it to something like 'home.local'.

No hadn't enter the lan domain

but fixed by

changing one setting

Internet Detection to DNS PROBE

thanks Josh

Sharesies

Affiliate link

Affiliate link: Trade NZ and US shares and funds with Sharesies.

michaelmurfy

/dev/ttys0
11027 posts

Uber Geek

Moderator

ID Verified

Trusted

Lifetime subscriber

#1771013 27-Apr-2017 07:06

@IPv6pipe I've already pointed out the problem to you guys however somebody closed the ticket without escalating it to ops...

mmurphy@pikachu:~$ dig @192.168.2.4 a bigpipe.co.nz

; <<>> DiG 9.10.3-P4-Ubuntu <<>> @192.168.2.4 a bigpipe.co.nz
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 38334
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 4, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;bigpipe.co.nz. IN A

;; ANSWER SECTION:
bigpipe.co.nz. 60 IN A 13.54.141.208
bigpipe.co.nz. 60 IN A 52.62.54.207

;; AUTHORITY SECTION:
bigpipe.co.nz. 33 IN NS ns-1146.awsdns-15.org.
bigpipe.co.nz. 33 IN NS ns-1696.awsdns-20.co.uk.
bigpipe.co.nz. 33 IN NS ns-348.awsdns-43.com.
bigpipe.co.nz. 33 IN NS ns-966.awsdns-56.net.

;; Query time: 40 msec
;; SERVER: 192.168.2.4#53(192.168.2.4)
;; WHEN: Thu Apr 27 07:04:38 NZST 2017
;; MSG SIZE rcvd: 214

This problem has been confirmed. Never seen this method of "load balancing" in place before... Putting the correct IP (52.62.54.207) in the hosts file of the machine allows access to the BigPipe website again.

Michael Murphy | https://murfy.nz | https://keybase.io/michaelmurfy - Referral Links: Sharesies | Electric Kiwi
Are you happy with what you get from Geekzone? Please consider supporting us by making a donation.

IPv6pipe

98 posts

Master Geek

Trusted

BigPipe

#1771437 27-Apr-2017 17:12

@michaelmurfy You have an email. :)

For anyone that may be wondering, both IP addresses on the bigpipe.co.nz A record reply to HTTP requests.

If anyone is having trouble accessing our website or app please get in touch via support@bigpipe.co.nz

michaelmurfy

/dev/ttys0
11027 posts

Uber Geek

Moderator

ID Verified

Trusted

Lifetime subscriber

#1771460 27-Apr-2017 18:01

@IPv6pipe cheers. It appears that the issue may have been somewhat unrelated to the Asus router issue but so happened to be an issue while I was investigating. Will be interesting to find out what is causing the Asus router issue and why it only looks to be affecting the BigPipe website :)

terror

2 posts

Wannabe Geek

Trusted

#1772396 29-Apr-2017 12:24

I've been working this week on IPv6 on the Apple Airport Extreme AC and can confirm that unfortunately it doesn't work.

Airport doesn't support native IPv6 on PPPoE connections. I switched to plain DHCP and it doesn't work either (even though the GUI looks like it should).

This is a log capture of the negotiation:

Apr 29 11:44:41 airport-extreme ether: (WAN) link state is Down.
Apr 29 11:45:04 airport-extreme ether: (WAN) link state is Up.
Apr 29 11:45:04 airport-extreme update-network: environment[] = : old_domain_name_servers=203.96.123.1 203.96.123.2
Apr 29 11:45:04 airport-extreme update-network: environment[] = : old_dhcp_message_type=5
Apr 29 11:45:04 airport-extreme update-network: environment[] = : initiator_script=dhclient-exit-hooks
Apr 29 11:45:04 airport-extreme update-network: environment[] = : PWD=/
Apr 29 11:45:04 airport-extreme update-network: environment[] = : old_expiry=1493423285
Apr 29 11:45:04 airport-extreme update-network: environment[] = : old_dhcp_lease_time=300
Apr 29 11:45:04 airport-extreme update-network: environment[] = : PATH=/usr/ucb:/usr/bin:/usr/sbin:/bin:/sbin
Apr 29 11:45:04 airport-extreme update-network: environment[] = : reason=EXPIRE
Apr 29 11:45:04 airport-extreme update-network: environment[] = : old_broadcast_address=210.54.32.255
Apr 29 11:45:04 airport-extreme update-network: environment[] = : old_ip_address=210.54.32.xxx
Apr 29 11:45:04 airport-extreme update-network: environment[] = : interface=bcmeth1
Apr 29 11:45:04 airport-extreme update-network: environment[] = : old_domain_name=bigpipe.co.nz
Apr 29 11:45:04 airport-extreme update-network: environment[] = : pid=459
Apr 29 11:45:04 airport-extreme update-network: environment[] = : old_subnet_mask=255.255.255.0
Apr 29 11:45:04 airport-extreme update-network: environment[] = : old_network_number=210.54.32.0
Apr 29 11:45:04 airport-extreme update-network: environment[] = : old_routers=210.54.32.254
Apr 29 11:45:04 airport-extreme update-network: environment[] = : old_dhcp_server_identifier=210.54.32.254
Apr 29 11:45:04 airport-extreme update-network: environment[] = : initiator_script=dhclient-exit-hooks
Apr 29 11:45:04 airport-extreme update-network: environment[] = : PWD=/
Apr 29 11:45:04 airport-extreme update-network: environment[] = : PATH=/usr/ucb:/usr/bin:/usr/sbin:/bin:/sbin
Apr 29 11:45:04 airport-extreme update-network: environment[] = : reason=PREINIT
Apr 29 11:45:04 airport-extreme update-network: environment[] = : interface=bcmeth1
Apr 29 11:45:04 airport-extreme update-network: environment[] = : pid=459
Apr 29 11:45:05 airport-extreme update-network: environment[] = : initiator_script=dhclient-exit-hooks
Apr 29 11:45:05 airport-extreme update-network: environment[] = : new_network_number=210.54.32.0
Apr 29 11:45:05 airport-extreme update-network: environment[] = : PWD=/
Apr 29 11:45:05 airport-extreme update-network: environment[] = : new_dhcp_message_type=5
Apr 29 11:45:05 airport-extreme update-network: environment[] = : new_routers=210.54.32.254
Apr 29 11:45:05 airport-extreme update-network: environment[] = : new_ip_address=210.54.32.xxx
Apr 29 11:45:05 airport-extreme update-network: environment[] = : new_domain_name_servers=203.96.123.1 203.96.123.2
Apr 29 11:45:05 airport-extreme update-network: environment[] = : PATH=/usr/ucb:/usr/bin:/usr/sbin:/bin:/sbin
Apr 29 11:45:05 airport-extreme update-network: environment[] = : reason=BOUND
Apr 29 11:45:05 airport-extreme update-network: environment[] = : new_domain_name=bigpipe.co.nz
Apr 29 11:45:05 airport-extreme update-network: environment[] = : new_broadcast_address=210.54.32.255
Apr 29 11:45:05 airport-extreme update-network: environment[] = : interface=bcmeth1
Apr 29 11:45:05 airport-extreme update-network: environment[] = : new_dhcp_max_message_size=1500
Apr 29 11:45:05 airport-extreme update-network: environment[] = : new_expiry=1493423405
Apr 29 11:45:05 airport-extreme update-network: environment[] = : pid=459
Apr 29 11:45:05 airport-extreme update-network: environment[] = : new_dhcp_server_identifier=210.54.32.254
Apr 29 11:45:05 airport-extreme update-network: environment[] = : new_server_name=dhcp.bigpipe.co.nz
Apr 29 11:45:05 airport-extreme update-network: environment[] = : new_subnet_mask=255.255.255.0
Apr 29 11:45:05 airport-extreme update-network: environment[] = : new_dhcp_lease_time=300
Apr 29 11:45:05 airport-extreme dhcpc: Internet configuration leased [IPv4] -- host <210.54.32.xxx/255.255.255.0> gateway <210.54.32.254> dns <203.96.123.1 203.96.123.2> wins <> lease <300> domain <bigpipe.co.nz>

If I manage to get it working I will update this forum.

Cheers

carlwithaK

14 posts

Geek

#1772443 29-Apr-2017 14:11

I've tried upgrading my ER-X to a newer firmware and while still not working with IPv6, there seems to be some extra packets seen with tcpdump - I am now getting advertise replies and sending requests.

05:58:34.322374 IP6 (hlim 1, next-header UDP (17) payload length: 93) fe80::4:2:249.546 > ff02::1:2.547: [udp sum ok] dhcp6 solicit (xid=6d6c63 (client-ID hwaddr/time type 1 time 545638043 802aa8df72d1) (rapid-commit) (elapsed-time 0) (option-request DNS-server DNS-search-list) (IA_PD IAID:0 T1:0 T2:0 (IA_PD-prefix ::/60 pltime:4294967295 vltime:4294967295)))
...
05:58:50.430575 IP6 (hlim 1, next-header UDP (17) payload length: 93) fe80::4:2:249.546 > ff02::1:2.547: [udp sum ok] dhcp6 solicit (xid=6d6c63 (client-ID hwaddr/time type 1 time 545638043 802aa8df72d1) (rapid-commit) (elapsed-time 1610) (option-request DNS-server DNS-search-list) (IA_PD IAID:0 T1:0 T2:0 (IA_PD-prefix ::/60 pltime:4294967295 vltime:4294967295)))

05:58:55.275565 IP6 (class 0xe0, hlim 30, next-header UDP (17) payload length: 50) fe80::e2ac:f1ff:fe81:b104.547 > fe80::4:2:249.546: [udp sum ok] dhcp6 advertise (xid=14a084 (server-ID hwaddr type 1 a80c0d2cce36) (client-ID hwaddr/time type 1 time 545638043 802aa8df72d1) (status-code unspec failure))

05:59:08.178572 IP6 (hlim 1, next-header UDP (17) payload length: 93) fe80::4:2:249.546 > ff02::1:2.547: [udp sum ok] dhcp6 solicit (xid=6d6c63 (client-ID hwaddr/time type 1 time 545638043 802aa8df72d1) (rapid-commit) (elapsed-time 3385) (option-request DNS-server DNS-search-list) (IA_PD IAID:0 T1:0 T2:0 (IA_PD-prefix ::/60 pltime:4294967295 vltime:4294967295)))
...
06:03:04.246875 IP6 (hlim 1, next-header UDP (17) payload length: 93) fe80::4:2:249.546 > ff02::1:2.547: [udp sum ok] dhcp6 solicit (xid=6d6c63 (client-ID hwaddr/time type 1 time 545638043 802aa8df72d1) (rapid-commit) (elapsed-time 26992) (option-request DNS-server DNS-search-list) (IA_PD IAID:0 T1:0 T2:0 (IA_PD-prefix ::/60 pltime:4294967295 vltime:4294967295)))

06:03:08.192766 IP6 (class 0xe0, hlim 30, next-header UDP (17) payload length: 50) fe80::e2ac:f1ff:fe81:b104.547 > fe80::4:2:249.546: [udp sum ok] dhcp6 advertise (xid=6d6c63 (server-ID hwaddr type 1 a80c0d2cce36) (client-ID hwaddr/time type 1 time 545638043 802aa8df72d1) (status-code unspec failure))

06:03:08.195005 IP6 (hlim 1, next-header UDP (17) payload length: 58) fe80::4:2:249.546 > ff02::1:2.547: [udp sum ok] dhcp6 request (xid=d92b83 (client-ID hwaddr/time type 1 time 545638043 802aa8df72d1) (server-ID hwaddr type 1 a80c0d2cce36) (elapsed-time 0) (option-request DNS-server DNS-search-list))
06:03:09.163925 IP6 (hlim 1, next-header UDP (17) payload length: 58) fe80::4:2:249.546 > ff02::1:2.547: [udp sum ok] dhcp6 request (xid=d92b83 (client-ID hwaddr/time type 1 time 545638043 802aa8df72d1) (server-ID hwaddr type 1 a80c0d2cce36) (elapsed-time 96) (option-request DNS-server DNS-search-list))
...

It is interesting that the advertise includes a status-code of "unspec failure"?

michaelmurfy

/dev/ttys0
11027 posts

Uber Geek

Moderator

ID Verified

Trusted

Lifetime subscriber

#1772474 29-Apr-2017 15:30

@carlwithaK Checked my Edgerouter tutorial? It has everything you need there.

carlwithaK

14 posts

Geek

#1772543 29-Apr-2017 18:31

@michaelmurfy yeah I have, slightly modifed for the ER-X. Also used similar configurations from the ubiquiti forums also without luck.

bhavikk

21 posts

Geek

ID Verified

#1772920 30-Apr-2017 17:06

@carlwithAK I am having the same issue. I cannot get a IPv6 address on the pppoe0 and I've been following the guides here and the thread you started on Ubnt forums.

Just for fun I tried the configuration below to see what would happen. And magically my /etc/radvd.conf got populated and I could see IPv6 addresses being allocated on the switch0 interface. If I remove the prefix-only then it will allocate a /128 on th eth0 interface, but this configuration is useless for internet traffic.

I actually got this working once when I only had eth1 and switch0 being made up of eth2-4. I saw a /127 allocated on my pppoe0 interface and managed to get a /64 on my eth2 interface when I first tried this (I got it my ER-X last week and bigpipe just happened to beta IPv6), since then I've not been able to get this to work. I should of taken a backup of my configuration but it was essentially the guide from @michaelmurfy. Unfortunately I didn't take note of what firmware it was running at the time.

bhavik@ubnt:/tmp$ show version
Version: v1.9.7alpha1
Build ID: 4968958
Build on: 03/28/17 00:52
Copyright: 2012-2016 Ubiquiti Networks, Inc.
HW model: EdgeRouter X 5-Port

ethernet eth0 {
description "Internet (PPPoE)"
dhcpv6-pd {
pd 0 {
interface switch0 {
service slaac
}
prefix-length /60
}
prefix-only
}
duplex auto
pppoe 0 {
default-route auto
dhcpv6-pd {
rapid-commit enable
}
firewall {
in {
ipv6-name WANv6_IN
name WAN_IN
}
local {
ipv6-name WANv6_LOCAL
name WAN_LOCAL
}
}
mtu 1492
name-server auto
password bigpipe
user-id bigpipe
}
speed auto
}

bhavik@ubnt:/tmp$ show interfaces
Codes: S - State, L - Link, u - Up, D - Down, A - Admin Down
Interface IP Address S/L Description
--------- ---------- --- -----------
eth0 - u/u Internet (PPPoE)
eth1 - u/u Local
eth2 - u/u Local
eth3 - u/D Local
eth4 - u/D Local
lo 127.0.0.1/8 u/u
::1/128
pppoe0 210.XXX.XXX.XXX u/u
switch0 192.168.2.1/24 u/u Local
2403:9800:c048:520:XXXX:XXXX:XXXX:XXXX/64

michaelmurfy

/dev/ttys0
11027 posts

Uber Geek

Moderator

ID Verified

Trusted

Lifetime subscriber

#1772951 30-Apr-2017 17:43

@bhavikk having a /128 allocated on your external interface is normal. If it is all working you'll note /64's allocated on your internal interfaces.

Resnick

231 posts

Master Geek

Lifetime subscriber

#1775409 4-May-2017 10:31

For those of you having problems with pfsense here is something to experiment with.

I have been talking to a friend in the US who had problems with comcast and ipv6 addressing drops. Apparently the drops were linked to gateway monitoring/apinger events and the solution was to disable gateway monitoring on the wan interface for ipv4 and ipv6 (system > routing > gateways - edit).

I can't try this myself until next week otherwise I would be reporting back, but it sounds like it's worth a look.

Brumfondl

1152 posts

Uber Geek

Trusted

#1777154 7-May-2017 14:17

So I think I have determined the cause of my issues with IPv6 on two out of three of my machines. It would appear that the built-in Intel NICs were not handling it well at all, possibly due to the age of the machines. I have installed a new Realtek based NIC in my desktop and that is now working fine, and I have switched to using WiFi on my laptop and that, too, now has no issues.

Has anyone else noticed problems on 5+ year old Intel NICs?

Behodar

8379 posts

Uber Geek

Trusted

Lifetime subscriber

#1777160 7-May-2017 14:42

terror:

I've been working this week on IPv6 on the Apple Airport Extreme AC and can confirm that unfortunately it doesn't work.

Airport doesn't support native IPv6 on PPPoE connections.

I can confirm that it doesn't work (although admittedly I'm with a different ISP). I raised it with Apple and was told that it's known to not work and that there are no plans to get it working.

Apple:

The base station firmware does not support the PPP “IPV6CP” (IPv6 Configuration Protocol), so it can’t negotiate native IPv6 over PPPoE. It only negotiates IPv4 with the PPPoE server, so the only way for it to do IPv6 over a PPPoE connection is to tunnel it inside IPv4.

The AirPort Utility “Behaves Correctly” here, in that it doesn’t allow you to configure the base station for things it doesn’t support and we have no plans to update the firmware to support this base station.

MrTomato

139 posts

Master Geek

Lifetime subscriber

#1777185 7-May-2017 15:33

Brumfondl:

It would appear that the built-in Intel NICs were not handling it well at all, possibly due to the age of the machines. I have installed a new Realtek based NIC in my desktop and that is now working fine

Congratulations - you're officially the first person in the history of the universe to have a problem solved by ripping out Intel NICs and putting in Realtek!

Brumfondl

1152 posts

Uber Geek

Trusted

#1777200 7-May-2017 16:11

MrTomato:

Brumfondl:

It would appear that the built-in Intel NICs were not handling it well at all, possibly due to the age of the machines. I have installed a new Realtek based NIC in my desktop and that is now working fine

Congratulations - you're officially the first person in the history of the universe to have a problem solved by ripping out Intel NICs and putting in Realtek!

So after I did some digging, I do get what you are implying but since brand new Realtek is working much better than 5+ year-old Intel I shall just be happy with the situation I have ended up with :)

1 | ... | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | ... | 29