vpnc plugin: order of resolv.conf entries when using Mobile Broadband vs. (W)LAN
- From: Marc Luethi <netztier bluewin ch>
- To: NetworkManager-list gnome org
- Subject: vpnc plugin: order of resolv.conf entries when using Mobile Broadband vs. (W)LAN
- Date: Sun, 18 Jan 2009 14:15:31 +0100
Hi all
I am running Ubuntu 8.10 with ...
network-manager 0.7~~svn20081018t105859-0ubuntu1.8.10.1
network-manager-gnome 0.7~~svn20081020t000444-0ubuntu1.8.10.1
network-manager-vpnc 0.7~~svn20081015t024626-0ubuntu1
... to build a VPN tunnel to the Cisco PIX at my home.
When using a public WLAN hotspot or some other form of (W)LAN
connectivity, /etc/resolv.conf looks like this after the VPN Tunnel is
up:
nameserver <my home DNS IP>
nameserver <hotspot LAN DNS1 IP>
nameserver <hotspot LAN DNS2 IP>
search <my private home domain>
This is exactly I want it to be (VPN connection's DNS listed first), so
I can resolve internal names of my home LAN.
Using the very same VPN connection entry, with either of my two
(swisscom) mobile phones to connect via "Mobile
Broadband", /etc/resolv.conf gets updated in a different way:
nameserver 138.188.101.186 (dnsscm3.swisscom.com)
nameserver 138.188.101.189 (dnsscm4.swisscom.com)
nameserver <my home DNS IP>
search <my private home domain>
This is unlucky, because now the mobile broadband ISPs get queried
first, and of course they wouldn't know anything about my private home
domain - and I can't resolve names in there.
Is this intentional, or can it be configured somewhere?
regards
Marc
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]