Re: nm 0.7 doesn't connect to wired device

[Dan Williams <dcbw redhat com>]

On Fri, 2008-03-28 at 21:21 +0100, Björn Martensen wrote:
> Hi,
> 
> I'm running NM 0.7 from trunk and connecting with the wired interface
> worked before when i was connecting my laptop to my router.
> 
> Now I'm currently visiting my parents and have my laptop connected to
> their DSL modem directly and have updated NM recently to the latest
> version, so maybe something is broken there.
> 
> Anyway, I'm using rp-pppoe to connect to the dsl modem, since NM's pppoe
> connection editor is not yet finished and that works fine.
> However, the nm-applet tries to establish the connection on the wired
> device, but fails to get a network address and gets back to disconnected
> state.
> The connection is there, the interface is there, but it doesn't work
> with NM.
> 
> I don't have specified an IP adress and don't bring up the device with
> Arch's network script, but let it be handled by NM instead.
> 
> Any Ideas why NM can't establish the connection correctly? Is something
> wrong with dhcp or what?

I don't think PPPoE uses DHCP at all, you'll get an IP address assigned
by the ISP from the other side of DSL.  So it's failing because you
can't make the PPPoE connection from inside NetworkManager.  You could
try adding the right bits to GConf though, and see if that works?
That's what Tambet was doing while developing it.

> btw, when I run nm-tool, I get this segfault:

Should be fixed now, I think.  At least I don't get this with latest
SVN.

Dan

> 
> > $ nm-tool 
> > 
> > NetworkManager Tool
> > 
> > State: disconnected
> > 
> > 
> > (process:8359): GLib-GObject-WARNING **: invalid uninstantiatable type `(null)' in cast to `NMDevice'
> > 
> > ** (process:8359): CRITICAL **: nm_device_get_state: assertion `NM_IS_DEVICE (device)' failed
> > 
> > ** (process:8359): CRITICAL **: nm_device_get_iface: assertion `NM_IS_DEVICE (device)' failed
> > - Device: (null) ----------------------------------------------------------------
> > 
> > ** (process:8359): CRITICAL **: nm_device_get_driver: assertion `NM_IS_DEVICE (device)' failed
> >   Driver:            (unknown)
> >   Active:            no
> > 
> > ** (process:8359): CRITICAL **: nm_device_get_capabilities: assertion `NM_IS_DEVICE (device)' failed
> > 
> >   Capabilities:
> >     Supported:       no
> > 
> > 
> > Segmentation fault
> 
> could this be causing the problem?
> 
> I don't have a wireless network here atm, but that worked fine the last time I tried (3 days ago or so).
> Unfortunately, the iwl3945 never worked for ad-hoc for me, so I can't try that either.
> The network is never created, NM always gets back to disconnected state. That's another issue,
> but maybe you can tell me, if it _should_ be able to create a new wireless network with that driver in
> in general ;)
> 
> 
> Greetings,
> Björn
> 
> _______________________________________________
> NetworkManager-list mailing list
> NetworkManager-list gnome org
> http://mail.gnome.org/mailman/listinfo/networkmanager-list