Is there anyone from AT&T on the list that could help with a likely misconfiguration? I have not received any response yet to my complaint (see below) submitted to the abuse address on July 26. We have since started advertising this space and would like to resolve the MOAS condition we have created. //////////////// The 128.1.0.0/16 address block is registered to BBN Technologies (AS11488) but is currently unused on any BBN networks. BBN would like to begin using this address space however AS7018 is currently originating public BGP routes for this address block. We believe this to be a configuration error. Please help us resolve this. A traceroute to 128.1.0.1 shows the following routers as the last 4 responding hops: cr1.n54ny.ip.att.net (12.122.81.106) cr81.nw2nj.ip.att.net (12.122.105.30) gar18.n54ny.ip.att.net (12.122.105.101) 12.89.231.190 //////////////// Thanks, Rick
Did you fix it? My traceroute shows last hop is 64.119.128.44. On Fri, Aug 5, 2011 at 12:07 AM, Rick Altmann <raltmann@bbn.com> wrote:
Is there anyone from AT&T on the list that could help with a likely misconfiguration? I have not received any response yet to my complaint (see below) submitted to the abuse address on July 26. We have since started advertising this space and would like to resolve the MOAS condition we have created.
////////////////
The 128.1.0.0/16 address block is registered to BBN Technologies (AS11488) but is currently unused on any BBN networks. BBN would like to begin using this address space however AS7018 is currently originating public BGP routes for this address block. We believe this to be a configuration error. Please help us resolve this.
A traceroute to 128.1.0.1 shows the following routers as the last 4 responding hops:
cr1.n54ny.ip.att.net (12.122.81.106) cr81.nw2nj.ip.att.net (12.122.105.30) gar18.n54ny.ip.att.net (12.122.105.101) 12.89.231.190
////////////////
Thanks, Rick
This issue has been cleared up. Thanks to everyone for their help. -Rick On Aug 4, 2011, at 12:07 PM, Rick Altmann wrote:
Is there anyone from AT&T on the list that could help with a likely misconfiguration? I have not received any response yet to my complaint (see below) submitted to the abuse address on July 26. We have since started advertising this space and would like to resolve the MOAS condition we have created.
////////////////
The 128.1.0.0/16 address block is registered to BBN Technologies (AS11488) but is currently unused on any BBN networks. BBN would like to begin using this address space however AS7018 is currently originating public BGP routes for this address block. We believe this to be a configuration error. Please help us resolve this.
A traceroute to 128.1.0.1 shows the following routers as the last 4 responding hops:
cr1.n54ny.ip.att.net (12.122.81.106) cr81.nw2nj.ip.att.net (12.122.105.30) gar18.n54ny.ip.att.net (12.122.105.101) 12.89.231.190
////////////////
Thanks, Rick
Wow, BBN, the reason we use the @ sign, second .com Domain, former AS1. Lots of history ;) On Mon, Aug 8, 2011 at 2:07 PM, Rick Altmann <raltmann@bbn.com> wrote:
This issue has been cleared up. Thanks to everyone for their help.
-Rick
On Aug 4, 2011, at 12:07 PM, Rick Altmann wrote:
Is there anyone from AT&T on the list that could help with a likely misconfiguration? I have not received any response yet to my complaint (see below) submitted to the abuse address on July 26. We have since started advertising this space and would like to resolve the MOAS condition we have created.
////////////////
The 128.1.0.0/16 address block is registered to BBN Technologies (AS11488) but is currently unused on any BBN networks. BBN would like to begin using this address space however AS7018 is currently originating public BGP routes for this address block. We believe this to be a configuration error. Please help us resolve this.
A traceroute to 128.1.0.1 shows the following routers as the last 4 responding hops:
cr1.n54ny.ip.att.net (12.122.81.106) cr81.nw2nj.ip.att.net (12.122.105.30) gar18.n54ny.ip.att.net (12.122.105.101) 12.89.231.190
////////////////
Thanks, Rick
They also made Interface Message Processors, like the grandpas of routers. .as On 8 Aug 2011, at 12:29, Peter Stockli wrote:
Wow, BBN, the reason we use the @ sign, second .com Domain, former AS1.
Lots of history ;)
On Mon, Aug 8, 2011 at 2:07 PM, Rick Altmann <raltmann@bbn.com> wrote:
This issue has been cleared up. Thanks to everyone for their help.
-Rick
On Aug 4, 2011, at 12:07 PM, Rick Altmann wrote:
Is there anyone from AT&T on the list that could help with a likely misconfiguration? I have not received any response yet to my complaint (see below) submitted to the abuse address on July 26. We have since started advertising this space and would like to resolve the MOAS condition we have created.
////////////////
The 128.1.0.0/16 address block is registered to BBN Technologies (AS11488) but is currently unused on any BBN networks. BBN would like to begin using this address space however AS7018 is currently originating public BGP routes for this address block. We believe this to be a configuration error. Please help us resolve this.
A traceroute to 128.1.0.1 shows the following routers as the last 4 responding hops:
cr1.n54ny.ip.att.net (12.122.81.106) cr81.nw2nj.ip.att.net (12.122.105.30) gar18.n54ny.ip.att.net (12.122.105.101) 12.89.231.190
////////////////
Thanks, Rick
Plus, technically, since symbolics.com was non-operational for a while, bbn.com is the oldest .com domain in continuous operation. And you'll notice that it has IPv6-reachable web and DNS servers :) On Mon, Aug 8, 2011 at 11:29 AM, Peter Stockli <petercs@gmail.com> wrote:
Wow, BBN, the reason we use the @ sign, second .com Domain, former AS1.
Lots of history ;)
On Mon, Aug 8, 2011 at 2:07 PM, Rick Altmann <raltmann@bbn.com> wrote:
This issue has been cleared up. Thanks to everyone for their help.
-Rick
On Aug 4, 2011, at 12:07 PM, Rick Altmann wrote:
Is there anyone from AT&T on the list that could help with a likely misconfiguration? I have not received any response yet to my complaint (see below) submitted to the abuse address on July 26. We have since started advertising this space and would like to resolve the MOAS condition we have created.
////////////////
The 128.1.0.0/16 address block is registered to BBN Technologies (AS11488) but is currently unused on any BBN networks. BBN would like to begin using this address space however AS7018 is currently originating public BGP routes for this address block. We believe this to be a configuration error. Please help us resolve this.
A traceroute to 128.1.0.1 shows the following routers as the last 4 responding hops:
cr1.n54ny.ip.att.net (12.122.81.106) cr81.nw2nj.ip.att.net (12.122.105.30) gar18.n54ny.ip.att.net (12.122.105.101) 12.89.231.190
////////////////
Thanks, Rick
participants (5)
-
Arturo Servin -
IT 8844 -
Peter Stockli -
Richard Barnes -
Rick Altmann