NetworkManager

Unable to create wireless network

Bug #6734 reported by Christian Elkjaer
8
Affects Status Importance Assigned to Milestone
NetworkManager
Fix Released
Undecided
Unassigned
network-manager (Ubuntu)
Fix Released
Medium
MOTU

Bug Description

Version: 0.5.1-0ubuntu6 (Dapper)

When trying to create a wireless network the program correctly put the network card into ad-hoc mode and setup it up with name (according to iwconfig). However, after only a few seconds it shifts back to whatever setup it had before. For instance being connected to a wireless network.

This program really does a nice job handling network connections in a changing environment. One thing it does not do, however, is setting up and handling a user created wireless network. Perhaps the program needs a special menu where the user can tell when the user created network is no longer needed as to allow the program to return to its smart behaviour.

Revision history for this message
Nafallo Bjälevik (nafallo) wrote :

What distro and version of the package are you using?

Changed in network-manager:
assignee: nobody → nafallo
Revision history for this message
Nafallo Bjälevik (nafallo) wrote :

Oops, don't mind me. I'm rejecting this for upstream and open it for Ubuntu then...

Revision history for this message
Nafallo Bjälevik (nafallo) wrote :

This is not an upstream bug.

Changed in network-manager:
assignee: nafallo → nobody
status: Unconfirmed → Rejected
assignee: nobody → motu
Revision history for this message
j^ (j) wrote :

its even more a bug in the dirver of your wireless card.

Revision history for this message
Arthur Peters (amp) wrote :

I have just spent some time investigating this bug and I thought I'd post my discoveries and logs.

Looking at the code it appears that NetworkManager cannot tell that the ad-hoc network is active and so it is switching to a different network.

I'll post my log file here.

Revision history for this message
Arthur Peters (amp) wrote : A log of the bug

An excerpt from /var/log/daemon.log that shows the ad-hoc net created and then destroyed by NM

Revision history for this message
Sebastien Estienne (sebest) wrote :

is it still valid with nm 0.6.2 ?

Revision history for this message
Christian Elkjaer (c.elkjaer) wrote :

It seems fixed. It will now let me create an adhoc network.

Changed in network-manager:
status: Unconfirmed → Fix Released
Revision history for this message
Xamusk (ronanpaixao) wrote :

I'm also having this problem with NM 0.6.3 in edgy
although this could be a bug with the wireless driver (bcm43xx) -> it's an HP NX6125 laptop
I have tried disabling NM and manually running iwconfig to put in ad-hoc mode, but it also doesn't seem to work.
Even though, NM does detect my Palm TX if I use it to create the ad-hoc network, but it still doesn't make the connection.

Christian Elkjaer (c.elkjaer)
Changed in network-manager:
status: Unconfirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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