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
** Attachment added: Syslog output when trying to create an ad-hoc unencrypted
network
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
--
ad-hoc networks don't work with ipw2200
https://bugs.launchpad.net/bugs/75358
You received this bug notification because you are a member of
** Changed in: network-manager (upstream)
Status: Unknown = Unconfirmed
** Changed in: deluge (upstream)
Status: Unknown = Unconfirmed
--
ad-hoc networks don't work with ipw2200
https://bugs.launchpad.net/bugs/75358
You received this bug notification because you are a member of
oops, wrong manipulation, this bug has nothing to do with deluge :D
If somebody knows how to remove this entry, you are welcome
** Bug watch added: GNOME Bug Tracker #384033
http://bugzilla.gnome.org/show_bug.cgi?id=384033
** Also affects: deluge (upstream) via
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
--
ad-hoc networks don't work with ipw2200
https://bugs.launchpad.net/bugs/75358
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
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.
--
ad-hoc networks don't work with ipw2200
https://launchpad.net/bugs/75358
