[122336] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: 192.255.103.x

daemon@ATHENA.MIT.EDU (Hector Herrera)
Thu Feb 11 22:28:30 2010

In-Reply-To: <20100212020851.GA30238@hezmatt.org>
Date: Thu, 11 Feb 2010 19:27:38 -0800
From: Hector Herrera <hectorherrera@gmail.com>
To: nanog@nanog.org
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org

On Thu, Feb 11, 2010 at 6:08 PM, Matthew Palmer <mpalmer@hezmatt.org> wrote=
:
> On Thu, Feb 11, 2010 at 05:30:11PM -0800, Hector Herrera wrote:
>> I'm trying to diagnose an issue with 192.255.103.x
>>
>> As far as I can tell from IANA, the block 192/8 is allocated to ARIN.
>> ARIN does not have a record of 192.255.103 being allocated to anybody.
>>
>> Here is the issue ... the customer insists that is the correct IP and
>> for a few hours yesterday, it was actually working. =A0Their satellite
>> phone can reach it, but we can't see it advertised today from any
>> networks.
>
> Smells to me like their satphone provider could be doing something dodgy.
> More info would be handy: what your customer's relationship to that IP bl=
ock
> is, and what they think should be available at that IP block.
>
> - Matt

According to the customer the IP is at their home network.  They are
in town for a certain large event *cough*fiverings*cough* and they
keep insisting (and their home IT department indicates the IP is
valid).

The customer is now claiming this IP is part of a "hidden" and
"secret" block of IPs ... How can you have hidden IPs?

Are IANA/ARIN/RIPE allowing certain agencies to receive allocations
without disclosing them in whois?

Reverse DNS shows nothing as well.

I think I'm just going to chalk this one up to a made up IP block that
is probably statically routed by their satphone provider.

Thank you all.

--=20
Hector Herrera
President
Pier Programming Services Ltd.


home help back first fref pref prev next nref lref last post