Bug#460200: vpnc does not always call resolvconf -d on terminaison

2011-02-07 Thread Vincent Danjean
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 f

Bug#460200: vpnc does not always call resolvconf -d on terminaison

2011-02-07 Thread Andrew Pimlott
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/resolvcon

Bug#460200: vpnc does not always call resolvconf -d on terminaison

2008-01-11 Thread Vincent Danjean
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