Skip to contentSkip to conversation

Dead gateway detection

LARTC Julian Anastasov 1 participant 1 message Aug 9, 2002

lore
Share & tools
lore
#0 lore raw

Hello,

Quoted 5 lines · Laurens van Alphen

Q1: In the Nano-HOWTO on your site, it says to include these statements:
"ip route append prohibit default table <tablename> metric 1 proto static"
Why? What does it do? If I use these I can't connect to the Internet, without them I can.

The reason can be that you have other rule/route settings.

The purpose is: traffic using source addresses from failed
links should not try to use another alive link (some ISPs do not allow spoofing from our side). Such prohibit rules avoid using less-specific routes from other tables if the previous route is deleted (metric 0).

Quoted 7 lines

Q2: I have the following multipath route to the Internet:
"default proto static
nexthop via GW1 dev eth1 weight 1
nexthop via GW2 dev eth2 weight 1"
If I unplug eth2 the second route is never marked as 'dead', why? Only if I 'ifconfig eth2 down' the second route is marked dead. I thought the patches would detect this?

Linux detects failed gateways and does not use them but
the nexthops remain alive. Dead are only the routes administratively marked as such. This is the current way.

Quoted 5 lines

Thanks,

--
Laurens van Alphen
Keen on dots

Regards

--
Julian Anastasov <[email protected]>

_______________________________________________
LARTC mailing list / [email protected]
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/