Weird Network Behavior

[KoReE <koree@ameth.org>]

I'm sure I'm missing something here, but here it goes.  I've got a linux
box acting as a router gateway with a couple of ethernet cards in it.  One
interface is 205.140.230.1, the other is on our main network.  I've routed
the 205 network to the linux box, and am routing it to eth1 (eth0 is our
mainnetwork).  I have a few devices plugged into a hub that is plugged
into eth1.  Theses devices have IP #s set to #s on the
205 network, and, they all have 205.140.230.1 as their gateway.  ipv4
fowarding is on.  Now, here's the weird part.  I can ping and access these
links all day.  And, their latency is not bad at all considering it's a
city-wide wireless LAN.  But, I cannot traceroute to any of these boxes at
all.  Example:

squishy /home/koree > ping mtv-ap-2
PING mtv-ap-2.mvn.net (205.140.230.12): 56 data bytes
64 bytes from 205.140.230.12: icmp_seq=0 ttl=31 time=2.8 ms
64 bytes from 205.140.230.12: icmp_seq=1 ttl=31 time=2.7 ms
64 bytes from 205.140.230.12: icmp_seq=2 ttl=31 time=2.7 ms
64 bytes from 205.140.230.12: icmp_seq=3 ttl=31 time=2.7 ms
64 bytes from 205.140.230.12: icmp_seq=4 ttl=31 time=4.6 ms

--- mtv-ap-2.mvn.net ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max = 2.7/3.1/4.6 ms


squishy /home/koree > traceroute mtv-ap-2
traceroute to mtv-ap-2.mvn.net (205.140.230.12), 30 hops max, 40 byte
packets
 1  mtv-cs3640-1.mvn.net (206.152.121.1)  11.129 ms  1.715 ms  1.421 ms
 2  troubledwater.mvn.net (206.152.121.102)  1.102 ms  1.056 ms  1.308 ms


And it just sticks there (206.152.121.102 is the Linux box).  Any idea
what this might be?

Koree
______________________________________________
Koree A. Smith  | Co-Administrator, ameth.org
koree@Ameth.org | http://www.koree.net/
koree@koree.net | Linux Rules!
NT < *IX        | I Corinthians 2:1-5

Nous pensons que Linux représente à terme une menace pour Windows.


-
To unsubscribe, send email to majordomo@silug.org with
"unsubscribe silug-discuss" in the body.