I do not have AT&T as an ISP. However, my ISP does have them as one of their upstream providers. It appears BGP is trying to route packets destined for 63.111.29.0/24 via the AT&T upstream and I can see it failing as soon as it hits AT&T's network. Jim On Nov 15, 2012, at 5:41 PM, Chris Adams wrote:
Once upon a time, Seth Mattinen <sethm@rollernet.us> said:
I'm curious to know if they're pushing a blocking ACL to MIS with managed (AT&T provided) routers or further up from that, which would mean that customers with their own router wouldn't be affected.
It appears to be dropped in their entire network. I tried it from route-server.ip.att.net (telnet); I can trace to 63.111.29.131 and 63.111.29.133 (at least into AS 11486), but trace to 63.111.29.132 dies after 1 hop. -- Chris Adams <cmadams@hiwaay.net> Systems and Network Administrator - HiWAAY Internet Services I don't speak for anybody but myself - that's enough trouble. _______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages