Bug#460200: vpnc does not always call resolvconf -d on terminaison
I have this problem too. I think there is a simple work-around. Just move tun* down in /etc/resolvconf/interface-order. This will put the VPN's nameservers at the end of /etc/resolv.conf, so your normal nameserver will be used first. In fact, I think that's a better default for /etc/resolvconf/interface-order, so I filed a wishlist bug: http://bugs.debian.org/612351 Andrew -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#460200: vpnc does not always call resolvconf -d on terminaison
On 07/02/2011 23:32, Andrew Pimlott wrote: I have this problem too. I think there is a simple work-around. Just move tun* down in /etc/resolvconf/interface-order. This will put the VPN's nameservers at the end of /etc/resolv.conf, so your normal nameserver will be used first. In fact, I think that's a better default for /etc/resolvconf/interface-order, so I filed a wishlist bug: http://bugs.debian.org/612351 It depends a lot on the local config of the VPN you are using. It can be a workaround for some user. It is a not fix for this bug (460200). In my university, it would be an error not to use the VPN provided DNS servers (they have entries for some resources on the VPN that are not visible to other external DNS). It seems more logical to me to ask VPN resolvers first and other next. And /etc/resolvconf/interface-order can be configured by the user to fit its needs if required. Regards, Vincent Andrew -- Vincent Danjean Adresse: Laboratoire d'Informatique de Grenoble Téléphone: +33 4 76 61 20 11ENSIMAG - antenne de Montbonnot Fax:+33 4 76 61 20 99ZIRST 51, avenue Jean Kuntzmann Email: vincent.danj...@imag.fr 38330 Montbonnot Saint Martin -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#460200: vpnc does not always call resolvconf -d on terminaison
Package: vpnc Version: 0.5.1r275-1 Severity: normal I often use vpnc in my university. Here, I connect to an wide-open wifi network (on the subnet 10.0.0.0/8). Then, I can start vpnc (which I do with vpnc-connect) to be able to talk to all internet. * If I stop with vpnc-disconnect, all goes well * If I stop the wifi before vpnc, then vpnc dies and does not call resolvconf to remove the interface. In this case, vpnc-disconnect tells me 'no vpnc found running' and I have to manually type 'resolvconf -d tun0' to remove nameservers linked to the VPN in /etc/resolv.conf The first time it occures, it took me some times before figuring out why /etc/resolv.conf was bad (the tun0 interface were not there anymore with ifconfig) and how to correct it (editing directly /etc/resolv.conf does not work as this file is regenerated at each DHCP lease) So, it would be good if vpnc can call 'resolvconf -d XXX' each time it stops. Best regards, Vincent -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.24-rc5-686 (SMP w/1 CPU core) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages vpnc depends on: ii libc6 2.7-5 GNU C Library: Shared libraries ii libgcrypt11 1.4.0-2LGPL Crypto library - runtime libr Versions of packages vpnc recommends: ii iproute 20071016-3 Professional tools to control the ii resolvconf1.37 nameserver information handler -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
