I'm using diferent ports. For the server is the default UDP port, as for
the client connection to site X, they have their server on 55555 UDP
port, so it's not from that... And yes, I'm using the latest stable
version of pfSense.
I thought too that each deamon would create his own tun device, but that
doesn't happen :\ It's really weird, the last service I start (be it
client or server) takes control of the only tun device I have, and the
service that lost that control doesn-t even notice that!!!
But I'll try to put the nobind option in my server and client
configuration, and latter will try also the option I've mentioned in the
last mail, too bad I can only do that after 6pm GMT, but hey, let's wait
and see...
Paul Mansfield escreveu:
David Meireles wrote:
Yes, but I want to use a pfsense box to act both as OpenVPN Server
and OpenVPN Client. For example, the box is now acting as a server,
althrough I have the client connection to site X configurated, but
not enabled... If I enable this connection, I immediately loose the
Server, because both are using the same interface (tun0). Isn't there
a way to use, maybye, tun0 for server ans tun1 for client!?
each ovpn daemon creates its own tun device.
there isn't actually that much difference between a server and a
client, except the latter initiates the connect, the former waits.
create multiple servers and clients on different ports - be sure to
set the source port differently for the client or consider using the
floating port option "nobind".
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
