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 through the OpenVPN client on pfSense and back if push options aren't established on both sides? Regards, Stefan -----Mensaje original----- De: Scott Ullrich [mailto:[EMAIL PROTECTED] Enviado el: lunes, 13 de noviembre de 2006 18:53 Para: discussion@pfsense.com Asunto: Re: [pfSense-discussion] NAT on tun0 used with OpenVPN 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 will flow if static routes wheren't defined on > BOTH sides of the tunnel. > > This supposes a problem for me. I have a centralized server > infraestructure where an openvpn server is running. > This server serves connections for different offices. Route push options. Look in the forum where this is also talked about. > If I have to set up static routes on the server to each of these > offices, the first problem I have is that several of them are using > the same network settings. In this scenario, I have to either make > sure each office uses a different network or this will not work. > > It sounds strange not to be able to establish outbound natting on the > tunnel. > > Not being able to establish firewall rules to control who gets access > to the tunnel also sounds weird. This was a known problem going into 1.0. We cannot make everyone happy overnight. Scott -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.409 / Virus Database: 268.14.3/531 - Release Date: 12/11/2006 -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.409 / Virus Database: 268.14.3/531 - Release Date: 12/11/2006
