dougs Hello- I upgraded my Windows x64 Openvpn Community Edition software to version 2.4.0 from 2.3.14 and right away I can see that I cannot resolve hostnames within the LAN via VPN. Rolling back to 2.3.14 allows me to successfully resolve hostnames. Here is the client script: dev tun persist-tun persist-key cipher AES-128-CBC auth SHA1 tls-client client resolv-retry infinite remote xxx.xxx.xxx.xxx 1194 udp lport 0 verify-x509-name "FirewallServerCert" name pkcs12 firewall-udp-1194.p12 tls-auth firewall-udp-1194-tls.key 1 ns-cert-type server comp-lzo adaptive passtos block-outside-dns I'm running the default openvpn 2.3 on our pfsense 2.3.2 firewall. I cannot locate the appropriate changes that need to be made in order for DNS resolution to function under 2.4.0. Can someone point me in the right direction? ~Doug
dougs Addendum: On the server side, these are the extra commends I've included to enable routing within the LANs: push "route 192.168.xxx.xxx 255.255.255.0"; push "route 192.168.xxx.xxx 255.255.255.0"; route-method exe; Do these need to be modified for the 2.4 clients? ~Doug
TinCanTech Do not use lport 0 in your client config, instead use nobind As for DNS resolution, that should not be effected by the upgrade. Perhaps using --block-outside-dns is causing some issue ? hard to say without logs. Please see: HOWTO: Request Help !
TiTex i'm using version 2.4 as a client and the server is a quite old version on the router appliance has , i think 2.2 ... and i don't have such issues.
