I realized that the tun interface was not present and also in the Rules
menu appeared a new tab named OPT1.
In my case i only have 2 NICS so i don't have and optional third interface.
I'm not sure if the vpn hung
- because there was not rules that explicitly allows such traffic
- because the tun driver was not present
- maybe the silliest: there's not openvpn config file in the firewall :)
I'm checking the openvpn configuration options on their website and
comparing the environment with pfsense.
The openvpn client logs don't say much information reason because i
don't post it. Anyway if you want to see the exit i will do.
Any thoughts will be welcomed ;)
Regards,
jonathan
Scott Ullrich wrote:
device tun # Packet tunnel.
We have tun in the kernel. What exactly is the problem?
On 10/12/05, jonathan gonzalez <[EMAIL PROTECTED]> wrote:
Hi,
i created a openvpn client (client3) using pkcs12 scripts so i can get
of the box a p12 file closed by password to send a client to access the
vpn.
I put this p12 file in my pc and tried to establish a connection to the
pfsense box.
The first part of the negotiation went fine, because the openvpn client
i'm using requested me the p12 passkey to open the p12 file.
Then the connection hangs with the firewall. I didn't look at the
openvpn server configuration yet but i think something is wrong with the
interface TUN becaue i can see it on the ifconfig -a listing.
If somebody have an idea, please tell ;)
Regards,
jonathan
---------------------------------------------------------------------
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
