[122338] in North American Network Operators' Group
Re: 192.255.103.x
daemon@ATHENA.MIT.EDU (Stephen John Smoogen)
Thu Feb 11 22:39:20 2010
In-Reply-To: <c7ef7cf71002111927o796bc03au7be6c50ab28c49ee@mail.gmail.com>
Date: Thu, 11 Feb 2010 20:38:06 -0700
From: Stephen John Smoogen <smooge@gmail.com>
To: Hector Herrera <hectorherrera@gmail.com>
Cc: nanog@nanog.org
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
On Thu, Feb 11, 2010 at 8:27 PM, Hector Herrera <hectorherrera@gmail.com> w=
rote:
> On Thu, Feb 11, 2010 at 6:08 PM, Matthew Palmer <mpalmer@hezmatt.org> wro=
te:
>> 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 b=
lock
>> is, and what they think should be available at that IP block.
>>
>> - Matt
>
> According to the customer the IP is at their home network. =A0They 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.
What it sounds like is one of the following:
1) They got confused with 192.168.xxx.xxx networks when setting it up.
2) They got 192.255.xx.xx from some group that said they could have it
when they couldn't
3) They grabbed it a long time ago and don't remember they did so.
4) Some combination of the above.
In any of the cases, its their local network which is foo-bared one
way or another. Their local routers must have had a route to it and no
longer does.. getting a traceroute from them or something to show
where their router thinks it should go (or if they have an old one to
show where it was.)
> --
> Hector Herrera
> President
> Pier Programming Services Ltd.
>
>
--=20
Stephen J Smoogen.
Ah, but a man's reach should exceed his grasp. Or what's a heaven for?
-- Robert Browning
