Skip to content
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

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

Closed
openwrt-bot opened this issue Sep 12, 2016 · 1 comment
Closed

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

openwrt-bot opened this issue Sep 12, 2016 · 1 comment
Labels

Comments

@openwrt-bot
Copy link

openwrt-bot commented Sep 12, 2016

dtaht:

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 172.22.140.0/22
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 172.22.140.0/22 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)

@openwrt-bot
Copy link
Author

openwrt-bot commented Nov 8, 2016

jch:

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.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant