[Pkg-utopia-maintainers] Bug#765356: clobbers resolv.conf
intrigeri
intrigeri at debian.org
Sat Nov 1 12:29:34 UTC 2014
Control: tag -1 + moreinfo
Hi Daniel,
Daniel Pocock wrote (14 Oct 2014 12:27:52 GMT) :
> I've rated this serious because it makes the network unusable when it
> happens and it requires a user with root privileges to rectify it.
IMO, given the unusual settings in which the problem happens, severity
should rather be important:
a bug which has a major effect on the usability of a package,
without rendering it completely unusable to everyone.
I'll let the maintainers judge, though.
> NetworkManager successfully connects to a WLAN
> Some time after that, I start an OpenSWAN VPN, for example, with "ipsec
> start"
> The VPN connects and the OpenSWAN log/console output shows something like:
> installing DNS server A.B.C.D to /etc/resolv.conf
> and then almost immediately afterwards, I see some NetworkManager
> entries in daemon.log:
> NetworkManager[5219]: <info> Policy set 'SSID-FOOBAR' (wlan0) as default
> for IPv4 routing and DNS.
> NetworkManager[5219]: <info> Policy set 'SSID-FOOBAR' (wlan0) as default
> for IPv6 routing and DNS.
> and the OpenSWAN entries from resolv.conf are gone again.
> If the VPN is being used for all routing (0.0.0.0/0) then the WLAN DNS
> servers may not be accessible any more and so there are no useful DNS
> servers in resolv.conf and all DNS requests time out.
> Manually adding the VPN DNS back into resolv.conf everything works
Indeed, NetworkManager has no way to guess that it should not touch
resolv.conf in this specific case. Your OpenSWAN VPN isn't managed by
NM, is it?
Could you please try checking "Use this connection only for resources
on its network" in the NM settings of your Wi-Fi connection, and see
if it fixes things for you?
Cheers,
--
intrigeri
More information about the Pkg-utopia-maintainers
mailing list