ipv6 broken: radvd: can't join ipv6-allrouters on <interface>
-
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.
-
@bimmerdriver
As @rschell said https://github.com/pfsense/FreeBSD-ports/pull/773 still need to be applied, but it's not accepted and applied yet. -
I updated Redmine issue #9577 with a revised RADVD install package for those continuing to experience problems. I left instructions there how to install.
I have had installs run for more than 35 days with the revised RADVD only to stop it to install new 2.5 updates..
-
@w0w I tried to apply the patch to 2.5.0-development using this commit ID: https://github.com/pfsense/FreeBSD-ports/pull/773/commits/387a6ef1e4fd514596502e162878f64f0002170c, but it could not be applied. Am I doing something wrong?
-
@bimmerdriver Not sure, I rebase my git with every update and it works here.
Are you applying it to the ports Git? What errors are you getting? -
@rschell I didn't do anything with git. I tried to apply the patch directly to the development snapshot and it failed. I guess that's the problem.
-
@bimmerdriver it’s applying changes to the C code of RADVD, so it needs to be compiled. I have uploaded a compiled version to redmine. You can install that package and it will survive most updates except full port replacements.
-
@rschell thank you - your patch fixed up my issues. Hopefully this gets pulled into main soon.
-
@rschell Thank you, sir. It's installed and I will keep an eye on it.
-
This 2.4.5-p1 version also has this problem