Skip to contentSkip to conversation

Two routing cache entries with different interface

LARTC Tushar Thakker 2 participants 2 messages Jan 10, 2004

lore
Share & tools
lore
#0 lore raw

hi all,
i am setting up a load balancing netwrok with failover,
i have applied julian patch,
but whenever i try to traceroute from any client node, it gives me two entries for that destination, but i get different interface for that entries, so it doesn't forward my requests,
i have done masquerading for client nodes,

the ip rule/route are as follows,

ip rule add prio 222 table 222
ip route add default table 222 proto static \
nexthop via $GWE1 dev $IFE1 weight 1\
nexthop via $GWE2 dev $IFE2 weight 1

Now after traceroute failure, if i see the routing cache for that ip, it shows following,

205.158.62.141 via 203.88.135.213 dev eth1 src 203.88.135.212

    cache  mtu 1500 advmss 1460

205.158.62.141 from 192.168.1.51 via 203.88.135.205 dev eth2 src 192.168.1.242
cache <src-direct> mtu 1500 advmss 1460 iif eth0

please see eth1 and eth2 in both entries,
now it does not forward this request,
what can be the reason behind this and please can anyone suggest me the solution, thanx in advance,
Regards,

----------------------------------------------------------------
Tushar Thakker
Elitecore Technologies Ltd.
----------------------------------------------------------------
Life gives all that one deserves, but not all that one desires...
----------------------------------------------------------------

#1 lore raw

Hello,

Quoted 7 lines · Tushar Thakker

hi all,
i am setting up a load balancing netwrok with failover,
i have applied julian patch,
but whenever i try to traceroute from any client node, it gives me two entries for that destination, but i get different interface for that entries, so it doesn't forward my requests,
i have done masquerading for client nodes,

Quoted 8 lines

the ip rule/route are as follows,

ip rule add prio 222 table 222
ip route add default table 222 proto static \
nexthop via $GWE1 dev $IFE1 weight 1\
nexthop via $GWE2 dev $IFE2 weight 1

Now after traceroute failure, if i see the routing cache for that ip, it shows following,

output route, probably created from -j MASQUERADE?:

Quoted 2 lines

205.158.62.141 via 203.88.135.213 dev eth1 src 203.88.135.212

    cache  mtu 1500 advmss 1460

input route:

Quoted 4 lines

205.158.62.141 from 192.168.1.51 via 203.88.135.205 dev eth2 src 192.168.1.242
cache <src-direct> mtu 1500 advmss 1460 iif eth0

please see eth1 and eth2 in both entries,

Nothing strange so far, may be they are created from different
connections. In fact, there should be more cache entries.

Quoted 1 line

now it does not forward this request,

Can you provide more information, in private mail if you
prefer so, including:

- tcpdump output(s) for all interfaces during the traceroute
- topology: are eth1 and eth2 connected to same hub?
- ip rules and routes

I hope you really have the "routes" patch applied and
running.

Quoted 7 lines

what can be the reason behind this and please can anyone suggest me the solution, thanx in advance,
Regards,

----------------------------------------------------------------
Tushar Thakker
Elitecore Technologies Ltd.

Regards

--
Julian Anastasov <[email protected]>

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