Hi, I'm fairly new to using ipv6 which I've been learning about due to my ISP's CG-NATing. I did have a working setup, but since yesterday it's no longer working. The ISP says I have a connection from there end and as I'm using the a custom router it's up to me to debug, so I'm looking for some help debugging my setup.
I "think" the issue is related to DHCPv6, as I see this in the logs repeatedly, which from https://en.wikipedia.org/wiki/DHCPv6 I should get a advertise message back from the server?
2025-02-09T16:17:00 Notice dhcp6c reset a timer on vtnet0, state=SOLICIT, timeo=8, retrans=273028
2025-02-09T16:17:00 Notice dhcp6c send solicit to ff02::1:2%vtnet0
2025-02-09T16:17:00 Notice dhcp6c set IA_PD
2025-02-09T16:17:00 Notice dhcp6c set IA_PD prefix
2025-02-09T16:17:00 Notice dhcp6c set option request (len 4)
2025-02-09T16:17:00 Notice dhcp6c set elapsed time (len 2)
2025-02-09T16:17:00 Notice dhcp6c set identity association
2025-02-09T16:17:00 Notice dhcp6c set client ID (len 14)
2025-02-09T16:17:00 Notice dhcp6c Sending Solicit
2025-02-09T16:14:42 Notice dhcp6c reset a timer on vtnet0, state=SOLICIT, timeo=7, retrans=137515
2025-02-09T16:14:42 Notice dhcp6c send solicit to ff02::1:2%vtnet0
2025-02-09T16:14:42 Notice dhcp6c set IA_PD
2025-02-09T16:14:42 Notice dhcp6c set IA_PD prefix
2025-02-09T16:14:42 Notice dhcp6c set option request (len 4)
2025-02-09T16:14:42 Notice dhcp6c set elapsed time (len 2)
2025-02-09T16:14:42 Notice dhcp6c set identity association
2025-02-09T16:14:42 Notice dhcp6c set client ID (len 14)
2025-02-09T16:14:42 Notice dhcp6c Sending Solicit
2025-02-09T16:13:33 Notice dhcp6c reset a timer on vtnet0, state=SOLICIT, timeo=6, retrans=69581
2025-02-09T16:13:33 Notice dhcp6c send solicit to ff02::1:2%vtnet0
2025-02-09T16:13:33 Notice dhcp6c set IA_PD
2025-02-09T16:13:33 Notice dhcp6c set IA_PD prefix
2025-02-09T16:13:33 Notice dhcp6c set option request (len 4)
2025-02-09T16:13:33 Notice dhcp6c set elapsed time (len 2)
2025-02-09T16:13:33 Notice dhcp6c set identity association
2025-02-09T16:13:33 Notice dhcp6c set client ID (len 14)
2025-02-09T16:13:33 Notice dhcp6c Sending Solicit
2025-02-09T16:12:58 Notice dhcp6c reset a timer on vtnet0, state=SOLICIT, timeo=5, retrans=34357
2025-02-09T16:12:58 Notice dhcp6c send solicit to ff02::1:2%vtnet0
2025-02-09T16:12:58 Notice dhcp6c set IA_PD
2025-02-09T16:12:58 Notice dhcp6c set IA_PD prefix
2025-02-09T16:12:58 Notice dhcp6c set option request (len 4)
2025-02-09T16:12:58 Notice dhcp6c set elapsed time (len 2)
2025-02-09T16:12:58 Notice dhcp6c set identity association
2025-02-09T16:12:58 Notice dhcp6c set client ID (len 14)
2025-02-09T16:12:58 Notice dhcp6c Sending Solicit
2025-02-09T16:12:41 Notice dhcp6c reset a timer on vtnet0, state=SOLICIT, timeo=4, retrans=17364
2025-02-09T16:12:41 Notice dhcp6c send solicit to ff02::1:2%vtnet0
2025-02-09T16:12:41 Notice dhcp6c set IA_PD
2025-02-09T16:12:41 Notice dhcp6c set IA_PD prefix
2025-02-09T16:12:41 Notice dhcp6c set option request (len 4)
2025-02-09T16:12:41 Notice dhcp6c set elapsed time (len 2)
2025-02-09T16:12:41 Notice dhcp6c set identity association
2025-02-09T16:12:41 Notice dhcp6c set client ID (len 14)
2025-02-09T16:12:41 Notice dhcp6c Sending Solicit
2025-02-09T16:12:32 Notice dhcp6c reset a timer on vtnet0, state=SOLICIT, timeo=3, retrans=8744
2025-02-09T16:12:32 Notice dhcp6c send solicit to ff02::1:2%vtnet0
2025-02-09T16:12:32 Notice dhcp6c set IA_PD
2025-02-09T16:12:32 Notice dhcp6c set IA_PD prefix
2025-02-09T16:12:32 Notice dhcp6c set option request (len 4)
2025-02-09T16:12:32 Notice dhcp6c set elapsed time (len 2)
2025-02-09T16:12:32 Notice dhcp6c set identity association
2025-02-09T16:12:32 Notice dhcp6c set client ID (len 14)
2025-02-09T16:12:32 Notice dhcp6c Sending Solicit
Also if I understand from reading other posts here I should expect ifctl -6pi vtnet0 to return the prefix delegated, but this return nothing.
Hopefully this the relevant bit of configuration, but if other bits are needed please let me know.
<ipv6allow>1</ipv6allow>
<dhcp6_norelease>yes</dhcp6_norelease>
<dhcp6_debug>2</dhcp6_debug>
</system>
<interfaces>
<wan>
<if>vtnet0</if>
<descr/>
<enable>1</enable>
<spoofmac/>
<blockpriv>1</blockpriv>
<blockbogons>1</blockbogons>
<ipaddr>dhcp</ipaddr>
<dhcphostname/>
<alias-address/>
<alias-subnet>32</alias-subnet>
<dhcprejectfrom/>
<adv_dhcp_pt_timeout/>
<adv_dhcp_pt_retry/>
<adv_dhcp_pt_select_timeout/>
<adv_dhcp_pt_reboot/>
<adv_dhcp_pt_backoff_cutoff/>
<adv_dhcp_pt_initial_interval/>
<adv_dhcp_pt_values>SavedCfg</adv_dhcp_pt_values>
<adv_dhcp_send_options/>
<adv_dhcp_request_options/>
<adv_dhcp_required_options/>
<adv_dhcp_option_modifiers/>
<adv_dhcp_config_advanced/>
<adv_dhcp_config_file_override/>
<adv_dhcp_config_file_override_path/>
<ipaddrv6>dhcp6</ipaddrv6>
<dhcp6-ia-pd-len>16</dhcp6-ia-pd-len>
<dhcp6-ia-pd-send-hint>1</dhcp6-ia-pd-send-hint>
<adv_dhcp6_interface_statement_send_options/>
<adv_dhcp6_interface_statement_request_options/>
<adv_dhcp6_interface_statement_information_only_enable/>
<adv_dhcp6_interface_statement_script/>
<adv_dhcp6_id_assoc_statement_address_enable/>
<adv_dhcp6_id_assoc_statement_address/>
<adv_dhcp6_id_assoc_statement_address_id/>
<adv_dhcp6_id_assoc_statement_address_pltime/>
<adv_dhcp6_id_assoc_statement_address_vltime/>
<adv_dhcp6_id_assoc_statement_prefix_enable/>
<adv_dhcp6_id_assoc_statement_prefix/>
<adv_dhcp6_id_assoc_statement_prefix_id/>
<adv_dhcp6_id_assoc_statement_prefix_pltime/>
<adv_dhcp6_id_assoc_statement_prefix_vltime/>
<adv_dhcp6_prefix_interface_statement_sla_len/>
<adv_dhcp6_authentication_statement_authname/>
<adv_dhcp6_authentication_statement_protocol/>
<adv_dhcp6_authentication_statement_algorithm/>
<adv_dhcp6_authentication_statement_rdm/>
<adv_dhcp6_key_info_statement_keyname/>
<adv_dhcp6_key_info_statement_realm/>
<adv_dhcp6_key_info_statement_keyid/>
<adv_dhcp6_key_info_statement_secret/>
<adv_dhcp6_key_info_statement_expire/>
<adv_dhcp6_config_advanced/>
<adv_dhcp6_config_file_override/>
<adv_dhcp6_config_file_override_path/>
</wan>
Thanks
I dug my ISP's router out the attic, and after plugging it in I was able to connect to it and get ipv6 working (i.e. test-ipv6.com passed fine) so my i've narrowed the problem down to my OPNsense configuration, however I struggle to understand what that might be (especially given that ipv6 was working fine before hand).
I tried created a new instance of OPNSense from scratch in my Proxmox host. Same problem ipv4 works, ipv6 doesn't.
Here is a selection from the overview of the WAN interface overview (which I think is relevant).
| Routes | default
89.45.xxx.xxx/25
default
2a02:6b60:0:11d::/64
fe80::%vtnet0/64
|
| Dynamic router received | 89.45.xxx.xxx
fe80::d666:24ff:fe5b:e4db |
| IPv6 Addresses | fe80::8269:1aff:fe76:529b/64 |
| Gateways | 89.45.xxx.xxx
fe80::d666:24ff:fe5b:e4db
|
The address fe80::d666:24ff:fe5b:e4db is not pingable and my WAN_DHCP6 interface is showing as offline.
I've tried requesting different prefixes from my ISP (my understanding and what was working before was 56, however they had previously changed from 48 to 56 without notice), but no luck.
Any suggestions on things I could try to debug would be gratefully received.
Edit: If I connect via the ISP router, the ip address I get start with 2a02:6b67:eef6:2100:..... which seems different from from the prefix `2a02:6b60:0:11d::/64` which from the above I assume it should be?
Can you post screenshots of your LAN and WAN interface settings from the GUI? I take it the LAN is already set to "track interface" for the IPv6 Configuration type?
For the LAN side delegation, are you using dhcpv6 or just Router Advertisements?
Hey, for the LAN side I'm just using Router Advertisements
Here are screenshots of my configuration (https://imgur.com/a/Yzvgtpq) on the WAN and LAN. I'm trying to also ping ipv6 address from Interfaces -> Diagnostics -> Ping which doesn't work (100% loss), could this be a fire wall issue?
(https://i.imgur.com/6MnLhrI.png)(https://i.imgur.com/U5nvg7y.png)
(https://i.imgur.com/cTVH2oZ.png)
I see one problem: You request an IPv6 "prefix only", but give no prefix ID for your WAN interface. I think this would result in "0", however, that is also used for your LAN prefix. You should use different prefixes on all interfaces.
Hmm, my understanding of "prefix only" was that no IA_NA is requested for the WAN interface. I don't think it implies use of a subnet from the IA_PD on the WAN interface. My expectation would be that the WAN interface would not get any GUA in that case. I'm fairly sure this is how mine was for a while - my ISP provides an IA_PD but no IA_NA.
Do we know what the OP's ISP provides in terms of delegated prefix? OP, in the interfaces overview, if you click on the Magnifier ("Details") next to your WAN interface, do you see any "Dynamic IPv6 prefix received"?
> Hmm, my understanding of "prefix only" was that no IA_NA is requested for the WAN interface.
Correct.
Cheers,
Franco
@meyergru this was a bit of a hail mary where I was trying some different settings (I found a post for the same ISP Community Fibre which did this), this been selected or not doesn't make any difference.
@dseven I don't see "Dynamic IPv6 prefix received" (I assume I would need a DHCPv6 response for this?)
(https://i.imgur.com/K10Rb4p.png)
Additional note, when attempting traceroute from OPNSense, it just stops at the Gateway address
(https://i.imgur.com/IP7ECJr.png)
Googling around a bit, this caught my eye: https://forums.thinkbroadband.com/otherisp/4688999-has-anyone-got-community-fibre-ipv6-set-up-right.html#Post4697615
Maybe try spoofing the MAC address of the router they supplied onto your OPNsense WAN interface?
The other thing I noticed is that several say the delegated prefix size is /48, but requesting a different size probably won't matter.
I think I looked at that thread when I initially got it setup and working. I was originally using a /48, but then they seemed to change to a /56 (which I found a few other folks talking about recently). I've tried /48 /56 and /64 (I guess I could iterate though all of them).
I have the MAC address of the router supplied spoofed by OPNsense WAN interface (I wondering if this was the issue, but it did't seem to help).
Btw, the gateway I'm been given fe80::d666:24ff:fe5b:e4db, where would that be assigned from, would that be the ISP, the Modem or something else? (still have a lot of ipv6 learning)
That is a link-local EUI-64 address that is derived from the MAC of the gateway. The MAC OUI seems to be D4:66:24, so that mean there is Cisco equipment on the other side. You should be able to ping that address, at least if you suffix it with an interface name: "ping fe80::d666:24ff:fe5b:e4db%vtnet0".
You are on a Proxmox VM, so have you disabled the Proxmox firewall for vtnet0?
What looks strange is that this does not seem to be a default route?
The firewall is disabled for both interfaces in Proxmox. I don't suppose it could be anything with OPNsenses autogenerated rules or something down that path could it?
Yea I can ping the gateway fine
~ $ ping fe80::d666:24ff:fe5b:e4db
PING(56=40+8+8 bytes) fe80::8269:1aff:fe76:529b%vtnet0 --> fe80::d666:24ff:fe5b:e4db
16 bytes from fe80::d666:24ff:fe5b:e4db%vtnet0, icmp_seq=0 hlim=64 time=1.392 ms
16 bytes from fe80::d666:24ff:fe5b:e4db%vtnet0, icmp_seq=1 hlim=64 time=1.296 ms
16 bytes from fe80::d666:24ff:fe5b:e4db%vtnet0, icmp_seq=2 hlim=64 time=1.854 ms
16 bytes from fe80::d666:24ff:fe5b:e4db%vtnet0, icmp_seq=3 hlim=64 time=1.420 ms
16 bytes from fe80::d666:24ff:fe5b:e4db%vtnet0, icmp_seq=4 hlim=64 time=1.427 ms
16 bytes from fe80::d666:24ff:fe5b:e4db%vtnet0, icmp_seq=5 hlim=64 time=1.464 ms
Are you still not seeing any DHCPv6 responses from your ISP? I wonder if it's worth copying the DUID from your working ISP router into OPNsense > Interfaces > Settings in case their DHCP server restricts to 'known' DUIDs only somehow. That assumes the ISP router lets you find out what the DUID is of course.
Yea still no responses :(
I can have a try at getting the DUID but the software on the router is pretty lack luster to say the least.
Quote from: meyergru on February 11, 2025, 03:00:43 PMThat is a link-local EUI-64 address that is derived from the MAC of the gateway. The MAC OUI seems to be D4:66:24, so that mean there is Cisco equipment on the other side. You should be able to ping that address, at least if you suffix it with an interface name: "ping fe80::d666:24ff:fe5b:e4db%vtnet0".
You are on a Proxmox VM, so have you disabled the Proxmox firewall for vtnet0?
What looks strange is that this does not seem to be a default route?
Re the default route, it is at least according to System -> Routes -> Status (so I assume this would be the default shown in Interfaces -> Overview -> Details)
(https://i.imgur.com/UsCxzAU.png)
My Interfaces: Overview looks mostly the same. Apparently, the gateway is the link-local-address of the ISP router, whereas the IPv6 route uses the LL prefix fe80::/64 to route that over pppoe0.
So, the route setup seems right, but neither your WAN nor your LAN has a GUA IPv6.
I found that with some ISPs, I had to play around with "send prefix hint" an "request prefix only" combinations, because they only supported a certain setting and did not answer at all when it did not conform to that. It does not really matter what they will provide, it they at least hand out a /56 prefix, because you can assign that to the WAN as well and that will even work better for dyndns purposes.
I would try all combinations and see what GUA you get for LAN and WAN (or look at the logs and see if you get IA_NA and IA_PD).
I'll give that a go later, although I did confirm with there technical support last night that I should be expecting a /48 PD delegation, but at this pint anything is worth a try :)
It might well be that if you request the wrong prefix size, they will deny that, too.
Looking into the package capture, is the the solicit and the advertisement response of DHCPv6?
WAN vtnet0 2025-02-12 11:52:11.727627 80:xx:xx:xx:xx:xx d4:66:24:5b:e4:db
ethertype IPv6 (0x86dd), length 86: (hlim 255, next-header ICMPv6 (58) payload length: 32) fe80::8269:1aff:fe76:529b > fe80::d666:24ff:fe5b:e4db: [icmp6 sum ok] ICMP6, neighbor solicitation, length 32, who has fe80::d666:24ff:fe5b:e4db
source link-address option (1), length 8 (1): 80:xx:xx:xx:xx:xx
0x0000: 8069 1a76 529b
WAN vtnet0 2025-02-12 11:52:11.744065 d4:66:24:5b:e4:db 80:xx:xx:xx:xx:xx
ethertype IPv6 (0x86dd), length 86: (class 0xe0, hlim 255, next-header ICMPv6 (58) payload length: 32) fe80::d666:24ff:fe5b:e4db > fe80::8269:1aff:fe76:529b: [icmp6 sum ok] ICMP6, neighbor advertisement, length 32, tgt is fe80::d666:24ff:fe5b:e4db, Flags [router, solicited, override]
destination link-address option (2), length 8 (1): d4:66:24:5b:e4:db
0x0000: d466 245b e4db
This is followed by this:
WAN
vtnet0 2025-02-12
11:52:11.938877 80:xx:xx:xx:xx:xx d4:66:24:5b:e4:db ethertype IPv6 (0x86dd), length 63: (hlim 64, next-header ICMPv6 (58) payload length: 9) fe80::8269:1aff:fe76:529b > fe80::d666:24ff:fe5b:e4db: [icmp6 sum ok] ICMP6, echo request, id 18980, seq 4205
WAN
vtnet0 2025-02-12
11:52:11.940055 d4:66:24:5b:e4:db 80:xx:xx:xx:xx:xx ethertype IPv6 (0x86dd), length 63: (hlim 64, next-header ICMPv6 (58) payload length: 9) fe80::d666:24ff:fe5b:e4db > fe80::8269:1aff:fe76:529b: [icmp6 sum ok] ICMP6, echo reply, id 18980, seq 4205
WAN
vtnet0 2025-02-12
11:52:12.966498 80:xx:xx:xx:xx:xx d4:66:24:5b:e4:db ethertype IPv6 (0x86dd), length 63: (hlim 64, next-header ICMPv6 (58) payload length: 9) fe80::8269:1aff:fe76:529b > fe80::d666:24ff:fe5b:e4db: [icmp6 sum ok] ICMP6, echo request, id 18980, seq 4206
WAN
vtnet0 2025-02-12
11:52:12.967682 d4:66:24:5b:e4:db 80:xx:xx:xx:xx:xx ethertype IPv6 (0x86dd), length 63: (hlim 64, next-header ICMPv6 (58) payload length: 9) fe80::d666:24ff:fe5b:e4db > fe80::8269:1aff:fe76:529b: [icmp6 sum ok] ICMP6, echo reply, id 18980, seq 4206
WAN
vtnet0 2025-02-12
11:52:14.008721 80:xx:xx:xx:xx:xx d4:66:24:5b:e4:db ethertype IPv6 (0x86dd), length 63: (hlim 64, next-header ICMPv6 (58) payload length: 9) fe80::8269:1aff:fe76:529b > fe80::d666:24ff:fe5b:e4db: [icmp6 sum ok] ICMP6, echo request, id 18980, seq 4207
WAN
vtnet0 2025-02-12
11:52:14.010783 d4:66:24:5b:e4:db 80:xx:xx:xx:xx:xx ethertype IPv6 (0x86dd), length 63: (hlim 64, next-header ICMPv6 (58) payload length: 9) fe80::d666:24ff:fe5b:e4db > fe80::8269:1aff:fe76:529b: [icmp6 sum ok] ICMP6, echo reply, id 18980, seq 4207
WAN
vtnet0 2025-02-12
11:52:15.022620 80:xx:xx:xx:xx:xx d4:66:24:5b:e4:db ethertype IPv6 (0x86dd), length 63: (hlim 64, next-header ICMPv6 (58) payload length: 9) fe80::8269:1aff:fe76:529b > fe80::d666:24ff:fe5b:e4db: [icmp6 sum ok] ICMP6, echo request, id 18980, seq 4208
WAN
vtnet0 2025-02-12
11:52:15.023689 d4:66:24:5b:e4:db 80:xx:xx:xx:xx:xx ethertype IPv6 (0x86dd), length 63: (hlim 64, next-header ICMPv6 (58) payload length: 9) fe80::d666:24ff:fe5b:e4db > fe80::8269:1aff:fe76:529b: [icmp6 sum ok] ICMP6, echo reply, id 18980, seq 4208
WAN
vtnet0 2025-02-12
11:52:16.072503 80:xx:xx:xx:xx:xx d4:66:24:5b:e4:db ethertype IPv6 (0x86dd), length 63: (hlim 64, next-header ICMPv6 (58) payload length: 9) fe80::8269:1aff:fe76:529b > fe80::d666:24ff:fe5b:e4db: [icmp6 sum ok] ICMP6, echo request, id 18980, seq 4209
WAN
vtnet0 2025-02-12
11:52:16.073848 d4:66:24:5b:e4:db 80:xx:xx:xx:xx:xx ethertype IPv6 (0x86dd), length 63: (hlim 64, next-header ICMPv6 (58) payload length: 9) fe80::d666:24ff:fe5b:e4db > fe80::8269:1aff:fe76:529b: [icmp6 sum ok] ICMP6, echo reply, id 18980, seq 4209
WAN
vtnet0 2025-02-12
11:52:17.120092 80:xx:xx:xx:xx:xx d4:66:24:5b:e4:db ethertype IPv6 (0x86dd), length 63: (hlim 64, next-header ICMPv6 (58) payload length: 9) fe80::8269:1aff:fe76:529b > fe80::d666:24ff:fe5b:e4db: [icmp6 sum ok] ICMP6, echo request, id 18980, seq 4210
WAN
vtnet0 2025-02-12
11:52:17.121742 d4:66:24:5b:e4:db 80:xx:xx:xx:xx:xx ethertype IPv6 (0x86dd), length 63: (hlim 64, next-header ICMPv6 (58) payload length: 9) fe80::d666:24ff:fe5b:e4db > fe80::8269:1aff:fe76:529b: [icmp6 sum ok] ICMP6, echo reply, id 18980, seq 4210
WAN
vtnet0 2025-02-12
11:52:18.192674 80:xx:xx:xx:xx:xx d4:66:24:5b:e4:db ethertype IPv6 (0x86dd), length 63: (hlim 64, next-header ICMPv6 (58) payload length: 9) fe80::8269:1aff:fe76:529b > fe80::d666:24ff:fe5b:e4db: [icmp6 sum ok] ICMP6, echo request, id 18980, seq 4211
WAN
vtnet0 2025-02-12
11:52:18.193722 d4:66:24:5b:e4:db 80:xx:xx:xx:xx:xx ethertype IPv6 (0x86dd), length 63: (hlim 64, next-header ICMPv6 (58) payload length: 9) fe80::d666:24ff:fe5b:e4db > fe80::8269:1aff:fe76:529b: [icmp6 sum ok] ICMP6, echo reply, id 18980, seq 4211
WAN
vtnet0 2025-02-12
11:52:19.222559 80:xx:xx:xx:xx:xx d4:66:24:5b:e4:db ethertype IPv6 (0x86dd), length 63: (hlim 64, next-header ICMPv6 (58) payload length: 9) fe80::8269:1aff:fe76:529b > fe80::d666:24ff:fe5b:e4db: [icmp6 sum ok] ICMP6, echo request, id 18980, seq 4212
WAN
vtnet0 2025-02-12
11:52:19.223691 d4:66:24:5b:e4:db 80:xx:xx:xx:xx:xx ethertype IPv6 (0x86dd), length 63: (hlim 64, next-header ICMPv6 (58) payload length: 9) fe80::d666:24ff:fe5b:e4db > fe80::8269:1aff:fe76:529b: [icmp6 sum ok] ICMP6, echo reply, id 18980, seq 4212
WAN
vtnet0 2025-02-12
11:52:20.246402 80:xx:xx:xx:xx:xx d4:66:24:5b:e4:db ethertype IPv6 (0x86dd), length 63: (hlim 64, next-header ICMPv6 (58) payload length: 9) fe80::8269:1aff:fe76:529b > fe80::d666:24ff:fe5b:e4db: [icmp6 sum ok] ICMP6, echo request, id 18980, seq 4213
WAN
vtnet0 2025-02-12
11:52:20.247535 d4:66:24:5b:e4:db 80:xx:xx:xx:xx:xx ethertype IPv6 (0x86dd), length 63: (hlim 64, next-header ICMPv6 (58) payload length: 9) fe80::d666:24ff:fe5b:e4db > fe80::8269:1aff:fe76:529b: [icmp6 sum ok] ICMP6, echo reply, id 18980, seq 4213
WAN
vtnet0 2025-02-12
11:52:21.258802 80:xx:xx:xx:xx:xx d4:66:24:5b:e4:db ethertype IPv6 (0x86dd), length 63: (hlim 64, next-header ICMPv6 (58) payload length: 9) fe80::8269:1aff:fe76:529b > fe80::d666:24ff:fe5b:e4db: [icmp6 sum ok] ICMP6, echo request, id 18980, seq 4214
WAN
vtnet0 2025-02-12
11:52:21.260060 d4:66:24:5b:e4:db 80:xx:xx:xx:xx:xx ethertype IPv6 (0x86dd), length 63: (hlim 64, next-header ICMPv6 (58) payload length: 9) fe80::d666:24ff:fe5b:e4db > fe80::8269:1aff:fe76:529b: [icmp6 sum ok] ICMP6, echo reply, id 18980, seq 4214
WAN
vtnet0 2025-02-12
11:52:21.871791 d4:66:24:5b:e4:db 80:xx:xx:xx:xx:xx ethertype IPv6 (0x86dd), length 86: (class 0xe0, hlim 255, next-header ICMPv6 (58) payload length: 32) fe80::d666:24ff:fe5b:e4db > fe80::8269:1aff:fe76:529b: [icmp6 sum ok] ICMP6, neighbor solicitation, length 32, who has fe80::8269:1aff:fe76:529b
source link-address option (1), length 8 (1): d4:66:24:5b:e4:db
0x0000: d466 245b e4db
WAN
vtnet0 2025-02-12
11:52:21.871818 80:xx:xx:xx:xx:xx d4:66:24:5b:e4:db ethertype IPv6 (0x86dd), length 78: (hlim 255, next-header ICMPv6 (58) payload length: 24) fe80::8269:1aff:fe76:529b > fe80::d666:24ff:fe5b:e4db: [icmp6 sum ok] ICMP6, neighbor advertisement, length 24, tgt is fe80::8269:1aff:fe76:529b, Flags [router, solicited]
WAN
vtnet0 2025-02-12
11:52:22.288753 80:xx:xx:xx:xx:xx d4:66:24:5b:e4:db ethertype IPv6 (0x86dd), length 63: (hlim 64, next-header ICMPv6 (58) payload length: 9) fe80::8269:1aff:fe76:529b > fe80::d666:24ff:fe5b:e4db: [icmp6 sum ok] ICMP6, echo request, id 18980, seq 4215
WAN
vtnet0 2025-02-12
11:52:22.289967 d4:66:24:5b:e4:db 80:xx:xx:xx:xx:xx ethertype IPv6 (0x86dd), length 63: (hlim 64, next-header ICMPv6 (58) payload length: 9) fe80::d666:24ff:fe5b:e4db > fe80::8269:1aff:fe76:529b: [icmp6 sum ok] ICMP6, echo reply, id 18980, seq 4215
WAN
vtnet0 2025-02-12
11:52:23.307621 80:xx:xx:xx:xx:xx d4:66:24:5b:e4:db ethertype IPv6 (0x86dd), length 63: (hlim 64, next-header ICMPv6 (58) payload length: 9) fe80::8269:1aff:fe76:529b > fe80::d666:24ff:fe5b:e4db: [icmp6 sum ok] ICMP6, echo request, id 18980, seq 4216
WAN
vtnet0 2025-02-12
11:52:23.308690 d4:66:24:5b:e4:db 80:xx:xx:xx:xx:xx ethertype IPv6 (0x86dd), length 63: (hlim 64, next-header ICMPv6 (58) payload length: 9) fe80::d666:24ff:fe5b:e4db > fe80::8269:1aff:fe76:529b: [icmp6 sum ok] ICMP6, echo reply, id 18980, seq 4216
WAN
vtnet0 2025-02-12
11:52:24.322136 80:xx:xx:xx:xx:xx d4:66:24:5b:e4:db ethertype IPv6 (0x86dd), length 63: (hlim 64, next-header ICMPv6 (58) payload length: 9) fe80::8269:1aff:fe76:529b > fe80::d666:24ff:fe5b:e4db: [icmp6 sum ok] ICMP6, echo request, id 18980, seq 4217
WAN
vtnet0 2025-02-12
11:52:24.323097 d4:66:24:5b:e4:db 80:xx:xx:xx:xx:xx ethertype IPv6 (0x86dd), length 63: (hlim 64, next-header ICMPv6 (58) payload length: 9) fe80::d666:24ff:fe5b:e4db > fe80::8269:1aff:fe76:529b: [icmp6 sum ok] ICMP6, echo reply, id 18980, seq 4217
WAN
vtnet0 2025-02-12
11:52:25.372505 80:xx:xx:xx:xx:xx d4:66:24:5b:e4:db ethertype IPv6 (0x86dd), length 63: (hlim 64, next-header ICMPv6 (58) payload length: 9) fe80::8269:1aff:fe76:529b > fe80::d666:24ff:fe5b:e4db: [icmp6 sum ok] ICMP6, echo request, id 18980, seq 4218
WAN
vtnet0 2025-02-12
11:52:25.373694 d4:66:24:5b:e4:db 80:xx:xx:xx:xx:xx ethertype IPv6 (0x86dd), length 63: (hlim 64, next-header ICMPv6 (58) payload length: 9) fe80::d666:24ff:fe5b:e4db > fe80::8269:1aff:fe76:529b: [icmp6 sum ok] ICMP6, echo reply, id 18980, seq 4218
WAN
vtnet0 2025-02-12
11:52:26.394745 80:xx:xx:xx:xx:xx d4:66:24:5b:e4:db ethertype IPv6 (0x86dd), length 63: (hlim 64, next-header ICMPv6 (58) payload length: 9) fe80::8269:1aff:fe76:529b > fe80::d666:24ff:fe5b:e4db: [icmp6 sum ok] ICMP6, echo request, id 18980, seq 4219
WAN
vtnet0 2025-02-12
11:52:26.396060 d4:66:24:5b:e4:db 80:xx:xx:xx:xx:xx ethertype IPv6 (0x86dd), length 63: (hlim 64, next-header ICMPv6 (58) payload length: 9) fe80::d666:24ff:fe5b:e4db > fe80::8269:1aff:fe76:529b: [icmp6 sum ok] ICMP6, echo reply, id 18980, seq 4219
WAN
vtnet0 2025-02-12
11:52:27.414085 80:xx:xx:xx:xx:xx d4:66:24:5b:e4:db ethertype IPv6 (0x86dd), length 63: (hlim 64, next-header ICMPv6 (58) payload length: 9) fe80::8269:1aff:fe76:529b > fe80::d666:24ff:fe5b:e4db: [icmp6 sum ok] ICMP6, echo request, id 18980, seq 4220
WAN
vtnet0 2025-02-12
11:52:27.415322 d4:66:24:5b:e4:db 80:xx:xx:xx:xx:xx ethertype IPv6 (0x86dd), length 63: (hlim 64, next-header ICMPv6 (58) payload length: 9) fe80::d666:24ff:fe5b:e4db > fe80::8269:1aff:fe76:529b: [icmp6 sum ok] ICMP6, echo reply, id 18980, seq 4220
WAN
vtnet0 2025-02-12
11:52:28.458791 80:xx:xx:xx:xx:xx d4:66:24:5b:e4:db ethertype IPv6 (0x86dd), length 63: (hlim 64, next-header ICMPv6 (58) payload length: 9) fe80::8269:1aff:fe76:529b > fe80::d666:24ff:fe5b:e4db: [icmp6 sum ok] ICMP6, echo request, id 18980, seq 4221
WAN
vtnet0 2025-02-12
11:52:28.460026 d4:66:24:5b:e4:db 80:xx:xx:xx:xx:xx ethertype IPv6 (0x86dd), length 63: (hlim 64, next-header ICMPv6 (58) payload length: 9) fe80::d666:24ff:fe5b:e4db > fe80::8269:1aff:fe76:529b: [icmp6 sum ok] ICMP6, echo reply, id 18980, seq 4221
WAN
vtnet0 2025-02-12
11:52:29.469843 80:xx:xx:xx:xx:xx d4:66:24:5b:e4:db ethertype IPv6 (0x86dd), length 63: (hlim 64, next-header ICMPv6 (58) payload length: 9) fe80::8269:1aff:fe76:529b > fe80::d666:24ff:fe5b:e4db: [icmp6 sum ok] ICMP6, echo request, id 18980, seq 4222
WAN
vtnet0 2025-02-12
11:52:29.471429 d4:66:24:5b:e4:db 80:xx:xx:xx:xx:xx ethertype IPv6 (0x86dd), length 63: (hlim 64, next-header ICMPv6 (58) payload length: 9) fe80::d666:24ff:fe5b:e4db > fe80::8269:1aff:fe76:529b: [icmp6 sum ok] ICMP6, echo reply, id 18980, seq 4222
WAN
vtnet0 2025-02-12
11:52:30.517364 80:xx:xx:xx:xx:xx d4:66:24:5b:e4:db ethertype IPv6 (0x86dd), length 63: (hlim 64, next-header ICMPv6 (58) payload length: 9) fe80::8269:1aff:fe76:529b > fe80::d666:24ff:fe5b:e4db: [icmp6 sum ok] ICMP6, echo request, id 18980, seq 4223
WAN
vtnet0 2025-02-12
11:52:30.518600 d4:66:24:5b:e4:db 80:xx:xx:xx:xx:xx ethertype IPv6 (0x86dd), length 63: (hlim 64, next-header ICMPv6 (58) payload length: 9) fe80::d666:24ff:fe5b:e4db > fe80::8269:1aff:fe76:529b: [icmp6 sum ok] ICMP6, echo reply, id 18980, seq 4223
WAN
vtnet0 2025-02-12
11:52:30.858885 80:xx:xx:xx:xx:xx d4:66:24:5b:e4:db ethertype IPv6 (0x86dd), length 86: (hlim 255, next-header ICMPv6 (58) payload length: 32) fe80::8269:1aff:fe76:529b > fe80::d666:24ff:fe5b:e4db: [icmp6 sum ok] ICMP6, neighbor solicitation, length 32, who has fe80::d666:24ff:fe5b:e4db
source link-address option (1), length 8 (1): 80:xx:xx:xx:xx:xx
0x0000: 8069 1a76 529b
WAN
vtnet0 2025-02-12
11:52:30.883867 d4:66:24:5b:e4:db 80:xx:xx:xx:xx:xx ethertype IPv6 (0x86dd), length 86: (class 0xe0, hlim 255, next-header ICMPv6 (58) payload length: 32) fe80::d666:24ff:fe5b:e4db > fe80::8269:1aff:fe76:529b: [icmp6 sum ok] ICMP6, neighbor advertisement, length 32, tgt is fe80::d666:24ff:fe5b:e4db, Flags [router, solicited, override]
destination link-address option (2), length 8 (1): d4:66:24:5b:e4:db
0x0000: d466 245b e4db
Those are only router advertisements and ping requests and replies, you do not seem to get any DHCPv6 replies, nor do you send requests.
That would explain why you only get a route and a link-local address. Then again, the DHCPv6 exchange may have happened before the dump starts.
Ah got it thanks, is there any way to force OPNsense to request DHCPv6 while I have package capture enabled?
I would try to disable and enable the interface or disable DHCPv6 and then re-enable. IDK if the running tcpdump will suvive that, however.
root@router:/home/kingamajick # tcpdump -i vtnet0 -Avvv '(port 546 or port 547)'
tcpdump: listening on vtnet0, link-type EN10MB (Ethernet), snapshot length 262144 bytes
14:48:04.822436 IP6 (hlim 1, next-header UDP (17) payload length: 89) fe80::8269:1aff:fe76:529b.dhcpv6-client > ff02::1:2.dhcpv6-server: [udp sum ok] dhcp6 solicit (xid=d8e126 (client-ID hwaddr/time type 1 time 748624729 22eb3b4e0e98) (elapsed-time 65535) (option-request DNS-server DNS-search-list) (IA_PD IAID:0 T1:0 T2:0 (IA_PD-prefix ::/48 pltime:4294967295 vltime:4294967295)))
`....Y...........i...vR..................".#.YFd...&........,..Y".;N...................)........................0................
No response to the solicit at all, I'll give it a try this evening to iterate though the prefix options and see If I have any luck.
Then again, the internet is full of reports on CF IPv6 problems, like this: https://forums.thinkbroadband.com/fibre/4697990-community-fibre-ipv6-or-lack-of-it.html
What many people will tell you is that DHCPv6 requests are being ignored then the MAC does not match what CF thinks it should be. You can ask them to clear that on their side. Also, with DHCPv6, it is usually a DUUID, which is derived from the MAC, but IDK exactly.
Well after doing absolutely nothing for a few days, ipv6 is working I have the prefix shown in the settings -> overview -> more details. So I guess the issue was somewhere on there end. Thanks for all the help @meyergru really appreciate it!