Re: [Bug 50214] Re: can't connect to hidden network
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 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 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
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 afterward. I will play with these things a bit more when I find time. In the meantime, I will check out the archive deb package and see how I go with that. Matt On Tue, Apr 1, 2008 at 11:01 AM, Alexander Sack [EMAIL PROTECTED] wrote: 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 connecting to hidden SSID (or connecting at all), please file a new ipw2200 bug. For the signing error during build: the failure to sign is not a problem for local tests. I think the error message would not have popped up if you build like: debuild -b -uc -- 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/13016043/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
Re: [Bug 50214] Re: can't connect to hidden network
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
Re: [Bug 50214] Re: can't connect to hidden network
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
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
Re: [Bug 50214] Re: can't connect to hidden network
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
Re: [Bug 50214] Re: can't connect to hidden network
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
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
Re: [Bug 50214] Re: can't connect to hidden network
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
Re: [Bug 50214] Re: can't connect to hidden network
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 its way downstream and we can see what happens. David Gene Caldwell wrote: 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 the second time the status has been changed from Confirmed = Fix Released. I changed the status back to confirmed FROM FIX released on 2007-12-15. It looks like there is a problem or disconnect between what end users see and what developers think has happened. Status should not be changed from confirmed to released until it can be confirmed that end users have access to the FIXED software AND confirm that the release has indeed resolved the problem. Since there are no confirmed reports from bug reporters of this bug that the fix worked, I believe that the status change in this bug was way too premature and SHOULD be changed back to confirmed until such time as it is confirmed that the bug is resolved in the real world. -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 50214] Re: can't connect to hidden network
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 need to get that fixed before you can use NetworkManager. Now NetworkManager may have a problem *using* your specific driver correctly... in my case, it is simply issuing the wrong command (AP_SCAN 1) to wpa_supplicant, when in fact it should be AP_SCAN 2 for ndiswrapper. But this is not (I don't think) a problem with the ndiswrapper kernel module. And bug 39707 is a completely separate issue altogether. -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 50214] Re: can't connect to hidden network
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) and a PCI Netgear WG311T (Atheros AR5211), they work perfect, as they did in Edgy (so now it's certainly time for an upgrade) Not to confuse anything, but I can mention that the Intel 2200BG and the Intel 2915ABG continues to work after a upgrade too, as they did before. Well done. Please backport this to Feisty (and Dapper since it's still supported). Thank you! Matt -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 50214] Re: can't connect to hidden network
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 file in /var/run'). The problem is that each time I install the package it breaks my connection; I have to run remove --purge and put my /etc/network/interfaces back in place just to run a search the problem on google. Hello Ludovico, For something so simple, I find manipulating the results of the scripts can help. They are in /var/lib/dpkg/info/ and have names like package.prerm and package.postinst etc remove --purge is rather extreme. Have you simply tried removing the pid file in /var/run/?? -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 50214] Re: can't connect to hidden network
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 documentation that explains the hex dumps. Thanks again, Ben Gladwell Alexander Sack [EMAIL PROTECTED] wrote: 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 direct subscriber of the bug. - Tonight's top picks. What will you watch tonight? Preview the hottest shows on Yahoo! TV. Sep 25 13:05:36 linspiron6400 ntpd_initres[5861]: ntpd returns a permission denied error! Sep 25 13:05:36 linspiron6400 last message repeated 4 times Sep 25 13:05:37 linspiron6400 kernel: [13180.384000] ''IN-world':'IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:18:8b:b3:e0:16:08:00 SRC=192.168.1.150 DST=192.168.1.255 LEN=78 TOS=0x00 PREC=0x00 TTL=128 ID=61052 PROTO=UDP SPT=137 DPT=137 LEN=58 Sep 25 13:05:38 linspiron6400 kernel: [13181.584000] ''IN-world':'IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:50:04:f2:71:7e:08:00 SRC=192.168.1.151 DST=192.168.1.255 LEN=78 TOS=0x00 PREC=0x00 TTL=128 ID=7858 PROTO=UDP SPT=137 DPT=137 LEN=58 Sep 25 13:05:39 linspiron6400 kernel: [13182.64] ''IN-world':'IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:18:8b:b3:e0:16:08:00 SRC=192.168.1.150 DST=192.168.1.255 LEN=78 TOS=0x00 PREC=0x00 TTL=128 ID=61058 PROTO=UDP SPT=137 DPT=137 LEN=58 Sep 25 13:05:40 linspiron6400 kernel: [13183.388000] ''IN-world':'IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:18:8b:b3:e0:16:08:00 SRC=192.168.1.150 DST=192.168.1.255 LEN=78 TOS=0x00 PREC=0x00 TTL=128 ID=61060 PROTO=UDP SPT=137 DPT=137 LEN=58 Sep 25 13:05:41 linspiron6400 kernel: [13184.748000] ''IN-world':'IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:50:04:f2:71:7e:08:00 SRC=192.168.1.151 DST=192.168.1.255 LEN=78 TOS=0x00 PREC=0x00 TTL=128 ID=7871 PROTO=UDP SPT=137 DPT=137 LEN=58 Sep 25 13:05:42 linspiron6400 kernel: [13185.50] ''IN-world':'IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:50:04:f2:71:7e:08:00 SRC=192.168.1.151 DST=192.168.1.255 LEN=78 TOS=0x00 PREC=0x00 TTL=128 ID=7874 PROTO=UDP SPT=137 DPT=137 LEN=58 Sep 25 13:05:43 linspiron6400 kernel: [13186.404000] ''IN-world':'IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:01:03:1d:54:22:08:00 SRC=192.168.1.149 DST=192.168.1.255 LEN=78 TOS=0x00 PREC=0x00 TTL=128 ID=61196 PROTO=UDP SPT=137 DPT=137 LEN=58 Sep 25 13:05:44 linspiron6400 kernel: [13187.90] ''IN-world':'IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:01:03:1d:54:22:08:00 SRC=192.168.1.149 DST=192.168.1.255 LEN=78 TOS=0x00 PREC=0x00 TTL=128 ID=61198 PROTO=UDP SPT=137 DPT=137 LEN=58 Sep 25 13:05:52 linspiron6400 kernel: [13195.38] ''IN-world':'IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:18:8b:b3:e0:16:08:00 SRC=192.168.1.150 DST=192.168.1.255 LEN=78 TOS=0x00 PREC=0x00 TTL=128 ID=61152 PROTO=UDP SPT=137 DPT=137 LEN=58 Sep 25 13:05:52 linspiron6400 kernel: [13195.38] ''IN-world':'IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:18:8b:b3:e0:16:08:00 SRC=192.168.1.150 DST=192.168.1.255 LEN=78 TOS=0x00 PREC=0x00 TTL=128 ID=61153 PROTO=UDP SPT=137 DPT=137 LEN=58 Sep 25 13:05:52 linspiron6400 kernel: [13195.38] ''IN-world':'IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:18:8b:b3:e0:16:08:00 SRC=192.168.1.148 DST=192.168.1.255 LEN=78 TOS=0x00 PREC=0x00 TTL=128 ID=61154 PROTO=UDP SPT=137 DPT=137 LEN=58 Sep 25 13:05:52 linspiron6400 kernel: [13195.38] ''IN-world':'IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:18:8b:b3:e0:16:08:00 SRC=192.168.1.148 DST=192.168.1.255 LEN=78 TOS=0x00 PREC=0x00 TTL=128 ID=61155 PROTO=UDP SPT=137 DPT=137 LEN=58 Sep 25 13:05:53 linspiron6400 kernel: [13196.132000] ''IN-world':'IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:18:8b:b3:e0:16:08:00 SRC=192.168.1.150 DST=192.168.1.255 LEN=78 TOS=0x00 PREC=0x00 TTL=128 ID=61156 PROTO=UDP SPT=137 DPT=137 LEN=58 Sep 25 13:05:53 linspiron6400 kernel: [13196.88] ''IN-world':'IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:18:8b:b3:e0:16:08:00 SRC=192.168.1.150 DST=192.168.1.255 LEN=78 TOS=0x00 PREC=0x00 TTL=128 ID=61160 PROTO=UDP SPT=137 DPT=137 LEN=58 Sep 25 13:05:54 linspiron6400 kernel: [13197.636000] ''IN-world':'IN=eth0 OUT= MAC=ff:ff:ff:ff:ff:ff:00:18:8b:b3:e0:16:08:00 SRC=192.168.1.150 DST=192.168.1.255 LEN=78 TOS=0x00 PREC=0x00 TTL=128 ID=61164 PROTO=UDP SPT=137 DPT=137 LEN=58 Sep 25 13:05:55 linspiron6400 NetworkManager: debug info^I[1190739955.300654] nm_device_802_11_wireless_get_activation_ap (): Forcing AP 'goawillow' Sep 25 13:05:55 linspiron6400 NetworkManager: information^IUser Switch: /org/freedesktop/NetworkManager/Devices/eth1 / goawillow Sep 25 13:05:55 linspiron6400 NetworkManager: information^IDeactivating device eth1. Sep 25 13:05:55 linspiron6400 dhcdbd: message_handler: message
Re: [Bug 50214] Re: can't connect to hidden network
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. I have to kill NetworkManager and run it again (with --no-daemon) if the association needs to be repeated. Can someone reproduce this workaround? and just restarting NetworkManager doesn't help? or killing and starting with --no-daemon parameter? - Alexander Who are you talking to? It sounds like Alexander answered your question before you asked it, and if you were not talking to Alexander, please indicate who you were talking to so that we can appropriately and promptly respond. I do not wish for this bug to be REJECTED because we dropped the ball on communication. -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 50214] Re: can't connect to hidden network
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 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 reproduce this workaround? and just restarting NetworkManager doesn't help? or killing and starting with --no-daemon parameter? - Alexander Who are you talking to? It sounds like Alexander answered your question before you asked it, and if you were not talking to Alexander, please indicate who you were talking to so that we can appropriately and promptly respond. I do not wish for this bug to be REJECTED because we dropped the ball on communication. Its obvious imo ... I quoted Vaclav (see above) ... so the questions was for him. - 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 the bug contact for 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
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 --no-daemon) if the association needs to be repeated. Can someone reproduce this workaround? and just restarting NetworkManager doesn't help? or killing and starting with --no-daemon parameter? - 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 the bug contact for 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
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 trigger the association and fix the problem. Is there a chance that this would fix it on Ubuntu too? I've done this to make the wifi work with other networks, but not to get access to a 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. -- 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
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 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 other system on my laptop and use *buntu only on my desktop (wired) system. We need to confirm that getting things in synch actually fixes things. For me it doesn't here on feisty. Have no idea where to get a wireless tools that is compatible with gutsy atm. Anyway: Please show more evidence that bringing them in sych fixes issues for you. If that is the case, I will take care that the kernel team acts more responsible in this regards. Thanks Alexander... Having one developer develop a deb (or two or three) and distributing them make more sense, as most of us aren't developers per se, and the recompiling is likely to provide inconsistent results. I'll install a package that I can remove and replace with the originals, but I'm not likely to compile from source, at least not without copy-and-paste instructions that we can all follow, making it more worth the time and potential down-time. I realize that I'm but one person. Perhaps one of the other folks who have indicated the fix could make debs available? -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 50214] Re: can't connect to hidden network
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 is using ndiswrapper / bcmwl5 for device 14E4:4311. lspci claims this is a Broadcom Dell Wireless 1390 WLAN Mini-PCI Card, though that's probably not what Compaq would like us to call it (since thisis a Presario F500). Everyone subscribed to this bug and running feisty ... can you please try to build the gutsy wireless tools package under feisty and see if your issues go away? You might need to build network-manager as well once you updated your wireless tools. If you need help on how to do that ping me on #ubuntu-devel or #ubuntu-bugs on freenode. Thanks for your help. ... the problem here still is that there are lots of people claiming different things ... so lets get this tracked down by testing first. - 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 the bug contact for 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
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 no Ubuntu dev who takes this fault seriously. until then I'll use other system on my laptop and use *buntu only on my desktop (wired) system. We need to confirm that getting things in synch actually fixes things. For me it doesn't here on feisty. Have no idea where to get a wireless tools that is compatible with gutsy atm. Anyway: Please show more evidence that bringing them in sych fixes issues for you. If that is the case, I will take care that the kernel team acts more responsible in this regards. - 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 the bug contact for 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
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. 2007/7/17, aquo [EMAIL PROTECTED]: 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 direct subscriber of the bug. -- 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 https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 50214] Re: 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 we know what the plans are? Is there something in the communication stream that needs to occur 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 the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
