Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 13 Aug 2002 19:29:48 -0400
From:      "Moti Levy" <moti@flncs.com>
To:        "Jim McAtee" <jmcatee@mediaodyssey.com>, "freebsd-questions" <freebsd-questions@freebsd.org>, "Sicco Miedema" <s.miedema@home.nl>
Subject:   Re: FreeBSD as VPN server
Message-ID:  <023901c24321$5689fa20$f901a8c0@win>
References:  <5.1.0.14.0.20020813214645.024a99a8@192.168.1.1> <5.1.0.14.0.20020813234000.024f5000@192.168.1.1>

next in thread | previous in thread | raw e-mail | index | archive | help

I use ssh port forwarding all the time to connect to terminal services
behind a fbsd firewall
it's simple and you already have ssh running anyway .

call me lazy ;-)


----- Original Message -----
From: "Sicco Miedema" <s.miedema@home.nl>
To: "Jim McAtee" <jmcatee@mediaodyssey.com>; <freebsd-questions@FreeBSD.ORG>
Sent: Tuesday, August 13, 2002 5:54 PM
Subject: Re: FreeBSD as VPN server


> At 14:16 13-8-2002 -0600, Jim McAtee wrote:
>
>
> >If you're just going to connect to a Win machine running terminal
services,
> >why the need for a VPN?  Terminal services already offers encryption.
>
> I tried that but I can't get the port to forward to my windows machine.
> I typed:
>    #natd -redirect_port 192.168.1.2:3389 3389
> causes error: aliasing not given, so i did some research and typed:
>   #natd -redirect_port 192.168.1.2:3389 3389 -a 213.51.240.XXX  (XXX =
last
> three numbers of external IP)
> gives error address already in use
>
>
> It might be a simple task for some BSD experts but i've been breaking my
> head on this one all day
>
> Sicco Miedema
> *well tomorrow is another day :)*
>
>
>
>
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-questions" in the body of the message
>
>



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?023901c24321$5689fa20$f901a8c0>