Two administrative boo-boos?

Mailman List Mirror (Read Only)
1

I believe I've found two administrative boo-boos.

4 mae-east.enkido.net (198.32.187.119) [5696] 27.268 ms 23.847 ms 24.667 ms

Problem #1: The hop above is showing up for traces into an exodus.

$ traceroute 216.33.96.162
1 CORE-0-GE-3-1000M.CMH.ENTERZONE.NET (66.35.65.1) 0.539 ms 0.756 ms 0.893 ms
2 core1-FE1.Columbus.fnsi.net (209.115.93.129) [6259] 1.227 ms 1.500 ms 1.856 ms
3 border1-atm6-0-0-2.Reston.fnsi.net (216.29.101.50) [6259] 22.570 ms 22.259 ms 22.417 ms
4 mae-east.enkido.net (198.32.187.119) [5696] 31.558 ms 23.003 ms 23.337 ms
5 bbr01-g4-0.hrnd01.exodus.net (216.33.203.125) [3967] 32.443 ms 24.051 ms 23.436 ms
6 bbr02-p6-0.stng01.exodus.net (209.185.249.137) [3967] 24.382 ms 24.204 ms 24.299 ms
7 dcr04-g10-0.stng01.exodus.net (216.33.96.162) [3967] 24.476 ms * 24.124 ms

   Netname: ECI-7
   Netblock: 216.32.0.0 - 216.35.255.255
   Maintainer: ECI

[whois.radb.net]
route: 216.33.96.0/19
descr: NET-EXODUS-STNG01
origin: AS3967
mnt-by: MAINT-AS3967
changed: radb@bengi.exodus.net 20001106
source: RADB

Paths: (3 available, best #1, table Default-IP-Routing-Table)
  6259 3967
    209.115.127.21 from 209.115.127.21 (206.183.226.33)
      Origin IGP, metric 1010, localpref 100, valid, external, best
      Community: 13944:6259
      Last update: Mon Apr 9 12:12:15 2001

I can find no reason why these would go through enkido.net on the way to 3967.

At first, I though this was just a typo in the an-addr records but, after consulting
http://www.mae.net/atm/east-addr.html the address is indeed enkido's mae-east connection. Perhaps someone can explain
why I'm seeing this path.

Problem #2: It looks like Winstar is announcing EP space.

BGP routing table entry for 198.32.187.0/24
Paths: (1 available, best #1, table Default-IP-Routing-Table)
  13706 5696
    66.35.64.10 from 66.35.64.10 (216.226.130.1)
      Origin IGP, metric 1000, localpref 100, valid, external, best
      Community: 13944:13706
      Last update: Sat Apr 7 13:49:33 2001

2

I know I must be stupid for replying but here goes :

I believe I've found two administrative boo-boos.

4 mae-east.enkido.net (198.32.187.119) [5696] 27.268 ms 23.847 ms 24.667 ms

Problem #1: The hop above is showing up for traces into an exodus.

3 border1-atm6-0-0-2.Reston.fnsi.net (216.29.101.50) [6259] 22.570 ms 22.259 ms 22.417 ms
4 mae-east.enkido.net (198.32.187.119) [5696] 31.558 ms 23.003 ms 23.337 ms
5 bbr01-g4-0.hrnd01.exodus.net (216.33.203.125) [3967] 32.443 ms 24.051 ms 23.436 ms

Did you contact FNSI and find out why they are doing this? I don't
see how nanog can help. Tons of people do funky and sometimes
downright stupid things on the Internet.. if we posted them all
to nanog you'd never be able to read it all :slight_smile:

Problem #2: It looks like Winstar is announcing EP space.

BGP routing table entry for 198.32.187.0/24
Paths: (1 available, best #1, table Default-IP-Routing-Table)
  13706 5696
    66.35.64.10 from 66.35.64.10 (216.226.130.1)
      Origin IGP, metric 1000, localpref 100, valid, external, best
      Community: 13944:13706
      Last update: Sat Apr 7 13:49:33 2001

route-views.oregon-ix.net>show ip bgp 198.32.187.0
BGP routing table entry for 198.32.187.0/24, version 41593
Paths: (17 available, best #16)

It looks like everyone is.. if you follow christians filters you would
not have this problem.. if it is a problem.. I mean.. who in this day
and age doesn't re-write next-hop.. :slight_smile:

  Thanks!