No IPv6 traffic (Init7)
-
@syhm said in No IPv6 traffic (Init7):
dhcp6c
Thank you. Thats the full log more or less. There are no more entries. And no entries related with process dhcp6c.
Is it the intention to see the dhcp settings releated to the WAN side?
-
@syhm said in No IPv6 traffic (Init7):
Unfortunately the log doesn't show the dhcp6c process.
-
Uugh. I need a moment to prepare that setup... I did a packet capture session for now.
(fe80::aaaa:bbbb:cccc:4b11 is the link local address of the WAN port)
22:34:10.389487 IP6 (hlim 255, next-header ICMPv6 (58) payload length: 32) :: > ff02::1:fff3:4b11: [icmp6 sum ok] ICMP6, neighbor solicitation, length 32, who has fe80::aaaa:bbbb:cccc:4b11 unknown option (14), length 8 (1): 0x0000: 24e4 2075 0d32 22:34:12.505358 IP6 (hlim 255, next-header ICMPv6 (58) payload length: 16) fe80::aaaa:bbbb:cccc:4b11 > ff02::2: [icmp6 sum ok] ICMP6, router solicitation, length 16 source link-address option (1), length 8 (1): ae:2e:85:f3:4b:11 0x0000: ae2e 85f3 4b11 22:34:16.510649 IP6 (hlim 255, next-header ICMPv6 (58) payload length: 16) fe80::aaaa:bbbb:cccc:4b11 > ff02::2: [icmp6 sum ok] ICMP6, router solicitation, length 16 source link-address option (1), length 8 (1): ae:2e:85:f3:4b:11 0x0000: ae2e 85f3 4b11 22:34:20.535123 IP6 (hlim 255, next-header ICMPv6 (58) payload length: 16) fe80::aaaa:bbbb:cccc:4b11 > ff02::2: [icmp6 sum ok] ICMP6, router solicitation, length 16 source link-address option (1), length 8 (1): ae:2e:85:f3:4b:11 0x0000: ae2e 85f3 4b11 -
Please upload the capture file. It contains a lot more info that what you show. When you open it in Wireshark, you can see a lot of detail.
Here's an example of one I did a few years ago.
DHCPv6 Solicit and Renew.pcapng -
@jknott said in No IPv6 traffic (Init7):
show full capture file
A long time ago that I used wireshark, my old friend.... Please see the capture file attached this post (not much of use in it I guess).
-
I thought you had a problem with dhcpv6. There is none of that in the capture. You have to filter on port 546 or 547 to capture dhcpv6.
-
@jknott
I unfortunately haven't got the slightest idea what to investigate. Mybe its DHCP, maybe its something else... So far, I went through anything, tryed any combination on the WAN interface settings, googled (people with the same setup/ provider habe a working environment with the settings stated in the initial post) - I even checked the cables and switches.I just don't get any traffic on IPv6 on the WAN-side. LAN-side works well and I can reach the LAN side of pfsense by its (LAN-)IPv6 address.
What I see, is that any traffic is blocked by a default rule
Default deny rule IPv6and a pending gateway
@syhm was asking for dhcp6c log entries, which I have found eventualy under "general".
Its as below and only just this repeating.Aug 9 22:46:15 php 420 rc.bootup: Unbound start waiting on dhcp6c. Aug 9 22:46:16 php 420 rc.bootup: Unbound start waiting on dhcp6c. Aug 9 22:46:17 php 420 rc.bootup: Unbound start waiting on dhcp6c. Aug 9 22:46:18 php 420 rc.bootup: Unbound start waiting on dhcp6c.However, the interfaces seem to be.. well... there
So long....
n3 -
Start by providing the dhcpv6 capture file as I have now requested a couple of times. Here again are the instructions.
-
@jknott
Roger that.
There isn't actually any thing more than what was captured in the attached file above. There is just nothing related to IPv6 coming on that WAN port.I'll connect a laptop directly to the switch but need to organize an ethernet dongle first and reconfigure the switch (the only non-company-locked laptop I have at hand has a USB C port only).
I'll report back. Takes a moment.
-
There is a lot more in a capture file than what you have provided. That's why I keep asking for it. To fully see what's happening, you examine the actual capture file with Wireshark. This will provide a lot more info than you have.
-
Here's an example of what I'm looking for in the captures. This is just part of one packet of 8.
