ipv6 broken: radvd: can't join ipv6-allrouters on <interface>
-
A fresh install causes the same error for me, once stateless IPv6 is setup. I can't find a stable working system whatever I do, other than back to 2.4.
Because I'm using an ESXi testbed, it's easy to spin up new installs.
I do think there is something fundamental here, given the reports from wide ranging setups.
-
the error is generated from device-bsd44.c, a patch it's inside the port of radvd for freebsd
tracking back there was similar problem. related Bug #2878 https://redmine.pfsense.org/issues/2878 from 2013/* XXX: See pfSense ticket #2878 */ + setsockopt(sock, IPPROTO_IPV6, IPV6_LEAVE_GROUP, &mreq, sizeof(mreq)); + + if (setsockopt(sock, IPPROTO_IPV6, IPV6_JOIN_GROUP, + &mreq, sizeof(mreq)) < 0) { + flog(LOG_ERR, "can't join ipv6-allrouters on %s", iface->props.name); + return (-1); + }
maybe it's time for a new ticket
https://redmine.pfsense.org/issues/9577 -
idk if we open a ticket devs might just ignore it, first we should get devs on the forums to tell us if we need to open a bug.
-
@strangegopher - they're aware of it, one of the devs referred to the ticket in a thread with an issue I'm having.
-
Now it hit me too:
Jun 29 07:17:29 radvd 62926 can't join ipv6-allrouters on hn0.10
Jun 29 07:15:22 radvd 62926 can't join ipv6-allrouters on hn0.10
Jun 29 07:15:00 radvd 62926 can't join ipv6-allrouters on hn0.9
Jun 29 07:13:07 radvd 62926 can't join ipv6-allrouters on hn0.7
Jun 29 07:12:47 radvd 62926 can't join ipv6-allrouters on hn0.10
Jun 29 07:11:25 radvd 62926 can't join ipv6-allrouters on hn0.8
Jun 29 07:11:23 radvd 62926 can't join ipv6-allrouters on hn0.9
Jun 29 07:10:22 radvd 62926 can't join ipv6-allrouters on hn0.10
Jun 29 07:08:10 radvd 62926 can't join ipv6-allrouters on hn0.10 -
welcome to the party !
-
@maverick_slo made any changes recently, or added any new IPv6 devices?
-
No changes no new devices.
I just came home from vacation... -
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 syslog
-
On the recent snapshot (2.5.0.a.20190728.0536) I now also get the following repeated in the routing system log:
Jul 30 16:50:49 radvd 72128 IPv6 forwarding on interface seems to be disabled, but continuing anyway Jul 30 16:50:42 radvd 72128 IPv6 forwarding on interface seems to be disabled, but continuing anyway Jul 30 16:50:41 radvd 72128 IPv6 forwarding on interface seems to be disabled, but continuing anyway Jul 30 16:50:34 radvd 72128 IPv6 forwarding on interface seems to be disabled, but continuing anyway Jul 30 16:50:29 radvd 72128 IPv6 forwarding on interface seems to be disabled, but continuing anyway Jul 30 16:50:24 radvd 72128 IPv6 forwarding on interface seems to be disabled, but continuing anyway Jul 30 16:50:21 radvd 72128 IPv6 forwarding on interface seems to be disabled, but continuing anyway
-
Yup same here, 2.5.0 is getting worse by every snapshot
Ah well probably Ill go back to 2.4.4... -
Looks like it is failing within this code in device-linux.c in radvd:
int check_ip6_forwarding(void) { int value; FILE *fp = NULL; fp = fopen(PROC_SYS_IP6_FORWARDING, "r"); . . .
Which I think is checking for /proc/sys./... but there is no /proc/sys/... directory. There is also alternative code called in device-bsd44.c. So I'm wondering if radvd in 2.5.0 is being built for the wrong platform, or it's expecting a file that is now removed. But I admit this is a wild guess.
-
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 syslog
What 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.
-
@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 syslog
Sorry for dumb question but where does it stored? I have executed this command, but I don't see anything similar in cron package. I can not also find any modified file on a system.
-
contrab -l (list)
crontab -e (edit)
from the terminal
you need to edit crontab withcrontab -e
then copy/past what i have in my crontab
@hourly killall radvd && sleep 5 && /usr/local/sbin/radvd -p /var/run/radvd.pid -C /var/etc/radvd.conf -m syslog
or you can install the cron pkg available in the gui and add
killall radvd && sleep 5 && /usr/local/sbin/radvd -p /var/run/radvd.pid -C /var/etc/radvd.conf -m syslog
as command line
what does it do: kill radvd & wait 5 seconds & restart radvd -
@kiokoman said in ipv6 broken: radvd: can't join ipv6-allrouters on <interface>:
contrab -l (list)
crontab -e (edit)
from the terminal
you need to edit crontab withcrontab -e
then copy/past what i have in my crontab
@hourly killall radvd && sleep 5 && /usr/local/sbin/radvd -p /var/run/radvd.pid -C /var/etc/radvd.conf -m syslog
or you can install the cron pkg available in the gui and add
killall radvd && sleep 5 && /usr/local/sbin/radvd -p /var/run/radvd.pid -C /var/etc/radvd.conf -m syslog
as command line
what does it do: kill radvd & wait 5 seconds & restart radvdThank you for clarification. Okay, in that case, then, my bad. I just was too lazy to run it from terminal and used GUI command prompt, stupid me... It does not work that way.
Since I have cron GUI package installed, I'll try to make it over GUI.
-
Does anybody else with HE tunnel have those messages in the log?
Aug 30 05:40:28 php 378 rc.bootup: Error starting gateway monitor for HENETV6_TUNNELV6 Aug 30 05:40:28 php 378 rc.bootup: The command '/usr/local/bin/dpinger -S -r 0 -i HENETV6_TUNNELV6 -B 2001:470:xx:191::2 -p /var/run/dpinger_HENETV6_TUNNELV6~2001:470:xx:191::2~2001:470:xx:191::1.pid -u /var/run/dpinger_HENETV6_TUNNELV6~2001:470:xx:191::2~2001:470:xx:191::1.sock -C "/etc/rc.gateway_alarm" -d 0 -s 500 -l 2000 -t 60000 -A 1000 -D 500 -L 20 2001:470:xx:191::1 >/dev/null' returned exit code '1', the output was '' Aug 30 05:40:28 php-fpm 343 /rc.newwanip: Error starting gateway monitor for HENETV6_TUNNELV6 Aug 30 05:40:28 php-fpm 343 /rc.newwanip: The command '/usr/local/bin/dpinger -S -r 0 -i HENETV6_TUNNELV6 -B 2001:470:xx:191::2 -p /var/run/dpinger_HENETV6_TUNNELV6~2001:470:xx:191::2~2001:470:xx:191::1.pid -u /var/run/dpinger_HENETV6_TUNNELV6~2001:470:xx:191::2~2001:470:xx:191::1.sock -C "/etc/rc.gateway_alarm" -d 0 -s 500 -l 2000 -t 60000 -A 1000 -D 500 -L 20 2001:470:xx:191::1 >/dev/null' returned exit code '1', the output was ''
I don't see any side effect, looks like gateway monitor works with no problem at least in GUI it shows correct data.
-
nope, never
-
anyway it seems like we are not alone with this
https://github.com/reubenhwk/radvd/issues/108
https://github.com/reubenhwk/radvd/issues/99 -
@kiokoman
Have seen this on the previous week, but it does not look promising. No answers from developer, no code changes, nothing. -
Wait a minute....
We all rely on 1 person alone?