CIDR FAQ
Arnold Nipper
nipper at xlink.net
Thu Aug 17 23:48:43 UTC 1995
Hank Nussbacher wrote:
>
> On Thu, 17 Aug 1995 00:30:19 +0200 (MET DST) you said:
> >Simon Poole wrote:
> >>
> >> Yakov, if you have data that CIDR is -not- working for new allocations
> >> please present it here.
> >>
> >> Simon
> >
> >CIDR doesn't work as it should. We had to inject all of the more specifics
> >of 194.45/16 cause Sprintlink isn't able to handle CIDR routes correctly.
>
> Can someone explain this a bit more? This sounds like a showstopper
> for CIDR.
>
Xlink (AS517) was announcing 194.45.0.0/16 via Ebone. There are some
networks within this block announced by PSI. Routing table at PSI looks
like
Mitch Levinn wrote:
>
> Hi there,
>
> >I've to second Mitch! Looks like a Sprint problem to me!! Mitch, would you be
> >so kind to provide "show ip bgp 194.45.0.0 255.255.0.0 subnet" from the PSI
> >box? Unfortunately neither Sprint nor Ebone NOC did anything (since Friday
> >morning local time!) but ignoring the problem. I would really appreciate if
> >EOT or Ebone NOC would try to fix this problem!
>
> Here's the output requested (from our MAE-East+ router):
>
> >show ip bgp 194.45.0.0 255.255.0.0 subnet
> BGP table version is 1444840, local router ID is 192.41.177.245
> Status codes: s suppressed, * valid, > best, i - internal
> Origin codes: i - IGP, e - EGP, ? - incomplete
>
> Network Next Hop Metric LocPrf Weight Path
> *> 194.45.0.0 38.1.2.10 5 32768 i
> *> 194.45.0.0/16 192.41.177.241 0 1239 1800 1755 517 ?
> *> 194.45.1.0 38.1.2.10 5 32768 i
> *> 194.45.2.0 38.1.2.10 5 32768 i
> *> 194.45.3.0 38.1.2.10 5 32768 i
> *> 194.45.4.0 38.1.2.10 5 32768 i
> *> 194.45.5.0 38.1.2.10 5 32768 i
> *> 194.45.6.0 38.1.2.10 5 32768 i
> *> 194.45.7.0 38.1.2.10 5 32768 i
> *> 194.45.16.0 192.41.177.181 0 3561 1220 ?
>
> This is just as it was last time the problem surfaced, I
> believe. Subnets 0 through 7 are properly being announced through us,
> subnet 16 goes to MCI, and the rest to Sprint.
>
> -Mitch
>
But Sprintlink was routing
>traceroute -g c.psi.net 194.45.41.1
>traceroute to 194.45.41.1 (194.45.41.1), 30 hops max, 40 byte packets
> 1 KarlSruhe.Core.xlink.net (193.141.40.252) 2 ms 5 ms
> 2 muenchen.core.xlink.net (192.54.104.241) 18 ms 10 ms
> 3 Munich-EBS.EBONE.NET (192.121.158.13) 12 ms 13 ms
> 4 icm-dc-1-S2/5-1984k.icp.net (198.67.129.17) 210 ms 141 ms
> 5 icm-mae-e-H1/0-T3.icp.net (198.67.131.9) 310 ms 253 ms
> 6 mae-east.psi.net (192.41.177.245) 254 ms 266 ms
> 7 c.psi.net (192.33.4.12) 257 ms 289 ms
> 8 192.33.4.1 (192.33.4.1) 227 ms 257 ms
> 9 sl-mae-e-F0/0.sprintlink.net (192.41.177.241) 245 ms 250 ms
>10 mae-east.psi.net (192.41.177.245) 203 ms 228 ms
>11 sl-mae-e-F0/0.sprintlink.net (192.41.177.241) 215 ms 193 ms
TT to Sprintlink didn't help. After 4 days still no response. I've fixed
this silly routing by announcing all more specifics.
> >
> >Arnold
>
> Hank
Arnold
More information about the NANOG
mailing list