Concerning 192.x.x.x and routing
----- 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 -----
Jon, I don't know why you were copied on this, but this was an internal WISCnet issue and has been resolved. -dorian On Mon, 8 Jan 1996 postel@ISI.EDU wrote:
----- 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 -----
______________________________________________________________________________ Dorian Kim Email: dorian@cic.net 2901 Hubbard Drive Network Engineer Phone: (313)998-6976 Ann Arbor MI 48105 CICNet Network Systems Fax: (313)998-6105 http://www.cic.net/~dorian
from my little nook: traceroute to 192.135.135.1 (192.135.135.1) 30 hops max, 38 byte packets 1 eth-3.gw-4.hck.idt.net (169.132.32.254) 2 ms 2 ms 2 ms 2 eth-0.gw-1.hck.idt.net (169.132.34.250) 3 ms 2 ms 2 ms 3 hck-t1.gw-1.nynap.idt.net (206.20.128.17) 8 ms 9 ms 8 ms 4 192.157.69.11 (192.157.69.11) 9 ms 9 ms 9 ms 5 border2-hssi1-0.NewYork.mci.net (204.70.45.5) 137 ms 41 ms 209 ms 6 core-fddi-1.NewYork.mci.net (204.70.3.17) 157 ms 195 ms 292 ms 7 core1-hssi-2.WestOrange.mci.net (204.70.1.98) 33 ms 15 ms 15 ms 8 core1-hssi-3.NorthRoyalton.mci.net (204.70.1.101) 27 ms 28 ms 31 ms 9 core-hssi-2.Chicago.mci.net (204.70.1.93) 36 ms 39 ms 38 ms 10 border2-fddi-0.Chicago.mci.net (204.70.3.82) 39 ms 36 ms 38 ms 11 cicnet.Chicago.mci.net (204.70.25.10) 41 ms 34 ms 40 ms 12 dgf-fddi1.cic.net (192.217.0.4) 41 ms 37 ms 34 ms 13 dgb-fddi0.cic.net (131.103.1.17) 34 ms 35 ms 36 ms 14 mke-dgb.cic.net (131.103.25.226) 131 ms 78 ms 60 ms 15 wiscnet.csd.uwm.edu (129.89.6.3) 128 ms 165 ms 109 ms 16 marquette-milwaukee.wiscnet.net (140.189.32.2) 235 ms 117 ms 278 ms 17 csdnb.csd.mu.edu (134.48.1.80) 110 ms (ttl=47!) 156 ms (ttl=47!) 182 ms (ttl=47!) 18 192.135.135.9 (192.135.135.9) 422 ms 387 ms 452 ms 19 192.135.135.1 (192.135.135.1) 329 ms (ttl=236!) 392 ms (ttl=236!) 403 ms (ttl=236!) yes, there is a redirect problem probably near the host, maybe that kills ya. Mike On Mon, 8 Jan 1996 postel@ISI.EDU wrote:
----- 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 -----
---------------------------------------------------------- IDT Michael F. Nittmann --------- Senior Network Architect \ / (201) 928 1000 xt 500 ------- (201) 928 1888 FAX \ / mn@tremere.ios.com --- V IOS
so what precisely is the problem?? rodan 184% traceroute 192.135.135.1 traceroute to 192.135.135.1 (192.135.135.1), 30 hops max, 40 byte packets 1 IBMpc02 (153.39.130.1) 2 ms 1 ms 1 ms 2 Fddi0/0.GW2.FFX1.Alter.Net (137.39.12.2) 3 ms 2 ms 2 ms 3 Hssi2/0.Vienna1.VA.Alter.Net (137.39.100.69) 5 ms 13 ms 3 ms 4 192.41.177.180 (192.41.177.180) 120 ms 6 ms 4 ms 5 borderx2-hssi2-0.Washington.mci.net (204.70.74.117) 190 ms 8 ms 13 ms 6 core2-fddi-1.Washington.mci.net (204.70.74.65) 6 ms 6 ms 7 ms 7 core2-hssi-3.WestOrange.mci.net (204.70.1.105) 334 ms 17 ms 510 ms 8 borderx1-fddi-1.WestOrange.mci.net (204.70.64.52) 19 ms 11 ms 11 ms 9 core1-fddi-0.WestOrange.mci.net (204.70.64.17) 10 ms 12 ms 12 ms 10 core1-hssi-3.NorthRoyalton.mci.net (204.70.1.101) 29 ms 23 ms 27 ms 11 core-hssi-2.Chicago.mci.net (204.70.1.93) 34 ms 33 ms 37 ms 12 border2-fddi-0.Chicago.mci.net (204.70.3.82) 35 ms 31 ms 34 ms 13 cicnet.Chicago.mci.net (204.70.25.10) 30 ms 32 ms 33 ms 14 dgf-fddi1.cic.net (192.217.0.4) 34 ms 31 ms 33 ms 15 dgb-fddi0.cic.net (131.103.1.17) 30 ms 33 ms 30 ms 16 mke-dgb.cic.net (131.103.25.226) 336 ms 104 ms 365 ms 17 wiscnet.csd.uwm.edu (129.89.6.3) 40 ms 92 ms 68 ms 18 marquette-milwaukee.wiscnet.net (140.189.32.2) 69 ms 148 ms 138 ms 19 csdnb.csd.mu.edu (134.48.1.80) 216 ms 148 ms 151 ms 20 192.135.135.9 (192.135.135.9) 497 ms 434 ms 428 ms 21 192.135.135.1 (192.135.135.1) 364 ms 349 ms 282 ms rodan 185%
participants (4)
-
Dorian Kim -
mike -
Mike O'Dell -
postel＠ISI.EDU