![]() ![]() ![]() ![]() |
|
Has IPv6 been enabled by default for all customers? I just noticed my router now has an IPv6 address as well even though I never asked for it. I don't seem to experience any problem though.
siyuan:
Has IPv6 been enabled by default for all customers? I just noticed my router now has an IPv6 address as well even though I never asked for it. I don't seem to experience any problem though.
Don't know what the official word is, but, I am not on the trial but can now get an ipv6 address (although native ipv6 dns is still an issue).
edit - native ipv6 dns is no longer an issue.
edit2 - incoming ipv6 access to my website also works (added aaaa record).
Great to hear it's working well! If you like, PM me your account email address and I'll have a look into what has happened regarding v6 on your account.
Nothing is impossible for the man who doesn't have to do it himself - A. H. Weiler
It's not on for everyone, no, but I would like to see that one day! :)
Hi, I have a recurring problem, whenever I reboot my router (Debian), I can't get ipv6 back for hours.
Basically I send dhcp6 requests on the ppp connections but never get a reply.
ie:
11:49:18.229493 IP6 fe80::41:2:561.546 > ff02::1:2.547: dhcp6 solicit
And then, hours later it start working.
Any ideas?
OK, turns out I still have the allocation and the routing is working. I just need to manually configure the delegation, so i'm up for now, but this will be an issue if the delegation changes.
Looks to me like the bigpipe dhcpv6 server doesn't answer while a reservation has not expired (TTL?) So intital connection is good, subsequent one not so good?
FWIW, no ping replies from ff02::1:2, so maybe the DHCP server is down?
It's possible you got a response the first time, if you can see the allocation in the logs, try manually configuring it.
ff02::1:2 is a special multicast address, so I'm not sure if ping would work and it might be firewalled off.
Finally noticed that the IPv6 Firewall configuration was established during the IPoE trial, and forwarded IPv6 packets to ether1-gateway.
With the return to PPPoE, and DHCPv6 over the pppoe-out1 interface, this interface wasn't changed. When it was, it was all good again.
Thanks for the opportunity.
jfp:ff02::1:2 is a special multicast address, so I'm not sure if ping would work and it might be firewalled off.
I don't see any reason why ping to this multicast address should not work, but you're right, that alone is not an indicator.
Anyway, last night at 4:23, the client actually received a DHCPv6 advertisement, to which is then replied with a request, but now it's waiting for a reply to that:
fe80::4:2:89 -> ff02::1:2 DHCPv6 108 Solicit XID: 0xedb806 CID: 0001000121f47882b827eb5d5c08
fe80::e2ac:f1ff:fe81:a104 -> fe80::4:2:89 DHCPv6 149 Advertise XID: 0xedb806 CID: 0001000121f47882b827eb5d5c08
fe80::4:2:89 -> ff02::1:2 DHCPv6 106 Request XID: 0xd52bc5 CID: 0001000121f47882b827eb5d5c08
fe80::4:2:89 -> ff02::1:2 DHCPv6 106 Request XID: 0xd52bc5 CID: 0001000121f47882b827eb5d5c08
fe80::4:2:89 -> ff02::1:2 DHCPv6 106 Request XID: 0xd52bc5 CID: 0001000121f47882b827eb5d5c08
…
Here's the corresponding bits in the log:
Jan 21 04:23:02 atom dhcp6c[30017]: client6_recv: receive advertise from fe80::e2ac:f1ff:fe81:a104%ppp0 on ppp0
Jan 21 04:23:02 atom dhcp6c[30017]: dhcp6_get_options: get DHCP option server ID, len 10
Jan 21 04:23:02 atom dhcp6c[30017]: DUID: 00:03:00:01:a8:0c:0d:2c:d3:3e
Jan 21 04:23:02 atom dhcp6c[30017]: dhcp6_get_options: get DHCP option client ID, len 14
Jan 21 04:23:02 atom dhcp6c[30017]: DUID: 00:01:00:01:21:f4:78:82:b8:27:eb:5d:5c:08
Jan 21 04:23:02 atom dhcp6c[30017]: dhcp6_get_options: get DHCP option status code, len 2
Jan 21 04:23:02 atom dhcp6c[30017]: status code: unspec failure
Jan 21 04:23:02 atom dhcp6c[30017]: client6_recvadvert: server ID: 00:03:00:01:a8:0c:0d:2c:d3:3e, pref=-1
Jan 21 04:23:02 atom dhcp6c[30017]: client6_recvadvert: reset timer for ppp0 to 0.000000
Jan 21 04:23:02 atom dhcp6c[30017]: select_server: picked a server (ID: 00:03:00:01:a8:0c:0d:2c:d3:3e)
Jan 21 04:23:02 atom dhcp6c[30017]: client6_send: a new XID (d52bc5) is generated
Jan 21 04:23:02 atom dhcp6c[30017]: copy_option: set client ID (len 14)
Jan 21 04:23:02 atom dhcp6c[30017]: copy_option: set server ID (len 10)
Jan 21 04:23:02 atom dhcp6c[30017]: copy_option: set elapsed time (len 2)
Jan 21 04:23:02 atom dhcp6c[30017]: client6_send: send request to ff02::1:2%ppp0
Jan 21 04:23:02 atom dhcp6c[30017]: dhcp6_reset_timer: reset a timer on ppp0, state=REQUEST, timeo=0, retrans=928
Jan 21 04:23:32 atom dhcp6c[30017]: copy_option: set client ID (len 14)
Jan 21 04:23:32 atom dhcp6c[30017]: copy_option: set server ID (len 10)
Jan 21 04:23:32 atom dhcp6c[30017]: copy_option: set elapsed time (len 2)
Jan 21 04:23:32 atom dhcp6c[30017]: client6_send: send request to ff02::1:2%ppp0
Jan 21 04:23:32 atom dhcp6c[30017]: dhcp6_reset_timer: reset a timer on ppp0, state=REQUEST, timeo=0, retrans=928
…
I sincerely hope this isn't PEBCAK on my side. 😇
You could always try SLAAC. Once you have your subnet you can harcode it for now.
|
![]() ![]() ![]() ![]() |