Project

General

Profile

Actions

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 over 6 years ago.

Status:
Resolved
Priority:
High
Assignee:
Category:
Routing
Target version:
Start date:
05/04/2018
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.4.4
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.

Actions #1

Updated by James Snell over 6 years ago

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.

Actions #2

Updated by James Snell over 6 years ago

Two reboots since 10am, routes ok.

Actions #3

Updated by Jim Pingle over 6 years ago

  • Assignee set to Jim Pingle
Actions #4

Updated by Jim Pingle over 6 years ago

  • Status changed from New to Feedback
  • % Done changed from 0 to 100
Actions #5

Updated by Jim Pingle over 6 years ago

  • Status changed from Feedback to Resolved

These errors haven't shown up since this commit.

Actions

Also available in: Atom PDF