2009/11/9 Kevin Kinsey k...@daleco.biz
Svante Kvarnstrom wrote:
Hello
Have you tried -f (for background) and -N for Do not execute a remote
command? See man 1 ssh for more details.
Svante
Cheers for you!
It was -f without -N that produced the error.
I'm guessing I got down the
Kevin Kinsey k...@daleco.biz wrote:
Greetings!
In order to continue to allow them to connect to an outbound
SMTP box on the LAN, I've done this on their server:
sudo ssh -L thisbox:24:remotebox:52525 m...@remotebox
I wrote a script to get around my home firewall, it doesn't do exactly
as
Greetings!
I have a client who recently dropped static IP service in
favor of a cheaper solution, so they're now on a DHCP network
blocking port 25, etc.
In order to continue to allow them to connect to an outbound
SMTP box on the LAN, I've done this on their server:
sudo ssh -L
Kevin Kinsey a écrit :
Greetings!
I have a client who recently dropped static IP service in
favor of a cheaper solution, so they're now on a DHCP network
blocking port 25, etc.
In order to continue to allow them to connect to an outbound
SMTP box on the LAN, I've done this on their server:
Check out /usr/ports/security/autossh
autossh is a program to start a copy of ssh and monitor it, restarting
it as necessary should it die or stop passing traffic.
The original idea and the mechanism were from rstunnel (Reliable SSH
Tunnel). With this version the method changes: autossh uses ssh
On 9 nov 2009, at 20:36, patrick wrote:
Check out /usr/ports/security/autossh
autossh is a program to start a copy of ssh and monitor it, restarting
it as necessary should it die or stop passing traffic.
The original idea and the mechanism were from rstunnel (Reliable SSH
Tunnel). With this
Hello
Have you tried -f (for background) and -N for Do not execute a remote
command? See man 1 ssh for more details.
Svante
On Nov 9, 2009, at 7:30 PM, Kevin Kinsey wrote:
Greetings!
I have a client who recently dropped static IP service in
favor of a cheaper solution, so they're now on
Svante Kvarnstrom wrote:
Hello
Have you tried -f (for background) and -N for Do not execute a remote
command? See man 1 ssh for more details.
Svante
Cheers for you!
It was -f without -N that produced the error.
I'm guessing I got down the manpage about as far as
-f and didn't go any
