vpnc and network manager conflict in their requirements for resolv.conf
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
vpnc (Ubuntu) |
New
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: vpnc
I have a desktop running Intrepid 64 bit and a laptop running Jaunty 32 bit. Both are updated to the latest updates. They both recently started having the exact same problem.
vpnc requires /etc/resolv.conf to be a symlink to /etc/resolvconf
network manager requires /etc/resolv.conf to be an actual file
if /etc/resolv.conf is not a symlink, then dns requests do not resolve correctly through the vpn
if /etc/resolv.conf is not a file, then dns requests do not resolve correctly through the vpn
I'm not sure if this is a network manager problem or vpnc problem, because in the past this wasn't an issue. They both worked.
ProblemType: Bug
Architecture: amd64
DistroRelease: Ubuntu 8.10
NonfreeKernelMo
Package: vpnc 0.5.1r275-1ubuntu1
ProcEnviron:
PATH=/
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: vpnc
Uname: Linux 2.6.27-11-generic x86_64
correction to the bug report
this
if /etc/resolv.conf is not a symlink, then dns requests do not resolve correctly through the vpn
if /etc/resolv.conf is not a file, then dns requests do not resolve correctly through the vpn
should say this,
if /etc/resolv.conf is not a symlink, then dns requests do not resolve correctly when using vpnc
if /etc/resolv.conf is not a file, then dns requests do not resolve correctly when using network manager