On Sun, 29 Sep 2002 22:23:21 -0700 (PDT) Scott Granados <scott@graphidelix.net> wrote:

Was wondering if anyone with clue from Cox is listening. My newly assigned arin block, 69.1.64.0/20 doesn't seem to be making it in to your filters even with the proper filed bbjects:).

Or maybe I'm missing something obvious.

Scott; I am a Cox Cable customer at home but I cannot seem to get to 69.1.64.0/20. At work (AS 16517) I have a route to 69.1.64.0, and can ping 69.1.64.1 [tme@lennon tme]$ ping 69.1.64.1 PING 69.1.64.1 (69.1.64.1) from 63.105.122.7 : 56(84) bytes of data. 64 bytes from 69.1.64.1: icmp_seq=0 ttl=245 time=74.096 msec 64 bytes from 69.1.64.1: icmp_seq=1 ttl=245 time=74.715 msec 64 bytes from 69.1.64.1: icmp_seq=2 ttl=245 time=77.553 msec multicasttech-1>show ip bgp 69.1.64.0 BGP routing table entry for 69.1.64.0/20, version 3334583 Paths: (2 available, best #2, table Default-IP-Routing-Table) Not advertised to any peer 701 3549 14743 26346 157.130.46.53 from 157.130.46.53 (137.39.4.186) Origin IGP, localpref 100, valid, external 1239 14743 26346 160.81.38.225 from 160.81.38.225 (144.228.242.54) Origin IGP, metric 43, localpref 100, valid, external, best multicasttech-1> trace 69.1.64.1 Type escape sequence to abort. Tracing the route to 69.1.64.1 1 sl-gw5-rly-9-0-0-TS19.sprintlink.net (160.81.38.225) 8 msec 4 msec 4 msec 2 sl-bb21-rly-0-0.sprintlink.net (144.232.25.244) [AS 1239] 4 msec 0 msec 4 msec 3 sl-bb25-rly-11-0.sprintlink.net (144.232.14.158) [AS 1239] 4 msec 4 msec 4 msec 4 sl-bb21-sj-5-3.sprintlink.net (144.232.20.91) [AS 1239] 68 msec 68 msec 64 msec 5 sl-gw13-sj-10-0.sprintlink.net (144.232.3.174) [AS 1239] 64 msec 72 msec 72 msec 6 sl-internap-56-0-155M.sprintlink.net (160.81.100.2) [AS 1239] 72 msec 68 msec 68 msec 7 border6.ge4-1-bbnet2.sfo.pnap.net (63.251.63.75) [AS 14743] 72 msec 72 msec 72 msec 8 digitalwire-3.border6.sfo.pnap.net (63.251.61.230) [AS 14743] 72 msec * 96 msec multicasttech-1>

From COX, nothing :

[localhost:~/awk] tme% ping 69.1.64.1 PING 69.1.64.1 (69.1.64.1): 56 data bytes ^C --- 69.1.64.1 ping statistics --- 9 packets transmitted, 0 packets received, 100% packet loss [localhost:~/awk] tme% So, I think that you do have transit problems - assuming that 69.1.64.1 is for sure a box inside your network. Give me the IP address of a box known to be in 69.1.64.0/20 and I will try to ping and traceroute to it. Regards Marshall Eubanks