On Wed, Dec 18, 2013 at 06:20:17PM +0000, William G. Gardella wrote:
> dee.su is working for me from Comcast. Of course, Comcast has already
> faced sanction from the FCC for running deep packet inspection to
> discover BitTorrent users, in violationn of FCC rulings; perhaps AT&T is
> more daring because they have not yet faced such an enforcement action.
> Perhaps we could change that.
I telnetted to route-server.ip.att.net, a public AT&T route server, and
poked around at this briefly. The IP address 31.170.163.154 is being
announced as 31.170.160.0/22, with an AS path of 7018 174 20115 15085 15085
15085 47583. However, traceroutes to 31.170.163.154 fail with a timeout
after the first hop. This is also true for a number of other IPs in the
same block which I spot checked, though.
I also looked at other announcements from 47583. For the ones that AT&T
has routes for, most are reachable via traceroute, however a number of
others fail in the same way after the first hop.
These prefixes appear to all be reachable:
31.220.48.0/20 *[BGP/170] 6d 10:13:09, localpref 100, from
12.123.33.249 AS path: 7018 1299 20115 15085 15085 15085 47583 I
185.28.22.0/24 *[BGP/170] 6d 10:13:10, localpref 100, from
12.123.33.249 AS path: 7018 1299 20115 15085 15085 15085 47583 I
185.28.23.0/24 *[BGP/170] 6d 10:13:10, localpref 100, from
12.123.33.249 AS path: 7018 1299 20115 15085 15085 15085 47583 I
212.1.208.0/21 *[BGP/170] 6d 10:13:11, localpref 100, from
12.123.33.249 AS path: 7018 1299 20115 15085 15085 15085 47583 I
212.1.208.0/24 *[BGP/170] 6d 10:13:11, localpref 100, from
12.123.33.249 AS path: 7018 1299 20115 15085 15085 15085 47583 I
212.1.210.0/24 *[BGP/170] 6d 10:13:11, localpref 100, from
12.123.33.249 AS path: 7018 1299 20115 15085 15085 15085 47583 I
212.1.211.0/24 *[BGP/170] 6d 10:13:11, localpref 100, from
12.123.33.249 AS path: 7018 1299 20115 15085 15085 15085 47583 I
212.1.212.0/22 *[BGP/170] 6d 10:13:11, localpref 100, from
12.123.33.249 AS path: 7018 1299 20115 15085 15085 15085 47583 I
212.1.212.0/24 *[BGP/170] 6d 10:37:58, localpref 100, from
12.122.83.238 AS path: 7018 174 20115 15085 15085 15085 47583 I
212.1.215.0/24 *[BGP/170] 6d 10:37:58, localpref 100, from
12.122.83.238 AS path: 7018 174 20115 15085 15085 15085 47583 I
These prefixes appear to be unreachable:
93.188.160.0/21 *[BGP/170] 6d 10:13:10, localpref 100, from
12.123.33.249 AS path: 7018 1299 20115 15085 15085 15085 47583 I
31.170.160.0/22 *[BGP/170] 6d 10:13:09, localpref 100, from
12.123.33.249 AS path: 7018 1299 20115 15085 15085 15085 47583 I
31.170.164.0/23 *[BGP/170] 1w2d 06:09:56, localpref 100, from
12.123.5.240 AS path: 7018 3257 9009 9009 9009 9009 47583 I
31.170.166.0/23 *[BGP/170] 6d 10:13:09, localpref 100, from
12.123.33.249 AS path: 7018 1299 20115 15085 15085 15085 47583 I
I don't see an obvious pattern offhand in the AS paths. Given the large
number of IPs involved, without knowing more information, I'm more likely
to attribute this to error than malice. But, I've only given it a cursory
examination.
Has any customer of AT&T attempted to contact them?
-mct
--
Liberationtech is public & archives are searchable on Google. Violations of
list guidelines will get you moderated:
https://mailman.stanford.edu/mailman/listinfo/liberationtech. Unsubscribe,
change to digest, or change password by emailing moderator at
compa...@stanford.edu.
