ipv6 broken: radvd: can't join ipv6-allrouters on <interface>
-
i'm start testing right now, we need at least 24 h to tell if it's ok. no prob so far :)
Feb 13 18:58:33 radvd 38033 adding ipv6-allrouters on ix0.100, sock: 4, iface->props.if_index:12 Feb 13 18:58:33 radvd 37849 version 2.18 started
-
Yes, I can confirm that IPv6 works good. About 36 hours and no problem.
-
after all this days it's still working good
great job @rschell -
@rschell idk if it's related to this update but lately i had trouble with my ipv6 tunnel, i still need to investigate but the problem is that my tunnel does not work after a reboot
the gif is up but gateway monitor say packet loss 100%
i had to reboot 2 / 3 times in a row to make it work again -
@kiokoman Unlikely related to the proposed patch. I'm using an 6RD stf interface and have noticed issues with loss of the WAN connection. Might be a timing issue with the gif interface, not certain.
-
some kind of race condition at boot maybe, also if i wait some hours the tunnel start to work alone. but it's faster if i reboot until it start working. idk the problem started last week just after i moved pfsense from bare metal to esxi, probably something to do with that
-
@kiokoman I've noticed that bare metal vs Hyper V behave differently in subtle ways.
-
ok i think that i found what's going on, if i disable openvpn before restarting pfsense the tunnel work.
so i have to disable openvpn, restart pfsense, and when it's up i can start the openvpn otherwise i have trouble -
Looks like there are no error messages on the latest STABLE snapshots.
-
do we no longer have to apply that patch manually?
I have not yet had time to update and verify -
@kiokoman
Wait for 24h and I tell you :) -
all clear for now
May 2 12:34:32 radvd 73936 resuming normal operation May 2 12:34:32 radvd 73936 attempting to reread config file May 2 12:02:28 radvd 73936 adding ipv6-allrouters on vmx1.100, sock: 4, iface->props.if_index:8 May 2 12:02:28 radvd 73720 version 2.18 started
-
ping -t ipv6.google.com Ping request could not find host ipv6.google.com. Please check the name and try again.
and
May 3 16:47:23 radvd 27820 can't join ipv6-allrouters on ix1 May 3 16:47:15 radvd 27820 can't join ipv6-allrouters on ix1 May 3 16:47:00 radvd 27820 can't join ipv6-allrouters on ix1 May 3 16:46:54 radvd 27820 can't join ipv6-allrouters on ix1 May 3 16:46:37 radvd 27820 can't join ipv6-allrouters on ix1 May 3 16:46:26 radvd 27820 can't join ipv6-allrouters on ix1 May 3 16:46:14 radvd 27820 can't join ipv6-allrouters on ix1 May 3 16:45:58 radvd 27820 can't join ipv6-allrouters on ix1 May 3 16:45:42 radvd 27820 can't join ipv6-allrouters on ix1
So, not yet.
Waiting for https://github.com/pfsense/FreeBSD-ports/pull/773 to be merged. I have no problems with patched binary.
-
@kiokoman It appears you are still using the patched binary. I had my main pfSense running for 35+ days with the patch, so I am reasonably certain that it is a good work around for the issues in stable-12.
-
@rschell
Yep, it can be true, I have found it right after installing STABLE. I looked for a error messages, did not found it and didpkg install -f -y radvd
It downgraded my version back to that one which is in the pfSense repository and sorry guys but it failed the same way as before. I just forgot that another one error message
IPv6 forwarding on interface seems to be disabled, but continuing anyway
got its own fix and I thought that the current version was updated so sorry guys for false hope!
-
ah ok, then the upgrade didn't remove the patched radvd, well no problem it works, I'm happy
-
I'm running the latest development release:
2.5.0-DEVELOPMENT (amd64)
built on Wed Jun 03 13:09:01 EDT 2020
FreeBSD 12.1-STABLEThis morning, I noticed the routing log filled with this message:
Jun 7 10:01:16 radvd 76671 can't join ipv6-allrouters on hn1
IPv6 was not working. I rebooted and the system is now working.
-
@bimmerdriver Still waiting for workaround ports PR #773 to be accepted and applied.
-
I also notice many messages like "Jun 11 11:02:57 pfSense radvd[84278]: can't join ipv6-allrouters on ix1.116"
However I would like to add:
- after installing the 3 june package a few days ago ..... they were gone
- today I installed the 10 june package and they where back
- and I did have an IPV6 routing problem ...
- than I did a reboot and ... the messages where gone
- and my IPV6 routing issue seems to be gone
Note that this is not at all an real test, just a quick obeservation.
Louis
-
The routing log was full of the messages this morning, so the problem is still present.