Re: Adhoc: IPV4 setting 'link-local'
- From: Dan Williams <dcbw redhat com>
- To: Simon Schampijer <simon schampijer de>
- Cc: networkmanager-list gnome org
- Subject: Re: Adhoc: IPV4 setting 'link-local'
- Date: Sun, 08 Aug 2010 01:32:32 -0500
On Wed, 2010-08-04 at 11:43 +0200, Simon Schampijer wrote:
> Hi,
>
> creating a wireless adhoc network setting the property 'method' of the
> setting 'ipv4' to 'link-local' does give me the following error:
> "nm_device_wifi_set_mode(): error setting card wlan0 to mode 2: Device
> or resource busy".
So you see this error on *both* iwl3945 and liberatas_sdio, or just
iwl3945? This is odd, but not completely expected; NM will only
force-set the device back to infrastructure when deactivating. That's
mostly historical as some older drivers couldn't scan well when in adhoc
mode for some reason.
> Using the property 'shared' does work fine. I have tested with nm-applet
> (you can edit the properties of the network in the edits menu as
> nm-applet set the property to 'shared' by default) and tried it from
> sugar over the dbus interface, too.
>
> I see this behavior on one machine with the iwl3945 driver and on the
> other machine using the libertas_sdio driver it does work fine, both
> running the latest NM F11 release
> NetworkManager-0.7.2.997-2.git20100609. So, the issue might be on the
> driver side? What do others think?
Looks like avahi-autoipd is being bitchy. Need to figure out why that
is, but at the moment there isn't any log help for avahi-autoipd at all.
Can you:
mv /usr/sbin/avahi-autoipd /usr/sbin/avahi-autoipd.orig
and put this into a script named /usr/sbin/avahi-autoipd:
#!/bin/bash
avahi-autoipd --debug --syslog $@
make sure you chmod 755 that script, then try the link-local connection
again; you shouldn't need to restart NM. This should cause avahi to
print out anything that's going wrong to /var/log/messages.
Dan
> Regards,
> Simon
>
>
>
> --- Full output ---
>
> Aug 4 11:26:56 laptop NetworkManager: <info> Activation
> (wlan0/wireless) Stage 2 of 5 (Device Configure) successful. Connected
> to wireless network 'mammamia'.
> Aug 4 11:26:56 laptop NetworkManager: <info> Activation (wlan0) Stage
> 3 of 5 (IP Configure Start) scheduled.
> Aug 4 11:26:56 laptop NetworkManager: <info> Activation (wlan0) Stage
> 3 of 5 (IP Configure Start) started...
> Aug 4 11:26:56 laptop NetworkManager: <info> (wlan0): device state
> change: 5 -> 7 (reason 0)
> Aug 4 11:26:56 laptop NetworkManager: <info> Activation (wlan0) Stage
> 3 of 5 (IP Configure Start) started avahi-autoipd...
> Aug 4 11:26:56 laptop NetworkManager: <info> Activation (wlan0) Stage
> 3 of 5 (IP Configure Start) complete.
> Aug 4 11:26:56 laptop NetworkManager: <WARN> aipd_watch_cb(): wlan0:
> avahi-autoipd exited with error code 1
> Aug 4 11:26:56 laptop NetworkManager: <info> (wlan0): device state
> change: 7 -> 9 (reason 22)
> Aug 4 11:26:56 laptop NetworkManager: <info> Activation (wlan0) failed
> for access point (mammamia)
> Aug 4 11:26:56 laptop NetworkManager: <info> Marking connection
> 'mammamia' invalid.
> Aug 4 11:26:56 laptop NetworkManager: <info> Activation (wlan0) failed.
> Aug 4 11:26:56 laptop NetworkManager: <info> (wlan0): device state
> change: 9 -> 3 (reason 0)
> Aug 4 11:26:56 laptop NetworkManager: <info> (wlan0): deactivating
> device (reason: 0).
> Aug 4 11:26:56 laptop NetworkManager: <WARN>
> nm_device_wifi_set_mode(): error setting card wlan0 to mode 2: Device or
> resource busy
> _______________________________________________
> networkmanager-list mailing list
> networkmanager-list gnome org
> http://mail.gnome.org/mailman/listinfo/networkmanager-list
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]