WAN and LAN IPv6
-
This begins to sound like my system. I have a PPPoE connection the negotiates on V4, then V6 is routed via the PPPoE link, my addresses are all static, although I can use dhcp6.
When you say you cannot ping the LAN client, are you trying to ping it from the WAN?
-
So now on the LAN client I can ping the IPv6 LAN static IP (ZZZ block). But also if I try to ping any other IPv6 address, it just terminates at that address (the IP statically assigned to the LAN).
Here's some examples from a LAN client:
ping -6 AAAA:XXXX:1:ZZZ::1 Pinging 2a01:5d00:1:6ed::1 with 32 bytes of data: Reply from AAAA:XXXX:1:ZZZ::1: time<1ms Reply from AAAA:XXXX:1:ZZZ::1: time<1ms Reply from AAAA:XXXX:1:ZZZ::1: time<1ms Reply from AAAA:XXXX:1:ZZZ::1: time<1ms Ping statistics for AAAA:XXXX:1:ZZZ::1: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0msSo far so good.
ping -6 google.com Pinging google.com [2a00:1450:4009:812::200e] with 32 bytes of data: Reply from 2a00:1450:4009:812::200e: time<1ms Reply from 2a00:1450:4009:812::200e: time<1ms Reply from 2a00:1450:4009:812::200e: time<1ms Reply from 2a00:1450:4009:812::200e: time<1ms Ping statistics for 2a00:1450:4009:812::200e: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0msDoesn't look right, the ping to my ISP's gateway is about 7ms. On traceroute we see:
tracert -6 google.com Tracing route to google.com [2a00:1450:4009:812::200e] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms pfsense.lan.xxxxx [AAAA:XXXX:1:ZZZ::1] Trace complete.This obviously isn't correct and it seems like very strange behaviour. Everything destined to somewhere not inside AAAA:XXXX:1:ZZZ::/64 seems to "terminate" at pfSense, and yet the LAN clients can use IPv6 only websites and connect to services on the public internet over IPv6.
From the outside, trying to traceroute one of the LAN IPv6 addresses from the public internet, I see that the last hop before it's unable to continue is my WAN IPv6 (not my LAN).
From inside the LAN, trying to connect or ping another LAN client over IPv6 works as I'd expect - it's direct and through the switch with no communication with pfSense.
To answer your question - if I try to ping a LAN client from Diagnostics -> Ping with source address set to WAN, this appears to work.
-
When pinging from the outside in, you'll need to have a rule set up to allow that. All inbound traffic is blocked by default, apart from that which is of course in response to an outbound request.
-
@marjohn56:
When pinging from the outside in, you'll need to have a rule set up to allow that. All inbound traffic is blocked by default, apart from that which is of course in response to an outbound request.
Sorry, of course I've been messing with this IPv6 specific stuff for so long now I forget the easy stuff. Rule added on WAN to allow ICMP echorep/rechoreq when destination = LAN net has solved traceroute/ping from the outside. So now the only remaining issue is traceroute/ping from the inside which is really weird.
-
Try this ping this address and see what you get.
2001:41c1:4008::bbc:1
-
@marjohn56:
Try this ping this address and see what you get.
2001:41c1:4008::bbc:1
Same thing, ping reports <1ms and tracert shows it stopping at my static LAN IP, 1 hop only.
A traceroute from Diagnotics -> Traceroute on pfSense with source address set as LAN works correctly, with the first hop being my ISP's fe80 link-local gateway. So it's only traffic from actual LAN clients which seems to be affected.
-
OK, got you, I misunderstood, I thought your LAN clients were pinging OK.
Right we are making progress. So you have a default pass out rule for the LAN, it should have been automatically created for you. LAN Net to Any, is that there?
-
@marjohn56:
OK, got you, I misunderstood, I thought your LAN clients were pinging OK.
Right we are making progress. So you have a default pass out rule for the LAN, it should have been automatically created for you. LAN Net to Any, is that there?
Yes it's there, and been doing some more testing my end - this issue might be client specific.
On Linux, it's not an issue at all, traceroute and ping both work normally, including traceroute using ICMP.
On Windows, tracert and ping are not working as expected (but this could be down to other software on the machine).
On Android, I am using PingTools Pro. In ICMP mode, traceroute works as expected, in UDP mode it doesn't seem to work properly. Pings do work as expected though.
-
Yeah it seems like the 1ms ping thing is a Kaspersky issue. It was difficult to find but I found some references to others experiencing the issue and it's a bug in their network filtering driver. So perhaps this issue is solved then.
https://forum.kaspersky.com/index.php?/topic/374028-kes-10-sp2-icmpv6-issue/&
-
:) Yes, well - Kaspersky… Hmm
Not allowed near any of my machines.
Apart from the fact they may or may not be in leagues with the Kremlin I have always found it slows my machines down.
I use Webroot, never have an issue.
-
@marjohn56:
:) Yes, well - Kaspersky… Hmm
Not allowed near any of my machines.
Apart from the fact they may or may not be in leagues with the Kremlin I have always found it slows my machines down.
I use Webroot, never have an issue.
Well either way, thanks for your help man - wouldn't have been able to do it without you. I think the issue is pretty much sorted now.