tag:blogger.com,1999:blog-4919301250565883027.post3992750285210098802..comments2023-10-12T07:27:42.362-07:00Comments on Linux And Other Rants: Having Linux Wireless Troubles? Try WPA!Rory Curtishttp://www.blogger.com/profile/03810740366674625135noreply@blogger.comBlogger10125tag:blogger.com,1999:blog-4919301250565883027.post-37455487402007623692007-09-27T10:03:00.000-07:002007-09-27T10:03:00.000-07:00so, is the problem of MSI 6877 solved?i dont think...so, is the problem of MSI 6877 solved?<BR/><BR/>i dont think we can push people not to use WEP.Try to flattening the Eartghttps://www.blogger.com/profile/16052686007647841925noreply@blogger.comtag:blogger.com,1999:blog-4919301250565883027.post-16151599799308359102007-09-23T02:36:00.000-07:002007-09-23T02:36:00.000-07:00I'm still having difficulties with this one. I hav...I'm still having difficulties with this one. I have exactly the same laptop, and am running the 7.04 release of Ubuntu... but no joy with regards to connection over WPA, WEP, or even an open network. The lappy can see the network, but when I try to connect to it, it will do it's little spinny icon thing for about ten seconds, and then give up. Bah.Kourosismhttps://www.blogger.com/profile/07295463060005759888noreply@blogger.comtag:blogger.com,1999:blog-4919301250565883027.post-13279572817267653322007-08-28T05:24:00.000-07:002007-08-28T05:24:00.000-07:00Hi, I had a similar problem but only this time it ...Hi, I had a similar problem but only this time it was on a desktop machine with Feisty installed. After going through everything (tutorials on the net, forums, etc), it turned out that the build-in knetworkmanager applet was having trouble connecting, so I disabled it and did everything manually (editing the network interfaces file) and bam! It worked. <A HREF="http://randomspark.wordpress.com/2007/08/26/kubuntu-fiesty-fawn-connect-your-rt61-to-the-wireless-network/" REL="nofollow"><BR/>Check out my post</A> on that one for more ;)Mikehttps://www.blogger.com/profile/10034013470734315283noreply@blogger.comtag:blogger.com,1999:blog-4919301250565883027.post-44928053422529863592007-08-28T02:52:00.000-07:002007-08-28T02:52:00.000-07:00I had a different experience. I had an old laptop ...I had a different experience. I had an old laptop at home running Windows 2K and I couldn't get it to connect to my wireless router at home using WEP. I stuck Mepis on it and couldn't believe it when it connected first time. The wireless setup on Mepis seemed so simple that I didn't think it would connect.Anonymoushttps://www.blogger.com/profile/07768227320292666938noreply@blogger.comtag:blogger.com,1999:blog-4919301250565883027.post-10305698291420572602007-08-27T23:40:00.000-07:002007-08-27T23:40:00.000-07:00Never, never use WEP encryption on a wireless conn...Never, never use WEP encryption on a wireless connection. WEP has been cracked since 2001 because of an internal error in the algorithm which gives you a 50% chance to break it at any given attempt. Any clueless script kiddie can crack into a WEP connection using freely available software. Always use WPA2.<BR/><BR/>Don't just take my word for it, google it or look it up in Wikipedia.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-4919301250565883027.post-68549330665967699532007-08-27T22:14:00.000-07:002007-08-27T22:14:00.000-07:00I've had similar experiences with Linux (or for th...I've had similar experiences with Linux (or for that matter OpenBSD) working a lot better and, more importantly, giving useful debugging information even when it doesn't. <BR/><BR/><I><plug type="shameless"></I><BR/>over in my own blog I have a couple of posts, <A HREF="http://bsdly.blogspot.com/2007/07/linux-is-easier-than-windows-hands-down.html" REL="nofollow">here</A> and <A HREF="http://bsdly.blogspot.com/2007/06/which-windows-xp-version-is-it-on-that.html" REL="nofollow">here</A> which illustrate the issues<BR/><I></plug></I><BR/><BR/>and in case you were wondering or you're not inclined to read the blog posts, non-techie users are generally very happy with their Ubuntu, thank you very much.Peter N. M. Hansteenhttps://www.blogger.com/profile/12852746787621165833noreply@blogger.comtag:blogger.com,1999:blog-4919301250565883027.post-89523958913098237062007-08-27T22:04:00.000-07:002007-08-27T22:04:00.000-07:00I just got a Linksys WRT300N and my SUSE 10.1 Acer...I just got a Linksys WRT300N and my SUSE 10.1 Acer Travelmate wouldn't connect until I switched the router to WPA2 personal w/ TKIP or AES<BR/><BR/>FWIWAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-4919301250565883027.post-90854451755692427982007-08-27T21:00:00.000-07:002007-08-27T21:00:00.000-07:00I ran into similar problems with a wifi PCMCIA car...I ran into similar problems with a wifi PCMCIA card on my laptop, and then I found a pretty good solution.<BR/><BR/>Check out WICD:<BR/>http://wicd.sourceforge.net/download.php<BR/>It's a wireless and wired network manager for Ubuntu Linux. Its got an intuitive GUI, it's pretty much automatic, and it'll easily install on most any debian/GNU system.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-4919301250565883027.post-40680384769466457352007-08-27T20:50:00.000-07:002007-08-27T20:50:00.000-07:00I've noticed that the NetworkManager applet (or ma...I've noticed that the NetworkManager applet (or maybe NM itself) has a really hard time guessing what keying method to use when you set it to "automatic." <BR/><BR/>Recently at my son's school I was trying to test a wireless connection using WPA2. They keying choices were "Automatic" and something else (I don't remember). After multiple failures, re-re-re-re-checking the password, etc., I manually selected the one keying option, and it worked like a charm!<BR/><BR/>Not that I think your dad should go back to WEP. Stick with WPA.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-4919301250565883027.post-8205835224107933952007-08-27T20:44:00.000-07:002007-08-27T20:44:00.000-07:00I have found that you may need to use the HEX vers...I have found that you may need to use the HEX version of your WEP passphrase - particularly if you are using a 40bit key and are using Knetworkmanager. It appears to only generates a 104bit key.Anonymousnoreply@blogger.com