subject:"\[Bug 50214\] Re\: can't connect to hidden network"

Dima, can you please attach your complete syslog and dmesg output of the
system that doesn't work? please also attach the output of nm-tool

Thanks,
 - Alexander

-- 
can't connect to hidden network
https://bugs.launchpad.net/bugs/50214
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 50214] Re: can't connect to hidden network

Dima, please take those logs _after_ a failed connect attempt.

-- 
can't connect to hidden network
https://bugs.launchpad.net/bugs/50214
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 50214] Re: can't connect to hidden network

Gene, Matt. sorry if my instructions where not appropriate. Though this
package is already in the archive, I'll try harder to post better
instructions next time. I certainly want developers to be able to test
these. But its much easier to request tests on a branch than rolling out
debs for each individual issues i want to track potential fixes for.

So please review if the following steps are detailed enough for you to
tests:

# install build requirements/dependencies
 1. sudo apt-get build-dep network-manager
 2. sudo apt-get install bzr devscripts

# branch the sources
 3. bzr branch 
https://code.edge.launchpad.net/~ubuntu-core-dev/network-manager/ubuntu.0.6.x.ap_scan
 network-manager.ubuntu

# build the sources:
 4. cd network-manager.ubuntu
 5. debuild -b

# install the bits for testing
 6. cd ../; dpkg -i network-manager*deb libnm-*deb

Is that good enough?

Thanks for your input,
 - Alexander

-- 
can't connect to hidden network
https://bugs.launchpad.net/bugs/50214
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 50214] Re: can't connect to hidden network

Gene, could you put your atheros test results to the ath_pci bug we have
now to track this: bug 208306.

-- 
can't connect to hidden network
https://bugs.launchpad.net/bugs/50214
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 50214] Re: can't connect to hidden network

Luke,

your log indicates that you have a atheros chipset as well. can you
follow up in bug 208306 which deals with this?

-- 
can't connect to hidden network
https://bugs.launchpad.net/bugs/50214
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 50214] Re: can't connect to hidden network

2008-03-31 Thread Christiansen

Anyone tested the ndiswrapper yet ? - Alexander

If it can be tested with an Atheros based PCMCIA card I think I might
give it a try - even thou I don't like chipset vendors that do not give
the Linux community a chance or just a clue how to make a driver, then I
certainly would like to see K/Ubuntu Hardy rock in any way possible.

Anyone ?

-- 
can't connect to hidden network
https://bugs.launchpad.net/bugs/50214
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 50214] Re: can't connect to hidden network

2008-03-31 Thread Matt Palmer

Alexander,

great instructions. I had to sudo a little bit more, and do an apt-get
update before it would install all the build dependencies. The only other
errors I got were not having your private GPG key to sign the packages! It
would be great if such simple instructions were obvious and available to
everyone on launchpad.

I ran it all from the live CD, and built a new network manager and installed
it (ubuntu4). I assume this is OK - you don't have to do this from a hard
disk install?

It installed cleanly over the existing one, maintaining my network
connection to an unhidden network. I changed the network back over to
hidden, and it stayed connected. However, when I disconnected and tried to
reconnect, it failed to re-connect, with the same issues. This is on a
thinkpad T43 using ipw2200. Attached is the dmesg and syslog outputs.

Matt

On Mon, Mar 31, 2008 at 11:21 AM, Alexander Sack [EMAIL PROTECTED]
wrote:

Gene, Matt. sorry if my instructions where not appropriate. Though this
package is already in the archive, I'll try harder to post better
instructions next time. I certainly want developers to be able to test
these. But its much easier to request tests on a branch than rolling out
debs for each individual issues i want to track potential fixes for.

So please review if the following steps are detailed enough for you to
tests:

# install build requirements/dependencies
1. sudo apt-get build-dep network-manager
2. sudo apt-get install bzr devscripts

# branch the sources
3. bzr branch
https://code.edge.launchpad.net/~ubuntu-core-dev/network-manager/ubuntu.0.6.x.ap_scanhttps://code.edge.launchpad.net/%7Eubuntu-core-dev/network-manager/ubuntu.0.6.x.ap_scannetwork-manager.ubuntu

# build the sources:
4. cd network-manager.ubuntu
5. debuild -b

# install the bits for testing
6. cd ../; dpkg -i network-manager*deb libnm-*deb

Is that good enough?

Thanks for your input,
- Alexander

--
can't connect to hidden network
https://bugs.launchpad.net/bugs/50214
You received this bug notification because you are a direct subscriber
of the bug.

Status in NetworkManager: Fix Released
Status in Source Package network-manager in Ubuntu: Fix Released
Status in Source Package knetworkmanager in Baltix GNU/Linux: Invalid

Bug description:
Since I installed dapper clean from CD, NM won't connect to my own hidden
network., however it did before. The network was even in the list after a
few seconds, the new feature of reverse mac scanning in 0.6.2.

Now even if I use connect to other network and I enter everything in
there, the connection won't be a success. Not hiding the SSID solves the
problem immediately, just as manually connecting to the AP with iwconfig
eth1 essid mine ...

** Attachment added: unnamed
http://launchpadlibrarian.net/13004539/unnamed

** Attachment added: syslog
http://launchpadlibrarian.net/13004541/syslog

** Attachment added: dmesg
http://launchpadlibrarian.net/13004544/dmesg

--
can't connect to hidden network
https://bugs.launchpad.net/bugs/50214
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 50214] Re: can't connect to hidden network

2008-03-31 Thread Gene Caldwell

wait, matt !

I got the same error at the gpg key but it said fatal error and all further 
processing stopped...I sent an email to Alexander and am waiting now for a 
response. I just sent it 2 minutes agoshould have taken a smoke break and I 
would have recieved your post...GRR fatal error to me means stop, you continued 
to the next step anyway ?
Gene

-- 
can't connect to hidden network
https://bugs.launchpad.net/bugs/50214
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 50214] Re: can't connect to hidden network

2008-03-31 Thread Martin Pool

On Tue, Apr 1, 2008 at 8:23 AM, Gene Caldwell [EMAIL PROTECTED] wrote:
 wait, matt !

  I got the same error at the gpg key but it said fatal error and all further 
 processing stopped...I sent an email to Alexander and am waiting now for a 
 response. I just sent it 2 minutes agoshould have taken a smoke break and 
 I would have recieved your post...GRR fatal error to me means stop, you 
 continued to the next step anyway ?

As I said previously (maybe on another dupe), yes, you can continue
and install the unsigned packages.

-- 
Martin http://launchpad.net/~mbp/

-- 
can't connect to hidden network
https://bugs.launchpad.net/bugs/50214
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 50214] Re: can't connect to hidden network

2008-03-30 Thread Matt Palmer

Gene,

oops, yes, I meant the reply to you!  I've also been using linux for 4
years, and I know enough to figure things out - I don't need step-by-step
instructions (although they certainly help!).  Having said that, I use
Ubuntu precisely because it doesn't force me to become an O/S expert - but
I'm still free to tinker with the bits I find interesting.

I'll continue to try out betas and submit bugs related to my hardware - it's
in my interest after all!  I would like to be able to build and test patches
running from the beta cd, not installed, as I also don't have a spare
testing machine or unlimited bandwidth.  I don't know if that's even
possible.

cheers,

Matt

On Sun, Mar 30, 2008 at 4:10 AM, Gene Caldwell [EMAIL PROTECTED]
wrote:

 Matt,
 Correct me if I'm wrong here but I think you meant your address to me, not
 to Alexander. Alexander is the guy who is providing the patches and is
 trying to get this bug fixed for all of us, he's the guy who knows how to do
 all this stuff.  It's funny tho, you seem to have the very same background
 as I do. however I am no longer able to work in my chosen profession. I
 choose to try to stay involved however I can. And like you, I have found it
 very difficult to gain enough of the requested talent that is needed to
 provide feed back to these guys on the patches et-al.   locating the much
 needed details or how-to's has also been been hopeless for me. I continue
 trying tho much like your self. its been over 4 years now for me since I
 started using linux and I still consider myself a newbie. lol, I guess since
 I cannot patch my own system shows I still  am a newbie.
 Gene

 --
 can't connect to hidden network
 https://bugs.launchpad.net/bugs/50214
 You received this bug notification because you are a direct subscriber
 of the bug.

 Status in NetworkManager: Fix Released
 Status in Source Package network-manager in Ubuntu: Fix Released
 Status in Source Package knetworkmanager in Baltix GNU/Linux: Invalid

 Bug description:
 Since I installed dapper clean from CD, NM won't connect to my own hidden
 network., however it did before. The network was even in the list after a
 few seconds, the new feature of reverse mac scanning in 0.6.2.

 Now even if I use connect to other network and I enter everything in
 there, the connection won't be a success. Not hiding the SSID solves the
 problem immediately, just as manually connecting to the AP with iwconfig
 eth1 essid mine ...



** Attachment added: unnamed
   http://launchpadlibrarian.net/12977137/unnamed

-- 
can't connect to hidden network
https://bugs.launchpad.net/bugs/50214
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 50214] Re: can't connect to hidden network

2008-03-30 Thread Gene Caldwell

Steve and Alexander,
Here are test results for 2 different wifi chipsets:

PRISM54:
The first was my bigger wish list fix: Prism54 SUCCESS using LiveCD 
tested hiding SSID while connected to exposed network, re-connected 
successfully. This was a problem prior. looks like its fixed.
logged on to completely hidden SSID sucessfully !
8.04 reports chipset as follows: Intersel ISL 3890 Prism GT/Prism Duette / ISL 
3886 Prism Javelin/ Prism Xbow - Prism54PCI driver used.
using this LiveCD looks like it solves the problem with that chipset, however 
as I said before, I had sucess on 7.10 also using LiveCD until I installed, 
then it switched to WEP drivers from WPA and was very very troublesome to get 
it to finally detect correctly and when it did finally, it had the hidden SSID 
issue. ATM, I think its good tho.

Atheros:
Second chipset FAILED completely AND crashed NM. NM could not be restarted. had 
to reboot computer. may have been low memory issue @ 256 mb causing some boot 
issues, raised to 384mb memory re-ran test,  booting fine now. NM no longer 
crashing, however could NOT connect to hidden SSID.  8.04 reported chipset as 
Atheros AR2413 802.11bg NIC - ath_pci driver.
tested connecting to hidden SSID FAILS
tested connecting to exposed SSID SUCEEDS.
This computer is just an old generic computer I built 10 years ago, PIII 
@500mhz, 384mb memory, Nvidia vedio card, SCSI HD subsystem. Runs 7.10 just 
fine.

I have suspicions that 256 mb memory is an issue right now with current
beta status. I'm assuming that basic hardware requirements are still the
same tho. Pentium class processor and min 256mb memory.

-- 
can't connect to hidden network
https://bugs.launchpad.net/bugs/50214
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 50214] Re: can't connect to hidden network

2008-03-30 Thread Dima Ryazanov

I'll add some info, too.

I have a Thinkpad T43p with a built-in wireless card that uses the
ipw2200 driver. NM identifies the card as Intel Corporation
PRO/Wireless 2915ABG Network Connection. It connects to hidden networks
fine. I'm using Gutsy.

I also have an Atheros PCMCIA card - ath_pci driver, Atheros Communications, 
Inc. AR5212/AR5213 Multiprocessor MAC/baseband processor. I normally use it 
with Thinkpad T20, running Hardy. It connects to my hidden network - but 
disconnects after a few seconds. Sometimes it won't connect at all. It connects 
fine to all other networks - even with WPA, etc.
Before, when I used Gutsy, it didn't connect to a hidden network, either. It 
would get stuck trying to connect, and iwconfig would not show the network 
name. If I told it to connect again, while it was already trying to connect, it 
would set the network name correctly, but wouldn't connect. If I did it the 
third time, it would actually connect - but not for very long.

However, if I plug it into my T43p (with Gutsy), it works perfectly there. It 
connects immediately, and stays connected.
Not sure what is happening here. Does the rest of the hardware make a 
difference? Did some bug in Gutsy get fixed after I installed Hardy on T20?

-- 
can't connect to hidden network
https://bugs.launchpad.net/bugs/50214
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 50214] Re: can't connect to hidden network

2008-03-30 Thread Christiansen

Dima, maby you should have look on Bug #208306  [ath_pci] cannot
connect to hidden ap, which deal with the Atheros based adapters. Using
the patch attached do make my 3 different Atheros adapters work.

I've testet Kubuntu from Edgy to Gutsy on a ThinkPad T21 several times,
and my experience is that thees laptops (T20-23) is getting rather old
for thees new OSs. It seemed to me that the amount of RAM and the
Prossesor speed (700~900 Mhz) has a certain influencer on
NetworkManager. Mine NM did crash too with Gutsy, using PCMCIA with both
Atheros AR5212 and other chipsets. Installing more RAM (128 - 256 -
512 Mb) did change things a little as fare as I remember.

Did you shutdown/switch off the buildin ipw2915abg in BIOS on the T43 while you 
tested the Atheros ?.
Having both Adapters activated on the same time, seems to help the Atheros 
finding and connecting to a specific hidden SSID   - when the one adaptor 
(ipw2915abg) have made an initial connection first.

-- 
can't connect to hidden network
https://bugs.launchpad.net/bugs/50214
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 50214] Re: can't connect to hidden network

Now might not be the best time to bring this up since additions are now
closed for hardy, but WiCD does not have this problemas least for
me(tried LinuxMint, wireless worked out of the box on hidden SSID's). I
have not been able to figure out to get it to work installing it on my
own tho for feisty. can this be added as a backup system to help insure
people can connect wirelessly ? just to insure people have an internet
capable distro ?

-- 
can't connect to hidden network
https://bugs.launchpad.net/bugs/50214
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 50214] Re: can't connect to hidden network

network-manager (0.6.6-0ubuntu4) hardy; urgency=low

Low ? urgency=low ? maybe this is the reason why this problem has
existed for 2 years now for so many people ???

-- 
can't connect to hidden network
https://bugs.launchpad.net/bugs/50214
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 50214] Re: can't connect to hidden network

2008-03-29 Thread Alexander Sack

Gene, could you test and report?

-- 
can't connect to hidden network
https://bugs.launchpad.net/bugs/50214
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 50214] Re: can't connect to hidden network

Alexander,
I am truly sorry, I cannot. The computer I have the problem with is a 
production machine, not a test machine. Its my Girl Friends work computer, I 
simply cannot take a work computer out of commission for beta testing as much 
as I really would like to try to provide you feed back on so this issue can be 
fixed. Thats the first problem.

The second problem is that I'm totally clueless as to what you need me
to do to test your patch, I read every post you guys have made for the
last several days and I simply do not know enough about linux to know
how to get the patch installed or even know if  messed up during the
process. I can however install a .deb package...duh, like its something
troublesome or complicated :) but as I did not see anyone asking for deb
packages from you to try, I have been just hoping that someone with my
same chipset will provide you the needed feedback. I'm sorry, I don't
know how to do as you ask and feel you are trying at the moment and
don't want to interfere with your efforts by asking for special just for
me.

I do have another computer I can test with tho that has a different
chipset that has the very same hidden SSID problem, however I still have
the same problem, I don't know how to install a patch if it is not
delivered in a deb package.

I would love to help and provide feed back ( I love testing things out )
if I only knew how to install your patch.  Just so you know, I really
did try, I'm not a dummy, I just can't figure out the linux way of doing
things, I guess I spent too many years in windows.

production machine: Dell C800 with prism54 wireless pcmcia card does not
yet work except for what Dave Ward helped out with several months back,
there were still problems with his patch tho. no automatic re-connection
etc.

other testable machine I CAN test on has atheros wifi card. but as I
said, I know nothing about patches.

-- 
can't connect to hidden network
https://bugs.launchpad.net/bugs/50214
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 50214] Re: can't connect to hidden network

2008-03-29 Thread Steve Langasek

Gene,

The package that's believed to fix this bug has already been uploaded to
the archive, and indeed is already present on the daily liveCD builds
present here:

  http://cdimage.ubuntu.com/daily-live/current/

So far I don't believe we have anyone else testing prism54; my
understanding is that this is an older and relatively uncommon chipset.
While the most recent network-manager changes are believed to
*generally* be correct, there's really no way we can guarantee that
hardy will work for your particular chipset unless someone in possession
of the hardware is able to test it.

-- 
can't connect to hidden network
https://bugs.launchpad.net/bugs/50214
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 50214] Re: can't connect to hidden network

Steve and Alexander,

I have no problem at all testing a liveCD on THAT production machine
with the Prism54 chipset card. I shall d/L and report later. I should
give advance notice that on my last liveCD test 7.10 final on that
machine I did not have the problem with connecting to my hidden AP. It
only became apparent AFTER I installed it to the HD. That really baffled
me as it took several installs to get it to know that I had WPA, and NOT
WEP. I know, sounds dumb, but the LiveCD 7.10 final worked
flawlessly(even hidden SSID) until I installed, then nothing but WEP was
detectable except if I held my breath, turned my head sideways, cough
twice while standing on my right leg only, not left leg, then it would
install correctly and detect WPA. I have read other reports of this
issue so I concluded I did nothing wrong.

I will also test on the other wireless chipset I have for hidden SSID.
will report back later. getting your new daily image image now

IF someone can recommend to me a replacement PCMCIA card that is
guaranteed to work I would be willing to get past this problem and buy
that since its so rarehowever I did not know that was the case. but
it seems like a lot of work to support just one person.

-- 
can't connect to hidden network
https://bugs.launchpad.net/bugs/50214
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 50214] Re: can't connect to hidden network

2008-03-29 Thread Matt Palmer

Alexander,

you are not alone!  I happily submitted a bug for the ipw2200 chipset having
used the beta cd, but didn't have the first clue about building branches,
patches or whatever.I actually work in software development - I'm just
not familiar with these tools or procedures, and I don't have endless hours
to spend figuring it out. I spent about an hour trying to find help, but
could find no documentation on what to do at all.

Some concise newbie help for technically minded beta testers would be very
useful.

Regards,

Matt


On Sat, Mar 29, 2008 at 7:04 PM, Gene Caldwell [EMAIL PROTECTED]
wrote:

 Alexander,
 I am truly sorry, I cannot. The computer I have the problem with is a
 production machine, not a test machine. Its my Girl Friends work computer, I
 simply cannot take a work computer out of commission for beta testing as
 much as I really would like to try to provide you feed back on so this issue
 can be fixed. Thats the first problem.

 The second problem is that I'm totally clueless as to what you need me
 to do to test your patch, I read every post you guys have made for the
 last several days and I simply do not know enough about linux to know
 how to get the patch installed or even know if  messed up during the
 process. I can however install a .deb package...duh, like its something
 troublesome or complicated :) but as I did not see anyone asking for deb
 packages from you to try, I have been just hoping that someone with my
 same chipset will provide you the needed feedback. I'm sorry, I don't
 know how to do as you ask and feel you are trying at the moment and
 don't want to interfere with your efforts by asking for special just for
 me.

 I do have another computer I can test with tho that has a different
 chipset that has the very same hidden SSID problem, however I still have
 the same problem, I don't know how to install a patch if it is not
 delivered in a deb package.

 I would love to help and provide feed back ( I love testing things out )
 if I only knew how to install your patch.  Just so you know, I really
 did try, I'm not a dummy, I just can't figure out the linux way of doing
 things, I guess I spent too many years in windows.

 production machine: Dell C800 with prism54 wireless pcmcia card does not
 yet work except for what Dave Ward helped out with several months back,
 there were still problems with his patch tho. no automatic re-connection
 etc.

 other testable machine I CAN test on has atheros wifi card. but as I
 said, I know nothing about patches.

 --
 can't connect to hidden network
 https://bugs.launchpad.net/bugs/50214
 You received this bug notification because you are a direct subscriber
 of the bug.

 Status in NetworkManager: Fix Released
 Status in Source Package network-manager in Ubuntu: Fix Released
 Status in Source Package knetworkmanager in Baltix GNU/Linux: Invalid

 Bug description:
 Since I installed dapper clean from CD, NM won't connect to my own hidden
 network., however it did before. The network was even in the list after a
 few seconds, the new feature of reverse mac scanning in 0.6.2.

 Now even if I use connect to other network and I enter everything in
 there, the connection won't be a success. Not hiding the SSID solves the
 problem immediately, just as manually connecting to the AP with iwconfig
 eth1 essid mine ...



** Attachment added: unnamed
   http://launchpadlibrarian.net/12972803/unnamed

-- 
can't connect to hidden network
https://bugs.launchpad.net/bugs/50214
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 50214] Re: can't connect to hidden network

Matt,
Correct me if I'm wrong here but I think you meant your address to me, not to 
Alexander. Alexander is the guy who is providing the patches and is trying to 
get this bug fixed for all of us, he's the guy who knows how to do all this 
stuff.  It's funny tho, you seem to have the very same background as I do. 
however I am no longer able to work in my chosen profession. I choose to try to 
stay involved however I can. And like you, I have found it very difficult to 
gain enough of the requested talent that is needed to provide feed back to 
these guys on the patches et-al.   locating the much needed details or how-to's 
has also been been hopeless for me. I continue trying tho much like your self. 
its been over 4 years now for me since I started using linux and I still 
consider myself a newbie. lol, I guess since I cannot patch my own system shows 
I still  am a newbie.
Gene

-- 
can't connect to hidden network
https://bugs.launchpad.net/bugs/50214
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 50214] Re: can't connect to hidden network

2008-03-28 Thread Launchpad Bug Tracker

This bug was fixed in the package network-manager - 0.6.6-0ubuntu4

---
network-manager (0.6.6-0ubuntu4) hardy; urgency=low

  * fix hidden networks for chipsets that do not have scan_capa enabled
driver. (LP: #50214, #200950, #203793, #199679). The following
behaviour is now implemented:
  * use scan_ssid 1 with AP_SCAN 1 for all scan_capa_ssid drivers
  * use scan_ssid 1 with AP_SCAN 1 for all drivers with buggy
scan_capa_ssid and buggy ap_scan and explicitly set essid through
wireless extensions to help driver to find bssids of hidden ssid
  Drivers with buggy scan_capa_ssid: ipw2200
  Drivers with buggy ap_scan 2: iwl3945, iwl4965
  * use AP_SCAN 2 for all other drivers and set essid through wireless
extensions forcefully.
- update debian/patches/42b_fix_ap_scan_hidden.patch
- add debian/patches/42b_fix_ap_scan_hidden.patch
- update debian/patches/series

 -- Alexander Sack [EMAIL PROTECTED]   Fri, 28 Mar 2008 10:38:42 +0100

** Changed in: network-manager (Ubuntu)
   Status: Fix Committed = Fix Released

-- 
can't connect to hidden network
https://bugs.launchpad.net/bugs/50214
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 50214] Re: can't connect to hidden network

2008-03-28 Thread Alexander Sack

i am uploading what we have now. I will close thise catch all bug for
now. if you still have issues, please open a new bug for each individual
chipset you know about.

title it  like [CHIPSET] cannot connect to hidden network.

maybe prod me (asac) on irc so i can bring your bug on track for hardy.

Thanks,
 - Alexander

** Changed in: network-manager (Ubuntu)
   Status: Confirmed = Fix Committed

-- 
can't connect to hidden network
https://bugs.launchpad.net/bugs/50214
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 50214] Re: can't connect to hidden network

2008-03-28 Thread Luke Hoersten

This problem has been reintroduced in Ubuntu 8.04. NetworkManager does
not work for all Ubuntu on the Purdue University campus because of this.
I've attached the output of /var/log/messages for three different
connection attempts.

** Attachment added: /var/log/messages
   http://launchpadlibrarian.net/12953971/nm-messages

-- 
can't connect to hidden network
https://bugs.launchpad.net/bugs/50214
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 50214] Re: can't connect to hidden network

2008-03-27 Thread sip

It's working for me! iwl3945, hidden SSID, no security, branch 110.

-- 
can't connect to hidden network
https://bugs.launchpad.net/bugs/50214
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 50214] Re: can't connect to hidden network

2008-03-27 Thread sip

Only one minor problem remains. After restart network manager doesn't
automatically reconnect to my hidden network, though it exists in the
wireless networks list.

-- 
can't connect to hidden network
https://bugs.launchpad.net/bugs/50214
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 50214] Re: can't connect to hidden network


 Alexander Sack wrote
 christiansen, does any of your chipsets work with broadcast SSID 
 (non-hidden)? or is everything broken for you?

When UNHIDING the WPA2 secured SSID, connecting with Hardy and network-
manager.0.6.6-0ubuntu4-test1 (2008-03-25 or branch ID110) seems to work
fine for both the Atheros and the ZyXEL chipset - Rebootet 2 times with
each and got connected. I will do further testing on the subject for a
WPA1 secured network later today.

BTW. The connection time SEEMS a to take a little longer than for Gutsy,
but I haven't timed it.

-- 
can't connect to hidden network
https://bugs.launchpad.net/bugs/50214
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 50214] Re: can't connect to hidden network

2008-03-27 Thread Alexander Sack

christiansen,

for the chipsets that don't work, does iwconfig ever show any essid?

(run iwconfig repeatetely while network manager is spinning)

If it doesn't, is setting essid through iwconfig while connecting
helping you? to do so, try to connect to hidden network through NM, then
set essid to whatever your hidden net uses and after that run a scan
(sudo iwlist scan) to help NM get the bssid.

-- 
can't connect to hidden network
https://bugs.launchpad.net/bugs/50214
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 50214] Re: can't connect to hidden network

2008-03-27 Thread Alexander Sack

sip,

what is your SSID used? is it a factory default?

-- 
can't connect to hidden network
https://bugs.launchpad.net/bugs/50214
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 50214] Re: can't connect to hidden network

Hi Alexander,

Did some further testing, using the buildin Atheros on one laptop. First
I used unhidden SSID on the WPA1 secured AP, as you asked for. The
connection was established, and network communication was okay.

Then I shutdown the laptop, and form an other computer enabled hiding of
the SSID again. A littel later I booted up the laptop once more, and
could not get connectet - tried manually a couple of times.

Attached the syslog for both the connection attempt with and without
hidden SSID.

Restarted the laptop, still with the AP SSID hidden, and did the tests
you asked for too. As you hopefully can see from the attached
iwconfig/iwpriv logfile piped out while executing the commands and
connecting with NM, the ESSID is set by NM right when it started
connecting. The iwpriv scan didn't seem to make any difference, and I
didn't get connected at all.

I will now try to make some tests with the ZyXEL USB adapters too...

** Attachment added: iwconfig-iwlist_scan-while_NM_connects.txt
   
http://launchpadlibrarian.net/12926801/iwconfig-iwlist_scan-while_NM_connects.txt

-- 
can't connect to hidden network
https://bugs.launchpad.net/bugs/50214
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 50214] Re: can't connect to hidden network

The syslog with hidden SSID

** Attachment added: syslog-pci_ath-3C_AP_HiddenSSID
   http://launchpadlibrarian.net/12926807/syslog-pci_ath-3C_AP_HiddenSSID

-- 
can't connect to hidden network
https://bugs.launchpad.net/bugs/50214
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 50214] Re: can't connect to hidden network

The syslog without hidden SSID

** Attachment added: syslog-pci_ath-3C_AP_NonHiddenSSID
   http://launchpadlibrarian.net/12926814/syslog-pci_ath-3C_AP_NonHiddenSSID

-- 
can't connect to hidden network
https://bugs.launchpad.net/bugs/50214
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 50214] Re: can't connect to hidden network

The tests with ZyXEL (chipset zd1211rw) seems exact identical with that
of Atheros above.

SSID Not Hidden: Connects
SSID Hidden : Do not connect

Executing iwconfig while connecting with NM shows the right ESSID, and
doing iwpriv scan do not make the make it connect.

BTW Got the syslog files for both hidden and nonhidden connections
attempts if they could be of any interest.

-- 
can't connect to hidden network
https://bugs.launchpad.net/bugs/50214
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 50214] Re: can't connect to hidden network

2008-03-27 Thread sip

 what is your SSID used? is it a factory default?

No, it's not a factory default, I've changed it in my router setup (I'm
not sure that I understand your question completely).

-- 
can't connect to hidden network
https://bugs.launchpad.net/bugs/50214
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 50214] Re: can't connect to hidden network

2008-03-27 Thread Martin Pool

Using network-manager built from this branch (0.6.6-0ubuntu4~test1) on
my x61s with iwl3945 and e1000:

Changing my network setup for testing seems to require choosing edit
wireless network and deleting it.  This is somewhat reasonable though
it would be good to get a clearer message along the lines of this
network is now unencrypted, are you really sure you want to connect,
but that's a separate bug.

I can connect to a public, wpa2 psk network.

I can connect to a private, non-encrypted network, but it seems that I
need to choose connect to other network every time.  Previously, nm
seemed to automatically detect hidden networks I had previously used.

However, this version breaks connections to a wired network, which was
always working in hardy previously.  When I try, I get stuck at one
light and the following log.

-- 
can't connect to hidden network
https://bugs.launchpad.net/bugs/50214
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 50214] Re: can't connect to hidden network

2008-03-27 Thread Martin Pool

I can't reproduce this problem after rebooting.

-- 
can't connect to hidden network
https://bugs.launchpad.net/bugs/50214
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 50214] Re: can't connect to hidden network

2008-03-26 Thread Christiansen

Connecting to hidden WPA secured SSID with Atheros based adapters and
Hardy still does not work. The labtops was updatet  from main repository
as of 2008-03-26 21:20 UTC.

First build network-manager.0.6.6-0ubuntu4-test1 (2008-03-24 or branch ID109) 
and tested both Internal IBM and external Cisco  AIR-CB21AG PCMCIA adapters 
(with internal switched off in BIOS) with no luck. Test was done against two 
different APs- a WPA1 and a WPA2 secured.
First then found out that there was a network-manager.0.6.6-0ubuntu4-test1 
(2008-03-25 or branch ID110). Build this one and did the same test as above 
without better luck - this test was only done against the WPA1 secured AP. 

BTW. Connecting with Kubuntu Gutsy or Hardy Beta 5 (NM 0.6.5) from the
same laptops works okay.

Attatches syslog from the latest failed connection attempt with internal
adapter.


** Attachment added: syslog-ath_pci
   http://launchpadlibrarian.net/12908631/syslog-ath_pci

-- 
can't connect to hidden network
https://bugs.launchpad.net/bugs/50214
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 50214] Re: can't connect to hidden network

2008-03-26 Thread Christiansen

Tested 2 different ZyXEL based USB adapters too - 3COM OfficeConnect and
ZyXEL AG-220 - without better luck.

Used network-manager.0.6.6-0ubuntu4-test1 (2008-03-25 or branch ID110),
and connecting to a WPA1 secured AP with hidden SSID.

BTW. Both adapters work with Gutsy.

Attached syslog from failed connection attempt with 3COM OfficeConnect
stick.


** Attachment added: syslog_zd1211rw
   http://launchpadlibrarian.net/12909134/syslog_zd1211rw

-- 
can't connect to hidden network
https://bugs.launchpad.net/bugs/50214
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 50214] Re: can't connect to hidden network

2008-03-26 Thread Alexander Sack

christiansen, does any of your chipsets work with broadcast SSID (non-
hidden)? or is everything broken for you?

-- 
can't connect to hidden network
https://bugs.launchpad.net/bugs/50214
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 50214] Re: can't connect to hidden network

2008-03-26 Thread Alexander Sack

anyone here can test this branch with ndiswrapper?

-- 
can't connect to hidden network
https://bugs.launchpad.net/bugs/50214
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 50214] Re: can't connect to hidden network

2008-03-25 Thread Fernando Pereira

On Monday 24 March 2008 05:22:24 Gene Caldwell wrote:
 If I have to expose my wireless network to the bad guys, then I should 
 probably look for another distro.

[off topic]
SSID hidding is in NO situation a good way to defend yourself. Its quite easy 
to either listen to packets or injecting packets to find out the real SSID even 
if hidden.
Its as secure as wep or mac address filtering. And it causes lots of problems 
when roaming between wifi nodes.
If hardware capable please migrate to WPA/WPA2 and a proper password scheme.
[/off topic]

Still this does not neglet the fact that Ubuntu should, and is working
for some ppl, when it encounters an hidden SSID WiFi network.


-- 
BUGabundo  :o)
(``-_-´´)   http://Ubuntu.BUGabundo.net
Linux user #443786GPG key 1024D/A1784EBB
My new micro-blog @ http://BUGabundo.net
ps. My emails tend to sound authority and aggressive. I'm sorry in advance. 
I'll try to be more assertive as time goes by...

-- 
can't connect to hidden network
https://bugs.launchpad.net/bugs/50214
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 50214] Re: can't connect to hidden network

i did some cleanups of the hidden ssid tweaks on the branch. Please
test!!

The new behaviour is:

  * use scan_ssid 1 with AP_SCAN 1 for all scan_capa_ssid drivers
  * use scan_ssid 1 with AP_SCAN 1 for all drivers with buggy 
scan_capa_ssid and buggy ap_scan and explicitly set essid through
wireless tools to help driver to find bssids of hidden ssid
  Drivers with buggy scan_capa_ssid: ipw2200
  Drivers with buggy ap_scan 2: iwl3945, iwl4965
  * use AP_SCAN 2 for all other drivers
- update debian/patches/42b_fix_ap_scan_hidden.patch

-- 
can't connect to hidden network
https://bugs.launchpad.net/bugs/50214
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 50214] Re: can't connect to hidden network

one more addition: to install the build dependencies to build the
branch, run:

 sudo apt-get build-dep network-manager

-- 
can't connect to hidden network
https://bugs.launchpad.net/bugs/50214
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 50214] Re: can't connect to hidden network

note: the branch has been reported to fix hidden ssid for ipw2200 in bug
199679. please give feedback for your driver/chipset as well.

-- 
can't connect to hidden network
https://bugs.launchpad.net/bugs/50214
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 50214] Re: can't connect to hidden network

2008-03-25 Thread bluej774

This bug did not occur for me in Dapper, Edgy, or Gutsy.  It is
occurring in Hardy.  I use the ipw3945 driver.

-- 
can't connect to hidden network
https://bugs.launchpad.net/bugs/50214
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 50214] Re: can't connect to hidden network

blue774, please test the bzr branch you can find at the top of this bug
reports web-page

-- 
can't connect to hidden network
https://bugs.launchpad.net/bugs/50214
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 50214] Re: can't connect to hidden network

2008-03-25 Thread Steve Langasek

bluej774,

On Tue, Mar 25, 2008 at 06:43:22PM -, bluej774 wrote:
 This bug did not occur for me in Dapper, Edgy, or Gutsy.  It is
 occurring in Hardy.  I use the ipw3945 driver.

Hardy does not use the ipw3945 driver, but rather the iwl3945 driver.  The
issue with iwl3945 connectivity is bug #200950; please test the indicated
branch following Alexander's instructions.

-- 
can't connect to hidden network
https://bugs.launchpad.net/bugs/50214
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 50214] Re: can't connect to hidden network

2008-03-24 Thread Steve Langasek

Gene,

On Mon, Mar 24, 2008 at 04:30:48AM -, Gene Caldwell wrote:
 I strongly DISAGREE ! this bug is one bug only.

Well yes, that's certainly how it's being treated in the bug report, and
that's what I'm explaining is a problem.  There are many discrete bugs being
discussed in this one bug report - to be able to make headway on any of
them, the developers need to be able to track, work on, and propose fixes
for each of these bugs individually, otherwise it's impossible to know when
we're making progress (and impossible to divide up the work between
developers, even when the bugs have unrelated causes).

I'm not just being contrary here, I'm speaking as a developer who is trying
to wade through the many unrelated comments in this report and extract some
semblance of order to be able to help the people who have commented to get
their various bugs fixed - because ultimately that /is/ what I'm trying to
do.  Treating each bug separately helps us do that.  Lumping all the
unrelated or distantly related bugs into a single bug report does not; it
just makes it more likely that some of the problems will be overlooked.

 By trying to open a new bug report for each chipset hides the fact that
 no one can connect to a hidden SSID

This is not a fact.  With the current versions of the kernel and
network-manager, there are many users who *can* connect to hidden SSIDs, and
the remaining issues need to be handled on a per-chipset basis.

-- 
can't connect to hidden network
https://bugs.launchpad.net/bugs/50214
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 50214] Re: can't connect to hidden network

2008-03-24 Thread Steve Langasek

A look at the kernel sources gives me the following list of drivers that
implement scan_capa:

ipw2200
hostap
mac80211, which is used by:
 - rt2x00usb
 - rt73usb
 - rt2x00pci
 - rt2500pci
 - rt2400pci
 - rt61pci
 - rt2500usb
 - b43
 - p54pci
 - b43legacy
 - p54usb
 - rtl8187
 - adm8211

This means that, as far as I'm able to determine from the kernel, all of
these drivers should be able to connect to hidden SSIDs with Linux
2.6.24-12 and network-manager 0.6.6-0ubuntu3.  Gene, this list seems to
cover your chipset; can you please confirm that you're running the
current versions of these packages, or if not, upgrade and report the
results?

David, ndiswrapper is clearly not in this list, so does not support the
scan_capa functionality; handling this driver will probably require
addition of another quirk in network-manager along with the existing
quirk for atheros drivers.  On the other hand, it's possible that
ndiswrapper does support the necessary interfaces when they're supported
by the underlying wrapped driver, so this could be a regression for some
other ndiswrapper users... on the gripping hand, it looks like it should
only be a performance regression rather than a regression in
functionality.  So we're probably ok to go ahead with a change like your
patch for ndiswrapper; it's probably best if Alexander comments on it
first, though, since he knows this code far better than I do.

-- 
can't connect to hidden network
https://bugs.launchpad.net/bugs/50214
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 50214] Re: can't connect to hidden network

2008-03-24 Thread Gene Caldwell

unfortunately the machine with the prism54 wireless is now a production
machine, and the current state of the beta 8.10 does not seem a likely
test candidate for 8.10 yet. I do have other wireless machines that I
can test, can't remember which chipset off the top of my head, but they
have the same hidden SSID problem, so I can test those.

-- 
can't connect to hidden network
https://bugs.launchpad.net/bugs/50214
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 50214] Re: can't connect to hidden network

2008-03-24 Thread Gene Caldwell

sorry, don't know why i'm calling it 8.10, I know its 8.04

-- 
can't connect to hidden network
https://bugs.launchpad.net/bugs/50214
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 50214] Re: can't connect to hidden network

please test the branch above. instructions on how to get it to your disc
can be found at the branch url given

to build you can just run

 $ debuild -b

out of the branch directory. use dpkg -i to install the packages for
testing.

If you still cannot connect to hidden SSID, please attach your complete
/var/log/syslog to the bug and state clearly if you could connect to
hidden networks in gutsy.

-- 
can't connect to hidden network
https://bugs.launchpad.net/bugs/50214
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 50214] Re: can't connect to hidden network

... after this round of testing I will sort the remaining issues to
specialised per-chipset bugs.

-- 
can't connect to hidden network
https://bugs.launchpad.net/bugs/50214
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 50214] Re: can't connect to hidden network

2008-03-24 Thread Gene Caldwell


 Alexander Sack wrote 1 hour ago: (permalink)

please test the branch above. instructions on how to get it to your disc
can be found at the branch url given

to build you can just run

 $ debuild -b

out of the branch directory. use dpkg -i to install the packages for
testing.

If you still cannot connect to hidden SSID, please attach your complete 
/var/log/syslog to the bug and state clearly if you could connect to hidden 
networks in gutsy.


I see no branch above that you are referring to in this post will
the latest beta release not work ?

-- 
can't connect to hidden network
https://bugs.launchpad.net/bugs/50214
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 50214] Re: can't connect to hidden network

2008-03-24 Thread Steve Langasek

Hi Alexander,

Doesn't this branch clobber the ath_pci quirk from the previous upload?:

-   else if (!nm_ap_get_broadcast (ap))
-   ap_scan = self-priv-has_scan_capa_ssid  
nm_null_safe_strcmp(ath_pci, kernel_driver) ? AP_SCAN 1 : AP_SCAN 2;

There is no other mention of ath_pci in the new patch, so it appears
atheros chips will now be handled according to the scan_capa value,
which I understood was incorrect.  Was the AP_SCAN change not necessary,
or is this a regression for atheros users?

-- 
can't connect to hidden network
https://bugs.launchpad.net/bugs/50214
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Re: [Bug 50214] Re: can't connect to hidden network

2008-03-24 Thread Matt Palmer

The branch is right at the top of the bug report web page, not in the
email.

cheers,

Matt.

On Mon, Mar 24, 2008 at 10:42 PM, Gene Caldwell [EMAIL PROTECTED]
wrote:

 
  Alexander Sack wrote 1 hour ago: (permalink)

 please test the branch above. instructions on how to get it to your disc
 can be found at the branch url given

 to build you can just run

  $ debuild -b

 out of the branch directory. use dpkg -i to install the packages for
 testing.

 If you still cannot connect to hidden SSID, please attach your complete
 /var/log/syslog to the bug and state clearly if you could connect to hidden
 networks in gutsy.
 

 I see no branch above that you are referring to in this post will
 the latest beta release not work ?

 --
 can't connect to hidden network
 https://bugs.launchpad.net/bugs/50214
 You received this bug notification because you are a direct subscriber
 of the bug.

 Status in NetworkManager: Fix Released
 Status in Source Package network-manager in Ubuntu: Confirmed
 Status in Source Package knetworkmanager in Baltix GNU/Linux: Invalid

 Bug description:
 Since I installed dapper clean from CD, NM won't connect to my own hidden
 network., however it did before. The network was even in the list after a
 few seconds, the new feature of reverse mac scanning in 0.6.2.

 Now even if I use connect to other network and I enter everything in
 there, the connection won't be a success. Not hiding the SSID solves the
 problem immediately, just as manually connecting to the AP with iwconfig
 eth1 essid mine ...


-- 
can't connect to hidden network
https://bugs.launchpad.net/bugs/50214
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 50214] Re: can't connect to hidden network

 Doesn't this branch clobber the ath_pci quirk from the previous
upload?:

there has been a report that the current ath_pci tweak doesn't work for
hidden APs. See: https://bugs.edge.launchpad.net/ubuntu/+source/network-
manager/+bug/50214/comments/131

-- 
can't connect to hidden network
https://bugs.launchpad.net/bugs/50214
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 50214] Re: can't connect to hidden network