My network assignment 204.82.160.0/22 (Sprint-announced) has become invisible to all Digex-connected networks, while my old assignment (204.97.218/219) is still seen normally.
I see both /16s.
The Almaty NATO networking conference is IN SESSION (trace to 206.82.161.1
Traffic is bouncing on your side. --asp@uunet.uu.net (Andrew Partan) Vienna1-gw#sh ip b 204.82.160.0 BGP routing table entry for 204.82.0.0 255.255.0.0, version 1489552 Paths: (1 available, best #1, advertised over IBGP, EBGP) 3561 577 807, (aggregated by 577 192.68.66.14) 192.41.177.181 from 192.41.177.181 (204.70.7.53) Origin EGP, metric 57, valid, external, atomic-aggregate, best Vienna1-gw#sh ip b 204.97.218.0 BGP routing table entry for 204.97.0.0 255.255.0.0, version 1145769 Paths: (1 available, best #1, advertised over IBGP, EBGP) 1239, (aggregated by 1239 144.228.61.1) 192.41.177.241 from 192.41.177.241 (144.228.101.1) Origin IGP, metric 9, valid, external, atomic-aggregate, best Vienna1-gw#trace 206.82.161.1 Type escape sequence to abort. Tracing the route to gate.almaty.belcom.net (206.82.161.1) 1 sl-mae-e-F0/0.sprintlink.net (192.41.177.241) 4 msec 4 msec 0 msec 2 sl-dc-8-H1/0-T3.sprintlink.net (144.228.10.41) [AS 1239] 104 msec 200 msec 16 msec 3 sl-dc-6-F0/0.sprintlink.net (144.228.20.6) [AS 1239] 8 msec 0 msec 4 msec 4 sl-pen-1-H2/0-T3.sprintlink.net (144.228.10.34) [AS 1239] 4 msec 4 msec 4 msec 5 sl-pen-4-F0/0.sprintlink.net (144.228.60.4) [AS 1239] 12 msec 8 msec 8 msec 6 sl-computel-1-S0-T1.sprintlink.net (144.228.64.74) [AS 1239] 16 msec 16 msec 16 msec 7 gate.belcom.net (204.97.218.1) [AS 1239] 20 msec 20 msec 20 msec 8 ny-msw-256k.belcom.net (204.97.218.4) [AS 1239] 32 msec 28 msec 20 msec 9 gate.moscow.belcom.net (206.82.160.1) [AS 1794] 168 msec 172 msec 168 msec 10 204.97.219.1 [AS 1239] 184 msec 184 msec 184 msec 11 gate.moscow.belcom.net (206.82.160.1) [AS 1794] 188 msec 188 msec 196 msec 12 204.97.219.1 [AS 1239] 204 msec 200 msec 200 msec 13 gate.moscow.belcom.net (206.82.160.1) [AS 1794] 204 msec 216 msec 208 msec 14 204.97.219.1 [AS 1239] 220 msec 220 msec 220 msec 15 gate.moscow.belcom.net (206.82.160.1) [AS 1794] 224 msec 224 msec 236 msec 16 204.97.219.1 [AS 1239] 232 msec 236 msec 236 msec 17 gate.moscow.belcom.net (206.82.160.1) [AS 1794] 240 msec 240 msec 240 msec 18 204.97.219.1 [AS 1239] 252 msec 252 msec 252 msec 19 gate.moscow.belcom.net (206.82.160.1) [AS 1794] 260 msec 388 msec 260 msec 20 204.97.219.1 [AS 1239] 288 msec 272 msec 436 msec 21 gate.moscow.belcom.net (206.82.160.1) [AS 1794] 272 msec 276 msec 340 msec 22 204.97.219.1 [AS 1239] 288 msec * 292 msec 23 gate.moscow.belcom.net (206.82.160.1) [AS 1794] 292 msec 292 msec 292 msec 24 204.97.219.1 [AS 1239] 304 msec 304 msec 304 msec 25 gate.moscow.belcom.net (206.82.160.1) [AS 1794] 312 msec 312 msec 308 msec 26 204.97.219.1 [AS 1239] 324 msec 324 msec 324 msec 27 gate.moscow.belcom.net (206.82.160.1) [AS 1794] 328 msec 328 msec 328 msec 28 204.97.219.1 [AS 1239] 340 msec 340 msec 340 msec 29 gate.moscow.belcom.net (206.82.160.1) [AS 1794] 344 msec 364 msec 364 msec 30 204.97.219.1 [AS 1239] 376 msec 356 msec 368 msec
--------- Received message begins Here --------- asp@uunet wrote:
The Almaty NATO networking conference is IN SESSION (trace to 206.82.161.1
Traffic is bouncing on your side. --asp@uunet.uu.net (Andrew Partan)
I get the same loop from DIGEX; it doesn't look like we're being routed any differently.
participants (2)
-
asp@uunet.uu.net
-
Dave Israel