network manager do not automaticaly perform dhcp request

From: Karel Kozlik <kk iptel org>
To: networkmanager-list gnome org
Subject: network manager do not automaticaly perform dhcp request
Date: Fri, 28 Nov 2008 18:03:05 +0100

 Hello,

I have configured bridge with static IP address in my/etc/network/interface file. When my computer boots up, the eth0interface have assigned same IP address as the bridge even thought it isconfigured to use dhcp in network manager. After clicking onknetworkmanager icon and then on the eth0 interface in the menu,networkmanager preform dhcp request and fix the address.

When I remove the bridge from /etc/network/interface file, everythingworks fine.


Is it a bug or is my configuration wrong?

I am useing network manager 0.7~~svn20081018t105859-0ubuntu1 fromkubuntu 8.10.


Below is my /etc/network/interface file and output of network manager.
thanks,
Karel

/etc/network/interface file:
----------------------------
auto lo
iface lo inet loopback

auto br0
iface br0 inet static
        address 192.168.111.1
        network 192.168.111.0
        netmask 255.255.255.0
        broadcast 192.168.111.255
        bridge_ports none

output of network manager
-------------------------

root kk-nb:/home/kk# /etc/init.d/NetworkManager stop

* Stopping NetworkManager...[ OK ]

root kk-nb:/home/kk# NetworkManager --no-daemon
NetworkManager: <info>  starting...
NetworkManager: <info>  eth0: driver is 'e1000e'.
NetworkManager: <info>  Found new Ethernet device 'eth0'.

NetworkManager: <info> (eth0): exported as/org/freedesktop/Hal/devices/net_00_17_42_ec_14_fd

NetworkManager: <info>  wlan0: driver is 'iwlagn'.
NetworkManager: <info>  wlan0: driver supports SSID scans (scan_capa 0x01).
NetworkManager: <info>  Found new 802.11 WiFi device 'wlan0'.

NetworkManager: <info> (wlan0): exported as/org/freedesktop/Hal/devices/net_00_16_ea_f0_46_fe

NetworkManager: <info>  (eth0): device state change: 1 -> 2
NetworkManager: <info>  (eth0): bringing up device.
NetworkManager: <info>  (eth0): preparing device.
NetworkManager: <info>  (eth0): deactivating device (reason: 2).

NetworkManager: <info> Unmanaged Device found; state CONNECTED forced.(see http://bugs.launchpad.net/bugs/191889)NetworkManager: <info> Unmanaged Device found; state CONNECTED forced.(see http://bugs.launchpad.net/bugs/191889)

NetworkManager: <info>  (wlan0): device state change: 1 -> 2
NetworkManager: <info>  (wlan0): bringing up device.
NetworkManager: <info>  (wlan0): preparing device.
NetworkManager: <info>  (wlan0): deactivating device (reason: 2).
NetworkManager: <info>  (wlan0): device state change: 2 -> 3
NetworkManager: <info>  (wlan0): supplicant interface state change: 1 -> 2.
NetworkManager: <info>  (eth0): carrier now ON (device state 2)
NetworkManager: <info>  (eth0): device state change: 2 -> 3

NetworkManager: <info> Activation (eth0) starting connection 'Ifupdown(br0)'

NetworkManager: <info>  (eth0): device state change: 3 -> 4

NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device Prepare)scheduled...NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device Prepare)started...NetworkManager: <info> Activation (eth0) Stage 2 of 5 (DeviceConfigure) scheduled...NetworkManager: <info> Activation (eth0) Stage 1 of 5 (Device Prepare)complete.NetworkManager: <info> Activation (eth0) Stage 2 of 5 (DeviceConfigure) starting...

NetworkManager: <info>  (eth0): device state change: 4 -> 5

NetworkManager: <info> Activation (eth0) Stage 2 of 5 (DeviceConfigure) successful.NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP ConfigureStart) scheduled.NetworkManager: <info> Activation (eth0) Stage 2 of 5 (DeviceConfigure) complete.NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP ConfigureStart) started...

NetworkManager: <info>  (eth0): device state change: 5 -> 7

NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP ConfigureGet) scheduled...NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP ConfigureStart) complete.NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP ConfigureGet) started...NetworkManager: <info> Activation (eth0) Stage 5 of 5 (IP ConfigureCommit) scheduled...NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP ConfigureGet) complete.NetworkManager: <info> Activation (eth0) Stage 5 of 5 (IP ConfigureCommit) started...

NetworkManager: <info>  (eth0): device state change: 7 -> 8
NetworkManager: <info>  (eth0): removing resolv.conf from /sbin/resolvconf

NetworkManager: <info> Policy set 'Ifupdown (br0)' (eth0) as defaultfor routing and DNS.

NetworkManager: <info>  Activation (eth0) successful, device activated.

NetworkManager: <info> Activation (eth0) Stage 5 of 5 (IP ConfigureCommit) complete.

>>>>>> At this moment I clicked the knetworkmanager icon as describedabove <<<<<<




NetworkManager: <info>  (eth0): device state change: 8 -> 3
NetworkManager: <info>  (eth0): deactivating device (reason: 0).
NetworkManager: <info>  (eth0): removing resolv.conf from /sbin/resolvconf
-- Error received: Numerical result out of range

-- Original message: type=0x19 length=56 flags=<REQUEST,ACK>sequence-nr=1227889134 pid=4200912NetworkManager: <WARN> check_one_route(): (eth0) error -34 returnedfrom rtnl_route_del(): Sucess


NetworkManager: <info>  Activation (eth0) starting connection 'ethernet'
NetworkManager: <info>  (eth0): device state change: 3 -> 4

NetworkManager: <info>  (eth0): device state change: 4 -> 5

NetworkManager: <info>  (eth0): device state change: 5 -> 7
NetworkManager: <info>  Activation (eth0) Beginning DHCP transaction.
NetworkManager: <info>  dhclient started with pid 6744

NetworkManager: <info> Activation (eth0) Stage 3 of 5 (IP ConfigureStart) complete.

Internet Systems Consortium DHCP Client V3.1.1
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

wmaster0: unknown hardware address type 801
NetworkManager: <info>  DHCP: device eth0 state changed (null) -> preinit
wmaster0: unknown hardware address type 801
Listening on LPF/eth0/00:17:42:ec:14:fd
Sending on   LPF/eth0/00:17:42:ec:14:fd
Sending on   Socket/fallback
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3
DHCPOFFER of 44.177.212.131 from 44.177.212.129
DHCPREQUEST of 44.177.212.131 on eth0 to 255.255.255.255 port 67
DHCPACK of 44.177.212.131 from 44.177.212.129
NetworkManager: <info>  DHCP: device eth0 state changed preinit -> bound

NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP ConfigureGet) scheduled...NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP ConfigureGet) started...

NetworkManager: <info>    address 44.177.212.131
NetworkManager: <info>    prefix 28 (255.255.255.240)
NetworkManager: <info>    gateway 44.177.212.129
NetworkManager: <info>    nameserver '44.177.212.129'
NetworkManager: <info>    domain name 'kufr.cz'

NetworkManager: <info> Activation (eth0) Stage 5 of 5 (IP ConfigureCommit) scheduled...NetworkManager: <info> Activation (eth0) Stage 4 of 5 (IP ConfigureGet) complete.NetworkManager: <info> Activation (eth0) Stage 5 of 5 (IP ConfigureCommit) started...

bound to 44.177.212.131 -- renewal in 1764 seconds.
NetworkManager: <info>  (eth0): device state change: 7 -> 8
NetworkManager: <info>  (eth0): writing resolv.conf to /sbin/resolvconf

NetworkManager: <info> Policy set 'ethernet' (eth0) as default forrouting and DNS.

NetworkManager: <info>  Activation (eth0) successful, device activated.

NetworkManager: <info> Activation (eth0) Stage 5 of 5 (IP ConfigureCommit) complete.

Follow-Ups:
- Re: network manager do not automaticaly perform dhcp request
  - From: Alexander Sack

[Date Prev][Date Next] [Thread Prev][Thread Next] [Thread Index] [Date Index] [Author Index]