SG-3100 Router Advertisement Daemon
-
SG-3100 is fantastic so far except that I cannot get IPV6 to my clients. The radvd Router Advertisement Daemon shows a red X. My previous pfSense device was built using an old desktop with an Intel dual NIC. I made a full backup of the config and used it to restore on the SG-3100. (modified the interface names) I get an IPV6 assignment on the WAN and LAN. I can use the GUI ping command to get a reply from ipv6.google.com.
I reconnected my previous system to compare, everything still works and I see no difference in the configs. I grabbed a copy of the restore from the portal, restored the SG-3100 and built from scratch to see if the issue was my config, no difference. Still no IPV6 to my clients. I'm not sure what else to try.
I am connected to a UVERSE gateway.
WAN:
IPV4-DHCP
IPV6-DHCP6
Request only a prefix-checked
Delegation size-64
Send prefix hint-checked
block bogon networks-uncheckedLAN:
IPV4-Static
IPV6-Track Interface
WAN 0DHCPV6 enabled on the LAN. RA is set to Assisted. IPV6 on in System. Cant think of anything else. This is the same setup that has worked for the last year on my old system.
Any ideas? -
This is probably why:
https://redmine.pfsense.org/issues/8022
-
This is probably why:
https://redmine.pfsense.org/issues/8022
Yes, that is the issue. If I read that correctly, 2.4.2 is going to address the issue?
-
The target version for a fix is currently 2.4.2.
-
Interesting, the screen shared on Twitter with 2.4.0 beta installed shows radvd working fine. The device comes with 2.4.1 which had some changes made for the switch drivers. Just sharing.
https://twitter.com/JeGroh/status/883043442749710336
-
Hi all,
Just received my 3100. (2.4.1-RELEASE) I need ravd to work reliably for it to
be deployed. I have not yet tested the box with ravd, but is this bug acknowledged
(and reproduceable ? ) ?Is there an estimate for 2.4.2 where a fix could | should be implemented ?
Thanks ! Rudi
-
Hi all,
Just received my 3100. (2.4.1-RELEASE) I need ravd to work reliably for it to
be deployed. I have not yet tested the box with ravd, but is this bug acknowledged
(and reproduceable ? ) ?Is there an estimate for 2.4.2 where a fix could | should be implemented ?
Thanks ! Rudi
See if the report matches your issue. https://redmine.pfsense.org/issues/8022