Re: cablemodem goes down then internal net goes down

[SLaSH <slash@arbornet.org>]

ssh causes a reverser lookup and since your dns server is offline it
needs to timeout before it does something again.

What I did to fix that is I created my own internal dns server that
serves my house and forwards my non home requests to my ISP. This works
like a champ for me.

/marco

----- Original Message -----
From: "Matthew Garman" <garman@c1858677-a.chmpgn1.il.home.com>
To: "OpenBSD Misc" <misc@openbsd.org>
Sent: Wednesday, October 31, 2001 2:34 PM
Subject: cablemodem goes down then internal net goes down


I'm using my OpenBSD 2.9 system (from CD) as my firewall/NAT box for my
cablemodem.  It's a very straightforward (and probably typical) setup:
OpenBSD box has two NICs, one connected to the cable modem (external
network, i.e. Internet), and the other connected to a switch (internal
network, i.e. 192.168.x.x private LAN).

However, I noticed that if the cablemodem service goes down (which
happens fairly often with crummy @home), I can't ssh into my OpenBSD
system.

My original thought was that the problem was due to DNS loockups being
disabled when the cablemodem is down.  But if I something like "ssh
192.168.0.1" (where 192.168.0.1 is the IP address of the OpenBSD
system), I still have the same problem---ssh just sits there, as though
the server ssh isn't responding.

Any thoughts on this?

Thanks,
Matt

--
Matt Garman, garman@uiuc.edu
I find it truly amazing that social progress exists in light of the vast
number of people who would rather persue shallow, unconsequential
personal goals than try to contribute to civilization.