[143899] in North American Network Operators' Group
Re: Prefix hijacking by Michael Lindsay via Internap
daemon@ATHENA.MIT.EDU (Erik Bais)
Sun Aug 21 06:57:01 2011
In-Reply-To: <CAL+GGzGzkB76Br-R=5EPvRJHiDvhOU6hcn+pMRL_h+GmLvx-tQ@mail.gmail.com>
From: Erik Bais <ebais@A2B-Internet.com>
Date: Sun, 21 Aug 2011 12:56:26 +0200
To: Denis Spirin <noc@link-telecom.net>
Cc: "nanog@nanog.org" <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
Hi Denis,
That is exactly why you might want to send an abuse msg to Tinet and NTT as t=
hey as accepting the prefixes fromm Portnap.
Erik
Verstuurd vanaf mijn iPad
Op Aug 21, 2011 om 12:44 heeft Denis Spirin <noc@link-telecom.net> het volge=
nde geschreven:
> Where do you see the permission of Internap to transit our AS31733?
>=20
> aut-num: AS31733
> as-name: LINKTEL-AS
> descr: Link Telecom PJSC
> org: ORG-LTP1-RIPE
> import: from AS8342 accept ANY
> import: from AS12695 accept ANY
> import: from AS44109 accept ANY
> export: to AS8342 announce AS31733
> export: to AS12695 announce AS31733
> export: to AS44109 announce AS31733
> admin-c: LN1688-RIPE
> tech-c: LN1688-RIPE
> mnt-by: RIPE-NCC-END-MNT
> mnt-by: MNT-LINKTEL
> mnt-routes: MNT-LINKTEL
> changed: noc@link-telecom.biz 20080917
> changed: hostmaster@ripe.net 20110414
> source: RIPE
>=20
> AS8342, AS12695, AS44109 can. AS12182 - can't.
>=20
> We already in touch with RIPE NCC and Internap. But networks are continue t=
o
> be hijacked. That is the reason I wrote to this list.
>=20
>=20
> 2011/8/21 Arturo Servin <arturo.servin@gmail.com>
>=20
>>=20
>> On 21 Aug 2011, at 00:28, Denis Spirin wrote:
>>=20
>>> Yes, they are using our ASN 31733 to originate networks. All the visible=
>>> paths are through AS12182. Internap was contacted about a week ago, but
>> did
>>> nothing.
>>=20
>> Which seems to be the right decision because the whois data backed=
>> it on.
>>=20
>>=20
>>> No, I'm not a venture capitalist, but IT specialist.
>>>=20
>>> I am too sleepy, so replied to Adrian directly while wanted to post in
>> the
>>> list.
>>=20
>> If you are claiming right over these prefixes I suggest you to
>> contact RIPE NCC.
>>=20
>> /as
>>=20
>>>=20
>>> 2011/8/21 Arturo Servin <aservin@lacnic.net>
>>>=20
>>>>=20
>>>> These prefix are originated by AS31733 which seems to be assigned to th=
e
>>>> same organisation than the ASN, which in turn seems to be you.
>>>>=20
>>>> I can see AS12182 in the path but not originating the route. So I do no=
t
>>>> understand what are your claiming.
>>>>=20
>>>> .as
>>>>=20
>>>>=20
>>>> On 20 Aug 2011, at 23:05, Denis Spirin wrote:
>>>>=20
>>>> Right now there are:
>>>> 46.96.0.0/16
>>>> 83.223.224.0/19
>>>> 94.250.128.0/19
>>>> 94.250.160.0/19
>>>> 188.164.0.0/24
>>>>=20
>>>>=20
>>>>=20
>>=20
>>=20
