OpenWrt/LEDE Project

  • Status Closed
  • Percent Complete
  • Task Type Feature Request
  • Category Base system
  • Assigned To
    Hans Dedecker
  • Operating System All
  • Severity Low
  • Priority Very Low
  • Reported Version Trunk
  • Due in Version Undecided
  • Due Date Undecided
  • Private
Attached to Project: OpenWrt/LEDE Project
Opened by Dave Täht - 12.09.2016
Last edited by Hans Dedecker - 25.01.2017

FS#170 - Adding routes with a proto field doesn't work

I was hoping to find a clean way of adding covering routes to elsewhere, and to minimize the amount of routing information propagated outside my core network.

config ‘route’

      option interface loopback              
      option target
      option type unreachable
      option proto 44  

inserts the route as “static”, rather than the proto I requested.

The equivalent command line would have been

ip route add unreachable proto 44

lacking proto support here makes for easy way to insert routes into another routing protocol a bit harder than it needs to be. In babel’s /etc/babeld.conf I’d stuck this:

redistribute proto 44

So I could add or subtract routes from that without having to restart the daemon. There are a couple other places where additionally defining the routing proto is useful (vpn tunnels), and one where it should probably be used (dhcp), also

(hnetd uses some similar tricks more directly, using proto 43, I’m talking about using it more directly in /etc/config/network here)

Closed by  Hans Dedecker
25.01.2017 08:59
Reason for closing:  Fixed
Juliusz Chroboczek commented on 08.11.2016 14:42
hnetd uses some similar tricks more directly, using proto 43

Hnet'd doesn't, it's shncpd that does.

and one where it should probably be used (dhcp)

Please don't do that, dhcp must not install routes with a non-boot proto by default. (Dhcp routes must not be redistributed into a routing protocol without explicit operator intervention, or the universe will collapse.)


Available keyboard shortcuts


Task Details

Task Editing