----- Begin Included Message -----
From: "John S. Pinnow" <jspinnow@allmalt.cs.uwm.edu>
Subject: Concerning 192.x.x.x and routing
To: paul.weber@mci.com, jeff@UWM.EDU, EJNORMAN@MACC.WISC.EDU,
hostmaster@cic.net, JKRey@ISI.EDU
Date: Sat, 6 Jan 1996 14:29:30 -0600 (CST)
Cc: jspinnow@allmalt.cs.uwm.edu (John S. Pinnow)
I am trying to reach 192.135.135.1 and I know it is up. They are
trying to get out with no success.
Now every time I trying to telnet,rlogin,ftp to this place. The packets
are sent down the wrong route.
192.135.135.1 is supposed to hop on to wiscnet.net and make its way
to csdnb.csd.mu.edu and then route over via that server. This is not
happening.
From serveral accounts I tried. Each funneling the packets down mci net.
Interesting enough I tried random destinations on the 192.x.x.x network
and they all want to wrote the same way. I think something is funny here.
Someone along the line has some weird mask set that is funneling the
whole 192 net down a pipe that it may not have to travel threw.
traceroute to csdnb.csd.mu.edu. It makes it fine. Thats where the
192.135.135.x packets are destined for, but they never get there.
Now... I ask you kindly to research this. I already got a message
to contact whois 192.135.135. Now don't give me that. I know the administrator
and he is just as puzzled as I am about this mess. They can't get out
and I can't get back in. I am a bit frustrated.
If you kindly give me information on who to contact to get this routing
mess back under control, I would greatly appreciate it.
Thank you for assistance!
--
John S. Pinnow `net:jspinnow@cs.uwm.edu ` Home Voice: [414] 761-1537
My opinions are not that of UWM, I am not operating in any official compacity
----- End Included Message -----
----- Begin Included Message -----
From: John Stewart Pinnow <jspinnow@winternet.com>
Subject: Why?
To: JKRey@ISI.EDU
Date: Wed, 3 Jan 1996 21:09:18 -0600 (CST)
Content-Type: text
Content-Length: 838
%/usr/etc/traceroute 192.135.135.1
traceroute to 192.135.135.1 (192.135.135.1), 30 hops max, 40 byte packets
1 winternet-gw.winternet.com (198.174.169.254) 8 ms 24 ms 41 ms
2 mrnet-Winternet1.MR.Net (137.192.18.1) 55 ms 13 ms 34 ms
3 MIXNet-gw.MR.Net (137.192.241.254) 49 ms 69 ms 41 ms
4 192.168.168.5 (192.168.168.5) 43 ms 56 ms 55 ms
5 border3-hssi1-0.Chicago.mci.net (204.70.26.5) 177 ms 189 ms 162 ms
6 *
Why is 192.135.135.x routing down threw MCINET????? it should be
routing to wiscnet and then to csdnb.csd.mu.edu
--
John S. Pinnow|net:jspinnow@cs.uwm.edu |Home Voice: [414] 761-1537
<=T=> TR <=R=>| jspinnow@world.std.com|Voice Mail: [414] 287-5252
Milwaukee, WI | jspinnow@winternet.com|http://www.uwm.edu/~jspinnow
Disclaimer----> The views expressed are not necessarily those of U.W.M
----- End Included Message -----
From: "John S. Pinnow" <jspinnow@allmalt.cs.uwm.edu>
Subject: Concerning 192.x.x.x and routing
To: paul.weber@mci.com, jeff@UWM.EDU, EJNORMAN@MACC.WISC.EDU,
hostmaster@cic.net, JKRey@ISI.EDU
Date: Sat, 6 Jan 1996 14:29:30 -0600 (CST)
Cc: jspinnow@allmalt.cs.uwm.edu (John S. Pinnow)
I am trying to reach 192.135.135.1 and I know it is up. They are
trying to get out with no success.
Now every time I trying to telnet,rlogin,ftp to this place. The packets
are sent down the wrong route.
192.135.135.1 is supposed to hop on to wiscnet.net and make its way
to csdnb.csd.mu.edu and then route over via that server. This is not
happening.
From serveral accounts I tried. Each funneling the packets down mci net.
Interesting enough I tried random destinations on the 192.x.x.x network
and they all want to wrote the same way. I think something is funny here.
Someone along the line has some weird mask set that is funneling the
whole 192 net down a pipe that it may not have to travel threw.
traceroute to csdnb.csd.mu.edu. It makes it fine. Thats where the
192.135.135.x packets are destined for, but they never get there.
Now... I ask you kindly to research this. I already got a message
to contact whois 192.135.135. Now don't give me that. I know the administrator
and he is just as puzzled as I am about this mess. They can't get out
and I can't get back in. I am a bit frustrated.
If you kindly give me information on who to contact to get this routing
mess back under control, I would greatly appreciate it.
Thank you for assistance!
--
John S. Pinnow `net:jspinnow@cs.uwm.edu ` Home Voice: [414] 761-1537
My opinions are not that of UWM, I am not operating in any official compacity
----- End Included Message -----
----- Begin Included Message -----
From: John Stewart Pinnow <jspinnow@winternet.com>
Subject: Why?
To: JKRey@ISI.EDU
Date: Wed, 3 Jan 1996 21:09:18 -0600 (CST)
Content-Type: text
Content-Length: 838
%/usr/etc/traceroute 192.135.135.1
traceroute to 192.135.135.1 (192.135.135.1), 30 hops max, 40 byte packets
1 winternet-gw.winternet.com (198.174.169.254) 8 ms 24 ms 41 ms
2 mrnet-Winternet1.MR.Net (137.192.18.1) 55 ms 13 ms 34 ms
3 MIXNet-gw.MR.Net (137.192.241.254) 49 ms 69 ms 41 ms
4 192.168.168.5 (192.168.168.5) 43 ms 56 ms 55 ms
5 border3-hssi1-0.Chicago.mci.net (204.70.26.5) 177 ms 189 ms 162 ms
6 *
Why is 192.135.135.x routing down threw MCINET????? it should be
routing to wiscnet and then to csdnb.csd.mu.edu
--
John S. Pinnow|net:jspinnow@cs.uwm.edu |Home Voice: [414] 761-1537
<=T=> TR <=R=>| jspinnow@world.std.com|Voice Mail: [414] 287-5252
Milwaukee, WI | jspinnow@winternet.com|http://www.uwm.edu/~jspinnow
Disclaimer----> The views expressed are not necessarily those of U.W.M
----- End Included Message -----