ipv6 broken: radvd: can't join ipv6-allrouters on <interface>

w0w

@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 with
crontab -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

Thank 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.

w0w

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.

kiokoman

nope, never

kiokoman

anyway it seems like we are not alone with this
https://github.com/reubenhwk/radvd/issues/108
https://github.com/reubenhwk/radvd/issues/99

w0w

@kiokoman
Have seen this on the previous week, but it does not look promising. No answers from developer, no code changes, nothing.

maverick_slo

Wait a minute....
We all rely on 1 person alone?

kiokoman

@maverick_slo what do you mean?

w0w

@maverick_slo
Generally not quite like that
https://github.com/reubenhwk/radvd/graphs/contributors

maverick_slo

Not quite that but still bad.
Really bad.

w0w

@maverick_slo
May be, but may be not, since we are not sure that it is not some configuration issue or not radvd issue at all.

I am testing now latest snapshot with radvd workaround disabled, may be we have some improvements, also I've enabled this patch. 24H already tested, no problem, IPv6 works, previous ended ~6hours with IPv6 fail.

w0w

Failed again. Same can't join ipv6-allrouters on ix1

kiokoman

yeah, you were too optimistic

w0w

What mode do everyone use as router mode with HE?
Should it be "Assisted" for use with DHCPv6?

Having squashed a regression to 6RD a few days ago (See #9649). At least for the first day, I thought my IPv6 problems were solved. No such luck, looks like I have joined this party now.

I first eliminated the log spamming "IPv6 forwarding" message. In the pfSense version "check_ipv6_iface_forwarding" is stubbed out, forcing the log spam. I removed the call and log message in interface.c (could have easily been changed to a dlog call instead on retrospect).

I begin to receive the "can't join ipv6-routers" message after about 24 hours. Hoping to capture the cause, I restarted radvd with debug level 4. When the "can't join" message begins to appear, a debug message that my interface, em0 in my case, "em0 is ready" stops. That suggests to me that radvd is failing in the call to "setup_allrouters_membership" code patch of device-bsd44.c in the calls to setsockopt. Not sure why this is occurring after 24 hours yet. will have to modify the patch code to get more debugging information.

kiokoman

welcome to the party ! i was unable to say hello earlier due to force majeure ...

w0w

@rschell
I see only one user-defined setting that is exactly 24H, it's
AdvValidLifetime 86400;
I don't think it's related, but...

yon 0

this still not fixed.

w0w

@yon-0
To be fixed, there must be someone who will fix. I see only @rschell going deeper so far.

yon 0

@w0w I don't understand this technology, so I can only feedback the problem.

kiokoman

@w0w
not exactly as you can see here https://forum.netgate.com/post/847189
the test that rschell is doing as already been made by me at that time, there was nothing usefull to share, i found out the same.. you can prevent the log to appear but that would not solve the problem.