Bug #8497
closed
route errors ("route has not been found") on current 2.4.4 snapshots
Added by Jim Pingle over 6 years ago.
Updated about 6 years ago.
Affected Architecture:
All
Description
During boot, the console logs numerous identical errors:
route: route has not been found
They happen, at a minimum, when configuring:
It looks like most of these places call route_add_or_change(), openvpn might be from openvpn_clear_route(). The routes appear correct, but the errors were not output to the console before.
FYI - I do have routing issues along with this error following a reboot (initial reboot from install was ok).
Routes were present to local sources, the default gateway, and ISP DHCP supplied nameservers - but not the rest of the internet.
In the UI (System -> Routing) the IPv6 route was missing (though IPv4 wasn't routing either but was present) resetting that seemed to solve the problem so far.
I'm planning on a reboot around 10am BST and will update if the problem recurs.
Two reboots since 10am, routes ok.
- Assignee set to Jim Pingle
- Status changed from New to Feedback
- % Done changed from 0 to 100
- Status changed from Feedback to Resolved
These errors haven't shown up since this commit.
Also available in: Atom
PDF