![]() ![]() I wonder if anyone has any idea why this might not be working in pfSense 2.4. The client config pfSense generates is as follows (Public IPs redacted and the key exists and is readable):ĭev ovpnc1 verb 1 dev-type tun dev-node /dev/tun1 writepid /var/run/openvpn_client1.pid #user nobody #group nobody script-security 3 daemon keepalive 10 60 ping-timer-rem persist-tun persist-key proto tcp4-client cipher AES-256-CBC auth SHA256 up /usr/local/sbin/ovpn-linkup down /usr/local/sbin/ovpn-linkdown local x.x.x.x lport 0 management /var/etc/openvpn/client1.sock unix remote y.y.y.y 1194 tcp4 ifconfig 192.168.221.46 192.168.221.45 route 192.168.3.0 255.255.255.0 secret /var/etc/openvpn/cret compress lzo resolv-retry infinite Worse still, if I run the server and client config out of pfSense on two test servers, it works fine, likewise in the previous version of pfSense I was running - I think 2.4.4. If I remove the line from the file and type it at the command line, the same thing happens. The problem is, proto tcp-client is specified in the config (see below). Please specify -proto tcp-server or -proto tcp-client The error message provided is: Options error: -proto tcp is ambiguous in this context. ![]() , teamviewer, launchd, pfsense, crystal reports, attachment. After upgrading pfSense to 2.4.5-RELEASE-p1 I have the peculiar issue of Server configs working perfectly fine but Client configs not so much. batch, awk, numbering, webform, apache 2.4, google search, hadoop, legal. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |