ipv6 broken: radvd: can't join ipv6-allrouters on <interface>
-
Netgate can't possibly ship 2.5.0 with this bug that essentially disables ipv6 support in pfsense. Still no dev replies or acknowledgment of Bug #9577. Hope people that are paying for netgate products or support ask for this to be fixed.
-
Actually it is working for me, it's only a message log spamming out, they have time to correct it before the official release
-
It's "working" here too with a radvd restart every 6 hours. I do a radvd service restart via Cron instead of a kill, which seemed cleaner but my approach causes IPv6 sessions to be dropped when the prefix is unadvertised briefly.
Looking at the source code, that spam logging should not even be executing on a freebsd platform. So maybe it's a hint of what's broken.
-
After 6 days my IPv6 died as well.
Static assigned IPv6 works just fine, slaac and RA doesn`t. Client does not get IPv6 address at all.LOG:
Aug 6 09:48:50 radvd 35714 can't join ipv6-allrouters on hn0.9
Aug 6 09:48:50 radvd 35714 IPv6 forwarding on interface seems to be disabled, but continuing anyway
Aug 6 09:48:10 radvd 35714 can't join ipv6-allrouters on hn0.7
Aug 6 09:48:10 radvd 35714 IPv6 forwarding on interface seems to be disabled, but continuing anyway
Aug 6 09:47:15 radvd 35714 can't join ipv6-allrouters on hn0.10
Aug 6 09:47:15 radvd 35714 IPv6 forwarding on interface seems to be disabled, but continuing anyway
Aug 6 09:44:37 radvd 35714 can't join ipv6-allrouters on hn0.10
Aug 6 09:44:37 radvd 35714 IPv6 forwarding on interface seems to be disabled, but continuing anyway
Aug 6 09:43:06 radvd 35714 can't join ipv6-allrouters on hn0.7
Aug 6 09:43:06 radvd 35714 IPv6 forwarding on interface seems to be disabled, but continuing anyway
Aug 6 09:42:05 radvd 35714 can't join ipv6-allrouters on hn0.8
Aug 6 09:42:05 radvd 35714 IPv6 forwarding on interface seems to be disabled, but continuing anyway
Aug 6 09:41:55 radvd 35714 can't join ipv6-allrouters on hn0.9
Aug 6 09:41:55 radvd 35714 IPv6 forwarding on interface seems to be disabled, but continuing anyway
Aug 6 09:41:46 radvd 35714 can't join ipv6-allrouters on hn0.10Ah well....
-
me too . how fix it?
-
for the moment afaik only this -> https://forum.netgate.com/post/851662
-
@kiokoman said in ipv6 broken: radvd: can't join ipv6-allrouters on <interface>:
i put here a workaround that seems to work for me
[2.5.0-DEVELOPMENT][root@pfSense.localdomain]/root: crontab -l @hourly killall radvd && sleep 5 && /usr/local/sbin/radvd -p /var/run/radvd.pid -C /var/etc/radvd.conf -m syslogWhat is this principle?
-
restart Router Advertisement Daemon every hour, to me the problem arise every some hours so restarting it mitigate the problem
-
I tried to restart the service yesterday and did not solve the problem. Restart the system to work.I have problems after about 20 hours of running.
-
well i dont know how to solve the problem, you have 2 options, wait for the staff to solve it or go back to 2.4.4
-
@yon-0 a restart using the GUI doesn't work, you need to stop the service, wait 5 seconds and start the service.
Or script it using cron, as suggested.
-
@Irata said in ipv6 broken: radvd: can't join ipv6-allrouters on <interface>:
@yon-0 a restart using the GUI doesn't work, you need to stop the service, wait 5 seconds and start the service.
Or script it using cron, as suggested.
ye, this is work. but we still need waiting for admin fix it.
-
Just tired enabling RA again and still having issues with log spam and dropouts.
-
My ISP disabled Ipv6 last month, so I am using HE tunnel now.
Same problem as TS mentioned — SPAM and drops after some hours. -
Interesting, I'm using an HE tunnel too
-
@Irata
I am not sure that my ISP native Ipv6 have been working, so I don't think it's HE related. I am parsing tons of syslog messages now, let me see, if I find something, I'll let you know. -
I have native with same issues...
-
my isp has ipv6, no tunnel. i don't think that matters. at this point i think everyone is affected.
-
nope, nothing to do with tunnel, it's radvd that is broken
-
According to my logs there was no any problem with ISP Ipv6, but it was special case — configured to track PPPoE interface and used stateless DHCP router mode, DHCPv6 server not enabled.
