IPV6 Works on pfsense, but unable to get on LAN side
I'm still new to pfsense. I need some help configuring my lan devices to get a ipv6 address/connectivity.
From webgui, I'm able to get ipv6 address using dhcp6 (WAN) and also able to ping6 ipv6.google.com via command prompt. Based on this test, i assume that my ipv6 is working well on pfsense. Except all my lan device is not able to get ipv6 address from pfsense.
On RA: Stateless, high priority, the rest are default.
On LAN: IPv6 Configuration Type track interface
IPv6 Interface: WAN
IPv6 Prefix ID: 0
Anyone able to help me out
ISP: Starhub (SG)
@enjawd How you set pfSense depends on how your ISP's IPv6 service is provisioned.
@derelict i believe the ISP side is working fine? Previously tested on my asus router, my lan device is able to get ipv6. As for pfsense i cant get ipv6 on lan, not sure if there's any setting i missed out.
JKnott last edited by
Please mention who your ISP is. That may provide a clue or someone may have experience with them.
@jknott updated post :)
@enjawd What is the guidance from your ISP regarding exactly how their service is provisioned?
@enjawd Fibre? MIF or MOL plan?
@derelict im not very sure, but previously on a asus router i would just set connection to:-
- connection: native
- dhcp-pd: enable
- auto config: stateless
- RA: enable
@jwj Fibre 1G plan
@enjawd That should give you native ipv6. So, get your wan by dhcp6c and apply the prefix via track interface for your LAN network, as you said you did.
How have you setup 'services->dhcpv6 server and RA'?
Sounds like you only have one private (LAN) network. Is that true? StarHUB only gives out a /64 prefix by default but will give out a /56 once you bug them about it for a while ;)
Almost forgot, your pfsense box is hooked up directly to the ONT?
@jwj hmm, i've uncheck dhcpv6 server. For RA, i've selected stateless & highest priority. Also only 1 LAN interface using ipv6 tracking wan
For now its connected to a ASUS AC5300 router(its faulty, only Port2 is working ). Need to get this pfsense setup correctly before connecting it directly to ONT.
Btw, i install pfsense to a zotac mini box which uses realtek NIC. not sure if this info is useful as i read that realtek NIC is problematic with pfsense/freebsd.
@enjawd I'd hook it up directly. If your nic is working, it's working.
Reboot the pfsense box. Does your LAN interface get a ipv6 address? Check by looking at Status->Interfaces.
StarHUB does have some history of awful ipv6 support. When I had it a few years ago (had an apartment paid for by my employer, my home was Thailand) it just didn't work. Full stop not working ;) But I understand things are much better lately.
I'll check in again in the morning. Now that we know what is going on with your ISP maybe @Derelict will chime in again, he forgets more about this each day than I will ever know :)
@jwj yeah, recently starhub ipv6 works well again.
My LAN interface doesn't seems to be able to get any ipv6 address. I think the ISP side does not have any issue, able to ping ipv6 using the cmd in webgui. Its probably pfsense side unable to push down ipv6 address to lan interface.
For realtek nic, i notice some problem with it getting re0:watchdog timeout when during speedtest, as i cant seems to get 1G download speed on it.
jwj last edited by
@enjawd Hook it up directly and see if your LAN interface gets an address.
Update: Tested when connected directly to ONT, IPV6 works. probably because pfsense is connected to another router hence unable to push ipv6 to device behind pfsense.
@jwj Yeah came across this post earlier today, updated the driver.. so far ok. shall monitor along the way. cheers
Bob.Dig last edited by Bob.Dig
So if this is true:
StarHUB only gives out a /64 prefix by default but will give out a /56 once you bug them about it for a while ;)
That behavior would be totally normal, if there is another router in between.
jwj last edited by
@bob-dig Yes, which is why I encouraged to connect directly. Which worked. Still going to only get a /64. Many ISPs do that for reasons known only to them. Makes no sense at all...