ad-hoc networks don't work with Intel wireless

I can confirm this exact same behavior on my Dell Inspiron 6000 (also w/ ipw2200 hardware). NM can't create or connect to ad-hoc networks (the association "ball" never goes green, so it doesn't even get to the DHCP step). Associating and acquiring an address using command line tools (iwconfig and dhclient) works fine.

Sorry, I forgot to mention that in my case at least, the ad-hoc network in question had no encryption and was created by an XP SP2 machine using the network creation wizard and the Internet connection sharing service.

Well, I do have the same issue with ipw3945

I have a router running a static wireless ad-hoc network with WEP encryption.

As Wes Morgan, the balls nerver get green.

The interfce run fine using the command line

oops, wrong manipulation, this bug has nothing to do with deluge :D
If somebody knows how to remove this entry, you are welcome

Ooops again.
I can now connect to my wireless network. Dumb me, I was using "WEP 128-bit passphrase" instead of "WEP 64/128-bit ASCII"

Sorry for that

I can confirm this bug in an up-to-date feisty beta install on my laptop.

My setup:

   Thinkpad T41 with ipw2100
   Network-manager 0.6.4-6ubuntu7
   Kernel 2.6.20-15-generic

Added by mistake by chantra. Rejecting.

I think this is because:

root@russ-laptop:/home/russ# iwconfig ath0 mode ad-hoc
Error for wireless request "Set Mode" (8B06) :
    SET failed on device ath0 ; Invalid argument.

I need to do:
root@russ-laptop:/home/russ# wlanconfig ath0 destroy
root@russ-laptop:/home/russ# wlanconfig ath0 create wlandev wifi0 wlanmode adhoc ath0

On Tue, Aug 14, 2007 at 04:51:09AM -0000, Russ Dill wrote:
> I think this is because:
>
> root@russ-laptop:/home/russ# iwconfig ath0 mode ad-hoc
> Error for wireless request "Set Mode" (8B06) :
> SET failed on device ath0 ; Invalid argument.

hmmm ... have you tried to ifconfig ath0 down before setting mode?

 - Alexander

No, this doesn't have any effect. The issue is that madwifi and wlanconfig function very differently from iwconfig.

With wlanconfig and madwifi, there is one master interface, wifi0. On top of that interfaces are added of a particular mode:

AVAILABLE MODES
       ahdemo Create the station in ad-hoc demo (aka pseudo IBSS) mode.

       adhoc Create the station in ad-hoc mode.

       ap Create the VAP in AP mode.

       monitor
              Create the station in monitor mode.

       sta Create the VAP in station mode.

       wds Create the station in WDS mode.

Once an interface (vap) is created, its type cannot be changed. One vap with infrastructure mode is created at module load time by default.

More info on madwifi is on http://madwifi.org

how does this work with /etc/network/interfaces? Can you please paste that config file and attach you syslog that captures a failed networkmanager attempt with ad-hoc networks?

This bug report is being closed because we received no reponse to the last inquiry for information. Please reopen it if this is still an issue in the current Gutsy Gibbon release. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Please don't hesitate to submit bug reports in the future, we really appreciate it. Thanks again!

Still in Hardy, Thinkpad t42, I can connect to any infrastructure networks, but no can't connect to any ad-hoc ones at all (using Windows XP SP2 Internet Connection Sharing)

Confirming this behavior on Hardy with ipw2200, using Wicd to attempt to create and join Ad-Hoc networks.

However, I can remember some times in the past when I have been able to connect to Macbook Ad-Hoc networks. Can't currently though, and definitely cannot create Ad-Hoc networks that others can connect to.

It looks like since we use iwl kernel modules, ad-hoc + wep does not
work anymore.

Well, it does work sometime, but it can take hours before connecting.

On the other hand, non ad-hoc networks wrk like a charm.

On Sat, 2008-06-28 at 15:32 +0000, Motin wrote:

> Confirming this behavior on Hardy with ipw2200, using Wicd to attempt to
> create and join Ad-Hoc networks.
>
> However, I can remember some times in the past when I have been able to
> connect to Macbook Ad-Hoc networks. Can't currently though, and
> definitely cannot create Ad-Hoc networks that others can connect to.
>

--
http://www.debuntu.org

Debuntu deb's repository

Also unable to connect to ad-hoc networks with iwl4965, using Hardy on a Dell XPS M1330. It shows up in KNetworkManager, but it never connects.

did you manage to manually setup an adhoc network (without network manager) using the same chipsets in hardy or intrepid?

No, I'm only using Network Manager to setup/connect-to ad-hoc networks and
both don't work.

On Thu, Sep 11, 2008 at 3:36 AM, Alexander Sack <email address hidden> wrote:

> did you manage to manually setup an adhoc network (without network
> manager) using the same chipsets in hardy or intrepid?
>
> ** Changed in: network-manager (Ubuntu)
> Status: Confirmed => Incomplete
>
> --
> ad-hoc networks don't work with Intel wireless
> https://bugs.launchpad.net/bugs/75358
> You received this bug notification because you are a direct subscriber
> of the bug.
>

reassigning to kernel. afaik, most drivers are just not capable of properly doing ad-hoc.

Cannot create ad-hoc network on Dell Inspiron 700m with stock into wirelss hardware + Hardy

Is this bug about not being able to connect to Ad Hoc networks or not being able to create Ad Hoc networks?

Has all tried using the command line https://help.ubuntu.com/community/WifiDocs/Adhoc and/or Wicd and thus excluded a bug in NetworkManager?

I suggest filing separate bugs for each driver and for each scenario that doesn't work (connecting or creating)

Both connecting and creating Ad-hoc networks don't work. I've also tried
wicd and it didn't do it, seems the problem with NetworkManager, but I'm not
the expert; I'm just reporting something that doesn't work with me.

On Wed, Oct 1, 2008 at 1:53 PM, Motin <email address hidden> wrote:

> Is this bug about not being able to connect to Ad Hoc networks or not
> being able to create Ad Hoc networks?
>
> Has all tried using the command line
> https://help.ubuntu.com/community/WifiDocs/Adhoc and/or Wicd and thus
> excluded a bug in NetworkManager?
>
> I suggest filing separate bugs for each driver and for each scenario
> that doesn't work (connecting or creating)
>
> --
> ad-hoc networks don't work with Intel wireless
> https://bugs.launchpad.net/bugs/75358
> You received this bug notification because you are a direct subscriber
> of the bug.
>

I have the same problem with iwl4965, driver version 1.2.25 and kernel 2.6.24-19 generic.

There has been a bug reported recently at http://intellinuxwireless.org/bugzilla/show_bug.cgi?id=1716. They say the problem is solved for 2.6.27.

hello,

I use the iwl4965 driver on my laptop with kernel 2.6.24-19.
I cannot connect to my ad hoc network from my wireless printer.
I'm not an expert, and I search solution... what make?

Same problem here. Can't create ad-hoc networks. With Intrepid, both balls get green, but then it says 'disconnected'.
Syslog output:
Oct 19 14:23:43 xlaptopx NetworkManager: <WARN> nm_device_activate_stage5_ip_config_commit(): Activation (wlan0) Stage 5 of 5 (IP Configure Commit) start sharing failed.
Oct 19 14:23:43 xlaptopx NetworkManager: <info> (wlan0): device state change: 7 -> 9
Oct 19 14:23:43 xlaptopx NetworkManager: <info> Activation (wlan0) failed for access point (xlapt)
Oct 19 14:23:43 xlaptopx NetworkManager: <info> Marking connection 'xlapt' invalid.
Oct 19 14:23:43 xlaptopx NetworkManager: <info> Activation (wlan0) failed.
Oct 19 14:23:43 xlaptopx NetworkManager: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) complete.
Oct 19 14:23:43 xlaptopx NetworkManager: <info> (wlan0): device state change: 9 -> 3
Oct 19 14:23:43 xlaptopx NetworkManager: <info> (wlan0): deactivating device (reason: 0).
Oct 19 14:23:43 xlaptopx kernel: [ 7031.834797] wlan0: disassociating by local choice (reason=3)
Oct 19 14:23:43 xlaptopx NetworkManager: <WARN> nm_device_wifi_set_ssid(): error setting SSID to '(null)' for device wlan0: Invalid argument
Oct 19 14:23:43 xlaptopx avahi-daemon[5162]: Withdrawing address record for 10.42.46.1 on wlan0.
Oct 19 14:23:43 xlaptopx avahi-daemon[5162]: Leaving mDNS multicast group on interface wlan0.IPv4 with address 10.42.46.1.
Oct 19 14:23:43 xlaptopx avahi-daemon[5162]: Interface wlan0.IPv4 no longer relevant for mDNS.
Oct 19 14:23:43 xlaptopx NetworkManager: <WARN> nm_device_wifi_set_mode(): error setting card wlan0 to mode 2: Device or resource busy

I'm getting this also on the Intrepid beta.

I think it may be related to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/263541

I'm using Ubuntu Intrepid and cannot create an ad-hoc network no matter what.

$iwconfig
lo no wireless extensions.

pan0 no wireless extensions.

eth1 IEEE 802.11 Nickname:""
          Access Point: Not-Associated

eth0 no wireless extensions.

I already tried to install dhcp-server and firestarter firewall to set a ad-hoc network manually in /etc/network/interfaces, however id didn't work either. The wireless card broadcasts fine, it can be detected by the other computer, but the other computer cannot establish the connection.

NM 0.7 does that right now. please look bug 256905 for an outstanding issue in intrepid ... but once the proposed patch/fix is in intrepid this will be fixed for real. for NM please followup on that bug from now on.

i have no indication that there are still iwl specific driver problem.

I am still having this problem on my Lenovo T61. The wireless network will be created, but then I cannot connect to it. My other devices are able to detect and connect to the adhoc network but it doesn't matter since my laptop that created the adhoc network can't connect to itself. This bug has existed for far too long.

Toward the problem of connecting an unsecured AdHoc Network (sg.openwireless.ch in my case) it's still in the 0.7.1 NM as delivered through the Network-Manager ppa for Hardy

But I was able to connect through wpa_supplicant to the network.

Here the wpa_supplicant.conf that made it possible, important was ap_scan=2 and mode=1
__________________________________________

ctrl_interface=/var/run/wpa_supplicant
eapol_version=1
ap_scan=2 #2 für Ad-Hoc Netzwerke wichtig!

 network={
 ssid="www.openwireless.ch"
 scan_ssid=1
 key_mgmt=NONE
 mode=1 #0 managed, 1 ad-hoc, 2 acces point
 }
__________________________________________
Since I use the madwifi-hal-0.10.5.6 I had to put the Card manually in AdHoc mode via
sudo modprobe -r ath_pci
sudo modprobe ath_pci autocreate=adhoc

The connecting via iwconfig was also possible, so it seems, that failure is in fact in NetworkManager.
(As a side note wicd had the same problem)

Problem stil there with ppa Network-Manager 0.7.1 for Hardy.

Hi Christopher,

Please be sure to confirm this issue exists with the latest development release of Ubuntu. ISO CD images are available from http://cdimage.ubuntu.com/releases/ . If the issue remains, please run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 75358

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

Jeremy, he just confirmed that this is a problem in Hardy. Please do not mark this bug as incomplete with your bug script, which will cause it to be invalidated after some time. This bug needs to be fixed, not ignored. Hardy is an LTS release; as far as Hardy's concerned, it doesn't matter whether it's working in Lucid.

Adam,
     While I understand the sentiment, I disagree. I need to understand whether this is still present in Lucid also since Lucid is also an LTS release. The request for further information is an effort to get more current information as a result of testing since there have been updates to Hardy since the earlier debugging. This is also a very relevant request since Ubuntu desires to take in -stable tree updates. This creates an environment where a previously existing problem can become resolved by way of updates. Please don't assume that all I care about is Lucid. I am in a position to work with Intel to address the issue before Lucid drops and to work those fixes into Hardy as well.

Thanks!

~JFo

Thanks for your explanation, Jeremy.

On Tue, Mar 16, 2010 at 21:00, Jeremy Foshee
<email address hidden> wrote:
> Adam,
>     While I understand the sentiment, I disagree. I need to understand whether this is still present in Lucid also since Lucid is also an LTS release. The request for further information is an effort to get more current information as a result of testing since there have been updates to Hardy since the earlier debugging. This is also a very relevant request since Ubuntu desires to take in -stable tree updates. This creates an environment where a previously existing problem can become resolved by way of updates. Please don't assume that all I care about is Lucid. I am in a position to work with Intel to address the issue before Lucid drops and to work those fixes into Hardy as well.
>
> Thanks!
>
> ~JFo
>
> --
> ad-hoc networks don't work with Intel wireless
> https://bugs.launchpad.net/bugs/75358
> You received this bug notification because you are a direct subscriber
> of the bug.
>

The people who test this should try to connect to an AdHoc Network via wpa_supplicant and/or iwconfig so you can see if the problem does also exists in the driver or to confirm, that the bug is only in NM. (What it seems to me, the sg.openwireless.ch site suggests to deactivate NM and to use the iwconfig way.)

For Sorry I can't help check it in Lucid since I don't get my w-lan card to work https://bugs.launchpad.net/ubuntu/+bug/539602
But for Hardy let me know what I can do, eventough I use an Atheros card.

O.k. solved my problem under Lucid

I tested adhoc with NetworkManager and it works. Without any further actions.

Towards Hardy, will there be a ppa for NM 0.8 for Hardy or isn't that possible?

I've just subscribed to this bug since I'm using Lucid on a Toshiba u-400 laptop with Intel wireless - I can't connect to my phone's WIFI Ad-Hoc network. In dmesg I see :
[18263.828668] iwlagn 0000:08:00.0: Microcode SW error detected. Restarting 0x2000000.
[18263.867730] Registered led device: iwl-phy0::radio
[18263.867777] Registered led device: iwl-phy0::assoc
[18263.867820] Registered led device: iwl-phy0::RX
[18263.867860] Registered led device: iwl-phy0::TX
[18263.930687] iwlagn 0000:08:00.0: Microcode SW error detected. Restarting 0x2000000.
<snip - this repeats for the 90 seconds or so that NM tries the connection before disconnecting unsuccessfully>

I'm not sure if it's relevant, but I'll run Jeremy's apport command and attach the results.

Or not. Apport-collect recognises that I didn't file this bug originally so wants me to file a new bug. Can anyone confirm the best course of action here?

Just wanted to keep this rolling towards a fix. I am experiencing the same issue with NM in Lucid. I am able to create an ad-hoc, users are able to connect, but there is no functionality. I am using a T40 with ipw2100

Scaine,
    Apologies for the late reply. Please file a new bug.

Thanks!

~JFo