setting up pfSense after years of uysing it
-
guy also suggested i use 2403:580B:FFFF:3E54::/64
but this come up with the wrror that i am not using a valid hexidecimal numer -
@randomaustralian said in setting up pfSense after years of uysing it:
the provider is saying hte prefix is 48 but the gateway says
The specified IPv6 Prefix ID is out of range. (wan) - (0) - (0)
You can select any prefix size you want, up to the max offered. How are they providing the prefix? Typically, DHCPv6-PD is used.
-
How do you have the two interfaces configured?
-
@randomaustralian said in setting up pfSense after years of uysing it:
provider is saying hte prefix is 48
That is like the largest prefix I have seen a isp give out.. Normally they are like /60 or /56 etc.
You can get a /48 from HE.. and not like there is not enough IPs for them to do that - whats the math there is enough space in the currently allocated IPv6 to give like everyone on the planet 4000 some /48s.. And the currently allocated portion of the total IPv6 space is just a small fraction.
up with the wrror that i am not using a valid hexidecimal numer
Are you trying to put that whole IP into the track prefix ID?
That would be like 0, or 1 or say F or even say A3, etc.. depending on which /64 out of the bigger prefix /48 or /56 or /60 it is..
https://docs.netgate.com/pfsense/en/latest/interfaces/configure-ipv6.html#track-interface
-
-
@randomaustralian said in setting up pfSense after years of uysing it:
yes that is were i was trying to put it.
Well then like I said you just put in the ID not the full address..
-
@johnpoz
it has magically started workingthanks everyone for the help
-
@randomaustralian said in setting up pfSense after years of uysing it:
it has magically started working
No magic about it..
-
considering i was banging my head on a brick wall for days trying to get it working and now suddenly its working..........
It was probably because i turned it off to plug it in to my UPS
-
