166217 – NetworkManager won't connect to AdHoc network

Bug 166217 - NetworkManager won't connect to AdHoc network

Summary: NetworkManager won't connect to AdHoc network

Status:	RESOLVED DUPLICATE of bug 153232

Alias:	None

Product:	SUSE Linux 10.1
Classification:	openSUSE
Component:	Network (show other bugs)
Version:	RC 1
Hardware:	i586 Other

Priority:	P5 - None Severity: Critical (vote)
Target Milestone:	---
Assignee:	Robert Love
QA Contact:	E-mail List

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Clone This Bug

Reported:	2006-04-14 09:50 UTC by Forgotten User mbQyAD5r4K
Modified:	2006-04-18 00:32 UTC (History)
CC List:	1 user (show)

See Also:
Found By:	Other
Services Priority:
Business Priority:
Blocker:	---
Marketing QA Status:	---
IT Deployment:	---

Attachments
netman-1.png (23.02 KB, image/png) 2006-04-18 00:24 UTC, Forgotten User mbQyAD5r4K	Details
netman-2.png (15.79 KB, image/png) 2006-04-18 00:29 UTC, Forgotten User mbQyAD5r4K	Details
netman-3.png (8.41 KB, image/png) 2006-04-18 00:30 UTC, Forgotten User mbQyAD5r4K	Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Forgotten User mbQyAD5r4K 2006-04-14 09:50:48 UTC

I can't make NetworkManager connect to my WEP "protected" AdHoc network from laptop with ipw2100 wifi card. When configured manually from command line with iwconfig it works just fine. Or am I just too dumb to find the Managed/AdHoc checkbox?

FWIW this is the output of iwconfig while NetworkManager says it tries to connect to the network:

eth1      unassociated  ESSID:off/any  Nickname:"ipw2100"
          Mode:Managed  Channel=0  Access Point: Not-Associated
          Bit Rate=0 kb/s   Tx-Power:16 dBm
          Retry min limit:7   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality:0  Signal level:0  Noise level:0
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

Comment 1 JP Rosevear 2006-04-17 12:07:42 UTC

Are you using the "Connect to other wireless network" if you left click on the icon in the notification area? (Under gnome).

Comment 2 Forgotten User mbQyAD5r4K 2006-04-18 00:23:18 UTC

I use KDE, click on the systray NetManager icon and either chose the shown "logix" network (see first screenshot) or go with "Connect to other wireless networks" and fill "logix" as the name. Then supply the correct (yes, I'm sure) password (see 2nd screenshot) and the it fails (see the last s/shot).

Comment 3 Forgotten User mbQyAD5r4K 2006-04-18 00:24:41 UTC

Created attachment 78728 [details]
netman-1.png

This is the default network that I try to connect to.

Comment 4 Forgotten User mbQyAD5r4K 2006-04-18 00:29:02 UTC

Created attachment 78729 [details]
netman-2.png

The only available options. No Managed/AdHoc switch, well it could as well be autodetected...

Comment 5 Forgotten User mbQyAD5r4K 2006-04-18 00:30:04 UTC

Created attachment 78730 [details]
netman-3.png

This dialog shows for several seconds and then it fails saying it can't connect.

Comment 6 Timo Hoenig 2006-04-18 00:32:05 UTC

KNetworkManager does not yet provide the option to create AdHoc networks.

However, nm-applet -- which comes with NetworkManager-gnome -- does.

Please track this issue with bug #153232.

Closing as duplicate of bug #153232.

*** This bug has been marked as a duplicate of 153232 ***

*** This bug has been marked as a duplicate of 153232 ***