🚀 go-pugleaf

Ehud Gavron (gavron@hearts.aces.com) wrote:
: 	Sorry, Tim, you don't understand TCP/IP.

You really should learn to think before you post.  If I didn't know
you, I'd say that you're the one that doesn't understand TCP/IP.
However, from what I've heard and seen, you seem to know your stuff.
I don't understand why you repeatedly disregard that knowledge when
posting.

Besides the technical evidence, Primenet even admins that they are
indeed filtering packets to ExtremeZone IP range(s).

: 	This is CLEARLY NOT a filter put in by PrimeNet, since they
: 	are delivering the packets to ExtremeZone's provider, MCI.

I fail to see how being able to talk to MCI precludes having a filter
that filters out ExtremeZone, let alone "CLEARLY" precludes such.

From looking at the traceroute, it looks to me like there's a filter
on Primenet's router discarding incoming packets from ExtremeZone's IP
range(s).  This would cause the packets from the traceroute to leave
Primenet's network successfully, but the return packets from hosts
using ExtremeZone's IP range(s) wouldn't make it back.

: 	If you don't know what you're talking about, a good position
: 	is to shut the fuck up

You should take your own advice.  Grow up too, while you're at it.

-nils