Ipv6 showing pending on gateway
-
I did a fresh install because i waited to long and could no longer update .So i did a config backup and did a fresh install .I did the restore backup and had it seemed to work .I have pending on the gateway but have a ipv6 address on interface and passes ipv6 tests .What is the problem ?
-
@nighthawk1967
I used to have a similar issue with my prior ISP. The gateway on the STATUS page would show pending and offline. But I had an IPV6 address, I had VLANS and they all had their own IPV6 prefix using the /60 I got from the ISP. I could ping in IPV6 and test OK on IPV6 test sites. I came to the conclusion that the ISP's IPV6 just wasn't playing nice with the gateway ping. You could try changing what it is trying to ping, under SYSTEM/ROUTING, and editing the IPV6 WAN gateway to ping something else. I just turned off the ping. -
@tzvia I do not have a ping option in wan IPV6
-
@nighthawk1967 In System/Routing/Gateways, you see both gateways, ipv4 and ipv6. Click to edit the IPV6 gateway- that is where you can set what is being pinged by PFSense to show the gateway as UP or DOWN. You can disable gateway monitoring there (disable the auto ping) or choose an address in ipv6 to ping, if the automatically configured IP doesn't respond to ping. I set Google's ipv6 ip. With my prior ISP, I just disabled it.
-
@tzvia I just get pending and unknown .If there is going to be no fix i guess it's time to buy router because ipv6 seems to broken in all router software i have tried .
-
@nighthawk1967 You have IPV6 IPs and pass all the IPV6 websites, as stated in a post here. So IPV6 is UP. Some ISPs just don't play nice with the ping test on the PFSense gateway though. I knew it was UP because it worked so the gateway ping not working didn't bother me with my prior ISP. I just disabled it, it's not needed to make anything work.
Did you try going into System/Routing/Gateways and adding a 'monitor IP' like GOOGLE's IPV6 DNS, (2001:4860:4860::8888), to see if that ping would work? If it doesn't, just disable IPV6 gateway monitoring. -
@tzvia I tried that it broke ipv6
-
@nighthawk1967 said in Ipv6 showing pending on gateway:
...I have pending on the gateway but have a ipv6 address on interface and passes ipv6 tests .What is the problem ?
According to your first post IPV6 is working and the only thing that isn't, is the ping that PFSense does automatically, of the gateway to confirm it is UP. Whatever that default that it is pinging is, may or may not respond to ping as I mentioned above. If you go into SYSTEM/ROUTING as I described in my prior post and change the monitoring IP that setting can't 'break' IPV6. It may ping and show the gateway as UP, or it may not, probably based on what your ISP does... But it won't break a working IPV6 if you change the monitoring IP. The monitoring NOT working does NOT mean that IPV6 isn't working. It only means that PFSense can't ping the monitoring IP, which can be blocked by the ISP and have nothing to do with IPV6 working or not, as you mentioned in your first post, IPV6 WORKING but gateway monitoring NOT working.
If IPV6 really isn't working then I've been going down a rabbit hole here looking at the gateway monitoring being the cosmetic problem when IPV6 is really DOWN and not working, a totally different problem.
-
@tzvia Shows ipv6 address but browser tests fail on windows 10 and 11
-
@nighthawk1967 I can replace the pfsense with a oem and ipv6 works no problem .I install pfsense box no ipv6 and before the upgrade to 23.01 everything works .There used to be help with pfsense years ago but nothing now ,time for new hardware and oem firewall .I should never did the useless update
-
@nighthawk1967
PFSense is not a 'turn it on and it works'. If that's the goal, and you don't care for the control it provides and extra functionality (VPN, VLANS, packages like PFBLOCKER and Suricata/Snort...) just stick with a basic home router. Windows 10/11 require a bit more setup for IPV6 here than just getting an IPV6 IP on the WAN interface from the ISP. Typically (varies by ISP) you may get a 128 from the ISP on the WAN interface, or nothing even. A 128 isn't used for much other than as an IPV6 IP to aim a VPN at. What matters is the LAN interface, does it have an IPV6 IP?
As you see here, step one is to verify that your LAN and any VLANs are getting IPV6 addresses using the PREFIX ID you specified in INTERFACES/LAN (and any VLANS)/IPv6 Prefix ID. Typically the IPV6 Configuration Type is set to Track Interface but this depends on the ISP. Once you have a valid IPV6 address on your LAN you can then move to setting IPV6 to play nice with Windows 10/11.
Go to Services/DHCPv6 Server & RA/LAN/Router Advertisements/. I found that in my case, setting ROUTER MODE here to STATELESS DHCP worked with Windows 10 and 11. You could also try UNMANAGED. I'm using Windows 10 and 11 PRO and ENTERPRISE. DHCP is not needed in a typical home environment. Router advertisement works just fine. -
Also just read some of this: No IPv6 after upgrade to 23.01. You did mention you upgraded...
I am on 2.6 still.