On Fri, 23 Aug 2013, Steve Meuse wrote:
As a quick fix, you could announce more specific prefixes, it looks like they are announcing a matching /23.
That is a great suggestion. While we were working on that the problem was fixed, presumably due to your intervention with Earthlink. I thank you very much. The problem was corrected before we could annouce the /24s but we left the commented out code in our router config to do so in the future if necessary.
Thanks for all the comments - they were all more helpful than our ISP nocs. I am especially annoyed with Windstream (owner of Paetec), who refused to open a ticket with their own upstream transit provider (Level3) that was accepting the false announcement over a peering link.
Daniel Feenberg NBER
-Steve On Fri, Aug 23, 2013 at 10:28 AM, Daniel Feenberg <[email protected]> wrote: I am beginning to believe that One Communications has hijacked our address space. At the moment any traceroute from a Comcast cable modem in the Boston area to us dies somewhere in New York on a One Communications router. How do I approach them when I am not a customer? I took this up with our ISP (Windstream) and they declined to assist, as did Comcast. In niether case could I speak with a person who understood what was going on. Our IPs are in the range 66.251.72.0/23. The Windstream side of our router is 63.139.191.117. Traceroutes from Comcast to the latter do succeed, to the former fail. They take completely different paths. Traceroutes from inside our LAN to Comcast also fail, usually ending at a Level3 router in NY. None of the ISP mentioned here have a working looking glass. Thanks for any advice, suggestions. Daniel Feenberg 617-863-0343 _______________________________________________ bblisa mailing list [email protected] http://www.bblisa.org/mailman/listinfo/bblisa
_______________________________________________ bblisa mailing list [email protected] http://www.bblisa.org/mailman/listinfo/bblisa
