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. Their satellite phone can reach it, but we can't see it advertised today from any networks. The ip block 192.255.0.0/16 is allocated to "VARIOUS RIRs" under a text file I found at potaroo.net I tried a few looking glass sites, but I still can't find a route to the advertising router. So ... any ideas how to go about finding out the source of the routing block? -- Hector Herrera
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. Their 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 block is, and what they think should be available at that IP block. - Matt
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. Their 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 block 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. -- Hector Herrera President Pier Programming Services Ltd.
On Thu, Feb 11, 2010 at 8:27 PM, Hector Herrera <hectorherrera@gmail.com> wrote:
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. Their 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 block 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.
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.
-- Stephen J Smoogen. Ah, but a man's reach should exceed his grasp. Or what's a heaven for? -- Robert Browning
On Thu, Feb 11, 2010 at 07:27:38PM -0800, Hector Herrera wrote:
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. ?Their 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 block is, and what they think should be available at that IP block.
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?
Pfft, that's just code for "we picked a block at random". See also: 1/8.
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.
Indeed. - Matt
On Thu, Feb 11, 2010 at 7:30 PM, Hector Herrera <hectorherrera@gmail.com> wrote:
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.
I can infer very strongly that the block has probably not been allocated, or if it was, has not been properly listed in the directory as allocated yet. Look at the DNS delegation of the reverse DNS. Y.arin.net replies NXDOMAIN for the 192.255.103.in-addr.arpa zone with authority, indicating no rDNS delegation. ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 16598 ;; flags: qr aa rd; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0 The RADB and RIS are good sources to query also. http://www.ris.ripe.net/mt/prefixdashboard.html?prefix=192.255.103.0 "This prefix does not appear to be announced. It was not seen by RIS in the last 3 months. See below for related prefixes. Related (overlapping) prefixes seen by RIS in the last 30 days No prefixes found. This prefix has 0 visibility. " -- -J
On Thu, Feb 11, 2010 at 9:12 PM, James Hess <mysidia@gmail.com> wrote:
On Thu, Feb 11, 2010 at 7:30 PM, Hector Herrera <hectorherrera@gmail.com> wrote:
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.
I can infer very strongly that the block has probably not been allocated, or if it was, has not been properly listed in the directory as allocated yet.
Look at the DNS delegation of the reverse DNS. Y.arin.net replies NXDOMAIN for the 192.255.103.in-addr.arpa zone with
<cough>103.255.192.in-addr.arpa.</cough> (though Y still gives back NXdomain, and points NS at chia.arin.net, for 192.in-addr.arpa.) -chris
participants (5)
-
Christopher Morrow -
Hector Herrera -
James Hess -
Matthew Palmer -
Stephen John Smoogen