The problem I have is similar. In my case, my VPN provides an internal search domain "blah.local" and an internal DNS server for answering queries about internal server addresses, i.e. the servers inside the VPN where I do my work.
With resolvconf package installed, VPN DNS settings never appear in /etc/resolv.conf, so I cannot look up any VPN servers by name. With resolvconf package NOT installed, /etc/resolv.conf is initially replaced with the information from VPN, and this works for a while, until the DHCP lease of my base network connection gets renewed, and then /etc/resolv.conf is replaced again by the standard network info, and I can no longer look up the VPN servers by name. It is pretty essential for normal VPN functionality to use the DNS information provided by the VPN. The VPN DNS server should be configured to answer queries about the internal VPN search domain and also proxy for the rest of the world. Otherwise, you have to know the IP addresses for every host on the VPN that you want to connect to, or use /etc/hosts, or some LDAP or windoze service, or NIS or something. Using `/etc/init.d/openvpn start` works with a conf file in there, and seems to merge the local connection DNS with the VPN search domain and DNS. Hmm I cannot see wireless anymore in NM, I have to use init.d when I use the control panel to turn on wireless. Mark -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
