![]() ![]() ![]() ![]() |
|
Yep, that's right. You should only be requesting a prefix (IA_PD). You shouldn't be requesting an address allocation (IA_NA).
This is indeed similar to how some other ISPs with IPv6 have deployed their service.
Happy Thursday Kekzone! We hope you enjoy the lovely weather for the long weekend coming up.
Just letting you know that we are now opening up IPv6 availability (still as an experimental / beta feature, for reasons explained in the blog post) outside of the Zone of Geeks. Same caveats as the Geekzone beta, pretty much - we're asking that people only opt in if they know what they're doing and they can troubleshoot any trouble that may arise and needs to be shot.
A big piping thanks from all of us here at Bagpipe for your help in testing this feature. We ask that you keep IPv6 discussion in this thread when possible, so your wisdom may remain for the edification of future generations.
https://www.facebook.com/BigPipeNZ
https://twitter.com/BigPipeNZ
Following up on my previous post. I am running LEDE (OpenWRT variant) on a WNDR3700v1 - IPv6 appears to be running without any issues.
It was a bit of a learning curve to get ports opened on my IPv6 address, but was able to quite easily following this information here: LEDE Wiki
There are some weird things to overcome in LEDE when opening ports if its for a particular IPv6 address, as for some reason it doesn't register the Internet addressable IPv6 for my PC in the LEDE address table. Manually entered, it works fine. But this is more about the firmware itself rather than BigPipe.
I am home over the next week or so, so will hopefully have some time to mess with the settings and see what happens.
@JoshBigpipe @IPv6Pipe for the Edgerouter Lite I've updated my router configuration guide (in my signature) to include IPv6 config for both IPoE and PPPoE you can link to. I've had 100% success with this on several routers.
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.
So I've figured out that I do have a "remote LL address", and I can ping that. However when I capture DHCPv6 packets by renewing the interface (which gives errors about the missing /etc/radvd.conf) I only see solicits, no replies:
tcpdump -n -i pppoe0 ip6 and udp port 546 or udp port 547
05:27:06.617633 IP6 (hlim 1, next-header UDP (17) payload length: 93) fe80::4:2:249.dhcpv6-client > ff02::1:2.dhcpv6-server: [udp sum ok] dhcp6 solicit (xid=fa333c (client-ID hwaddr/time type 1 time 545027330 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:27:07.666155 IP6 (hlim 1, next-header UDP (17) payload length: 93) fe80::4:2:249.dhcpv6-client > ff02::1:2.dhcpv6-server: [udp sum ok] dhcp6 solicit (xid=fa333c (client-ID hwaddr/time type 1 time 545027330 802aa8df72d1) (rapid-commit) (elapsed-time 104) (option-request DNS-server DNS-search-list) (IA_PD IAID:0 T1:0 T2:0 (IA_PD-prefix ::/60 pltime:4294967295 vltime:4294967295)))
05:27:09.691752 IP6 (hlim 1, next-header UDP (17) payload length: 93) fe80::4:2:249.dhcpv6-client > ff02::1:2.dhcpv6-server: [udp sum ok] dhcp6 solicit (xid=fa333c (client-ID hwaddr/time type 1 time 545027330 802aa8df72d1) (rapid-commit) (elapsed-time 307) (option-request DNS-server DNS-search-list) (IA_PD IAID:0 T1:0 T2:0 (IA_PD-prefix ::/60 pltime:4294967295 vltime:4294967295)))
Any thoughts? thanks
05:27:06.617633 IP6 (hlim 1, next-header UDP (17) payload length: 93)
fe80::4:2:249.dhcpv6-client > ff02::1:2.dhcpv6-server:
[udp sum ok] dhcp6 solicit (xid=fa333c
(client-ID hwaddr/time type 1 time 545027330 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)))
Woooooot!
IPv6 working from a Debian 8 router/firewall.
WIN!
Reading through this thread, I can't help but feel that IPV6 adoption would be far greater if they didn't make it so overly complicated
nas:
Reading through this thread, I can't help but feel that IPV6 adoption would be far greater if they didn't make it so overly complicated
IPv6 is "overcomplicated" in this thread, because 95% of these users have intense setups.
Most reasonable RSP's have actually been sending out preconfigured and ready devices for v6.
#include <std_disclaimer>
Any comments made are personal opinion and do not reflect directly on the position my current or past employers may have.
Compared to ipv4 it's overly complicated and you can't deny that
Agree with @hio77 the number of people with HG659 tick a box and away they go. in time that box will be pre-ticked for new devices being sent.
the non consumer devices, which are not designed for easy operation are where the difficulty lies.
CPU: AMD 5900x | RAM: GSKILL Trident Z Neo RGB F4-3600C16D-32GTZNC-32-GB | MB: Asus X570-E | GFX: EVGA FTW3 Ultra RTX 3080Ti| Monitor: LG 27GL850-B 2560x1440
Quic: https://account.quic.nz/refer/473833 R473833EQKIBX
nas:
Compared to ipv4 it's overly complicated and you can't deny that
There are a few complications sure.
But you need to remember v6 is kinda new to the market in terms of residential support
v4 has been here for yonks..
#include <std_disclaimer>
Any comments made are personal opinion and do not reflect directly on the position my current or past employers may have.
nas:
Compared to ipv4 it's overly complicated and you can't deny that
Most users don't have IPv4 subnets, so shifting from a many to one, to a one to one relationship between hosts and public IPs makes IPv6 seem more complicated. In some ways, IPv6 is actually easier than IPv4. In particular, it makes NAT redundant (although you should have firewall rules instead, but these are no more complicated than port forwarding rules), and SLAAC can replace DHCP, allowing hosts to configure themselves automatically, without a server handing out and tracking addresses.
The temporary addressing feature is probably the most annoying complexity. The feature does restore the obscurity provided by NAT, and in the case of EUI-64 addressing, avoids exposing the MAC address of hardware on the Internet, but otherwise this feature does seem quite pointless to me. It can be turned off if you prefer.
The setup I currently run, I would never recommend to anyone else unless they really knew what they were doing. Half the time I don't quite know what I'm doing, but i also don't mind breaking something just to figure out how to fix it. I enjoy the challenge, and look at it as a learning opportunity for myself.
My parents in the US both have had IPV6 for over 2 years with their ISPs. They have had absolutely zero issues and their consumer devices picked it up with no problem. They don't even know what it is or how it works, just that their internet works. And trust me, if they can do it, anyone can. I literally had to teach my dad how to search on youtube earlier this week.
ZL2TOY/ZL1DMP
|
![]() ![]() ![]() ![]() |