Skip to contentSkip to conversation

failover does not work for static ip rules

LARTC Tushar Thakker 2 participants 2 messages Jan 19, 2004 – Jan 21, 2004

lore
Share & tools
lore
#0 lore raw

hello all,
previously i had some problems setting up a load balancing network, but now after re-applying the julian patch, it works good, but my doubt is that if we have statically provided and IP Rule for some network to use some particular gateway like follows,

ip rule add prio 203 from 192.168.1.0/24 table 203
ip route add default via 203.88.135.213 dev eth1 src 203.88.135.212 proto static table 203
ip route append prohibit default table 203 metric 1 proto static

but now, if the gateway goes down, then will it refer to the next priority table , i.e. 221?
the next priority table is as follows,

ip rule add prio 221 table 221

ip route add default table 221 proto static \

            nexthop via 203.88.135.213  dev eth1 weight 1\
            nexthop via 203.88.135.193  dev eth2 weight 1

so, if the static route fails, will that refer the next priotiry table? failover works if i have not specified the static ip rule, but it does not work in case of this rule 203,
can anyone explain why this happens?
thanks and regards ----------------------------------------------------------Tushar Thakker Elitecore Technologies Ltd. ----------------------------------------------------------Life gives all that one deserves, but not all that one desires...
----------------------------------------------------------

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

#1 lore raw
Quoted 19 lines

hello all,
previously i had some problems setting up a load balancing network, but now after re-applying the julian patch, it works good, but my doubt is that if we have statically provided and IP Rule for some network to use some particular gateway like follows,

ip rule add prio 203 from 192.168.1.0/24 table 203
ip route add default via 203.88.135.213 dev eth1 src 203.88.135.212 proto static table 203
ip route append prohibit default table 203 metric 1 proto static

but now, if the gateway goes down, then will it refer to the next priority
table , i.e. 221?
the next priority table is as follows,

ip rule add prio 221 table 221

ip route add default table 221 proto static \

Quoted 8 lines
            nexthop via 203.88.135.213  dev eth1 weight 1\
            nexthop via 203.88.135.193  dev eth2 weight 1

so, if the static route fails, will that refer the next priotiry table? failover works if i have not specified the static ip rule, but it does not work in case of this rule 203,
can anyone explain why this happens?
thanks and regards

Yes, i think that all is working fine,
take a look, you have only rule from 192.168.1.0/24 to table 203 in normal operational status.

So propably, when you are tracerouting , etc, system bind uses different source ip, so you don't see the same thing as being done by kernel for packet with sources 192.168.1.0/24.

Add the same rule as "ip rule add prio 221 table 221" to put everything to table 203, then everything to table 221.

Try it, and hope to hear you soon.

Arkadiusz Binder

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