-
Notifications
You must be signed in to change notification settings - Fork 2
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
Broken policy routing table observed #36
Comments
Rebooting resolved the issue and it is now showing:
This same node seemed to have also changed its own root password after some number of hours even though we had manually changed the password before that time. Is it possible that both of these issues were somehow caused by the script that runs after some number of hours after flashing to remove the default root password? @paidforby |
Maybe has something to do with the way meshrouting is being started? See sudomesh/sudowrt-firmware#135 |
@Juul If this happens again I would look in /var/log/messages for evidence of meshrouting failing to start. That's where those rules get set AFAIK: https://github.com/sudomesh/sudowrt-firmware/blob/master/files/opt/mesh/templates/etc/init.d/meshrouting#L143-L160. |
On a node flashed with latest available built firmware images as of June 28 2018 (sudowrt v0.3.0) I observed the following:
This resulted in no IPs being reachable from the public interfaces (except for those of the node itself) because (due to missing ip policy routing rules) traffic was attempting to use the
main
routing table even when coming from the public interfaces and that traffic was then of course being dropped by the firewall FORWARD rules.The text was updated successfully, but these errors were encountered: