Re: forcing boxA to use gateway to get to boxB all on same sub-net...
- From: Jesper <xyborx+usenet@xxxxxxxxx>
- Date: 13 Jul 2006 18:20:15 GMT
On 2006-07-13, en2guy@xxxxxxxxxxxxx wrote:
When I try to traceroute to boxB from boxA, the first time, I can see
it pass via the gateway (machine names removed):
traceroute to (192.168.40.110), 30 hops max, 38 byte packets
1 (192.168.40.7) 0.230 ms 0.204 ms 0.234 ms
2 (192.168.40.110) 0.358 ms 0.225 ms 0.115 ms
However, subsequently, traceroute goes directly to boxB, missing out
the gateway machine.
traceroute to (192.168.40.110), 30 hops max, 38 byte packets
1 (192.168.40.110) 0.236 ms 0.204 ms 0.235 ms
Could you check if an entry for 192.168.40.110 is automatically added in
the routing table? I'm just wondering that maybe the gateway sends back
an icmp redirect message, telling 192.168.40.50 that 192.168.40.110 can
be reached directly. tcpdump might also give some clues.
--
Jesper <xyborx+usenet@xxxxxxxxx>
.Because it's difficult to read.Why is top-posting bad?
- References:
- Prev by Date: Re: List-based login screen?
- Next by Date: Re: Using SSH as a simple VPN: timeouts?
- Previous by thread: forcing boxA to use gateway to get to boxB all on same sub-net...
- Next by thread: Re: forcing boxA to use gateway to get to boxB all on same sub-net...
- Index(es):
Relevant Pages
|
