Date: Mon, 13 Nov 2000 21:51:26 -0500 From: Rod Taylor <rbt@zort.on.ca> To: chat@gtabug.org, freebsd-stable@freebsd.org Subject: Problems with Firewall???? Message-ID: <3A10A8AE.7AD404EA@zort.on.ca>
next in thread | raw e-mail | index | archive | help
I have an appropriately unique situation... 3 remote boxes all with FreeBSD -STABLE (4.1.1 around the 2nd or so..) using OpenSSH. These are all running IPF (rules available upon request). I'm having problems with SSH locking up the terminal. Ie. CTRL C and CTRL BREAK do absolutly nothing (as does any other key). This occurs when running such things as top, man, dmesg or anything with alot of output fairly quickly (cvs is my primary concern). Now... to make it interesting, this problem only manifests itself on machines behind a nat box. Tested on 4 machines behind both a FreeBSD nat and a Cisco Pix nat. Server was always one of the 3 above, clients were FreeBSD 4.0 to FreeBSD 5.x using OpenSSH. Linux 2.2.16 client (same situation) not using OpenSSH didn't cause this problem, nor do the above listed FreeBSD boxes when NOT behind Nat. Needless to say, it's something weird with IPF, Nat, and SSH on both ends of the connection through the previous two... Removing either IPF or Nat does the trick, as does making one connection non-freebsd (or atleast non-openssh). Please help! I don't like using Linux that much ;) I intend to update to 4.2-Beta on one box behind nat soon to see if that helps (assumming openssh has been touched since 4.1.1). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3A10A8AE.7AD404EA>