Date: Thu, 26 Apr 2001 11:36:38 +0100 (BST) From: Jan Grant <Jan.Grant@bristol.ac.uk> To: Robert L Sowders <rsowders@usgs.gov> Cc: G D McKee <freebsd@gdmckee.com>, Questions FreeBSD <freebsd-questions@freebsd.org>, owner-freebsd-questions <owner-freebsd-questions@FreeBSD.ORG> Subject: Re: Connecting to FreeBSD over SSH2 using SecureCRT Message-ID: <Pine.GSO.4.31.0104261134450.28850-100000@mail.ilrt.bris.ac.uk> In-Reply-To: <OFBEAC55ED.3F861A56-ON88256A3A.002E96A9@wr.usgs.gov>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 26 Apr 2001, Robert L Sowders wrote: > Your problem is you are trying to do port forwarding through a firewall. > Setting up port forwarding with SecureCRT is simple between two boxes, but > put the third box between them and now you have a problem. > > To do port forwarding for pop you're telling SecureCRT to connect to the > remote machine at port 110 and locally at localhost port. The firewall is > disallowing connections to port 110. Eh? This doesn't sound like a description of what SSH port forwarding does at all. If there's a firewall between you and the remote machine that allows an ssh connection to the remote machine, AND the remote sshd is configured to allow port forwarding, AND the remote machine can make a connection to the port on the mail machine, then you can forward connections to an arbitrary port on localhost to the remote mail machine via the remote ssh machine. -- jan grant, ILRT, University of Bristol. http://www.ilrt.bris.ac.uk/ Tel +44(0)117 9287163 Fax +44 (0)117 9287112 RFC822 jan.grant@bris.ac.uk __/\____/\_____/\____/|_____________________________________ flatline To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.31.0104261134450.28850-100000>