-
Notifications
You must be signed in to change notification settings - Fork 94
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Babeld "Interface lan4_17 has no link-local address" [was: Assorted error messages] #1003
Comments
This is the logread on a YouHua WR1200JS running LibreMesh packages installed on OpenWrt 22.03: and this is another router of the same model with LibreMesh packages installed on OpenWrt 19.07: |
According to this comment, we have to consider that all the error messages coming from Busybox components, including cron, could be both errors or info: |
But the Babeld errors seems real. The most abundant flooding of messages look like this:
|
For getting rid of these ones, we could manually assign link-local addresses like we add IPv4 addresses here: lime-packages/packages/lime-proto-babeld/files/usr/lib/lua/lime/proto/babeld.lua Lines 117 to 120 in 7664098
@G10h4ck @spiccinini do you know if there is a better way? |
Just switch on an isolated router running the current code on OpenWrt 22.03 and observed some error messages in logread:
The text was updated successfully, but these errors were encountered: