CIDR deployment

Fri Mar 18 11:36:11 UTC 1994

Hi,

when finding trouble in connection with CIDR deployment (reachability), I'm
not too sure whether using "finger pointing in public places" is the best
approach...  Other suggestions are welcome.  On the other hand, these
wrinkles really needs to be sorted out, so here goes:

I can't reach ecn.purdue.edu from within my CIDR block (129.240/15, host
129.241.1.99) -- it seems that Purdue University has a problem with their
default route, and that they're not running BGP-4.  This is part of their
routing table -- I think the next hop for the default route is screwed up
(that is, if the SNMP agent doesn't lie to me):

% snmpnetstat 192.5.102.3 public -rm
Routing tables
Destination     RouteMask   Gateway          Flags Interface       RouteProto
default         0x00000000  0.0.0.0          U     if0             Local/Static
6               0xff000000  enss152.gw.purdu UG    if0             BGP
7               0xff000000  enss152.gw.purdu UG    if0             BGP
...

Can somebody please fix this?

- Havard

------------------------------ traceroute from nac.no:

% traceroute ecn.purdue.edu
traceroute to ecn.purdue.edu (128.46.128.78), 30 hops max, 40 byte packets
 1  uio-gw.uio.no (129.240.2.1)  2 ms  2 ms  2 ms
 2  oslo-gw.uninett.no (129.240.212.1)  2 ms  3 ms  2 ms
 3  trd-gw.uninett.no (128.39.17.1)  11 ms  11 ms  12 ms
 4  no-gw.nordu.net (128.39.9.1)  10 ms  12 ms  12 ms
 5  nord-gw.nordu.net (192.36.148.145)  46 ms  161 ms  52 ms
 6  Stockholm-EBS1.Ebone.NET (192.121.154.21)  33 ms  37 ms  32 ms
 7  icm-dc-1.icp.net (192.121.154.234)  626 ms  686 ms  730 ms
 8  icm-dc-2-F0.icp.net (144.228.1.36)  634 ms  631 ms  616 ms
 9  icm-fix-e-H0-T3.icp.net (192.157.65.122)  631 ms  664 ms  626 ms
10  192.203.229.246 (192.203.229.246)  652 ms *  646 ms
11  t3-1.Washington-DC-cnss58.t3.ans.net (140.222.58.2)  666 ms  645 ms  654 ms
12  mf-0.Washington-DC-cnss56.t3.ans.net (140.222.56.222)  622 ms  639 ms  634 ms
13  t3-0.New-York-cnss32.t3.ans.net (140.222.32.1)  715 ms  673 ms  636 ms
14  t3-1.Cleveland-cnss40.t3.ans.net (140.222.40.2)  653 ms  663 ms  670 ms
15  t3-2.Chicago-cnss24.t3.ans.net (140.222.24.3)  685 ms  645 ms  662 ms
16  mf-0.Chicago-cnss27.t3.ans.net (140.222.24.195)  683 ms  682 ms  688 ms
17  t1-0.enss152.t3.ans.net (140.222.152.1)  956 ms  694 ms *
18  cisco1-oc.gw.purdue.edu (192.5.102.3)  667 ms  682 ms  683 ms
19  noose.ecn.purdue.edu (128.46.129.11)  699 ms nscmsee.ecn.purdue.edu (128.46.129.99)  699 ms *
20  zoo.ecn.purdue.edu (128.46.128.78)  674 ms *  707 ms
% 

------------------------------ traceroute from aun.uninett.no:

% traceroute ecn.purdue.edu
traceroute to ecn.purdue.edu (128.46.128.78), 30 hops max, 40 byte packets
 1  unit-gw.unit.no (129.241.1.2)  7 ms  5 ms  7 ms
 2  no-gw.nordu.net (128.39.9.1)  4 ms  9 ms  5 ms
 3  nord-gw.nordu.net (192.36.148.145)  23 ms  19 ms  28 ms
 4  Stockholm-EBS1.Ebone.NET (192.121.154.21)  23 ms  29 ms  25 ms
 5  icm-dc-1.icp.net (192.121.154.234)  643 ms  739 ms  943 ms
 6  icm-dc-2-F0.icp.net (144.228.1.36)  641 ms  618 ms  617 ms
 7  icm-fix-e-H0-T3.icp.net (192.157.65.122)  1130 ms  631 ms  625 ms
 8  192.203.229.246 (192.203.229.246)  639 ms *  609 ms
 9  t3-1.Washington-DC-cnss58.t3.ans.net (140.222.58.2)  622 ms  639 ms  649 ms
10  mf-0.Washington-DC-cnss56.t3.ans.net (140.222.56.222)  624 ms  685 ms  611 ms
11  t3-0.New-York-cnss32.t3.ans.net (140.222.32.1)  620 ms *  618 ms
12  t3-1.Cleveland-cnss40.t3.ans.net (140.222.40.2)  644 ms * *
13  t3-2.Chicago-cnss24.t3.ans.net (140.222.24.3)  651 ms  662 ms *
14  mf-0.Chicago-cnss27.t3.ans.net (140.222.24.195)  689 ms  666 ms  634 ms
15  t1-0.enss152.t3.ans.net (140.222.152.1)  672 ms  658 ms  673 ms
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *

------------------------------