On 11/13/06, Stefan Tunsch [EMAIL PROTECTED] wrote:
The problem is that push route options need to be established on both sides
of the tunnel.
If I establish them only on one side, routing does not happen.
Can you please confirm me that there is no way to route traffic from a local
network
I understand exactly what you are saying. The device does not exist until the VPN has actually been created. When I went through the same process 2 days ago I did exactly this.1. Configured/Established the OpenVPN connection2. Went to the assign option for interfaces3. Created an OPENVPN
place...
Regards, Stefan
De: Scott Roeder [mailto:[EMAIL PROTECTED]
Enviado el: lunes, 13 de noviembre de 2006 8:43Para:
discussion@pfsense.comAsunto: Re: [pfSense-discussion] NAT on tun0
used with OpenVPN
I understand exactly what you are saying. The device does not exist
until the VPN has
to the
tunnel also sounds weird.
Regards, Stefan
-Mensaje original-
De: Scott Ullrich [mailto:[EMAIL PROTECTED]
Enviado el: lunes, 13 de noviembre de 2006 17:54
Para: discussion@pfsense.com
Asunto: Re: [pfSense-discussion] NAT on tun0 used with OpenVPN
Tun0 is no longer used
On 11/13/06, Stefan Tunsch [EMAIL PROTECTED] wrote:
I have seen several posts in the forum stating that tun or tap interfaces
should not be assigned to an interface of pfSense.
That any/any firewall rules are automatically created when openvpn client
establishes connection.
And that no traffic
It will be available to add as an interface after you establish the vpn. Once you have done that it will work like any other nat config.On 12 Nov 2006, at 21:29, Stefan Tunsch wrote: Hi! I need to set up outbound natting on tun0. tun0 is the virtual interface created and used by an OpenVPN
: Re: [pfSense-discussion] NAT on tun0
used with OpenVPN
It will be available to add as an interface after you establish the
vpn. Once you have done that it will work like any other nat
config.
On 12 Nov 2006, at 21:29, Stefan Tunsch wrote:
Hi!
I need to set up
outbound natting
