** Changed in: network-manager
Importance: Unknown = Wishlist
--
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
I'm still having this issue on Ubuntu 10.04 Lucid Lynx with latest
updates (kernel 2.6.32-24-generic): The Intel 3945ABG adapter in my ASUS
A8Js notebook cannot connect to to my FRITZ!Box Fon WLAN 7270 (security
is set to WPA + WPA2) if my SSID is hidden. It works fine if I
broadcast the SSID, but
I have a similar problem on Kubuntu Karmic Netbook Remix. The problem
affects also wicd, not network manager alone, maybe it's a
wpa_supplicant related issue? Or maybe the way NM/wicd creates config
files for hidden networks...
At the moment I worked around it activating SSID broadcast on my AP.
No,i'm using a Intel Wireless 2200, but i can connect fine before the RC
version.
El dl 28 de 04 de 2008 a les 22:21 +, en/na HDave va escriure:
I can confirm this bug on Hardy with wireless device is a Broadcom
BCM4328 (Vendor = 0x14E4, Product = 0x4328). I am using ndiswrapper
I can confirm this bug on Hardy with wireless device is a Broadcom
BCM4328 (Vendor = 0x14E4, Product = 0x4328). I am using ndiswrapper
still...is this correct?
--
can't connect to hidden network
https://bugs.launchpad.net/bugs/50214
You received this bug notification because you are a member of
Alexander,
Thanks for your patience! I have followed your instructions as below,
while it doesn't work for me:
1. sudo apt-get build-dep network-manager
2. sudo apt-get install bzr devscripts
3. bzr branch
https://code.edge.launchpad.net/~ubuntu-core-dev/network-manager/ubuntu.0.6.x.ap_scan
I've opened a new bug #217006 on the ipw2200, as it seems that the bugs
with this chipset has not been fully solved yet.
--
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
I want to get in the changes so I gotta reply did we fine a
solution? sorry to everybody else who wants to hear changes about the
bug and is going to get an e-mail so that I can get the reports too.
--
can't connect to hidden network
https://bugs.launchpad.net/bugs/50214
You received
Tested ndiswrapper on the latest kernel and SUCCESS for both AR5211
based Netgear PCMCIA adapter an zd1211rw based ZyXEL USB adapter,
connecting to hidden SSID with WPA1 security. ZyXEL gives shows higher
bandwidth on 54 Mbps than the native driver with only 24 Mbps when using
ZyXEL driver version
Alexander,
thanks. I wasn't sure it was correct either - it seemed to be showing
AP_SCAN 1 in the log files, and I thought the replacement should have
changed that to AP_SCAN 2. However, dpkg did seem to do a replacement, and
Synaptic showed an ubuntu2 version before, and an ubuntu4 version
Matt, i cannot tell if you are really running the right network manager
package as i miss some log output i would expect to see in the latest
packages. Anyway, the branch is now available as .deb package in the
archive, so you can test the prebuild debs directly. If you still have
issues
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
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
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
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.
--
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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.
--
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
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
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
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
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
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.
--
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
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
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
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
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
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
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
... 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
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
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
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
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
I see no branch above that you are referring to in this post will the
latest beta release not work ?
https://code.launchpad.net/~ubuntu-core-dev/network-
manager/ubuntu.0.6.x.ap_scan
--
can't connect to hidden network
https://bugs.launchpad.net/bugs/50214
You received this bug
This bug has unfortunately become a catch-all for any bugs that users
are experiencing connecting to hidden networks, which is a problem
because there are many, separate bugs involved here - each chipset may
require different handling due to driver-specific limitations, and the
nature of the
I strongly DISAGREE ! this bug is one bug only. Its a bug report for
people that are trying to wirelessly connect to hidden SSID's , and
can't. Thats all this bug is about. if you cannot cannot to a hidden
SSID then this is where it should be reported. just because you have a
different chipset
No, Steve is right. This is not one problem, but several problems that
have the same apparent outcome, which is making this impossible to fix
if it's treated as a single problem. Suppose your computer stopped
booting into Ubuntu altogether. Could it be because your hard drive has
physically
I'm not going to pretend I followed your example because you suggested
hardware issues in your example DavidI read each and every one of
the posts in this bug report. and in short, the problem can be divided
into exactly 2 groups,, driver issue, and NM. in both cases the result
is the same, no
I can confirm that this bug is true in the Hardy 8.04 Beta that was just
released. I have a Toshiba laptop with a built-in intel 3945 wireless
adapter. Fron the nm-applet I can see my neighbors' networks. Since my
SSID is hidden, I have to manually configure it. When manually
configuring using
David :
Thanks a lot your patch worked for me and now I am able
to connect to hidden SSID networks.
--
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
David:
can I use your patch to connect to a hidden SSID network with 64/128 bit
WEP encryption
thanks
--
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.
--
Rama, I am connecting to a network with 64-bit WEP encryption.
The patch I wrote will only fix the issue if you are using the
ndiswrapper or prism54 wireless drivers. These are both breaking
because NetworkManager is issuing the incorrect AP_SCAN value to
wpa_supplicant. Beyond that, there are
Sorry Alexander, but the latest upgrade to Hardy network-
manager-0.6.6-0ubuntu2 didn't change the non-working atheros for my
AR5211 and AR5212's - when connecting to the different APs with WPA1 and
hidden SSIDs I have access to. Rolling back to the network-
manager_0.6.5-0ubuntu16.7.10.0_i386.deb
for ipw2200 i don't know, but most likely it doesn't expose the
scan_capa capability 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
1. atheros should work again with latest upload.
2. drivers for intel 3945 was switched to iwl3945 which still uses a bad mac
implementation that lacks the scan_capa capability patches. I won't tweak this
unless I know that the mac implementation will stay broken like
now for final. thus
Can confirm this in Hardy Alpha 6. I can not connect to a wireless lan
(WPA Enterprise) that has a hidden SSID. This worked fine in 7.10. This
is on a Dell XPS M1210 using the Intel 945 chipset.
--
can't connect to hidden network
https://bugs.launchpad.net/bugs/50214
You received this bug
until all the drivers for WiFi cards are changed to add an argument that
is now required by NM, its doubtful that wifi will work properly. The
fix if the hidden SSID problems is solved in NM with a new parameter
argument that is supplied by the wireless driver. there have been no
driver updates as
After upgrading Hardy beta 5 to Hardy beta 6 connectivity to hidden
SSIDs with ipw2200/2915 and atheros based cards (AR5212 chip) don't work
any more.
Done some further testing, and found the patched/changed network manager
0.6.6-0ubuntu1 was installed. After experiencing the problem on a couple
** Changed in: knetworkmanager (Baltix)
Status: New = Fix Released
** Changed in: knetworkmanager (Baltix)
Status: Fix Released = Invalid
--
can't connect to hidden network
https://bugs.launchpad.net/bugs/50214
You received this bug notification because you are a member of Ubuntu
I can automatically connect to hidden AP in either Vanilla Ubuntu
(Gutsy) or LinuxMint (Darnya(based on Gutsy)).
I was trying out the latest alpha build of Xubuntu (Hardy) and I guess
the bug is back because i was unable to connect to it at all. Also if i
tried a second time to connect it would
scubanator87 - the issue here is not automatic connection - it's being
able to connect period to hidden networks. The issue seems to be that
network-manager is not interfacing with several drivers the way it is
supposed to (using the wrong AP_SCAN value, for example). I assume then
that there is
The patch also works fine for me too on 7.10.0. If only I could connect
automatically to the hidden SSID at the university.
--
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
I created an account here just to say, THANKS! to David Ward. The
patch worked great. Why on earth isn't this bug been fixed since it has
been known for nearly 2 years
--
can't connect to hidden network
https://bugs.launchpad.net/bugs/50214
You received this bug notification because you
Thank you for that work around, but I think the ability beeing able to change
and connect a wlan with the user interface (knetworkmanager or under gnome)
should work out of the box, it is a core feature !
I'm experiencing the same problem under hardy 5, even when connecting via
connect another
I am using NDISWRAPPER with Feisty Fawn 7.04 and can't connect to hidden
network. If the patch is simply just changing to AP_SCAN2, where is
this change made at? I can just do it manually without applying the
patch and see if there is any success. In other news, I am still
appalled that this
In case anyone is interested, here is a workaround found for ipw2200 and
gutsy. I found these instructions in some ipw2200 forum, and they DO
work! Just add ap_scan=2 and an explicit key_mgmt= line in your
/etc/wpa_supplicant.conf file.
Example:
ctrl_interface=/var/run/wpa_supplicant
** Tags added: qa-hardy-platform
** Tags removed: qa-hardy-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 the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
Alexander, once the fix is confirmed, will it make it to Hardy? I am
running Hardy Alpha4 now and I still can not connect to hidden SSID's
(In my case I am using WPA Encryption). And I am also using your
Network-Manager 0.7 PPA also.
P.S. NM 0.7 is working great BTW (Minus the hidden SSID issue).
ok, I can confirm that the NM update as well as the gnome-N-M update
that came out several weeks ago DID NOT resolve the problem I am having
with hidden SSID AP's, however I seem to recall that the wireless
drivers had to be updated to accept or pass some new Variable that was
needed. I really did
** Changed in: network-manager
Status: Confirmed = 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 the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
Gene, the released fix appears to be for the upstream NetworkManager
package in GNOME, not the Ubuntu network-manager package that is linked
to the same bug report. Take a look at the bug page:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/50214
So hopefully that fix will make
I received an email message this morning stating :
** Changed in: network-manager
Status: Confirmed = Fix Released
So I did a manual update of the affected computer and nothing was
updated. If this bug fix has been released, then why would there be no
NM updates today ? Also, this will be
, my bad.hummm, no way to edit. I did not realize how this
launchpad thing was setup, it looks like I did not understand that this
was not a Ubuntu bug reporting tool, but rather a common location for
affected distros ? is that correct ?
I guess that really answers my next question, I
NetworkManager is just a tool to control your network connections. It
assumes that you already have a network/wireless driver installed
correctly, which is either compiled in the kernel or is a kernel
module. So if you are having a trouble with the kernel driver for your
network card, you
** Changed in: network-manager
Status: Invalid = Confirmed
--
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 the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
1 - 100 of 215 matches
Mail list logo
