No IPv6 after upgrade to 23.01
-
@maverickws Can you ping ipv6.google.com from pfSense? Routing tables ok?
Your other post mentioned a gateway group I think? What if you just pick one?
Pre-2.7.2/23.09: Only install packages for your version, or risk breaking it. Select your branch in System/Update/Update Settings.
When upgrading, allow 10-15 minutes to restart, or more depending on packages and device speed.
Upvote 👍 helpful posts! -
@maverickws Same here.
-
Same here...
-
@steveits I cannot ping ipv6.google.com nor any other IPv6 address. Doesn't matter the source interface.
I had already selected the WAN6 gateway as default gateway, also didn't make a difference.
-
@maverickws said in No IPv6 after upgrade to 23.01:
WAN using DHCP6
So .... what did you see in the DHCP logs ?
I see :
and from what I make of this :
dhcp6c gets and IPv6 for WAN usage : 2a01:cb19:xxxx:a600:92ec:77ff:fe29:392a (edit : but I can't tell where this happens in the dhcp6c log lines )
It makes / creates whatever a fe80::92ec:77ff:fe29:392a%ix3
It also ask for a 'prefix ' /64, and it got the 2a01:cb19:xxxx:a6dc::/64 so it I can assign 2a01:cb19:xxxx:a6dc::1 to my LAN; and create a IPv6 pool out off the rest of the 2a01:cb19:xxxx:a6dc::/64 range.Note : my ISP box tells me that I have a :
(ISP WAN BOX) IPv6 : 2a01:cb19:xxxx:a600:46d4:54ff:fe2a:3600
(Prefix range handed over to my pfSense as a sub delegation) : 2a01:cb19:xxxx:a600::/56Out of this /56 ( 256 x /64, the '00', the first is used by the ISP box to hand over an IPv6 to the WAN interface of pfSense.
And it decided to give the 'dc' prefix so my DHCP6 server can use that so my pfSense LAN clients can get their /128 out of it.Btw : I can't use TRACK for IPv6 on my LAN interface, as that utterly fails.
My ISP box, even if it states it has a /56 for me, only gives me one prefix, the 'dc'.
No way to ask '0xdc' out of the proposed /56.I proclaim up front : I'm new to this, as before, my ISP could not offer any kind of IPv6 functionality. The box didn't support it. Now : ISP Gigabit fiber came .... and a new box.
This new ISP box doesn't pas the "6in4" (IPv6 over IPv4) protocol, so I can't use what I was using before "tunnel.huricane.net", which worked flawlessly for me for many years. A no bullshit free IPv6 stack, and a whopping /48 to play with.
But I doubt they would pass a "close to 1 Gbits/sec" over their IPv6 tunnel /access servers. -
@gertjan I have to reboot my pfSense in order to get to that.
However, my experience here is this:
My main ISP has IPv6. Haven't changed ISP or modem or anything.
IPv6 was working before 23.01. Perfectly. No configuration has been changed.I have WAN with IPv6 config DHCP6 and local interfaces have tracking configuration for the WAN interface.
I get an IPv6 on my lan interface and on all hosts connected with IPv6 config.
The same configuration that always worked. Just doesn't work now.
On the Gateway Monitor the IPv6 gateway is pending because it can't be reached for whatever motive I have no idea about. (and my IPv6 knowledge to debug this isn't great honestly.) But I'll reboot when I can to see the logs.
-
[23.01-RELEASE][admin@pfSense.local.net]/root: ifconfig ix3 ix3: flags=8863<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 description: WAN options=4e53fbb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,TSO4,TSO6,LRO,WOL_UCAST,WOL_MCAST,WOL_MAGIC,VLAN_HWFILTER,VLAN_HWTSO,RXCSUM_IPV6,TXCSUM_IPV6,NOMAP> ether 90:ec:77:29:39:2a inet6 fe80::92ec:77ff:fe29:392a%ix3 prefixlen 64 scopeid 0x8 inet6 2a01:cb19:xxxx:a600:92ec:77ff:fe29:392a prefixlen 64 autoconf inet 192.168.10.4 netmask 0xffffff00 broadcast 192.168.10.255 media: Ethernet autoselect (1000baseT <full-duplex,rxpause,txpause>) status: active nd6 options=23<PERFORMNUD,ACCEPT_RTADV,AUTO_LINKLOCAL>So my IPv4 WAN is 192.168.10.4, obtained from my ISP box : 192.168.10.1, which is my IPv4 gateway.
( this what I'm sure about after many years ;) )My local IPv6 is "inet6 fe80::92ec:77ff:fe29:392a%ix3 prefixlen 64 scopeid 0x8"
and the IPv6 WAN IP is "inet6 2a01:cb19:xxxx:a600:92ec:77ff:fe29:392a prefixlen 64 autoconf"
As my IPS Box has /56, everything after the 'a6' is for me.
The first prefix '00' is for my ISP box LAN clients and pfSense is the only client.And then pfSense gets also a '0xdc' to play with.
I can, of course, from pfSense, ping my ISP WAN IPv6 :
[23.01-RELEASE][admin@pfSense.local.net]/root: ping6 2a01:cb19:xxxx:a600:46d4:54ff:fe2a:3600 PING6(56=40+8+8 bytes) 2a01:cb19:xxxx:a600:92ec:77ff:fe29:392a --> 2a01:cb19:xxxx:a600:46d4:54ff:fe2a:3600 16 bytes from 2a01:cb19:xxxxx:a600:46d4:54ff:fe2a:3600, icmp_seq=0 hlim=64 time=1.437 ms 16 bytes from 2a01:cb19:xxxx:a600:46d4:54ff:fe2a:3600, icmp_seq=1 hlim=64 time=0.704 ms 16 bytes from 2a01:cb19:xxxx:a600:46d4:54ff:fe2a:3600, icmp_seq=2 hlim=64 time=0.384 ms .....But, strange : if
2a01:cb19:xxxx:a600:92ec:77ff:fe29:392a
is my pfSense WAN IPv6, how can
2a01:cb19:xxxx:a600:46d4:54ff:fe2a:3600
be my ISP Box WAN IPv6 ?You said you have a modem ?
In that case, my ISP (router) story isn't valid for you.
The DHCP4 client and DHCP6 client obtain their info from the ISP DHCP4 server - and DHCP6 server, both are upstream and not local to you.Different might be : the dhcp6c process
It's settings.
Your local WAN MAC did not change, right ? -
Well it's actually an ISP router but it has a bridge interface that bypasses the ISP router and I'm directly connected so to speak.
Here's my interface info and the routing table. Some IP's have been changed for privacy:
[23.01-RELEASE][admin@pfs-fw.pt.domain.net]/root: ifconfig igb5 igb5: flags=8863<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 description: WAN options=4e120bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,WOL_MAGIC,VLAN_HWFILTER,RXCSUM_IPV6,TXCSUM_IPV6,NOMAP> ether 40:62:31:03:bd:15 inet6 fe80::4262:31ff:fe03:bd15%igb5 prefixlen 64 scopeid 0x6 inet 80.254.254.111 netmask 0xffffff00 broadcast 80.254.254.255 media: Ethernet autoselect (1000baseT <full-duplex>) status: active nd6 options=23<PERFORMNUD,ACCEPT_RTADV,AUTO_LINKLOCAL>[23.01-RELEASE][admin@pfs-fw.pt.domain.net]/root: ifconfig igb0 igb0: flags=8863<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 description: LAN options=4e120bb<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,JUMBO_MTU,VLAN_HWCSUM,WOL_MAGIC,VLAN_HWFILTER,RXCSUM_IPV6,TXCSUM_IPV6,NOMAP> ether 40:62:31:03:bd:10 inet6 fe80::4262:31ff:fe03:bd10%igb0 prefixlen 64 scopeid 0x1 inet6 fe80::1:1%igb0 prefixlen 64 scopeid 0x1 inet6 2001:8ZZ:6cZZ:f500:4262:31ff:fe03:bd10 prefixlen 64 inet 192.168.130.254 netmask 0xffffff00 broadcast 192.168.230.255 inet 10.10.254.254 netmask 0xffffffff broadcast 10.10.254.254 media: Ethernet autoselect (1000baseT <full-duplex>) status: active nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>[23.01-RELEASE][admin@pfs-fw.pt.domain.net]/root: netstat -r Routing tables Internet: Destination Gateway Flags Netif Expire default bl10-170-1.dsl.tel UGS igb5 10.10.254.254 link#1 UH lo0 10.49.10.0/24 10.ABC.XX.2 UGS ipsec6 10.49.130.0/24 10.ABC.XX.2 UGS ipsec6 10.254.XX.1 link#14 UHS lo0 10.254.XX.2 link#14 UH ipsec6 10.254.YY.1 link#15 UHS lo0 10.254.YY.2 link#15 UH ipsec7 80.254.254.0/24 link#6 U igb5 bl10-170-111.dsl.t link#6 UHS lo0 90.90.20.0/21 link#5 U igb4 a90-90-20-00.cpe.n link#5 UHS lo0 localhost link#7 UH lo0 pfs-gw.de.domain bl10-170-1.dsl.tel UGHS igb5 192.168.0.0/24 10.254.YY.2 UGS ipsec7 192.168.10.0/24 link#13 U igb0.1 192.168.10.254 link#13 UHS lo0 192.168.130.0/24 link#1 U igb0 pfs-fw link#1 UHS lo0 192.168.100.0/24 10.254.YY.2 UGS ipsec7 192.168.140.0/24 10.254.YY.2 UGS ipsec7 192.168.230.0/24 link#11 U igb0.3 192.168.230.254 link#11 UHS lo0 192.168.254.0/24 link#12 U igb0.2 192.168.254.254 link#12 UHS lo0 lis1-cr1.cprm.net bl10-170-1.dsl.tel UGHS igb5 190-00-0-1.net.nov a90-90-30-254.cpe. UGHS igb4 190.00.00.83 bl10-170-1.dsl.tel UGHS igb5 Internet6: Destination Gateway Flags Netif Expire localhost link#7 UHS lo0 2001:8ZZ:6cZZ:f500 link#1 U igb0 pfs-fw link#1 UHS lo0 2001:8ZZ:6cZZ:f501 link#13 U igb0.1 2001:8ZZ:6cZZ:f501 link#13 UHS lo0 2001:8ZZ:6cZZ:f503 link#11 U igb0.3 2001:8ZZ:6cZZ:f503 link#11 UHS lo0 2001:8ZZ:6cZZ:f5ff link#12 U igb0.2 2001:8ZZ:6cZZ:f5ff link#12 UHS lo0 fe80::%igb0/64 link#1 U igb0 fe80::1:1%igb0 link#1 UHS lo0 fe80::4262:31ff:fe link#1 UHS lo0 fe80::%igb4/64 link#5 U igb4 fe80::4262:31ff:fe link#5 UHS lo0 fe80::%igb5/64 link#6 U igb5 fe80::4262:31ff:fe link#6 UHS lo0 fe80::%lo0/64 link#7 U lo0 fe80::1%lo0 link#7 UHS lo0 fe80::%igb0.3/64 link#11 U igb0.3 fe80::1:1%igb0.3 link#11 UHS lo0 fe80::4262:31ff:fe link#11 UHS lo0 fe80::%igb0.2/64 link#12 U igb0.2 fe80::1:1%igb0.2 link#12 UHS lo0 fe80::4262:31ff:fe link#12 UHS lo0 fe80::%igb0.1/64 link#13 U igb0.1 fe80::1:1%igb0.1 link#13 UHS lo0 fe80::4262:31ff:fe link#13 UHS lo0 fe80::%ipsec6/64 link#14 U ipsec6 fe80::4262:31ff:fe link#14 UHS lo0 fe80::%ipsec7/64 link#15 U ipsec7 fe80::4262:31ff:fe link#15 UHS lo0No MAC Address changes.
-
M maverickws referenced this topic on
-
@maverickws said in No IPv6 after upgrade to 23.01:
Internet6:
Destination Gateway Flags Netif Expire
localhost link#7 UHS lo0
2001:8ZZ:6cZZ:f500 link#1 U igb0
pfs-fw link#1 UHS lo0netstat -r shows me :
There should be a default route.
-
@gertjan yeah I also noticed that.
So, what's wrong with the pfSense software and why isn't a default route added?
It's nothing with the config for sure. Don't even have the IPv6 gateway on automatic, explicitly selected the WAN interface.The very same config was working for the previous version. Looking at some posts around, seems like many users are getting the IPv6 broken. Should I go and add routes manually? I can, but I shouldn't have to.
As you said:
The DHCP4 client and DHCP6 client obtain their info from the ISP DHCP4 server - and DHCP6 server, both are upstream and not local to you.
The DHCP6 server upstream is working correctly for sure. It didn't stop working because I updated my software.
Actually if I plug my machine directly to the modem I get IPv6 connectivity without issues. -
@maverickws Show your configs, like WAN, LANs and Routing with the Gateways, also your rules on LAN.
Pending Gateways you often have to change the monitor address.
Here it is working as always. -
@bob-dig sure, here goes:
The gateway is pending because something is blocking IPv6 otherwise, wouldn't have any issue in reaching it, just as it didn't BEFORE the update, just like my machine is able if I plug it directly to the modem.
-
You can make DHCPD on WAN so it logs with a lot more details. Go to System > Advanced > Networking and check :
Now do a Status > Interfaces Release and then a Renew for WAN.
You should see a lot of dhcp6c log lines on the DHCP log page.
If, by any change, the IPv6 gateway isn't replying to ping, then you could give it an IPv6 'monitor' IP that will reply.
For example :nslookup dns.google.comand instead of the usual 8.8.8.8, pick the IPv6 equivalent, like 2001:4860:4860::8888.
They reply both (for me) to ICMP6.
Or : (ok during test phase) check "Disable Gateway Monitoring".
No "help me" PM's please. Use the forum, the community will thank you.
Edit : and where are the logs ?? -
@maverickws said in No IPv6 after upgrade to 23.01:
Don't even have the IPv6 gateway on automatic, explicitly selected the WAN interface
Did you try automatic? (Usually it's the other way around, automatic has some issue and selecting the gateway works...)
Does Status/Interfaces show an IPv6 gateway?
-
Here's the debug log, rebooted after enabling the option. The log starts on the end.
Feb 21 13:56:21 dhcp6c 39062 advertise contains no address/prefix Feb 21 13:56:21 dhcp6c 39062 server ID: 00:03:00:01:20:e0:9c:14:e4:01, pref=-1 Feb 21 13:56:21 dhcp6c 39062 status code: no addresses Feb 21 13:56:21 dhcp6c 39062 get DHCP option status code, len 33 Feb 21 13:56:21 dhcp6c 39062 IA_NA: ID=0, T1=0, T2=0 Feb 21 13:56:21 dhcp6c 39062 get DHCP option identity association, len 49 Feb 21 13:56:21 dhcp6c 39062 get DHCP option DNS, len 32 Feb 21 13:56:21 dhcp6c 39062 DUID: 00:01:00:01:28:7b:34:3b:40:62:31:03:bd:10 Feb 21 13:56:21 dhcp6c 39062 get DHCP option client ID, len 14 Feb 21 13:56:21 dhcp6c 39062 DUID: 00:03:00:01:20:e0:9c:14:e4:01 Feb 21 13:56:21 dhcp6c 39062 get DHCP option server ID, len 10 Feb 21 13:56:21 dhcp6c 39062 receive advertise from fe80::22e0:9cff:fe14:e401%igb5 on igb5 Feb 21 13:56:21 dhcp6c 39062 reset a timer on igb5, state=SOLICIT, timeo=6, retrans=64125 Feb 21 13:56:21 dhcp6c 39062 send solicit to ff02::1:2%igb5 Feb 21 13:56:21 dhcp6c 39062 set option request (len 4) Feb 21 13:56:21 dhcp6c 39062 set elapsed time (len 2) Feb 21 13:56:21 dhcp6c 39062 set identity association Feb 21 13:56:21 dhcp6c 39062 set client ID (len 14) Feb 21 13:56:21 dhcp6c 39062 Sending Solicit Feb 21 13:55:49 dhcp6c 39062 advertise contains no address/prefix Feb 21 13:55:49 dhcp6c 39062 server ID: 00:03:00:01:20:e0:9c:14:e4:01, pref=-1 Feb 21 13:55:49 dhcp6c 39062 status code: no addresses Feb 21 13:55:49 dhcp6c 39062 get DHCP option status code, len 33 Feb 21 13:55:49 dhcp6c 39062 IA_NA: ID=0, T1=0, T2=0 Feb 21 13:55:49 dhcp6c 39062 get DHCP option identity association, len 49 Feb 21 13:55:49 dhcp6c 39062 get DHCP option DNS, len 32 Feb 21 13:55:49 dhcp6c 39062 DUID: 00:01:00:01:28:7b:34:3b:40:62:31:03:bd:10 Feb 21 13:55:49 dhcp6c 39062 get DHCP option client ID, len 14 Feb 21 13:55:49 dhcp6c 39062 DUID: 00:03:00:01:20:e0:9c:14:e4:01 Feb 21 13:55:49 dhcp6c 39062 get DHCP option server ID, len 10 Feb 21 13:55:49 dhcp6c 39062 receive advertise from fe80::22e0:9cff:fe14:e401%igb5 on igb5 Feb 21 13:55:49 dhcp6c 39062 reset a timer on igb5, state=SOLICIT, timeo=5, retrans=31623 Feb 21 13:55:49 dhcp6c 39062 send solicit to ff02::1:2%igb5 Feb 21 13:55:49 dhcp6c 39062 set option request (len 4) Feb 21 13:55:49 dhcp6c 39062 set elapsed time (len 2) Feb 21 13:55:49 dhcp6c 39062 set identity association Feb 21 13:55:49 dhcp6c 39062 set client ID (len 14) Feb 21 13:55:49 dhcp6c 39062 Sending Solicit Feb 21 13:55:37 dhcpd 67775 Server starting service. Feb 21 13:55:37 dhcpd 67775 Sending on Socket/6/igb0/2001:8XX:6YY0:1600::/64 Feb 21 13:55:37 dhcpd 67775 Listening on Socket/6/igb0/2001:8XX:6YY0:1600::/64 Feb 21 13:55:37 dhcpd 67775 Sending on Socket/6/igb0.3/2001:8XX:6YY0:1603::/64 Feb 21 13:55:37 dhcpd 67775 Listening on Socket/6/igb0.3/2001:8XX:6YY0:1603::/64 Feb 21 13:55:37 dhcpd 67775 Sending on Socket/6/igb0.1/2001:8XX:6YY0:1601::/64 Feb 21 13:55:37 dhcpd 67775 Listening on Socket/6/igb0.1/2001:8XX:6YY0:1601::/64 Feb 21 13:55:37 dhcpd 67775 Bound to *:547 Feb 21 13:55:37 dhcpd 67775 Wrote 0 NA, 0 TA, 0 PD leases to lease file. Feb 21 13:55:37 dhcpd 67775 For info, please visit https://www.isc.org/software/dhcp/ Feb 21 13:55:37 dhcpd 67775 All rights reserved. Feb 21 13:55:37 dhcpd 67775 Copyright 2004-2022 Internet Systems Consortium. Feb 21 13:55:37 dhcpd 67775 Internet Systems Consortium DHCP Server 4.4.3-P1 Feb 21 13:55:37 dhcpd 67775 PID file: /var/run/dhcpdv6.pid Feb 21 13:55:37 dhcpd 67775 Database file: /var/db/dhcpd6.leases Feb 21 13:55:37 dhcpd 67775 Config file: /etc/dhcpdv6.conf Feb 21 13:55:37 dhcpd 67775 For info, please visit https://www.isc.org/software/dhcp/ Feb 21 13:55:37 dhcpd 67775 All rights reserved. Feb 21 13:55:37 dhcpd 67775 Copyright 2004-2022 Internet Systems Consortium. Feb 21 13:55:37 dhcpd 67775 Internet Systems Consortium DHCP Server 4.4.3-P1 Feb 21 13:55:37 dhcpd 67305 Server starting service. Feb 21 13:55:37 dhcpd 67305 Sending on Socket/fallback/fallback-net Feb 21 13:55:37 dhcpd 67305 Sending on BPF/igb0/40:62:31:03:bd:10/192.168.AA.0/24 Feb 21 13:55:37 dhcpd 67305 Listening on BPF/igb0/40:62:31:03:bd:10/192.168.AA.0/24 Feb 21 13:55:37 dhcpd 67305 Sending on BPF/igb0.3/40:62:31:03:bd:10/192.168.BB.0/24 Feb 21 13:55:37 dhcpd 67305 Listening on BPF/igb0.3/40:62:31:03:bd:10/192.168.BB.0/24 Feb 21 13:55:37 dhcpd 67305 Sending on BPF/igb0.2/40:62:31:03:bd:10/192.168.CC.0/24 Feb 21 13:55:37 dhcpd 67305 Listening on BPF/igb0.2/40:62:31:03:bd:10/192.168.CC.0/24 Feb 21 13:55:37 dhcpd 67305 Sending on BPF/igb0.1/40:62:31:03:bd:10/192.168.DD.0/24 Feb 21 13:55:37 dhcpd 67305 Listening on BPF/igb0.1/40:62:31:03:bd:10/192.168.DD.0/24 Feb 21 13:55:37 dhcpd 67305 Wrote 18 leases to leases file. Feb 21 13:55:37 dhcpd 67305 Wrote 0 new dynamic host decls to leases file. Feb 21 13:55:37 dhcpd 67305 Wrote 0 deleted host decls to leases file. Feb 21 13:55:37 dhcpd 67305 Wrote 0 class decls to leases file. Feb 21 13:55:37 dhcpd 67305 For info, please visit https://www.isc.org/software/dhcp/ Feb 21 13:55:37 dhcpd 67305 All rights reserved. Feb 21 13:55:37 dhcpd 67305 Copyright 2004-2022 Internet Systems Consortium. Feb 21 13:55:37 dhcpd 67305 Internet Systems Consortium DHCP Server 4.4.3-P1 Feb 21 13:55:37 dhcpd 67305 PID file: /var/run/dhcpd.pid Feb 21 13:55:37 dhcpd 67305 Database file: /var/db/dhcpd.leases Feb 21 13:55:37 dhcpd 67305 Config file: /etc/dhcpd.conf Feb 21 13:55:37 dhcpd 67305 For info, please visit https://www.isc.org/software/dhcp/ Feb 21 13:55:37 dhcpd 67305 All rights reserved. Feb 21 13:55:37 dhcpd 67305 Copyright 2004-2022 Internet Systems Consortium. Feb 21 13:55:37 dhcpd 67305 Internet Systems Consortium DHCP Server 4.4.3-P1 Feb 21 13:55:33 dhcp6c 39062 advertise contains no address/prefix Feb 21 13:55:33 dhcp6c 39062 server ID: 00:03:00:01:20:e0:9c:14:e4:01, pref=-1 Feb 21 13:55:33 dhcp6c 39062 status code: no addresses Feb 21 13:55:33 dhcp6c 39062 get DHCP option status code, len 33 Feb 21 13:55:33 dhcp6c 39062 IA_NA: ID=0, T1=0, T2=0 Feb 21 13:55:33 dhcp6c 39062 get DHCP option identity association, len 49 Feb 21 13:55:33 dhcp6c 39062 get DHCP option DNS, len 32 Feb 21 13:55:33 dhcp6c 39062 DUID: 00:01:00:01:28:7b:34:3b:40:62:31:03:bd:10 Feb 21 13:55:33 dhcp6c 39062 get DHCP option client ID, len 14 Feb 21 13:55:33 dhcp6c 39062 DUID: 00:03:00:01:20:e0:9c:14:e4:01 Feb 21 13:55:33 dhcp6c 39062 get DHCP option server ID, len 10 Feb 21 13:55:33 dhcp6c 39062 receive advertise from fe80::22e0:9cff:fe14:e401%igb5 on igb5 Feb 21 13:55:33 dhcp6c 39062 reset a timer on igb5, state=SOLICIT, timeo=4, retrans=16314 Feb 21 13:55:33 dhcp6c 39062 send solicit to ff02::1:2%igb5 Feb 21 13:55:33 dhcp6c 39062 set option request (len 4) Feb 21 13:55:33 dhcp6c 39062 set elapsed time (len 2) Feb 21 13:55:33 dhcp6c 39062 set identity association Feb 21 13:55:33 dhcp6c 39062 set client ID (len 14) Feb 21 13:55:33 dhcp6c 39062 Sending Solicit Feb 21 13:55:24 dhcp6c 39062 advertise contains no address/prefix Feb 21 13:55:24 dhcp6c 39062 server ID: 00:03:00:01:20:e0:9c:14:e4:01, pref=-1 Feb 21 13:55:24 dhcp6c 39062 status code: no addresses Feb 21 13:55:24 dhcp6c 39062 get DHCP option status code, len 33 Feb 21 13:55:24 dhcp6c 39062 IA_NA: ID=0, T1=0, T2=0 Feb 21 13:55:24 dhcp6c 39062 get DHCP option identity association, len 49 Feb 21 13:55:24 dhcp6c 39062 get DHCP option DNS, len 32 Feb 21 13:55:24 dhcp6c 39062 DUID: 00:01:00:01:28:7b:34:3b:40:62:31:03:bd:10 Feb 21 13:55:24 dhcp6c 39062 get DHCP option client ID, len 14 Feb 21 13:55:24 dhcp6c 39062 DUID: 00:03:00:01:20:e0:9c:14:e4:01 Feb 21 13:55:24 dhcp6c 39062 get DHCP option server ID, len 10 Feb 21 13:55:24 dhcp6c 39062 receive advertise from fe80::22e0:9cff:fe14:e401%igb5 on igb5 Feb 21 13:55:24 dhcp6c 39062 reset a timer on igb5, state=SOLICIT, timeo=3, retrans=8193 Feb 21 13:55:24 dhcp6c 39062 send solicit to ff02::1:2%igb5 Feb 21 13:55:24 dhcp6c 39062 set option request (len 4) Feb 21 13:55:24 dhcp6c 39062 set elapsed time (len 2) Feb 21 13:55:24 dhcp6c 39062 set identity association Feb 21 13:55:24 dhcp6c 39062 set client ID (len 14) Feb 21 13:55:24 dhcp6c 39062 Sending Solicit Feb 21 13:55:20 dhcp6c 39062 advertise contains no address/prefix Feb 21 13:55:20 dhcp6c 39062 server ID: 00:03:00:01:20:e0:9c:14:e4:01, pref=-1 Feb 21 13:55:20 dhcp6c 39062 status code: no addresses Feb 21 13:55:20 dhcp6c 39062 get DHCP option status code, len 33 Feb 21 13:55:20 dhcp6c 39062 IA_NA: ID=0, T1=0, T2=0 Feb 21 13:55:20 dhcp6c 39062 get DHCP option identity association, len 49 Feb 21 13:55:20 dhcp6c 39062 get DHCP option DNS, len 32 Feb 21 13:55:20 dhcp6c 39062 DUID: 00:01:00:01:28:7b:34:3b:40:62:31:03:bd:10 Feb 21 13:55:20 dhcp6c 39062 get DHCP option client ID, len 14 Feb 21 13:55:20 dhcp6c 39062 DUID: 00:03:00:01:20:e0:9c:14:e4:01 Feb 21 13:55:20 dhcp6c 39062 get DHCP option server ID, len 10 Feb 21 13:55:20 dhcp6c 39062 receive advertise from fe80::22e0:9cff:fe14:e401%igb5 on igb5 Feb 21 13:55:20 dhcp6c 39062 reset a timer on igb5, state=SOLICIT, timeo=2, retrans=4058 Feb 21 13:55:20 dhcp6c 39062 send solicit to ff02::1:2%igb5 Feb 21 13:55:20 dhcp6c 39062 set option request (len 4) Feb 21 13:55:20 dhcp6c 39062 set elapsed time (len 2) Feb 21 13:55:20 dhcp6c 39062 set identity association Feb 21 13:55:20 dhcp6c 39062 set client ID (len 14) Feb 21 13:55:20 dhcp6c 39062 Sending Solicit Feb 21 13:55:18 dhcp6c 39062 advertise contains no address/prefix Feb 21 13:55:18 dhcp6c 39062 server ID: 00:03:00:01:20:e0:9c:14:e4:01, pref=-1 Feb 21 13:55:18 dhcp6c 39062 status code: no addresses Feb 21 13:55:18 dhcp6c 39062 get DHCP option status code, len 33 Feb 21 13:55:18 dhcp6c 39062 IA_NA: ID=0, T1=0, T2=0 Feb 21 13:55:18 dhcp6c 39062 get DHCP option identity association, len 49 Feb 21 13:55:18 dhcp6c 39062 get DHCP option DNS, len 32 Feb 21 13:55:18 dhcp6c 39062 DUID: 00:01:00:01:28:7b:34:3b:40:62:31:03:bd:10 Feb 21 13:55:18 dhcp6c 39062 get DHCP option client ID, len 14 Feb 21 13:55:18 dhcp6c 39062 DUID: 00:03:00:01:20:e0:9c:14:e4:01 Feb 21 13:55:18 dhcp6c 39062 get DHCP option server ID, len 10 Feb 21 13:55:18 dhcp6c 39062 receive advertise from fe80::22e0:9cff:fe14:e401%igb5 on igb5 Feb 21 13:55:18 dhcp6c 39062 reset a timer on igb5, state=SOLICIT, timeo=1, retrans=2075 Feb 21 13:55:18 dhcp6c 39062 send solicit to ff02::1:2%igb5 Feb 21 13:55:18 dhcp6c 39062 set option request (len 4) Feb 21 13:55:18 dhcp6c 39062 set elapsed time (len 2) Feb 21 13:55:18 dhcp6c 39062 set identity association Feb 21 13:55:18 dhcp6c 39062 set client ID (len 14) Feb 21 13:55:18 dhcp6c 39062 Sending Solicit Feb 21 13:55:17 dhcp6c 39062 advertise contains no address/prefix Feb 21 13:55:17 dhcp6c 39062 server ID: 00:03:00:01:20:e0:9c:14:e4:01, pref=-1 Feb 21 13:55:17 dhcp6c 39062 status code: no addresses Feb 21 13:55:17 dhcp6c 39062 get DHCP option status code, len 33 Feb 21 13:55:17 dhcp6c 39062 IA_NA: ID=0, T1=0, T2=0 Feb 21 13:55:17 dhcp6c 39062 get DHCP option identity association, len 49 Feb 21 13:55:17 dhcp6c 39062 get DHCP option DNS, len 32 Feb 21 13:55:17 dhcp6c 39062 DUID: 00:01:00:01:28:7b:34:3b:40:62:31:03:bd:10 Feb 21 13:55:17 dhcp6c 39062 get DHCP option client ID, len 14 Feb 21 13:55:17 dhcp6c 39062 DUID: 00:03:00:01:20:e0:9c:14:e4:01 Feb 21 13:55:17 dhcp6c 39062 get DHCP option server ID, len 10 Feb 21 13:55:17 dhcp6c 39062 receive advertise from fe80::22e0:9cff:fe14:e401%igb5 on igb5 Feb 21 13:55:17 dhcp6c 39062 reset a timer on igb5, state=SOLICIT, timeo=0, retrans=1025 Feb 21 13:55:17 dhcp6c 39062 send solicit to ff02::1:2%igb5 Feb 21 13:55:17 dhcp6c 39062 set option request (len 4) Feb 21 13:55:17 dhcp6c 39062 set elapsed time (len 2) Feb 21 13:55:17 dhcp6c 39062 set identity association Feb 21 13:55:17 dhcp6c 39062 set client ID (len 14) Feb 21 13:55:17 dhcp6c 39062 a new XID (234d9d) is generated Feb 21 13:55:17 dhcp6c 39062 Sending Solicit Feb 21 13:55:17 dhcp6c 39062 got an expected reply, sleeping. Feb 21 13:55:17 dhcp6c 39062 removing server (ID: 00:03:00:01:20:e0:9c:14:e4:01) Feb 21 13:55:17 dhcp6c 39062 removing an event on igb5, state=REQUEST Feb 21 13:55:17 dhcp6c 39062 script "/var/etc/dhcp6c_wan_dhcp6withoutra_script.sh" terminated Feb 21 13:55:17 dhcp6c 73605 dhcp6c REQUEST on igb5 - running rtsold Feb 21 13:55:15 dhcp6c 39062 executes /var/etc/dhcp6c_wan_dhcp6withoutra_script.sh Feb 21 13:55:15 dhcp6c 39062 reset a timer on igb5, state=INIT, timeo=0, retrans=118 Feb 21 13:55:15 dhcp6c 39062 remove an IA: NA-0 Feb 21 13:55:15 dhcp6c 39062 IA NA-0 is invalidated Feb 21 13:55:15 dhcp6c 39062 status code for NA-0: no addresses Feb 21 13:55:15 dhcp6c 39062 make an IA: NA-0 Feb 21 13:55:15 dhcp6c 39062 add an address 2001:8XX:6YY0:16ff:4262:31ff:fe03:bd10/64 on igb0.2 Feb 21 13:55:15 dhcp6c 39062 add an address 2001:8XX:6YY0:1603:4262:31ff:fe03:bd10/64 on igb0.3 Feb 21 13:55:15 dhcp6c 39062 add an address 2001:8XX:6YY0:1601:4262:31ff:fe03:bd10/64 on igb0.1 Feb 21 13:55:15 dhcp6c 39062 add an address 2001:8XX:6YY0:1600:4262:31ff:fe03:bd10/64 on igb0 Feb 21 13:55:15 dhcp6c 39062 create a prefix 2001:8XX:6YY0:1600::/56 pltime=90000, vltime=90000 Feb 21 13:55:15 dhcp6c 39062 make an IA: PD-0 Feb 21 13:55:15 dhcp6c 39062 nameserver[1] 2001:8XX:2206:5:212:55:154:190 Feb 21 13:55:15 dhcp6c 39062 nameserver[0] 2001:8XX:2106:5:212:55:154:174 Feb 21 13:55:15 dhcp6c 39062 dhcp6c Received REQUEST Feb 21 13:55:15 dhcp6c 39062 IA_PD prefix: 2001:8XX:6YY0:1600::/56 pltime=90000 vltime=90000 Feb 21 13:55:15 dhcp6c 39062 get DHCP option IA_PD prefix, len 25 Feb 21 13:55:15 dhcp6c 39062 IA_PD: ID=0, T1=45000, T2=72000 Feb 21 13:55:15 dhcp6c 39062 get DHCP option IA_PD, len 41 Feb 21 13:55:15 dhcp6c 39062 status code: no addresses Feb 21 13:55:15 dhcp6c 39062 get DHCP option status code, len 33 Feb 21 13:55:15 dhcp6c 39062 IA_NA: ID=0, T1=0, T2=0 Feb 21 13:55:15 dhcp6c 39062 get DHCP option identity association, len 49 Feb 21 13:55:15 dhcp6c 39062 get DHCP option DNS, len 32 Feb 21 13:55:15 dhcp6c 39062 DUID: 00:01:00:01:28:7b:34:3b:40:62:31:03:bd:10 Feb 21 13:55:15 dhcp6c 39062 get DHCP option client ID, len 14 Feb 21 13:55:15 dhcp6c 39062 DUID: 00:03:00:01:20:e0:9c:14:e4:01 Feb 21 13:55:15 dhcp6c 39062 get DHCP option server ID, len 10 Feb 21 13:55:15 dhcp6c 39062 receive reply from fe80::22e0:9cff:fe14:e401%igb5 on igb5 Feb 21 13:55:15 dhcp6c 39062 reset a timer on igb5, state=REQUEST, timeo=0, retrans=909 Feb 21 13:55:15 dhcp6c 39062 send request to ff02::1:2%igb5 Feb 21 13:55:15 dhcp6c 39062 set IA_PD Feb 21 13:55:15 dhcp6c 39062 set IA_PD prefix Feb 21 13:55:15 dhcp6c 39062 set option request (len 4) Feb 21 13:55:15 dhcp6c 39062 set elapsed time (len 2) Feb 21 13:55:15 dhcp6c 39062 set identity association Feb 21 13:55:15 dhcp6c 39062 set status code Feb 21 13:55:15 dhcp6c 39062 set server ID (len 10) Feb 21 13:55:15 dhcp6c 39062 set client ID (len 14) Feb 21 13:55:15 dhcp6c 39062 a new XID (c0df77) is generated Feb 21 13:55:15 dhcp6c 39062 Sending Request Feb 21 13:55:15 dhcp6c 39062 picked a server (ID: 00:03:00:01:20:e0:9c:14:e4:01) Feb 21 13:55:14 dhcp6c 39062 reset timer for igb5 to 0.810179 Feb 21 13:55:14 dhcp6c 39062 server ID: 00:03:00:01:20:e0:9c:14:e4:01, pref=-1 Feb 21 13:55:14 dhcp6c 39062 IA_PD prefix: 2001:8XX:6YY0:1600::/56 pltime=90000 vltime=90000 Feb 21 13:55:14 dhcp6c 39062 get DHCP option IA_PD prefix, len 25 Feb 21 13:55:14 dhcp6c 39062 IA_PD: ID=0, T1=45000, T2=72000 Feb 21 13:55:14 dhcp6c 39062 get DHCP option IA_PD, len 41 Feb 21 13:55:14 dhcp6c 39062 status code: no addresses Feb 21 13:55:14 dhcp6c 39062 get DHCP option status code, len 33 Feb 21 13:55:14 dhcp6c 39062 IA_NA: ID=0, T1=0, T2=0 Feb 21 13:55:14 dhcp6c 39062 get DHCP option identity association, len 49 Feb 21 13:55:14 dhcp6c 39062 get DHCP option DNS, len 32 Feb 21 13:55:14 dhcp6c 39062 DUID: 00:01:00:01:28:7b:34:3b:40:62:31:03:bd:10 Feb 21 13:55:14 dhcp6c 39062 get DHCP option client ID, len 14 Feb 21 13:55:14 dhcp6c 39062 DUID: 00:03:00:01:20:e0:9c:14:e4:01 Feb 21 13:55:14 dhcp6c 39062 get DHCP option server ID, len 10 Feb 21 13:55:14 dhcp6c 39062 receive advertise from fe80::22e0:9cff:fe14:e401%igb5 on igb5 Feb 21 13:55:14 dhcp6c 39062 reset a timer on igb5, state=SOLICIT, timeo=0, retrans=1091 Feb 21 13:55:14 dhcp6c 39062 send solicit to ff02::1:2%igb5 Feb 21 13:55:14 dhcp6c 39062 set IA_PD Feb 21 13:55:14 dhcp6c 39062 set option request (len 4) Feb 21 13:55:14 dhcp6c 39062 set elapsed time (len 2) Feb 21 13:55:14 dhcp6c 39062 set identity association Feb 21 13:55:14 dhcp6c 39062 set client ID (len 14) Feb 21 13:55:14 dhcp6c 39062 a new XID (254c18) is generated Feb 21 13:55:14 dhcp6c 39062 Sending Solicit Feb 21 13:55:13 dhcp6c 39062 reset a timer on igb5, state=INIT, timeo=0, retrans=891 Feb 21 13:55:13 dhcp6c 39062 called Feb 21 13:55:13 dhcp6c 39062 called Feb 21 13:55:13 dhcp6c 39062 <3>end of sentence [;] (1) Feb 21 13:55:13 dhcp6c 39062 <3>end of closure [}] (1) Feb 21 13:55:13 dhcp6c 39062 <3>end of sentence [;] (1) Feb 21 13:55:13 dhcp6c 39062 <3>end of closure [}] (1) Feb 21 13:55:13 dhcp6c 39062 <3>end of sentence [;] (1) Feb 21 13:55:13 dhcp6c 39062 <3>[8] (1) Feb 21 13:55:13 dhcp6c 39062 <3>[sla-len] (7) Feb 21 13:55:13 dhcp6c 39062 <3>end of sentence [;] (1) Feb 21 13:55:13 dhcp6c 39062 <3>[255] (3) Feb 21 13:55:13 dhcp6c 39062 <3>[sla-id] (6) Feb 21 13:55:13 dhcp6c 39062 <3>begin of closure [{] (1) Feb 21 13:55:13 dhcp6c 39062 <5>[igb0.2] (6) Feb 21 13:55:13 dhcp6c 39062 <3>[prefix-interface] (16) Feb 21 13:55:13 dhcp6c 39062 <3>end of sentence [;] (1) Feb 21 13:55:13 dhcp6c 39062 <3>end of closure [}] (1) Feb 21 13:55:13 dhcp6c 39062 <3>end of sentence [;] (1) Feb 21 13:55:13 dhcp6c 39062 <3>[8] (1) Feb 21 13:55:13 dhcp6c 39062 <3>[sla-len] (7) Feb 21 13:55:13 dhcp6c 39062 <3>end of sentence [;] (1) Feb 21 13:55:13 dhcp6c 39062 <3>[3] (1) Feb 21 13:55:13 dhcp6c 39062 <3>[sla-id] (6) Feb 21 13:55:13 dhcp6c 39062 <3>begin of closure [{] (1) Feb 21 13:55:13 dhcp6c 39062 <5>[igb0.3] (6) Feb 21 13:55:13 dhcp6c 39062 <3>[prefix-interface] (16) Feb 21 13:55:13 dhcp6c 39062 <3>end of sentence [;] (1) Feb 21 13:55:13 dhcp6c 39062 <3>end of closure [}] (1) Feb 21 13:55:13 dhcp6c 39062 <3>end of sentence [;] (1) Feb 21 13:55:13 dhcp6c 39062 <3>[8] (1) Feb 21 13:55:13 dhcp6c 39062 <3>[sla-len] (7) Feb 21 13:55:13 dhcp6c 39062 <3>end of sentence [;] (1) Feb 21 13:55:13 dhcp6c 39062 <3>[1] (1) Feb 21 13:55:13 dhcp6c 39062 <3>[sla-id] (6) Feb 21 13:55:13 dhcp6c 39062 <3>begin of closure [{] (1) Feb 21 13:55:13 dhcp6c 39062 <5>[igb0.1] (6) Feb 21 13:55:13 dhcp6c 39062 <3>[prefix-interface] (16) Feb 21 13:55:13 dhcp6c 39062 <3>end of sentence [;] (1) Feb 21 13:55:13 dhcp6c 39062 <3>end of closure [}] (1) Feb 21 13:55:13 dhcp6c 39062 <3>end of sentence [;] (1) Feb 21 13:55:13 dhcp6c 39062 <3>[8] (1) Feb 21 13:55:13 dhcp6c 39062 <3>[sla-len] (7) Feb 21 13:55:13 dhcp6c 39062 <3>end of sentence [;] (1) Feb 21 13:55:13 dhcp6c 39062 <3>[0] (1) Feb 21 13:55:13 dhcp6c 39062 <3>[sla-id] (6) Feb 21 13:55:13 dhcp6c 39062 <3>begin of closure [{] (1) Feb 21 13:55:13 dhcp6c 39062 <5>[igb0] (4) Feb 21 13:55:13 dhcp6c 39062 <3>[prefix-interface] (16) Feb 21 13:55:13 dhcp6c 39062 <13>begin of closure [{] (1) Feb 21 13:55:13 dhcp6c 39062 <13>[0] (1) Feb 21 13:55:13 dhcp6c 39062 <13>[pd] (2) Feb 21 13:55:13 dhcp6c 39062 <3>[id-assoc] (8) Feb 21 13:55:13 dhcp6c 39062 <3>end of sentence [;] (1) Feb 21 13:55:13 dhcp6c 39062 <3>end of closure [}] (1) Feb 21 13:55:13 dhcp6c 39062 <13>begin of closure [{] (1) Feb 21 13:55:13 dhcp6c 39062 <13>[0] (1) Feb 21 13:55:13 dhcp6c 39062 <13>[na] (2) Feb 21 13:55:13 dhcp6c 39062 <3>[id-assoc] (8) Feb 21 13:55:13 dhcp6c 39062 <3>end of sentence [;] (1) Feb 21 13:55:13 dhcp6c 39062 <3>end of closure [}] (1) Feb 21 13:55:13 dhcp6c 39062 <3>comment [# we'd like nameservers and RTSOLD to do all the work] (53) Feb 21 13:55:13 dhcp6c 39062 <3>end of sentence [;] (1) Feb 21 13:55:13 dhcp6c 39062 <3>["/var/etc/dhcp6c_wan_dhcp6withoutra_script.sh"] (46) Feb 21 13:55:13 dhcp6c 39062 <3>[script] (6) Feb 21 13:55:13 dhcp6c 39062 <3>end of sentence [;] (1) Feb 21 13:55:13 dhcp6c 39062 <3>[domain-name] (11) Feb 21 13:55:13 dhcp6c 39062 <3>[request] (7) Feb 21 13:55:13 dhcp6c 39062 <3>end of sentence [;] (1) Feb 21 13:55:13 dhcp6c 39062 <3>[domain-name-servers] (19) Feb 21 13:55:13 dhcp6c 39062 <3>[request] (7) Feb 21 13:55:13 dhcp6c 39062 <3>comment [# request prefix delegation] (27) Feb 21 13:55:13 dhcp6c 39062 <3>end of sentence [;] (1) Feb 21 13:55:13 dhcp6c 39062 <3>[0] (1) Feb 21 13:55:13 dhcp6c 39062 <3>[ia-pd] (5) Feb 21 13:55:13 dhcp6c 39062 <3>[send] (4) Feb 21 13:55:13 dhcp6c 39062 <3>comment [# request stateful address] (26) Feb 21 13:55:13 dhcp6c 39062 <3>end of sentence [;] (1) Feb 21 13:55:13 dhcp6c 39062 <3>[0] (1) Feb 21 13:55:13 dhcp6c 39062 <3>[ia-na] (5) Feb 21 13:55:13 dhcp6c 39062 <3>[send] (4) Feb 21 13:55:13 dhcp6c 39062 <3>begin of closure [{] (1) Feb 21 13:55:13 dhcp6c 39062 <5>[igb5] (4) Feb 21 13:55:13 dhcp6c 39062 <3>[interface] (9) Feb 21 13:55:13 dhcp6c 39062 skip opening control port Feb 21 13:55:13 dhcp6c 39062 failed initialize control message authentication Feb 21 13:55:13 dhcp6c 39062 failed to open /usr/local/etc/dhcp6cctlkey: No such file or directory Feb 21 13:55:13 dhcp6c 39062 extracted an existing DUID from /var/db/dhcp6c_duid: 00:01:00:01:28:7b:34:3b:40:62:31:03:bd:10 Feb 21 13:55:13 dhclient 32283 bound to 80.000.000.111 -- renewal in 1800 seconds. Feb 21 13:55:13 dhclient 37953 Creating resolv.conf Feb 21 13:55:13 dhclient 37774 Adding new routes to interface: igb5 Feb 21 13:55:13 dhclient 37217 New Routers (igb5): 80.000.000.1 Feb 21 13:55:13 dhclient 37165 New Broadcast Address (igb5): 80.000.000.255 Feb 21 13:55:13 dhclient 37076 New Subnet Mask (igb5): 255.255.255.0 Feb 21 13:55:13 dhclient 37054 New IP Address (igb5): 80.000.000.111 Feb 21 13:55:13 dhclient 36880 ifconfig igb5 inet 80.000.000.111 netmask 255.255.255.0 broadcast 80.000.000.255 Feb 21 13:55:13 dhclient 36606 Starting add_new_address() Feb 21 13:55:13 dhclient 36260 REBOOT Feb 21 13:55:13 dhclient 32283 DHCPACK from 10.116.112.1 Feb 21 13:55:13 dhclient 32283 DHCPREQUEST on igb5 to 255.255.255.255 port 67 Feb 21 13:55:13 dhclient 35339 PREINIT Feb 21 13:55:08 dhclient 23313 bound to 90.00.00.66 -- renewal in 6836 seconds. Feb 21 13:55:08 dhclient 29666 Creating resolv.conf Feb 21 13:55:08 dhclient 29389 Adding new routes to interface: igb4 Feb 21 13:55:08 dhclient 28933 New Routers (igb4): 90.00.00.254 Feb 21 13:55:08 dhclient 28623 New Broadcast Address (igb4): 90.00.00.255 Feb 21 13:55:08 dhclient 28597 New Subnet Mask (igb4): 255.255.248.0 Feb 21 13:55:08 dhclient 28396 New IP Address (igb4): 90.00.00.66 Feb 21 13:55:08 dhclient 28188 ifconfig igb4 inet 90.00.00.66 netmask 255.255.248.0 broadcast 90.00.00.255 Feb 21 13:55:08 dhclient 28121 Starting add_new_address() Feb 21 13:55:08 dhclient 27711 REBOOT Feb 21 13:55:08 dhclient 23313 unknown dhcp option value 0x65 Feb 21 13:55:08 dhclient 23313 unknown dhcp option value 0x64 Feb 21 13:55:08 dhclient 23313 DHCPACK from 109.00.00.254 Feb 21 13:55:08 dhclient 23313 DHCPREQUEST on igb4 to 255.255.255.255 port 67 Feb 21 13:55:08 dhclient 27124 PREINIT -
pfSense asked for a prefix. I got one :
IA_PD prefix: 2001:8XX:6YY0:1600::/56 pltime=90000 vltime=90000
So : It uses create a prefix
2001:8XX:6YY0:1600::/56 pltime=90000, vltime=90000The ‘0x00’ ID goes to the first interface :
2001:8XX:6YY0:1600:4262:31ff:fe03:bd10/64 on igb0
This means your first LAN interface has the IPv6 2001:8XX:6YY0:1600:4262:31ff:fe03:bd10The ‘0x01’ ID goes to the next interface :
2001:8XX:6YY0:1601:4262:31ff:fe03:bd10/64 on igb0.1Etc.
2001:8XX:6YY0:16ff:4262:31ff:fe03:bd10/64 on igb0.2
Etc.
2001:8XX:6YY0:1603:4262:31ff:fe03:bd10/64 on igb0.3Other LAN 'igb0' based devices should also get an IPv6 in the /64 range of 2001:8XX:6YY0:1600:4262:31ff:fe03:bd10
Btw : first time I see interface (LAN) TRACKING actually working.
-
@gertjan interface tracking has been working here for YEARS.
All local interfaces are correctly assigned an IPv6 from upstream correctly.
Now, NO Gateway. WHY?
All I did was update the software. There were no changes in the config. I'm here day after day providing every single thing I'm asked. It's all wonder, but in the end, IPv6 isn't working.
In my opinion there is clearly an issue with this software version. I'm starting to be alarmed for not seeing any involvement from anyone of Netgate on this thread. It's like something alike Schrödinger's cat? There is a problem and there isn't, let's not open the box and find out?
-
@maverickws Mine doesn't say dynamic, so something is wrong there I guess.
-
@bob-dig your's doesn't say dynamic?
When it gets the GW from the upstream DHCP it changes from dynamic to something. Dynamic because it's configured by DHCP: Dynamic Host Configuration Protocol. Go figure.
If I unplug the network cable from WAN and reboot, IPv4 WAN will also show "dynamic" until its configured (by DHCP).
-
@maverickws said in No IPv6 after upgrade to 23.01:
IPv4 WAN will also show "dynamic" until its configured (by DHCP).
That looks like
IPv6 WAN will also show "dynamic" until its configured (by DHCP).
So, yeah, it doesn't get configured.This is :
@maverickws said in No IPv6 after upgrade to 23.01:
receive advertise from fe80::22e0:9cff:fe14:e401%igb5 on igb5
your gateway I guess, if igb5 is your WAN interface.
I see the same lines in my dhcp6c log :
2023-02-21 16:15:36.288257+01:00 dhcp6c 76460 receive reply from fe80::46d4:54ff:fe2a:3600%ix3 on ix3and then
Strange indeed.
I'll locate my IPv6-expert list, see if I can ping request some one.
The thing is : it - the thing that communicates with the other side = dhcp6c, works "for me".
With the identical bare bone "DHCP6 Client Configuration" settings.
I'm using 23.01 Release.
( and I'm pretty sure we don't have the same ISP ... )Anyway, we should find what we haven't seen yet ;)
edit : do you need to check "Do not wait for a RA" ?
No "help me" PM's please. Use the forum, the community will thank you.
Edit : and where are the logs ??
