You learn something new every day:
"D-Bus interface to the ISC DHCP client dhcdbd provides a D-Bus interface to dhclient, the DHCP client from ISC, so applications such as NetworkManager can query and control dhclient. This allows an application-neutral interface for such operations." Whether the messages you are seeing are significant or fatal is unknown to me. FWIW I have seen windows do this too. Spent a frustrating hour or two recently getting a friend's teenager's wireless going. Ended up deleting all the settings and starting from scratch. The same seems to often be the way with network manager. Other alternative? set up a /etc/network/interfaces file for each location and have a script to swap tham over and do /etc/init.d/network restart (PS check those filenames, I am working from alzheimers). On Fri, Feb 20, 2009 at 1:41 PM, Roger Searle <[email protected]> wrote: > Wireless hardware: > 01:02.0 Network controller: Intel Corporation PRO/Wireless 2200BG Network > Connection (rev 05) > > Nothing that I can see in the logs that help, this being of the closest > relevance: > > dmesg: > [ 53.150976] ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready > [ 53.211164] NET: Registered protocol family 17 > [ 54.442580] ieee80211_crypt: registered algorithm 'CCMP' > [ 124.569329] eth1: no IPv6 routers present > [ 142.547930] ADDRCONF(NETDEV_UP): eth1: link is not ready > [ 142.717830] ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready > [ 142.740940] ieee80211_crypt: registered algorithm 'TKIP' > [ 143.351586] eth1: no IPv6 routers present > [ 145.828294] eth1: no IPv6 routers present > > /var/log/messages: > eb 20 10:36:46 acer4150 dhcdbd: message_handler: message handler not found > under /com/redhat/dhcp/eth1 for sub-path eth1.dbus.get.reason > Feb 20 10:36:48 acer4150 kernel: [ 53.150976] ADDRCONF(NETDEV_CHANGE): > eth1: link becomes ready > Feb 20 10:36:48 acer4150 kernel: [ 53.211164] NET: Registered protocol > family 17 > Feb 20 10:41:32 acer4150 dhcdbd: message_handler: message handler not found > under /com/redhat/dhcp/eth1 for sub-path eth1.dbus.get.reason > Feb 20 10:41:32 acer4150 kernel: [ 142.547930] ADDRCONF(NETDEV_UP): eth1: > link is not ready > Feb 20 10:41:34 acer4150 kernel: [ 142.717830] ADDRCONF(NETDEV_CHANGE): > eth1: link becomes ready > Feb 20 10:41:48 acer4150 dhcdbd: message_handler: message handler not found > under /com/redhat/dhcp/eth1 for sub-path eth1.dbus.get.host_name > Feb 20 10:41:48 acer4150 dhcdbd: message_handler: message handler not found > under /com/redhat/dhcp/eth1 for sub-path eth1.dbus.get.domain_name > Feb 20 10:41:48 acer4150 dhcdbd: message_handler: message handler not found > under /com/redhat/dhcp/eth1 for sub-path eth1.dbus.get.nis_domain > Feb 20 10:41:48 acer4150 dhcdbd: message_handler: message handler not found > under /com/redhat/dhcp/eth1 for sub-path eth1.dbus.get.nis_servers > Feb 20 10:41:48 acer4150 dhcdbd: message_handler: message handler not found > under /com/redhat/dhcp/eth1 for sub-path eth1.dbus.get.interface_mtu > >
