64 bit wifi.sh gives me "failed to connect"

[aus9]

Ok so I loaded a different distro and got similar results.

then I read the arch wpa supplicant wiki and it had another method to try which is

This means that wpa_supplicant can be associated with wpa_passphrase and started with:

# wpa_supplicant -B -i interface -c <(wpa_passphrase MYSSID passphrase)


#########################

so

Code: [Select]

sudo su
wpa_supplicant -B -i wlan0 -c <(wpa_passphrase lucky2 <my-passphrase>)
Successfully initialized wpa_supplicant
nl80211: Driver does not support authentication/association or connect commands
nl80211: deinit ifname=wlan0 disabled_11b_rates=0
wlan0: Failed to initialize driver interface
its not looking good

and yes I do know I have drifted offtopic to wifi.sh but if members read these posts you may find it was at the request of another member I do so.

[aus9]

ahhhh  hang on....the arch wiki mentions this

Alternatively, when using special characters in the passphrase, rather than escaping them, simply invoke wpa_passphrase without specifying the passphrase. It will then prompt for it to be entered in the standard input where users can paste it even if it contains special characters.

my passphrase uses things like $ @ symbols

let me change my passphrase and see if that makes a diff

[aus9]

I deleted all wicd persistent files and the /opt wpa config and set up in my router a very simple temporary password by

Code: [Select]

wpa_passphrase lucky2 123456789 > wpa.conf
tc@box:~$ cat wpa.conf
network={
ssid="lucky2"
#psk="123456789"
psk=11ee6ba77897bad66d4670aa1f8934512a12f7dc1ba609d73fb8c5e2b4e2dbab
}

so its /home/tc/wpa.conf

2)

Code: [Select]

sudo su
root@box:/home/tc# wpa_supplicant -B -i wlan0 -c /home/tc/wpa.conf
Successfully initialized wpa_supplicant
nl80211: Driver does not support authentication/association or connect commands
nl80211: deinit ifname=wlan0 disabled_11b_rates=0
wlan0: Failed to initialize driver interface
I think at this stage I have tested nl80211 as far as my skills allow me.

I will add the -D wext option later when I get a chance

thanks for reading

[aus9]

have not got around to -D wext but wish to report a quirk???

Code: [Select]

wpa_passphrase lucky2 123456789$@  > wpa.conf
tc@box:~$ cat wpa.conf
network={
ssid="lucky2"
#psk="123456789"
psk=11ee6ba77897bad66d4670aa1f8934512a12f7dc1ba609d73fb8c5e2b4e2dbab
}

I changed passwd to add $@ but it is not being accepted.

and that means that the psk string is the same no mater if I enter 1-9 or 1-9#@
You can see this when you look at my last post

#psk="123456789"
   psk=11ee6ba77897bad66d4670aa1f8934512a12f7dc1ba609d73fb8c5e2b4e2dbab

and this is not faked.....so other members, with luck should be able to duplicate this quirk

This may explain why with my original password....under deleted /opt/wpa*.conf it was not working?

[aus9]

but the trouble is.....I now realize that I do not want to have a non-special symbol router passphrase.

I may not be the most secure person in LInux but I have always used  special characters.

Dear Moderators


I will  send a pm to coreplayer2, Juanito and Greg Erskine to see if they object to this entire thread  being removed.

Optionally I might create a new post that (unless you use special characters) that the method below IMHO is better than the wiki

Code: [Select]

wpa_passphrase ssid-name passphrase   > wpa.confresolves making copy and paste errors

[Juanito]

Why remove the thread - there's useful information in it.

[aus9]

@ Moderators and others
I repeat my request that this thread be deleted as I am the original poster and I have received pms and no-one has asked that the thread remain
including a recent poster

I have received some private messages and am aware that I can not reveal who said what. As a result of one or more of those pms....

1) Apparently wifi.sh can not handle special characters. This fact might be best to show in the info file
Remember I normally use ethernet so not adept at wifi.

2) I repeat wifi.sh does not work for me......it does not work in OP because I had special characters. Its my fault that I did not report that after I changed to simple passphrase wifi.sh still failed....for me.

At worse you could call it a bug......only if everyone used  my dog pile of a dongle....which is a class N dongle

I repeat that I believe the reason is the actual dongle and the actual module 8188eu.

unfortunately no-one read my OP section 2 where I asked

I can use ethernet  and I CAN use wicd but looking for help on how to get a log to try and find out why wifi.sh does not party

3) Unfortunately no-one has directly challenged my assertion in OP section 3.....which is also in the info file for 8188eu
that I believe the reason for not being able to use wifi.sh is the actual hardware with the actual kernel module.

I  do appreciate that I have received some suggestions  but all of those suggestions only cemented my view that people were responding to one issue they saw and not directly answering my questions in OP.

BUT
As the original poster, as rude as it may sound, I have not resolved this issue. I think it may be in the best long term interests to protect the reputation of TC, this entire post be deleted.  I now repeat that request to Moderators.

and because I am now cranky (well more cranky than normal ) I no longer wish or desire to spend any more time on this issue.

I have other things I want to do.....

thanks in advance

[aus9]

@ moderators

if for any reason you prefer this post remain,

suggest you change subject to

8188eu wifi dongles can only use wicd

and then I request, if you won't delete,  lock the thread as I will not spend any more time on this issue

[coreplayer2]

Hello

I'm not sure this will help but if you use auto connect "wifi.sh -a" you should find a log at "/tmp/wifi.log"