IPv6 can't ping from WAN and other problems

Started by opnsense-user123, March 16, 2023, 09:37:47 PM

Previous topic - Next topic
March 16, 2023, 09:37:47 PM Last Edit: March 16, 2023, 11:04:17 PM by opnsense-user123
Hello:

I think someone is just going to know the answer once I state the problem. I have a PPPoE connection which requires (not sure why) static config for IPv6. The ISP (Andrews and Arnold in UK) gave me an IPv6 WAN IP to use through which they will route my actual v6 IP block (a /48 and a /64 within that). The WAN IP is not in my /48 or /64.  I may well have an incorrect network prefix set somewhere. Everywhere I have defined an address I used /64 except the WAN IP since it was not in my /64 or /48 I came up with /96 which was at least accepted by Opnsense.

On IPv4, the WAN IP and gateway come up fine automatically on the PPPoE interface. I have then put the IPv6 WAN IP they gave me (/96) on the PPPoE Interface (v6 Static address) and a gateway comes up automatically.

With this setting, when I try to ping6 to a host, I cannot do it from the default interface (WAN). But if I ping with source address of one of my LAN IPv6 addresses (I have three LANs, and statically assigned an IP within my /64 block to each) I can ping.

I wouldn't care about that, but I seem to be having other issues also. Like, only from one of my LANs am I able to communicate on IPv6 (a mac and a linux desktop on wifi through that LAN work fine) but on another LAN I cannot communicate even though the computer has a real IPv6 address (2001:etc) and can do IPv6 dns lookups.

Any suggestions?

What additional info should I show you?

The failed ping does attempt to work, does not show an error, but gets no replies.

# ping6 -v google.com
PING6(56=40+8+8 bytes) 2001:xxx:ffff:4d8:xxx --> 2a00:1450:4009:820::200e

(where that masked source address is the WAN IP the ISP gave me to use.)

Actually, now I see if I keep pinging longer in verbose I see some messages about Neighbor Solicitation and Neighbor Advertisement and Router Advertisement from other interfaces on my system.

Thanks!

I have the impression that 23.3.5 messed it, I got my ipv6 broken after it did the upgrade few days ago.