Closed tvand closed 3 years ago
FWIW v2.19 has been released.
If you haven't already, try increasing the log level...
" -d, --debug=NUM Set the debug level. Values can be 1, 2, 3, 4 or 5.\n"
...and see what else the log tells you. I used to compile radvd and test it on OSX, but haven't been doing so for a long while. It uses some different sources vs linux. The OSX stuff is most likely using the bsd44 source rather than the linux ones (some of the files are conditionally compiled based on the platform). If you can debug radvd on OSX and get it working, I'd be happy to merge the changes.
Thanks in advance, Reuben
On Sun, Dec 6, 2020 at 1:27 AM Geert Stappers notifications@github.com wrote:
FWIW v2.19 has been released.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/reubenhwk/radvd/issues/122#issuecomment-739477391, or unsubscribe https://github.com/notifications/unsubscribe-auth/AABRG644JNQ53TQDIGD6REDSTNFBZANCNFSM4NQQ3WWA .
I would like to have the privilege of power to close issues like this. Yes, I saying that I, teammember of radvd project, feel unable to help.
(Thanks for granting, now using that privilege to reduce the number of open issues.)
@tvand it is the lack of any follow-up from you that made me close this issue. Do know that the
If you can debug radvd on OSX and get it working, I'd be happy to merge the changes.
is since closing of #135
If you can debug radvd on OSX and get it working, we are happy to merge the changes.
I compiled radvd 2.18 from source on macOS High Sierra. The host to run this has two network interfaces, en0 and en3. I'd like to announce a route on en3.
The log file shows:
If I try to
ping6 ff02::1
, I get the same behavior - no route to host. Pingingff02::1%en3
works, however. Could it be that the zone index is missing or wrong? How would I debug this?