Network manager & DNS
 

Hi,

Squeeze 6.05 amd64, I had backports enabled and made the mistake of
updating to the latest back port kernel amongst other updates a few days
ago.


When I rebooted I had no internet connectivity so I removed the back
port kernel thinking it was that.


But now with my original 2.6.32-5-amd64 kernel every time I reboot,
/etc/resolve.conf is empty and I have to enter my DNS server by hand.


If I can remember correctly I do not use network manger but placed my
entries in the interfaces file.


Can't figure this out from Google?

Cheers
Marek



--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Archive: 505EC592.8000601@pawinski.co.za">http://lists.debian.org/505EC592.8000601@pawinski.co.za

Network manager & DNS
 

On Sun, Sep 23, 2012 at 4:17 AM, Marek Pawinski <linux@pawinski.co.za> wrote:
>
> Squeeze 6.05 amd64, I had backports enabled and made the mistake of updating
> to the latest back port kernel amongst other updates a few days ago.
>
> When I rebooted I had no internet connectivity so I removed the back port
> kernel thinking it was that.
>
> But now with my original 2.6.32-5-amd64 kernel every time I reboot,
> /etc/resolve.conf is empty and I have to enter my DNS server by hand.
>
> If I can remember correctly I do not use network manger but placed my
> entries in the interfaces file.

What are the contents of "/etc/network/interfaces" and
/etc/NetworkManager/NetworkManager.conf"?

Do you have any scripts in "/etc/NetworkManager/dispatcher.d/"?


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: http://lists.debian.org/CAOdo=Syz_zZ9YK+cWM7vrdUpKGvkt0UBFiueeD5Zf-39x+FJ9w@mail.gmail.com

Network manager & DNS
 

On 23/09/2012 13:06, Tom H wrote:

On Sun, Sep 23, 2012 at 4:17 AM, Marek Pawinski<linux@pawinski.co.za> wrote:

Squeeze 6.05 amd64, I had backports enabled and made the mistake of updating
to the latest back port kernel amongst other updates a few days ago.

When I rebooted I had no internet connectivity so I removed the back port
kernel thinking it was that.

But now with my original 2.6.32-5-amd64 kernel every time I reboot,
/etc/resolve.conf is empty and I have to enter my DNS server by hand.

If I can remember correctly I do not use network manger but placed my
entries in the interfaces file.

What are the contents of "/etc/network/interfaces" and
/etc/NetworkManager/NetworkManager.conf"?

Do you have any scripts in "/etc/NetworkManager/dispatcher.d/"?




Here they are, three of them:

cat /etc/network/interfaces
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

# The primary network interface
#allow-hotplug eth0
#NetworkManager#iface eth0 inet dhcp

# The primary network interface
auto eth0
iface eth0 inet static
address 192.168.2.106
gateway 192.168.2.1
netmask 255.255.255.0
network 192.168.2.0
broadcast 192.168.2.255


cat /etc/NetworkManager/NetworkManager.conf
[main]
plugins=ifupdown,keyfile

[ifupdown]
managed=false


cat /etc/NetworkManager/dispatcher.d/01ifupdown
#!/bin/sh -e
# Script to dispatch NetworkManager events
#
# Runs ifupdown scripts when NetworkManager fiddles with interfaces.
# See NetworkManager(8) for further documentation of the dispatcher events.

if [ -z "$1" ]; then
echo "$0: called with no interface" 1>&2
exit 1;
fi

# Fake ifupdown environment
export IFACE="$1"
export LOGICAL="$1"
export ADDRFAM="NetworkManager"
export METHOD="NetworkManager"
export VERBOSITY="0"

# Run the right scripts
case "$2" in
up|vpn-up)
export MODE="start"
export PHASE="post-up"
exec run-parts /etc/network/if-up.d
;;
down|vpn-down)
export MODE="stop"
export PHASE="post-down"
exec run-parts /etc/network/if-post-down.d
;;
# pre-up/pre-down not implemented. See
# https://bugzilla.gnome.org/show_bug.cgi?id=387832
# pre-up)
# export MODE="start"
# export PHASE="pre-up"
# exec run-parts /etc/network/if-pre-up.d
# ;;
# pre-down)
# export MODE="stop"
# export PHASE="pre-down"
# exec run-parts /etc/network/if-down.d
# ;;
hostname|dhcp4-change|dhcp6-change)
# Do nothing
;;
*)
echo "$0: called with unknown action `$2'" 1>&2
exit 1
;;
esac



--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Archive: 505F1184.7050401@pawinski.co.za">http://lists.debian.org/505F1184.7050401@pawinski.co.za

Network manager & DNS
 

On Sun, Sep 23, 2012 at 9:41 AM, Marek Pawinski <linux@pawinski.co.za> wrote:
> On 23/09/2012 13:06, Tom H wrote:
>> On Sun, Sep 23, 2012 at 4:17 AM, Marek Pawinski<linux@pawinski.co.za>
>> wrote:
>>>
>>> Squeeze 6.05 amd64, I had backports enabled and made the mistake of
>>> updating to the latest back port kernel amongst other updates a few
>>> days ago.
>>>
>>> When I rebooted I had no internet connectivity so I removed the back
>>> port kernel thinking it was that.
>>>
>>> But now with my original 2.6.32-5-amd64 kernel every time I reboot,
>>> /etc/resolve.conf is empty and I have to enter my DNS server by hand.
>>>
>>> If I can remember correctly I do not use network manger but placed my
>>> entries in the interfaces file.
>>
>> What are the contents of "/etc/network/interfaces" and
>> /etc/NetworkManager/NetworkManager.conf"?
>>
>> Do you have any scripts in "/etc/NetworkManager/dispatcher.d/"?
>
> cat /etc/network/interfaces
> auto lo
> iface lo inet loopback
>
> # The primary network interface
> #allow-hotplug eth0
> #NetworkManager#iface eth0 inet dhcp
>
> # The primary network interface
> auto eth0
> iface eth0 inet static
> address 192.168.2.106
> gateway 192.168.2.1
> netmask 255.255.255.0
> network 192.168.2.0
> broadcast 192.168.2.255
>
> cat /etc/NetworkManager/NetworkManager.conf
> [main]
> plugins=ifupdown,keyfile
>
> [ifupdown]
> managed=false

Short answer: Change "managed=false" to "managed=true" in
"/etc/NetworkManager/NetworkManager.conf" for NM to manage eth0.

Longer answer: NM commented out eth0 in order to control it (given
"managed=false"). You then configured eth0 in
"/etc/network/interfaces" (by the way, you don't need the "network..."
and "broadcast..." lines) so between "managed=false" being set and
"/etc/init.d/networking" being disabled, eth0 isn't brought up by
either NM or ifupdown.


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: http://lists.debian.org/CAOdo=Sx1+iv5FS3pyTDT0a+B0r4Zxhn9kXD1zN3EfM96KHNeY g@mail.gmail.com

Network manager & DNS
 

On 23.09.2012 15:41, Marek Pawinski wrote:
> On 23/09/2012 13:06, Tom H wrote:
>> On Sun, Sep 23, 2012 at 4:17 AM, Marek Pawinski<linux@pawinski.co.za> wrote:
>>> Squeeze 6.05 amd64, I had backports enabled and made the mistake of updating
>>> to the latest back port kernel amongst other updates a few days ago.
>>>
>>> When I rebooted I had no internet connectivity so I removed the back port
>>> kernel thinking it was that.
>>>
>>> But now with my original 2.6.32-5-amd64 kernel every time I reboot,
>>> /etc/resolve.conf is empty and I have to enter my DNS server by hand.
>>>
>>> If I can remember correctly I do not use network manger but placed my
>>> entries in the interfaces file.
>> What are the contents of "/etc/network/interfaces" and
>> /etc/NetworkManager/NetworkManager.conf"?
>>
>> Do you have any scripts in "/etc/NetworkManager/dispatcher.d/"?
>>
>>
>
> Here they are, three of them:
>
> cat /etc/network/interfaces
> # This file describes the network interfaces available on your system
> # and how to activate them. For more information, see interfaces(5).
>
> # The loopback network interface
> auto lo
> iface lo inet loopback
>
> # The primary network interface
> #allow-hotplug eth0
> #NetworkManager#iface eth0 inet dhcp
>
> # The primary network interface
> auto eth0
> iface eth0 inet static
> address 192.168.2.106
> gateway 192.168.2.1
> netmask 255.255.255.0
> network 192.168.2.0
> broadcast 192.168.2.255
>
>
> cat /etc/NetworkManager/NetworkManager.conf
> [main]
> plugins=ifupdown,keyfile
>
> [ifupdown]
> managed=false

Do you have any other network interfaces besides eth0?
If eth0 is your only one and it is *not* managed by NM, then NM
shouldn't touch /etc/resolv.conf and this would be a valid bug.
In that case please file a bug against the network-manager package.
Please follow the advice at [1] and include the logs for NM.

Thanks,
Michael

[1] https://live.gnome.org/NetworkManager/Debugging
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

Network manager & DNS
 

On Sun, 23 Sep 2012 10:17:22 +0200, Marek Pawinski wrote:

> Squeeze 6.05 amd64, I had backports enabled and made the mistake of
> updating to the latest back port kernel amongst other updates a few days
> ago.

Check whether along those updates it was also installed the "resolvconf"
package and if yes, remove it.

> When I rebooted I had no internet connectivity so I removed the back
> port kernel thinking it was that.
>
> But now with my original 2.6.32-5-amd64 kernel every time I reboot,
> /etc/resolve.conf is empty and I have to enter my DNS server by hand.
>
> If I can remember correctly I do not use network manger but placed my
> entries in the interfaces file.

If you aren't using N-M neither DHCP, there's only one package I can
think of which can overwrite the "/etc/resolv.con file", and that's
resolvconf.

> Can't figure this out from Google?

I would ensure that:

1/ N-M service is not started ("ps aux | grep -i networkmanager").

2/ "Resolvconf" package was not installed inadvertently (it usually comes
unnoticed as a "recommended" package).

Greetings,

--
Camaleón


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: http://lists.debian.org/k3n9bj$lsj$8@ger.gmane.org

Network manager & DNS
 

On 23/09/2012 16:47, Tom H wrote:

Short answer: Change "managed=false" to "managed=true" in
"/etc/NetworkManager/NetworkManager.conf" for NM to manage eth0.


Thanks that did the trick.


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Archive: 505F44E5.6040106@pawinski.co.za">http://lists.debian.org/505F44E5.6040106@pawinski.co.za

Network manager & DNS
 

On Sun, Sep 23, 2012 at 1:20 PM, Marek Pawinski <linux@pawinski.co.za> wrote:
> On 23/09/2012 16:47, Tom H wrote:
>>
>> Short answer: Change "managed=false" to "managed=true" in
>> "/etc/NetworkManager/NetworkManager.conf" for NM to manage eth0.
>
> Thanks that did the trick.

You're welcome.


--
To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: http://lists.debian.org/CAOdo=SzUy5BmT=QgCf+gbMEqxMCrL_z=ALTrnfMKNPCtBi6os w@mail.gmail.com