Re: Restarting connection with dbus

[Dan Williams <dcbw redhat com>]

On Wed, 2006-10-25 at 14:26 +0200, Christian G�rote:
> On Wed, 2006-10-25 at 08:02 -0400, Dan Williams wrote:
> > 1) first argument is not a DBUS_TYPE_OBJECT_PATH.  Try:
> > 
> >     if props[4] == True:
> >         nm.setActiveDevice(dbus.ObjectPath(op))

I ran you python code and debugged stuff this morning; if you're using
HEAD the 'fallback' variable exists, but on stable it does not.  So for
a wireless device on stable, you only need (1) object path, (2) essid,
(3) security (optional).  Just a note, which doesn't matter to you
because you're doing wired.

> Tried that now. NM prints out the following in syslog:
> 
> Oct 25 14:24:22 bluelagoon dhcdbd: message_handler: message handler not
> found under /com/redhat/dhcp/eth1 for sub-path eth1.dbus.get.host_name
> Oct 25 14:24:22 bluelagoon dhcdbd: message_handler: message handler not
> found under /com/redhat/dhcp/eth1 for sub-path eth1.dbus.get.nis_domain
> Oct 25 14:24:22 bluelagoon dhcdbd: message_handler: message handler not
> found under /com/redhat/dhcp/eth1 for sub-path eth1.dbus.get.nis_servers

These are harmless, and they simply mean that your DHCP server is not
returning any values for NIS servers or a hostname.  But other than
that, NM should reconnect.  Can you post the section of logs from syslog
(or the output if you ran NM with --no-daemon) of where where the
reconnection attempt restarts?

Dan

> I don't know why I get /com/redhat/.. but this seems to be the error to
> me.
> 
> // Christian
>