On 4 Mar 2016 08:23:22 -0800, in bit.listserv.ibm-main you wrote:

>On Fri, Mar 4, 2016 at 10:16 AM, Leonardo Vaz <[email protected]> wrote:
>
>> That's not a private IP address on his LAN, it is the gist.github.com IP
>> address.
>>
>
>?Correct. But if the LAN authorities think, as he did, that 192.0.0.0/8 is
>all private, instead of just 192.168.0.0/16, then their routing tables may
>be set up to not forward 192.30.252.141 to the outside world, but route the
>entire 192.0.0.0/8 to the inside only. Which would time out. As it did.?
>
My Internet provider uses 192.169.2.1-255 as private for its
customers.  All of the devices on my home network are 192.169.2.n.

Clark Morris
>
>>
>> -----Original Message-----
>> From: IBM Mainframe Discussion List [mailto:[email protected]] On
>> Behalf Of John McKown
>> Sent: Friday, March 04, 2016 11:13 AM
>> To: [email protected]
>> Subject: Re: gist.github.com unreachable [was: RE: rexx and tso alllocate]
>>
>> On Fri, Mar 4, 2016 at 9:50 AM, Farley, Peter x23353 <
>> [email protected]> wrote:
>>
>> > You aren't the only one Steve.  From my employer's network I can't
>> > reach gist.github.com at all, even just the main site never mind John's
>> area.
>> > Trying a tracert to gist.github.com only gets timeouts:
>> >
>> > Tracing route to gist.github.com [192.30.252.141] over a maximum of 30
>> > hops:
>> >
>> >   1     *        *        *     Request timed out.
>> > Etc.
>> >
>> > That DNS address (192.30.252.141) looks odd to me.  I thought
>> > 192.*.*.* was reserved for private local networks, or is that only
>> 192.168.*.*?
>> >
>>
>> ?the private IPv4 address ranges are:? 10.0.0.0/8, 172.16.0.0/12, and
>> 192.168.0.0/16 ref: https://en.wikipedia.org/wiki/Private_network
>>
>> ?I'll almost bet your LAN people are laboring under the same delusion.
>>
>>
>> >
>> > I can reach gist from home though, maybe you can as well.
>> >
>> > Peter
>> >
>>
>>
>> --
>> A fail-safe circuit will destroy others. -- Klipstein
>>
>> Maranatha! <><
>> John McKown
>>
>> ----------------------------------------------------------------------
>> For IBM-MAIN subscribe / signoff / archive access instructions, send email
>> to [email protected] with the message: INFO IBM-MAIN
>>
>> ----------------------------------------------------------------------
>> For IBM-MAIN subscribe / signoff / archive access instructions,
>> send email to [email protected] with the message: INFO IBM-MAIN
>>

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to