James Yonan said the following on 7/9/2004 8:40 PM:
Try running both sides at --verb 4. You should see debug messages showing the
client asking the server for an ifconfig-pool address and the server
responding. If that doesn't work, then try with the sample configs in the
2.0 release notes.*Not exactly sure what to be looking for in the debug messages, but the
configs are very close to being identical to those in the release
notes. Here they are:
ifconfig-pool 192.168.39.240 192.168.39.249
push "route 172.31.4.0 255.255.255.0 192.168.39.10"
push "ping 10"
push "ping-restart 60"
lport 55555 #
 lport has been defined on the client side because of the possibility
of multiple clients connecting to the server from the same remote LAN
and Public IP address
Currently the client(s) are getting 'DHCP-ed' from a source /other than/
the OpenVPN server. In doing so, the default gateway as well as the
nameserver(s) are being passed to the client, which renders their local
Internet connections inoperable.
The entire client and server debug logs can be viewed here: