ipv6 broken: radvd: can't join ipv6-allrouters on <interface>
-
@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
