Rogers pfSense configuration
-
What you can select on the WAN page has nothing to do with what the ISP will or will not do.
You can set it to anything from /48 on down.
If you want to change it you probably need to copy out the DUID file to a safe place like /root so you can put it back if you need to, delete it, then change the prefix hint and save. Otherwise the ISP might ignore the prefix hint and give you your old delegation based on the DUID.
The DUID file is: /var/db/dhcp6c_duid
You might also need to clear it out of System > Advanced, Networking if you have saved it there (or change it there if you know what you are doing).
-
What you can select on the WAN page has nothing to do with what the ISP will or will not do.
You can set it to anything from /48 on down.
I don't recall ever seeing /48 before, though I could be mistaken. I'll give it a try later and see what happens.
-
What you can select on the WAN page has nothing to do with what the ISP will or will not do.
You can set it to anything from /48 on down.
My mistake. It appears you're right. I guess I'll just have to make do with a /56. ;)
-
Can anyone validate these settings still work? Trying to get IPV6 running on an XB6 Gateway in bridge mode running on PFSense 2.4 and no joy on getting the WAN interface to draw an IP. I've tried the settings above and various other combinations with no success.
-
@mjnr said in Rogers pfSense configuration:
Can anyone validate these settings still work? Trying to get IPV6 running on an XB6 Gateway in bridge mode running on PFSense 2.4 and no joy on getting the WAN interface to draw an IP. I've tried the settings above and various other combinations with no success.
Those settings are still good. Try connecting a computer directly to the modem, to see if that works. You should get an IPv6 address.
-
Use IPv4 connectivity as parent interface: yes
This can be set to no now. You no longer have to request over ipv4
-
@james2432 said in Rogers pfSense configuration:
Use IPv4 connectivity as parent interface: yes
This can be set to no now. You no longer have to request over ipv4
I thought that meant use the same interface as IPv4, not use IPv4 to get IPv6. A different connection can also be used for IPv6. For example, many use a tunnel to get IPv6, as I did for almost 6 years.
-
Use IPv4 Connectivity as Parent Interface:
When set, the IPv6 DHCP request is sent using IPv4 on this interface, rather than using native IPv6. This is only required in special cases when the ISP requires this type of configuration. -
I was just reviewing the earlier posts. I don't ever recall using that setting and I've had IPv6 via Rogers for 3 years.
-
@JKnott said in Rogers pfSense configuration:
I was just reviewing the earlier posts. I don't ever recall using that setting and I've had IPv6 via Rogers for 3 years.
Yeah Rogers can dhcp request over native ipv6 now, probably at the time of writing the guide the network engineer was correct as ipv6 wasnt wildly adopted
-
@mjnr said in Rogers pfSense configuration:
Can anyone validate these settings still work? Trying to get IPV6 running on an XB6 Gateway in bridge mode running on PFSense 2.4 and no joy on getting the WAN interface to draw an IP. I've tried the settings above and various other combinations with no success.
Did you figure this out? I'm having trouble with an XB7 getting IPv6.
With my previous Hitron modem, I dont' recall having this much trouble getting IPv6 configured.
-
I'm still using those settings with the Ignite modem, whatever that model is.
Maybe if you post the settings you're using and what's happening. -
Old thread I get but I just set up a Netgate 6100 and have Rogers XB8 modem bridged to the 6100. I just cannot get IPV6 to work. Is anyone able to do a step by step for setting this up?
I have WAN interface, LAN interface, 3 VLANs off the LAN interface and a separate network on another interface.
Would really appreciate a steer here if possible. Thanks in advance.
-
Did you follow the instructions above? Does pfSense get an IPv6 address?
Post a screen capture of your WAN & LAN settings. Keep things simple and get one LAN going first and once that's up, configure the rest.You could also do a packet capture of the full DHCPv6 sequence and paste the capture file here.
-
@jknott - yes, I did follow all the settings here and then also from other threads. I will post screen captures later on when I get home. but was hoping there was a simple fix.
On the Dashboard Interfaces - both WAN and LAN show an IPV6 address. On the Dashboard Gateways - WAN_DHCP has my ISPs IPV4 address and shows ONLINE (Green), WAN_DHCP6 has an IPV6 address and shows Offline, packetloss (Red). Any IPB6 test fails and says it cannot get an address.
-
@jasonreg said in Rogers pfSense configuration:
but was hoping there was a simple fix
There very well could be, but until I know what you've done, I can't say.
-
@jknott - OK now I am confused. So I removed the configuration for the LAN interface and I added the same configuration to one of my VLANs (JasonOffice) and everything works. So why can I not set up the LAN?
WAN is set up per above recommended configuration as is the JasonOffice Network. However, when I try to add this same configuration to the LAN or one of the other VLANs, I cannot track the WAN - says it is already assigned (which I guess it is). Have tried SLAAC and still get nothing.
On the Dashboard Interfaces, I see an IPV6 address under WAN and one under JasonOffice now. Gateways show WAN_DHCP Online and WAN_DHCP6 Offline, Packetloss though I do have an address.
-
Here are some screen captures.
WAN
VLAN
-
@jasonreg Probably this issue: [https://redmine.pfsense.org/issues/14072](link url) . It gives these symptoms.
-
@mhillmann Do you have unique prefix IDs for each interface?
