Messages

I didn't release this wasn't a problem, I thought that the issue with the speakers was it was doing some weird requests with my domain stuck on the end, I didn't know this was a standard thing that occurred in this sistuation.

Just for context, I've bought a few Sonos speakers recently and 1 or 2 or them are proving problematic and not registering with the Sonos system so I was seeing if I could see anything in the package capture, and that looked strange to me, but turns out it's completely normal.

Thanks for your help.

I've send the package capture over to Sonos to see if they can work out whats happening with the speakers, and at least I know this is a dead end in term of the problem (the adding lan.mydomain.com) and learnt something in the process.

Thanks

It looks like it's just repeating this sequence from the logs

LAN
vtnet1   2025-05-21
14:10:07.665756   38:42:0b:9e:f9:92   72:a9:94:69:59:9a   ethertype IPv4 (0x0800), length 85: (tos 0x0, ttl 64, id 35643, offset 0, flags [DF], proto UDP (17), length 71)
    192.168.1.140.59440 > 192.168.1.1.53: [udp sum ok] 745+ A? registration.ws.sonos.com. (43)
LAN
vtnet1   2025-05-21
14:10:07.665899   72:a9:94:69:59:9a   d4:3a:2c:a4:72:75   ethertype IPv4 (0x0800), length 189: (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP (17), length 175)
    192.168.1.1.53 > 192.168.1.140.59440: [udp sum ok] 745 q: A? registration.ws.sonos.com. 3/0/0 registration.ws.sonos.com. CNAME registration.ws.sonos.com-v2.edgekey.net., registration.ws.sonos.com-v2.edgekey.net. CNAME e8047.e2.akamaiedge.net., e8047.e2.akamaiedge.net. A 23.215.236.36 (147)
LAN
vtnet1   2025-05-21
14:10:12.669364   38:42:0b:9e:f9:92   72:a9:94:69:59:9a   ethertype IPv4 (0x0800), length 85: (tos 0x0, ttl 64, id 35644, offset 0, flags [DF], proto UDP (17), length 71)
    192.168.1.140.59440 > 192.168.1.1.53: [udp sum ok] 745+ A? registration.ws.sonos.com. (43)
LAN
vtnet1   2025-05-21
14:10:12.669479   72:a9:94:69:59:9a   d4:3a:2c:a4:72:75   ethertype IPv4 (0x0800), length 189: (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP (17), length 175)
    192.168.1.1.53 > 192.168.1.140.59440: [udp sum ok] 745 q: A? registration.ws.sonos.com. 3/0/0 registration.ws.sonos.com. CNAME registration.ws.sonos.com-v2.edgekey.net., registration.ws.sonos.com-v2.edgekey.net. CNAME e8047.e2.akamaiedge.net., e8047.e2.akamaiedge.net. A 23.215.236.36 (147)
LAN
vtnet1   2025-05-21
14:10:12.670359   38:42:0b:9e:f9:92   72:a9:94:69:59:9a   ethertype ARP (0x0806), length 60: Ethernet (len 6), IPv4 (len 4), Request who-has 192.168.1.1 tell 192.168.1.140, length 46
LAN
vtnet1   2025-05-21
14:10:12.670373   72:a9:94:69:59:9a   38:42:0b:9e:f9:92   ethertype ARP (0x0806), length 42: Ethernet (len 6), IPv4 (len 4), Reply 192.168.1.1 is-at 72:a9:94:69:59:9a, length 28
LAN
vtnet1   2025-05-21
14:10:17.671490   38:42:0b:9e:f9:92   72:a9:94:69:59:9a   ethertype IPv4 (0x0800), length 105: (tos 0x0, ttl 64, id 36644, offset 0, flags [DF], proto UDP (17), length 91)
    192.168.1.140.48368 > 192.168.1.1.53: [udp sum ok] 37908+ A? registration.ws.sonos.com.lan.mydomain.com. (63)
LAN
vtnet1   2025-05-21
14:10:17.671623   72:a9:94:69:59:9a   d4:3a:2c:a4:72:75   ethertype IPv4 (0x0800), length 164: (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP (17), length 150)
    192.168.1.1.53 > 192.168.1.140.48368: [udp sum ok] 37908 NXDomain q: A? registration.ws.sonos.com.lan.mydomain.com. 0/1/0 ns: mydomain.com. SOA norm.ns.cloudflare.com. dns.cloudflare.com. 2372644829 10000 2400 604800 1800 (122)
LAN
vtnet1   2025-05-21
14:10:22.675586   38:42:0b:9e:f9:92   72:a9:94:69:59:9a   ethertype IPv4 (0x0800), length 105: (tos 0x0, ttl 64, id 36645, offset 0, flags [DF], proto UDP (17), length 91)
    192.168.1.140.48368 > 192.168.1.1.53: [udp sum ok] 37908+ A? registration.ws.sonos.com.lan.mydomain.com. (63)
LAN
vtnet1   2025-05-21
14:10:22.675691   72:a9:94:69:59:9a   d4:3a:2c:a4:72:75   ethertype IPv4 (0x0800), length 164: (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP (17), length 150)
    192.168.1.1.53 > 192.168.1.140.48368: [udp sum ok] 37908 NXDomain q: A? registration.ws.sonos.com.lan.mydomain.com. 0/1/0 ns: mydomain.com. SOA norm.ns.cloudflare.com. dns.cloudflare.com. 2372644829 10000 2400 604800 1800 (122)

The only other thing that looks different to that cycle is

LAN
vtnet1   2025-05-21
14:11:26.809292   38:42:0b:9e:f9:92   01:00:5e:00:00:fb   ethertype IPv4 (0x0800), length 704: (tos 0x0, ttl 255, id 57310, offset 0, flags [DF], proto UDP (17), length 690)
    192.168.1.140.5353 > 224.0.0.251.5353: [udp sum ok] 0*- [0q] 1/0/7 _sonos._tcp.local. PTR RINCON_38420B9EF99201400@Kitchen 2._sonos._tcp.local. ar: Sonos-38420B9EF992.local. (Cache flush) A 192.168.1.140, Sonos-38420B9EF992.local. (Cache flush) AAAA 2a02:6b67:eef7:a200:3a42:bff:fe9e:f992, Sonos-38420B9EF992.local. (Cache flush) AAAA fe80::3a42:bff:fe9e:f992, RINCON_38420B9EF99201400@Kitchen 2._sonos._tcp.local. (Cache flush) TXT "mdnssequence=0" "variant=2" "infohash=y881jLo4YXcbbmrapGmjGt4BWqbiDmgBk4HluQZBP9I" "hhsslport=1843" "wss=/websocket/api" "location=http://192.168.1.140:1400/xml/device_description.xml" "hhid=Sonos_hZinSZqUrDP5MEi7uDkoEmWttu" "bootseq=2" "uuid=RINCON_38420B9EF99201400" "minApiVersion=1.1.0" "sslport=1443" "protovers=1.46.0" "mhhid=Sonos_hZinSZqUrDP5MEi7uDkoEmWttu.Diewi8GJ33Z5IYI9Z7LA" "vers=5" "info=/api/v1/players/RINCON_38420B9EF99201400/info", RINCON_38420B9EF99201400@Kitchen 2._sonos._tcp.local. (Cache flush) SRV Sonos-38420B9EF992.local.:1443 0 0, Sonos-38420B9EF992.local. (Cache flush) NSEC, RINCON_38420B9EF99201400@Kitchen 2._sonos._tcp.local. (Cache flush) NSEC (662)

https://pastebin.com/raw/3YLntRAV <-- Complete logs

Thanks for the info, that's good to understand! I thought I was on the path to the root cause :) The issue with the speakers seems is a bit of a head scratcher. 1 worked, the other two didn't on my network, but did on the neighbour's (simple ISP router type setup).

In the logs there are requests for the domain without my local domain appended, which IIUC returns 23.215.236.36 so I assume in this case it shouldn't continue to add the various domains?

LAN
vtnet1   2025-05-21
14:10:12.669479   72:a9:94:69:59:9a   d4:3a:2c:a4:72:75   ethertype IPv4 (0x0800), length 189: (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP (17), length 175)
    192.168.1.1.53 > 192.168.1.140.59440: [udp sum ok] 745 q: A? registration.ws.sonos.com. 3/0/0 registration.ws.sonos.com. CNAME registration.ws.sonos.com-v2.edgekey.net., registration.ws.sonos.com-v2.edgekey.net. CNAME e8047.e2.akamaiedge.net., e8047.e2.akamaiedge.net. A 23.215.236.36 (147)

(Per chance did you see anything else in the logs that sticks out as a incorrectly configured network on my end?)

Thanks

Apologies is the title is a bit misleading, I'm not sure how I would exactly describe this problem.

I've been trying to get some Sonos speakers working on my system and they keep failing during registration.

After running a package capture, I've noticed the following in the logs that doesn't seem correct.

LAN
vtnet1   2025-05-21
14:12:16.892595   38:42:0b:9e:f9:92   72:a9:94:69:59:9a   ethertype IPv4 (0x0800), length 105: (tos 0x0, ttl 64, id 48566, offset 0, flags [DF], proto UDP (17), length 91)
    192.168.1.140.50520 > 192.168.1.1.53: [udp sum ok] 26539+ A? registration.ws.sonos.com.lan.mydomain.com. (63)
LAN
vtnet1   2025-05-21
14:12:16.892744   72:a9:94:69:59:9a   d4:3a:2c:a4:72:75   ethertype IPv4 (0x0800), length 164: (tos 0x0, ttl 64, id 0, offset 0, flags [DF], proto UDP (17), length 150)
    192.168.1.1.53 > 192.168.1.140.50520: [udp sum ok] 26539 NXDomain q: A? registration.ws.sonos.com.lan.mydomain.com. 0/1/0 ns: mydomain.com. SOA norm.ns.cloudflare.com. dns.cloudflare.com. 2372644829 10000 2400 604800 1800 (122)

It appears registration.ws.sonos.com has .lan.mydomain.com appended to it.

I'm using ISC DHCPv4 which has the domain name set as lan.mydomain.com and domain search list as lan.mydomain.com;mydomain.com.

And Unbound DNS has DHCP Domain Override set to lan.mydomain.com.

Can any one point me in the direction of what may be causing this issue?


Full packet capture https://pastebin.com/raw/3YLntRAV

Thanks :)

 

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!

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.

Were you able to verify your token as detailed here? https://developers.cloudflare.com/fundamentals/api/get-started/create-token/

Ah got it thanks, is there any way to force OPNsense to request DHCPv6 while I have package capture enabled?

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

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 :)

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?

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)

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.

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

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)