** Changed in: network-manager (Ubuntu)
Status: Incomplete = Confirmed
Target: ubuntu-7.10 = ubuntu-8.04-beta
--
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
David,
I did tried your patch and it worked nicely for me. Thanks for the nice
instructions.
I am using Gutsy and Ndiswrapper for bcm4318 .
If somehow I can save this hidden ssid setting for my network .. then I do not
have to enter it every time.
Thanks
--
can't connect to hidden network
Yes, I got it done also David. I'm still trying to decide if the cure is
worse than the illness though, jury is still out on that - not
remembering the SSID or password on each boot is the sh**s. But It works
just fine and SSID is now hidden.
--
can't connect to hidden network
Glad that both of you were able to get it working.
NetworkManager should be remembering the SSID for hidden networks, but
it is not. This is a separate issue that is raised in bug 39707 (which
has also been open for a very long time). I'd suggest nominating that
bug for Hardy if you want to see
Can anyone confirm if this issue is affecting the upstream package in
Debian or GNOME? If so, we should change the status of that to
something other than Invalid. I don't see how this could only be
affecting Ubuntu unless they are using a later version of NetworkManager
(unless changes the
Okay so I did leave at least one step out... after
cd network-manager-0.6.5/
do this for quilt to work:
sudo ln -s debian/patches patches
I cleaned up the patch slightly and have re-attached it. The earlier
ones have been deleted to avoid confusion.
** Attachment removed:
Bravo, lets turn up the heat. I wish I could help, but I can't so all I
can do is report the problems I find. I have no clue if this patch will
fix my problem or not as I have no clue if I am using ndiswrapper or
not. I installed 7.10 fresh on a DELL Latitude C800 that has a netgear
PCMCIA WiFi
Gene, you can see if you are using ndiswrapper by typing the command:
ndiswrapper -l
If it's been set up, you should see at least one line containing driver
installed.
The only change I made in the patch was to always use AP_SCAN 2 for the
ndiswrapper driver.
--
can't connect to hidden network
nope, says its not installed, but can install it using apt-get. but I
read your patch and I don't think it applies to me, I can read code and
your patch seems to rule me out. I have a hidden AP, its not ad-hock,
and I see wpa_supplicant running as well as the prism54PCI running in
the task
Gene, I did some Google searching, and it appears that prism54 also
requires AP_SCAN 2 rather than AP_SCAN 1 to work properly, so you are
probably being affected by the same issue. I expanded the earlier patch
to fix prism54 in addition to ndiswrapper. (Disregard the earlier
patch; this one
ok, the stress is not that I have no clue what you want me to do, nor is
it that I will have to trust you didn't leave a step out, the stress is
that its the girlfriends computer and I won't know how long she becomes
ankle locked if I mess up her computer and she cannot get back onto the
web to do
has any one taken note that this has been an ongoing bug for well over
18 months now or three going on 4 releases of ubuntu ? why can't this
security threat get a higher priority ? I did a google for AP_SCAN 1 and
find that this issue affects more than just Ubuntu, most of the major
distros have a
** Tags added: 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
ubuntu-bugs@lists.ubuntu.com
This is bug is either not fixed or not released so I changed the status
from fixed release to incomplete. can someone who worked on this bug
add some comment about the actual status ? this is after all a security
issue.
** Changed in: network-manager (Ubuntu)
Status: Fix Released =
I have this very same problembut I did not see in this bug report
that NM see's the AP but refuses to connect if SSID broadcast is turned
off. I can understand why it might be a problem connecting if the AP is
hidden, but for Gutsy (NM) to know the AP is there, display the hidden
AP as a
** Changed in: network-manager
Status: New = 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
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
Same problem for me at Purdue. I have to restart NM after suspend/resume
to get it to connect again.
Also, every time I reboot, I have to type in all my connection
information again. Shouldn't this be saved in gconf?
--
can't connect to hidden network
https://bugs.launchpad.net/bugs/50214
You
I can connect to Purdue University's campus-wide wireless network with
NM, but NM doesn't reconnect to the network on the reboot or after
resume/suspend. I use 64bit Feisty on a HP laptop with ndswrapper and
Broadcom 4306 chipset. Is there a solution for this in Network Manager
0.6.4?
--
can't
I just identified that NM is surely the cause of my problem. I am using
ipw3945 and I can't connect to hidden WEP networks. I tried the some
commands [1] and I could connect without a problem. In order for me to
connect, I need to shut NM down. I can't connect with NM active.
[1]
I can confirm that versions -15 and -16 of NetworkManager have *broken
my ability to connect at all to hidden networks*, let alone
automatically re-connect to them after restart/suspend, for both me and
my two roommates' laptops. We all have different models of laptops but
are all using Gutsy,
I can confirm that versions -15 and -16 of NetworkManager have *broken
my ability to connect at all to hidden networks*, let alone
automatically re-connect to them after restart/suspend, for both me and
my two roommates' laptops. We all have different models of laptops but
are all using Gutsy,
ipw3945 works for me with Alexander's patch
It took me a couple tries, but I am now able to connect to my WPA-PSK
TKIP hidden SSID AP. I noticed at least one person using ipw3945 saying
the patch didn't work, so here are some things I did wrong at first:
1) You have to be running Gutsy
2) Make
I am still having problems connecting to my WEP encrypted hidden
network. Attached is the relevant portion of my syslog during the time
that my NetworkManager is trying to connect to the router.
Mark Ferguson helped to point out one of the key problems. In the
syslog, at line 19, despite my
I think there are two issues:
First: I can't connect at all using the free driver for RaLink: I can't
even connect to unhidden unprotected networks! So this would be the free
driver development issue.
Second: NM seems to be screwed (only for certain chips?). NM is not ok
from version -15
Jose,
I could be wrong, but this sounds like an issue unrelated to this bug report.
Christiansen suggesting following a different bug located here:
https://bugs.launchpad.net/ubuntu/+source/linux-ubuntu-modules-2.6.22/+bug/134660
It might be in your best interest to post your feedback there
josesuarez1983, Ioanna Ramfos and others with the RaLink chipset.
I seems that Gutsy has overall problems with the RaLink Chipset (or the
driver development seems to be the actual problem), so could it be that
your problem isn't a problem connecting to hidden access points with NM,
but a problem
Hi Alexander,
This patch you have applied has affected the ndiswrapper driver.
I am running Kubuntu on IBM laptop Z60t with Atheros wireless card
AR5212
Originally I think it was on Fiesty I had problems with a kernel
upgrade that effected my wireless connectivity to hidden networks.
I
This is the exact procedure I went about to get my internet working again. I
lost the package for 0.6.5-0ubuntu14, so I was forced to use those for Feisty,
which work just as well. (This is for a i386 system running Kubuntu; in order
words, I'm using KNetworkManager, not the GNOME one. Modify
josesuarez1983 is correct. This problem still persists for me. I
cannot connect to my hidden WEP-encrypted network, but as soon as I
unhide it, I can connect to it fine.
I'm running the latest Gutsy release with network-manager version
0.6.5-0ubuntu16. I've been working on this problem for
Since nm version 0.6.5-15 (this version included) I can't connect to my hidden
WEP-secured network. It worked fine with -14 version (the one included in Gutsy
Beta).
I use a Conceptronic C54Ri and I have never been able to connect to this
network using the rt61pci drivers contained in the
OK, it definately is a problem with nm versions -15 and -16 because with a
clean upgrade to Gutsy final release wireless doesn't work but then I down
grade all nm related packages to -14 version and... voilá wireless works again.
As I said before, I use a Conceptronic C54Ri with ndiswrapper
Hi guys,
i also still have the same problem. My mini-pci card Intersil Corporation
ISL3890 [Prism GT/Prism Duette]/ISL3886 [Prism Javelin/Prism Xbow] (rev 01)
refuses to connect to a network with a hidden ssid. I have Ubuntu gutsy with
the latest updates (networkmanager 0.6.5-Oubuntu16) and as
Unfortunately, this still doesn't work for the Ralink rt73 usb chipset
(rt2x00 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 the bug contact for Ubuntu.
--
ubuntu-bugs
I still can't connect to a hidden WEP network using intel 3945. I am
going to try out wlassistant and wicd (wicd.sf.net) next. Anyone
successful with that?
--
can't connect to hidden network
https://bugs.launchpad.net/bugs/50214
You received this bug notification because you are a member of
With the new network-manager installed, my hp dv6500t with Intel 4965 is
connecting fine to my hidden ssid.
--
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.
Great work Alexander and others ??, thanks for the well done work on
this one.
Tested the NM 0.6.5-0ubuntu16 from the repository on a buildin IBM 11a/b/g
Wireless LAN Mini PCI Adapter II (Athero AR5212), a PCMCIA Netgear WG511T
(Atheros AR5211) and a PCI Netgear WG311T (Atheros AR5211), they
On Tuesday 16 October 2007, Christiansen wrote:
Great work Alexander and others ??, thanks for the well done work on
this one.
Tested the NM 0.6.5-0ubuntu16 from the repository on a buildin IBM 11a/b/g
Wireless LAN Mini PCI Adapter II (Athero AR5212), a PCMCIA Netgear
WG511T (Atheros AR5211)
network-manager (0.6.5-0ubuntu16) gutsy; urgency=low
* debian/README.Debian: adapt README to match the new behaviour of
network-manager, which doesn't manage _any_ device configured in
/etc/network/interfaces anymore.
* debian/patches/42a_lp50214_gnome464215_fix_hidden.patch,series:
** Attachment added: patch to fix this
http://launchpadlibrarian.net/10004375/42a_gnome464215_fix_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 the bug contact for
** Changed in: network-manager (Ubuntu)
Target: None = ubuntu-7.10-rc
--
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
** Changed in: network-manager (Ubuntu)
Target: ubuntu-7.10-rc = ubuntu-7.10
--
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
this looks fine - it's working here, too.
--
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
ubuntu-bugs@lists.ubuntu.com
On Friday 12 October 2007, Ludovico Fischer wrote:
Hello, I managed to install the package but it does not work for me at
the moment. I think though it may not be related directlyto the bug, but
there seems to be a conflict with my manual setup (it says something
like 'there is already a pid
Thanks for the advice to apt-get remove network-manager and network-
manager-gnome. Unfortunately, that didn't work. I still have quite a
few unmet dependencies:
The following packages have unmet dependencies:
network-manager: Depends: libc6 (= 2.6-1) but 2.5-0ubuntu14 is installed.
Ben, I had to sudo apt-get remove network-manager and network-manager-
gnome. I then installed the package. Then I reinstalled network-manager-
gnome.
And it works perfectly! I connected to a hidden network with WPA2 no
problem. I'm running Gutsy with the latest updates.
*does a little dance*
When I try to install the test package, I get this error:
$ sudo dpkg -i network-manager_0.6.5-0ubuntu16~ppa3_i386.deb
Preparing to replace network-manager 0.6.4-6ubuntu7 (using
network-manager_0.6.5-0ubuntu16~ppa3_i386.deb) ...
Unpacking replacement network-manager ...
dpkg: error processing
Hello, I managed to install the package but it does not work for me at
the moment. I think though it may not be related directlyto the bug, but
there seems to be a conflict with my manual setup (it says something
like 'there is already a pid file in /var/run'). The problem is that
each time I
** Changed in: network-manager
Status: Unknown = New
--
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
gutsy is _required_ to test this package.
--
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
ubuntu-bugs@lists.ubuntu.com
Above fix let me connect to hidden open and WPA networks.
I tried switching between wired, WPA and open with a mix of hidden and open
network without seeing any problem.
I'm using it for a couple of hour now and didn't see any regression from
current gutsy yet.
--
can't connect to hidden
i uploaded a testpackage to my ppa with a patch i found in the upstream
bug added a minute ago to this bug.
Please get the network manager packages for version 0.6.5-0ubuntu16~ppa3
from my PPA and if you can connect to hidden networks.
** Changed in: network-manager (Ubuntu)
Status: Confirmed = In Progress
--
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
With the testpackage provided by Alexander it seems to work (tested with
ipw2200 and WPA/WPA2 encrypted network). Connected right after entering SSID
and Password.
As I have no Gutsy installed (needed because of newer libc etc. dependencies) I
used a USB pendrive system. Later I reinstalled the
Agreed, I'm running Gutsy with the latest updates and this is still a
problem.
--
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
This bug persists in Gutsy as well - see
https://bugs.launchpad.net/ubuntu/+source/gnome-network/+bug/136504
--
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.
bumping importance.
** Changed in: network-manager (Ubuntu)
Importance: Undecided = High
--
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
Ben, could you please attach your /var/log/syslog when trying to connect
to hidden network?
--
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
Thanks for taking the initiative on this.
I've attached my syslog as requested. I have edited out a bunch of hex
dumps, b/c I don't know what they represent and I don't want to submit
my WPA key. If I edited out something you need, I can get you that
information if you can point me to some
Killing NetworkManager and restarting with --no-daemon doesn't fix the
problem for me. (and its hard to see why it would)
ipw3945
uname -r: 2.6.20-16-generic
iwconfig --version:
iwconfig Wireless-Tools version 28
Compatible with Wireless Extension v11 to v20.
KernelCurrently
On Saturday 25 August 2007, Alexander Sack wrote:
On Thu, Aug 16, 2007 at 08:19:35AM -, Václav Šmilauer wrote:
I was able to work around this problem by killing NetworkManager and
running NetworkManager --no-daemon from root console. Then it associated
with the hidden network just fine.
On Mon, Aug 27, 2007 at 11:06:18AM -, Matthew Carpenter wrote:
On Saturday 25 August 2007, Alexander Sack wrote:
On Thu, Aug 16, 2007 at 08:19:35AM -, Václav Šmilauer wrote:
^^
I was able to work around this problem by killing
On Thu, Aug 16, 2007 at 08:19:35AM -, Václav Šmilauer wrote:
I was able to work around this problem by killing NetworkManager and
running NetworkManager --no-daemon from root console. Then it associated
with the hidden network just fine. I have to kill NetworkManager and run
it again (with
I was able to work around this problem by killing NetworkManager and
running NetworkManager --no-daemon from root console. Then it associated
with the hidden network just fine. I have to kill NetworkManager and run
it again (with --no-daemon) if the association needs to be repeated. Can
someone
Hi guys. Just a suggestion. While I do not have a similar setup to test
this in at the moment, I did have the same problem on a SuSE laptop
recently, running kernel 2.6.22.1-default and wireless-tools-29pre10-22.
Simply running iwlist scan seems to trigger the association and fix
the problem. Is
Hi clifford,
I'll try that, but I think that what you suggest is more a workaround
than a real solution. I don't want to have to type iwlist scan in the
console every time I need to connect to a wlan and most of ubuntu users
probably don't want too.
--
can't connect to hidden network
On Friday 27 July 2007, clifford wrote:
Hi guys. Just a suggestion. While I do not have a similar setup to test
this in at the moment, I did have the same problem on a SuSE laptop
recently, running kernel 2.6.22.1-default and wireless-tools-29pre10-22.
Simply running iwlist scan seems to
Hi Alexander. Before things got out of synch (Dapper AFAIK) it was
working correctly for me on few different machines.
Have no idea where to get a wireless tools that is compatible with
gutsy atm.
There is only one wireless tools and in gutsy there is the latest version - 29.
The trouble is
On Thursday 26 July 2007, Alexander Sack wrote:
On Tue, Jul 17, 2007 at 08:48:32AM -, Witold Krakowski wrote:
i want to see the fix for the kernel.
Me too. The trouble is that the kernel team, the NM team and whoever else
doesn't seem to care. This damn fault is here since dapper. I
On Tue, Jul 17, 2007 at 06:27:33PM -, SPaul wrote:
I've run into a similar problem on a laptop running Fiesty running
2.6.20-16-generic.
iwconfig --version says it is Wireless-Tools version 28, compatible with
v11-v20
and the kernel is compiled with Wireless Extension v21. The machine
On Tue, Jul 17, 2007 at 08:48:32AM -, Witold Krakowski wrote:
i want to see the fix for the kernel.
Me too. The trouble is that the kernel team, the NM team and whoever else
doesn't seem to care. This damn fault is here since dapper. I don't care
about it too anymore as long as there is
Confirmed on Feisty, ipw3945 (Lenovo 3000 N100 0689).
On the same box, wlassistant (Wireless Assistant 0.5.7) *can* connect to
a WPA2 AP with hidden ESSID (I put NM to sleep first). What's it doing
right..?
--
can't connect to hidden network
https://bugs.launchpad.net/bugs/50214
You received
I can also confirm this issue with hidden networks. please see my post
at: https://bugs.launchpad.net/bugs/127660. This is really making my
Kubuntu experience unpleasant! Help!!! Thanks!
--
can't connect to hidden network
https://bugs.launchpad.net/bugs/50214
You received this bug notification
Is there a configuration option for compiling the kernel and all the
modules with a different version of Wireless Extension? How have you
done this, you said This is a simple mismatch and the kernel team can
easily solve this by recompiling the kernel. I already did that on my
system and it works.
i want to see the fix for the kernel.
Me too. The trouble is that the kernel team, the NM team and whoever else
doesn't seem to care. This damn fault is here since dapper. I don't care about
it too anymore as long as there is no Ubuntu dev who takes this fault
seriously. until then I'll use
So you don't have any working fix at the moment?
--
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
ubuntu-bugs@lists.ubuntu.com
As I already told, I made it work on one of my computers, but I certainly
didn't make any patch.
Ubuntu Kernel Team and Ubuntu NM team should sort it out. That's all. This
bug is here for well over a year and I think it's time to fix it. If the
Ubuntu developers don't care, neither do I.
I've run into a similar problem on a laptop running Fiesty running
2.6.20-16-generic.
iwconfig --version says it is Wireless-Tools version 28, compatible with v11-v20
and the kernel is compiled with Wireless Extension v21. The machine is using
ndiswrapper / bcmwl5 for device 14E4:4311. lspci
I further investigated on this bug and can confirm there is a bug.
Connecting to a hidden network with the network manager doesn't work on
my feisty installation with kernel 2.6.20-16.
As already stated the wireless extensions of the kernel and Wireless
Tools don't match.
[EMAIL PROTECTED]:~$
It would be nice if Witold Krakowski could comment on how to
recompile the kernel with older wireless extension.
You're wrong. The right sentence is: It would be nice if Ubuntu Kernel
Team could recompile the damn kernel correctly
They KNOW how to do that and they should fix this, not me. I'm
My Wireless-Tools and Extension are compatible with each other:
[EMAIL PROTECTED]:~$ iwconfig --version
iwconfig Wireless-Tools version 28
Compatible with Wireless Extension v11 to v20.
KernelCurrently compiled with Wireless Extension v20.
wlan0 Recommend Wireless Extension
But You CAN connect to a hidden network, and you can because Wireless-
Tools and Extension are compatible with each other.
Your problem is quite different and i already seen it somewhere in the
forums. What we are talking about here is the incompatible Wireless-
Tools and Extensions.
--
can't
witold, can you please summarize the steps to take so we can set this
bug to triaged and finally implement a solution?
--
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
taking the lead for now.
** Changed in: network-manager (Ubuntu)
Assignee: (unassigned) = Alexander Sack
--
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.
Hi Alexander,
Are You asking me for steps necessary to solve the problem?
If so, the answer is simple - you have to compile the kernel with Wireless
Extension that is supported by the Wireless Tools used.
Here's a simple example: If we use Wireless Tools v29, which is compatible with
Wireless
Hi Julie, upgrading only wireless tools won't make difference, because
the kernel is recompiled with Wireless Extension version that is not
supported by Wireless Tools. This is a simple mismatch and the kernel
team can easily solve this by recompiling the kernel. I already did that
on my system
Confirmed in Kubuntu/Xubuntu/Ubuntu Feisty. I upgraded to the Gutsy
wireless-tools 29, which doesn't make any difference.
This is an -extremely- important bug and it needs to be addressed, since
it seems to have been a problem through several versions of Ubuntu.
In order to make my wireless
Oh wellthe ubuntu team is screwing this again...now, if you type
iwconfig --version you'll get the following:
[EMAIL PROTECTED]:~$ iwconfig --version
iwconfig Wireless-Tools version 29
Compatible with Wireless Extension v11 to v21.
KernelCurrently compiled with Wireless
Indeed it does. Do we know what the plans are?
I certainly don't know. I guess the ubuntu kernel team should know more about
this.
Is there something in the communication stream that needs to occur yet?
The first thing that should occur, is that somebody from QA should assign an
importance
Confirmed: Feisty latest, IPW3945.
I didn't have the problem in Edgy, but it's likely because I used manual
config of /etc/network/interfaces to setup my own maintained
/etc/wpa_supplicant.conf file. Even doing that, at some point I believe
I was force to tell iwconfig what the ssid was and then
Recompiling the kernel by yourself certainly not, but there are kernel
updates every now and then, so these kernels could be recompiled with
drivers supported by current stable version of Wireless tools. This does
make sense.
--
can't connect to hidden network
On Friday 15 June 2007, Witold Krakowski wrote:
Recompiling the kernel by yourself certainly not, but there are kernel
updates every now and then, so these kernels could be recompiled with
drivers supported by current stable version of Wireless tools. This does
make sense.
Indeed it does. Do
Same problem here...
If I try to connect the first time, NetworkManager sets the wrong
channel (at least, according to iwconfig). If I tell it to connect
again, before it times out, it associates with the AP correctly - but
still waits, for whatever reason. If I try to connect for the third
time,
Same problem here, on a thinkpad T41 with AR5212 in combination with an
apple airport wlan base station (hidden ssid, WPA2). The problem exists
here since my update to feisty, everything worked well with dapper.
Thanks
Kaspar Metz
--
can't connect to hidden network
Confirming this for ipw2200 as of Feisty. Since I switched from WEP to
WPA+WPA2 on my router, enabling SSID broadcast is the workaround I
currently use.
Small workaround that worked for me before figuring this out: After
logging in and entering the password for the keyring where the WPA
I have been having what seems to be the same issue. I use MAC filtering
and do not broadcast my SSID on my home wireless router. Using xubuntu
6.10 was not a problem, but after reinstalling fresh from the xubuntu
7.04 cd, it initially found the AP and got an IP address during install,
but after
I've been having this problem since I started trying FIesty. Disabled hiding
the SSID and Network Manager was able to connect. Otherwise, NM would sit at
28% and timeout eventually.
I'm also using the Atheros chipset to connect to a WGT624.
Thanks, Nathan
--
can't connect to hidden network
I also have the same problem with my HP Compaq nc6000 laptop, Atheros
driver, and using the new Feisty 7.04 release. If I understand what
you're saying, Witold, we need to recompile the kernel with Wireless
Extension v20 until Wireless Tools v29 is released. Any idea when that
release will
Hi David,
Yes, You understand correctly. Please find below the answer about availability
(this comes from Jean Tourrilhes, maintainer of Wireless Tools)
Personally, I tried to install the v29 pre17 (it is a beta version) and it
worked correctly, but I think that it is better to recompile kernel
I can firm - I have Atheros based card and Feisty beta with all updates
as of today. Cannot connect to Netgear WGT624 router if SSID is hidden.
Changing the router to broadcast SSID allows Feisty to connect.
--
can't connect to hidden network
https://bugs.launchpad.net/bugs/50214
You received
Same problem here with my hidden AP and my Inspiron 8200 laptop with a
Netgear WAG511 card (/using madwifi). A solution seems to be
uninstalling the NM and install Wicd. By the way I'm running Ubuntu 7.04
Beta with all updates installed as of the 12th of April 2007.
Regards
André
--
can't
101 - 200 of 215 matches
Mail list logo
