Network manager immediately disconnects from ad-hoc network

Bug #352777 reported by funkatron
12
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Binary package hint: network-manager

I cannot create an ad-hoc wireless network in networkmanager as it sets up the network and then immediately (within about 1 second) disconnects. The created network will then appear in the menu but attempting to connect to it will have the same effect (connection and immediate disconnection).

I am using the Jaunty beta and my network card uses the rt61pci driver.

Revision history for this message
Alexander Sack (asac) wrote :

reproduce and attach your complete syslog please. also describe how you exactly setup the adhoc network.

Changed in network-manager (Ubuntu):
status: New → Incomplete
Revision history for this message
Lucas Saliés Brum (sistematico) wrote :
Download full text (5.1 KiB)

Same problem here with Atheros AR5001X+ and Ubuntu Jaunty (amd64) Stable.

1 - Click on NetworkManager icon
2- Create new Wireless Network
3- Name: Net (no encription)

module -> ath5k

/var/log/syslog

May 3 00:12:52 sistematico NetworkManager: <info> Activation (ath0) starting connection 'Net'
May 3 00:12:52 sistematico NetworkManager: <info> (ath0): device state change: 3 -> 4
May 3 00:12:52 sistematico NetworkManager: <info> Activation (ath0) Stage 1 of 5 (Device Prepare) scheduled...
May 3 00:12:52 sistematico NetworkManager: <info> Activation (ath0) Stage 1 of 5 (Device Prepare) started...
May 3 00:12:52 sistematico NetworkManager: <info> Activation (ath0) Stage 2 of 5 (Device Configure) scheduled...
May 3 00:12:52 sistematico NetworkManager: <info> Activation (ath0) Stage 1 of 5 (Device Prepare) complete.
May 3 00:12:52 sistematico NetworkManager: <info> Activation (ath0) Stage 2 of 5 (Device Configure) starting...
May 3 00:12:52 sistematico NetworkManager: <info> (ath0): device state change: 4 -> 5
May 3 00:12:52 sistematico NetworkManager: <info> Activation (ath0/wireless): connection 'Net' requires no security. No secrets needed.
May 3 00:12:52 sistematico NetworkManager: <info> Config: added 'ssid' value 'Net'
May 3 00:12:52 sistematico NetworkManager: <info> Config: added 'mode' value '1'
May 3 00:12:52 sistematico NetworkManager: <info> Config: added 'frequency' value '2412'
May 3 00:12:52 sistematico NetworkManager: <info> Config: added 'key_mgmt' value 'NONE'
May 3 00:12:52 sistematico NetworkManager: <info> Activation (ath0) Stage 2 of 5 (Device Configure) complete.
May 3 00:12:52 sistematico NetworkManager: <info> Config: set interface ap_scan to 2
May 3 00:12:52 sistematico NetworkManager: <info> (ath0): supplicant connection state: scanning -> disconnected
May 3 00:12:52 sistematico NetworkManager: <info> (ath0): supplicant connection state: disconnected -> scanning
May 3 00:12:52 sistematico NetworkManager: <info> (ath0): supplicant connection state: scanning -> associating
May 3 00:13:02 sistematico NetworkManager: <info> (ath0): supplicant connection state: associating -> disconnected
May 3 00:13:02 sistematico NetworkManager: <info> (ath0): supplicant connection state: disconnected -> scanning
May 3 00:13:02 sistematico NetworkManager: <info> (ath0): supplicant connection state: scanning -> associating
May 3 00:13:08 sistematico NetworkManager: <info> ath0: link timed out.
May 3 00:13:12 sistematico NetworkManager: <info> (ath0): supplicant connection state: associating -> disconnected
May 3 00:13:12 sistematico NetworkManager: <info> (ath0): supplicant connection state: disconnected -> scanning
May 3 00:13:12 sistematico NetworkManager: <info> (ath0): supplicant connection state: scanning -> associating
May 3 00:13:22 sistematico NetworkManager: <info> (ath0): supplicant connection state: associating -> disconnected
May 3 00:13:22 sistematico NetworkManager: <info> (ath0): supplicant connection state: disconnected -> scanning
May 3 00:13:22 sistematico NetworkManager: <info> (ath0): supplicant connection state: scanning -> a...

Read more...

Revision history for this message
andor (andreasfleig) wrote :

I got the same behaviour at first. Ad-hoc networking would not work if i used "Create New Wireless Network". The solution was to create wireless profiles and install iptables:
- Ad-hoc profiles with manually configured ip addresses did always work. Use "Connect to Hidden Network" to find the preset.
- Ad-hoc with the "Shared to other Computers" method worked after I installed iptables (and dnsmasq).
Since then, "Create New Wireless Network" also works. I guess that "Shared to other Computers" is the default for Ad-hoc networks. In that case, iptables and dnsmasq should be part of the standard distribution.

Jaunty Netbook Remix / Dell Mini 9

Revision history for this message
mrnmart (mrnmart) wrote :

Same problem between:

1 ubuntu 9.04 desktop edition on hp compaq nx7010
02:02.0 Network controller: Intel Corporation PRO/Wireless LAN 2100 3B Mini PCI Adapter (rev 04)
modules:
ipw2100 79536 0
ieee80211 38344 1 ipw2100

and

1 ubuntu 9.04 netbook remix on acer aspire one 150AW
03:00.0 Ethernet controller: Atheros Communications Inc. AR242x 802.11abg Wireless PCI Express Adapter (rev 01)
modules:
ath5k 107520 0
mac80211 217592 1 ath5k
led_class 12036 2 ath5k,acer_wmi
cfg80211 38288 2 ath5k,mac80211

Using the same method than Lucas:

1 - Click on NetworkManager icon
2- Create new Wireless Network
3- Name: Net (no encription)

Its works doing something like this on what i mean client:

/etc/init.d/NetworkManager stop
ifconfig wlan0 down
iwconfig wlan0 essid NAME mode Ad-Hoc ap 00:0c:f1:26:bd:09 key s:XXXXX
ifconfig wlan0 up
ifconfig wlan0 192.168.122.122
route add -net 0.0.0.0 gw 192.168.122.1

And something like this on what i mean server (which haves the internet connection)

/etc/init.d/NetworkManager stop
ifconfig eth1 down
iwconfig eth1 essid NAME mode Ad-Hoc key s:XXXXX
ifconfig eth1 up
ifconfig eth1 192.168.122.1

and making forwarding with eth0, etc...

thank you

Revision history for this message
komputes (komputes) wrote :

@andor - The idea has been suggested to have dnsmasq be included with the distribution. Please visit/comment the following brainstorm to encourage the distribution to ship with dnsmasq and simplify internet sharing:
Idea #15663: Facilitate "Internet Sharing" within Network Manager
http://brainstorm.ubuntu.com/idea/15663/

For more information on how Adhoc networks are currently setup see:
https://help.ubuntu.com/community/WifiDocs/Adhoc

Revision history for this message
Jurgis Pralgauskis (jurgis-pralgauskis) wrote :

I have similar or same problem on Lubuntu 10.04.
But on the same computer with Ubuntu 10.04 creating ad-hock network works ok.

Should I report new bug?

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for network-manager (Ubuntu) because there has been no activity for 60 days.]

Changed in network-manager (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.