@mubtcez: to use the OpenVPN server's pushed DNS servers, add this to
your .conf file:
script-security 2
up /etc/openvpn/update-resolv-conf
down /etc/openvpn/update-resolv-conf
If you want to use your own DNS servers, add the above plus a line for
each DNS server:
dhcp-option DN
Actually, I'd like to retract part of what I said above. Via tcpdump, I
was able to confirm that --push on the server for "dhcp-option DNS ..."
and "redirect-gateway" ARE ACTUALLY WORKING, though the changes are not
visible in /etc/resolv.conf. Rather, they are updated in dnsmasq and
resolv.conf p
Whether this is a bug or feature request, I don't know, but to be sure,
it is possible to do this with a .conf file and "sudo service openvpn
start" and not possible to do it via network-manager-openvpn (unless you
count disabling dnsmasq--I'm curious what side effects this has). As
described in t
Public bug reported:
Binary package hint: openvpn
When generating a new certificate, if the variables CA_EXPIRE or
KEY_EXPIRE put the expiration date after 19-Jan-2038, then pkitool will
create a certificate which expires around 1902 and also corrupt
keys/index.txt so that the next certificate to
This one bit me when I deleted my old ssh keys and generated new ones on
Karmic. Both work-arounds worked for me (I tried them
individually)--adding the line "export SSH_AUTH_SOCK=0" to ~/.bashrc OR
running "ssh-add ~/.ssh/id_rsa". I like the latter better because it
doesn't require extra work to
