>Note: the fact that this site was "only intermittently accessibile"
>probably has more to do with the site getting slashdotted or maybe
>its network connection is inherently flakey or maybe it's under a
>Code Red attack or...
>
>The fact that one of the carriers is using a RFC1918 address for
>their internal router communications *probably* isn't the cause of
>this observed behavior.


Understood - I initially did that traceroute because I was
just wondering if I could divine from the various nodenames
whether the server in question had a fat or skinny pipe and
whether it might reasonably be expected to withstand such
spikes in traffic.

>> Isn't it borken for that site to have an address in the 192.168.* range?
>
>Oh, yes, it's "borken".  In fact, this is probably the best term for
>it...  (-:


I think borken is a wonderful term (Nothing Can Go Worng!) and
my usage was intentional.  For further entertainment try saying
    "fgrep -ir borken yourKernelSourceDirectory"


> But is this "broken"?  Well, *very technically*, yes, but in
> general, the fact that they've violated the RFC1918 rules isn't
> precluding you from sending packets to and from this endpoint.


Right.  But even at best it's still evidence that their admin
staff are careless and that you might want to think twice
before doing any important business with them.


>A lot of carriers are using such addresses for their internal routes
>*right now*.


...as do I in my own little home network, though I'm careful to
not allow leakage out onto the Net.


>Of course, the best way to fix all of this is to deploy IPv6...


Ah, yes - IPv6.  One of the many items on my List of Things
to Get a Clue About.   panic!  E_BRAIN_TOO_SMALL !


Regards,
 ----------------------------------------
 Michael O'Donnell     [EMAIL PROTECTED]
 ----------------------------------------


**********************************************************
To unsubscribe from this list, send mail to
[EMAIL PROTECTED] with the following text in the
*body* (*not* the subject line) of the letter:
unsubscribe gnhlug
**********************************************************

Reply via email to