Re: strange SSH behavior

["Robert Winder" <robertwinder@hetnet.nl>]

Same situation here Nick,  @home cable account etc. Thanks for the
enlightening explanation ;-)

Robert

> Another thing that happened last week was @Home was unplugged.  I
> found at least two systems (so far) out in the field that I didn't
> have easy access to the ISP's DNS server numbers (or in one case, was
> given bogus numbers by the ISP), so I just punched in a publicly
> accessible DNS server I knew of...which happened to be my @Home
> numbers...  Guess what quit working last week?  (fortunately, these
> were not problems the clients would notice...I am more careful on
> stuff the client would be affected by...)
>
> On top of that, it sounds like much of the Detroit area was down for a
> while Saturday night, wasn't just me.  The replacement services for
> @Home seem to be going through some adjustments and changes...one of
> those changes may have been to have their DNS servers quit responding
> to unregistered IPs...(remember, they don't want you running internal
> networks).
>
>
> In short, no, in spite of the fact that I experienced these same
> problems over the last week -- in fact BECAUSE I experienced these
> same problems, I am rather sure the issue is NOT a "mysterious bug in
> OpenBSD", but rather a bunch of misconfigured computers which were not
> showing their problem, and now, due to external changes, are.
>
> Nick.
> --
> http://www.holland-consulting.net