|
Originally Posted by arsie
 LOL if that were the case, I may as well jump of a bridge instead of trying to conquer linux
  Anyways, I had some success (even with the static IP. See below) I do have MAC address filtering set up. And I'm 100% sure the MAC address for this wireless card is on the list. But just so I could be 100% sure it wasn't interfering in any way I had disabled MAC filtering ever since my first post in this thread. --- A small taste of SUCCESS! I reinstalled ubuntu from scratch and this time I followed this guide. After that, I installed WICD to make my life easier. Then I disabled encryption in my router, and set up WICD with all my settings. And this time... I was able to get online WIRELESS  So then I enabled WPA, set up WICD to use WPA, but no luck... I get the same problem (an infinite loading page that never loads). Though WICD states that the connection is fine. I tried with WEP also. Same problem. btw, this is all with my Static IP and everything. When I connected wirelessly without encryption, it was also with my static IP set up. So I think we can eliminate that as a problem now. Why is it so hard to secure a wireless connection in linux? Sheeeesh...  I'm open to more suggestions. In the meantime, I'm going to get back to my research and see what I can find.  |
wpa_passphrase yourssid yourpassphrase
wpa_passphrase "yourssid" "yourpassphrase"
wpa_passphrase 'yourssid' 'yourpassphrase'
sudo /etc/init.d/networking restart
|
Originally Posted by arsie
IT WORKS!!!!!!!!!!!!!!!!!!!!!!!!
Last night I decided to give it one last attempt and I solved the puzzle! What was the culprit? This simple command:
Code:
wpa_passphrase yourssid yourpassphrase Code:
wpa_passphrase "yourssid" "yourpassphrase" In order to get the correct info, you must use single-quotes:
Code:
wpa_passphrase 'yourssid' 'yourpassphrase' Now everything works, and I don't need WICD or any other GUI for that matter. All I did was edit some simple files like you guys instructed me to do and all is good The only thing now is that every time I boot up the notebook, I have to enter the following command in order to get online:
Code:
sudo /etc/init.d/networking restart |
I'm particularly gratified to see that you were willing to put in a good deal of effort on your own. Makes it much more likely you'll get help in the future than if you'd just kept coming back with: "that didn't work, what else can I try?" good show!
|
Originally Posted by seablade
If memory serves, and this is digging a bit as Gentoo doesn't quite act like this, most linux distros do their startup procedure by having a series of scripts called S**ScriptName
It then runs the script based on the numbers where I put the stars, where 01 would be first and 99 would be last. So if you already have a link to a script in that directory called S40SomeScriptName you would need ot use a different number. I would recommend you even consider possibly having it after you X startup script and see if that works(After giving it time to connect) that way you can still have your bootup process pretty quick. Seablade |
|
Originally Posted by abf
good way to make boot process quick is to background all daemons, especially the networking which might take a while to start up...so it might as well do that while you are fiddling w/ login info @ gdm since its built in wait time anyway...rather than having to wait for it, then login (while the computer is not doing much). also of course go to System > Administration > Services and disable everything you are not gonna use (like bluetooth, printer, even cron and syslog might be a good idea)
|
|
Originally Posted by drlouis
first off, congrats! feels good to get a troublesome problem solved, huh?
|
|
Originally Posted by drlouis
now, I think it's interesting what finally fixed it for you, because I just double checked this on my system and I get the EXACT SAME OUTPUT with no quotes, single quotes OR double quotes..... it doesn't make a lick of difference. would you try it again? I suspect a typo may be the culprit.
|
|
Originally Posted by drlouis
I don't want to sound like I'm scolding, so please dont take it that way, but when asking for help, it's good to point out things like the need for quotes that weren't mentioned. often little seemingly inconsequential things can make a big difference.
|
|
Originally Posted by drlouis
I'm particularly gratified to see that you were willing to put in a good deal of effort on your own. Makes it much more likely you'll get help in the future than if you'd just kept coming back with: "that didn't work, what else can I try?" good show!
|
|
Originally Posted by arsie
I'm 110% sure the culprit was the quotes because I was able to reproduce it every time I tried. I'm pretty certain that the complexity of the password plays a huge role in this. If your password is simple then you can get away without any quotes at all. If your password is complex, then no quotes will give you an error. Double-quotes will let the command go through and you will get an output, although if your password is extremely complex, the double-quoted output would be incorrect. Single-quotes seem to always work no matter how complex the password is. So the lesson to learn from all of this: Always use single quotes no matter what and you will be fine.
Yep I know what you mean. The best part about troubleshooting a problem is what we learn from it in the end. In this particular case, it's important to know exactly what caused it so that when the next guy comes along we'll be ready |
louis@louis-laptop:~$ wpa_passphrase Ason35s5DFwz*58lswkSdiw aosW%2##0vsJBH49^FI5fg4dlGU7sd%
network={
ssid="Ason35s5DFwz*58lswkSdiw"
#psk="aosW%2##0vsJBH49^FI5fg4dlGU7sd%"
psk=8c8898f1ec6db332b7bea005826a3918602da25b8461d11ebaf630133cc53627
}
louis@louis-laptop:~$ wpa_passphrase 'Ason35s5DFwz*58lswkSdiw' 'aosW%2##0vsJBH49^FI5fg4dlGU7sd%'
network={
ssid="Ason35s5DFwz*58lswkSdiw"
#psk="aosW%2##0vsJBH49^FI5fg4dlGU7sd%"
psk=8c8898f1ec6db332b7bea005826a3918602da25b8461d11ebaf630133cc53627
}
louis@louis-laptop:~$ wpa_passphrase "Ason35s5DFwz*58lswkSdiw" "aosW%2##0vsJBH49^FI5fg4dlGU7sd%"
network={
ssid="Ason35s5DFwz*58lswkSdiw"
#psk="aosW%2##0vsJBH49^FI5fg4dlGU7sd%"
psk=8c8898f1ec6db332b7bea005826a3918602da25b8461d11ebaf630133cc53627
}
louis@louis-laptop:~$ wpa_passphrase a4Av894$Rfs83sf7^R aue2#Di8y987^Rfhoa3GSdiy87
network={
ssid="a4Av894^R"
#psk="aue2#Di8y987^Rfhoa3GSdiy87"
psk=7aa85285758f50bed5da0e9d731875d8dcd1e677673cd9e016a80a74c18b7115
}
louis@louis-laptop:~$ wpa_passphrase 'a4Av894$Rfs83sf7^R' 'aue2#Di8y987^Rfhoa3GSdiy87'
network={
ssid="a4Av894$Rfs83sf7^R"
#psk="aue2#Di8y987^Rfhoa3GSdiy87"
psk=06c16b12b2c30d970c1035a846900bc938701ecec80a81591f99de7bd9dd6ff2
}
louis@louis-laptop:~$ wpa_passphrase "a4Av894$Rfs83sf7^R" "aue2#Di8y987^Rfhoa3GSdiy87"
network={
ssid="a4Av894^R"
#psk="aue2#Di8y987^Rfhoa3GSdiy87"
psk=7aa85285758f50bed5da0e9d731875d8dcd1e677673cd9e016a80a74c18b7115
}
|
Originally Posted by drlouis
...and as arsie noted single quotes gives bad info.
|
Your results are also strange. This definitely has to be a bug. But all I know is no matter what double-quotes and no-quotes tell you, you better listen to single-quotes because he is always right Even in your example above, single-quotes is the only one giving you the correct information. No-quotes and double-quotes are liars. Here is my latest test (with a simple SSID and a complex Pass):
Note: With no-quotes you just get an error.
arsie@ubuntu:~$ wpa_passphrase MYSSID "bAFWWxS$s}i>5&xx.]p42"
network={
ssid="MYSSID"
#psk="bAFWWxS}i>5&xx.]p42"
psk=7051cba8702aa532b3ab20fb9b222c5773b5a65edcd7d530ca4d2c06fc88168e
}
arsie@ubuntu:~$ wpa_passphrase MYSSID 'bAFWWxS$s}i>5&xx.]p42'
network={
ssid="MYSSID"
#psk="bAFWWxS$s}i>5&xx.]p42"
psk=54a4974eb0e892e86bbbc07e0bc3c98f3186e2e82ae6d9b140c4584c3c855942
}
