[14312] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

test Nets being routed?

daemon@ATHENA.MIT.EDU (Matthew D. Lammers)
Tue Dec 23 14:24:30 1997

From: "Matthew D. Lammers" <lammers@zeus.netset.com>
To: nanog@merit.edu
Date: Tue, 23 Dec 1997 14:23:30 -0500 (EST)
Cc: lammers@zeus.netset.com (Matthew D. Lammers)


Happy Holidays To You All!

Am I the only one seeing the 192.168.0.0 test net going somewhere?  RFC 1918
mandates 192.168.0.0/255.255.0.0 [192.168/16] for private networks (testing),
right?  Inc.net seems to have some problems...

From 206.183.227.10, I can get to them via telnet...These are
definately NOT my hosts, either...  :)


======
zeus% telnet 192.168.1.2

Trying 192.168.1.2 ...
Connected to 192.168.1.2.
Escape character is '^]'.


ComOS - Livingston PortMaster

login:

======


	And this one:


======
zeus% traceroute 192.168.1.2

 1  gw0-core0-ser1-eth0.Hilliard.netset.com (206.183.227.1)  1 ms  1 ms  4 ms
 2  core1-hssi1-NETSET.Columbus.fnsi.net (206.183.239.73)  5 ms  4 ms  4 ms
 3  aads.nap.net (198.32.130.39)  17 ms  27 ms  19 ms
 4  aads.atm.inc.net (198.32.130.68)  25 ms  39 ms  21 ms
 5  baryon.atm.inc.net (207.67.1.3)  21 ms  21 ms  24 ms
 6  border-233.noc.inc.net (204.95.160.233)  31 ms  24 ms  30 ms

======

Just wanted some other expertise and input....

Regards,
-Matt.

-- 
  Matthew D. Lammers -- NetSet Internet Solutions, Inc.
  http://www.netset.com/

home help back first fref pref prev next nref lref last post