[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Routes from AS17299 via AS24246

Subject: Routes from AS17299 via AS24246
From: georgeb at gmail.com (George B.)
Date: Sat, 21 Sep 2013 20:38:29 -0700
In-reply-to: <CAL9jLaY0DGx7G0+ptShW-+cDOqm3ahS5dKQ_OS8UW+U0nVTW2g@mail.gmail.com>
References: <CAJ2iOjSYVY3XAsOPS-f7vRyqS_BrxR+t7frLTBT5=8z0E43ByA@mail.gmail.com> <CAL9jLaY0DGx7G0+ptShW-+cDOqm3ahS5dKQ_OS8UW+U0nVTW2g@mail.gmail.com>

Because it is being announced by the ASN that is owned by the same company
that owns the address block.  Look up the originating ASN,  look up the IP
block.  You don't have to take MY word for it but I am employed by that
company.  That's why.

On Sat, Sep 21, 2013 at 8:23 PM, Christopher Morrow <morrowc.lists at gmail.com
> wrote:

> On Sat, Sep 21, 2013 at 10:41 PM, George B. <georgeb at gmail.com> wrote:
> > 216.231.203.0/24
>
> you don't appear to be on the whois list for that block nor asn... so,
> why would someone accept this block on your say-so? Are you asking as
> a customer of the ASN or as the ASN owner/operator?
>

References:
- Routes from AS17299 via AS24246
  - From: georgeb at gmail.com (George B.)
- Routes from AS17299 via AS24246
  - From: morrowc.lists at gmail.com (Christopher Morrow)

Prev by Date: Routes from AS17299 via AS24246
Next by Date: Routes from AS17299 via AS24246
Previous by thread: Routes from AS17299 via AS24246
Next by thread: Routes from AS17299 via AS24246
Index(es):
- Date
- Thread