Tiny Core Linux
Tiny Core Extensions => TCE Talk => Topic started by: aus9 on July 21, 2018, 03:48:57 AM
-
Hi
I normally get the net via ethernet cable and so this is a low priority request.
In case ethernet interferes with wifi I first
tce-load -i wicd
sudo /usr/local/etc/init.d/dbus start
sudo /usr/local/etc/init.d/wicd start
then use wicd to disconnect ethernet
then
tce-load -i wifi
sudo wifi.sh
I can not capture the next output but it scans networks and gives me something like this
Select Wifi Network
ESSID Enc Qual Channel Type
1. WiFi-Y5VY on 0 1 WPA
2. lucky2 on 0 6 WPA
3. SMA1992022723 on 0 6 WPA
4. Fon WiFi off 0 11
Enter selection ( 1 - 4 ) or (q)uit:
I select my router by number and input the passphrase and press enter
Sending credentials to requested access point <router-name> .......
under /tmp I can see a file with the correct passphrase....filename is wpa.<4 digit number>
contents is the correct passphrase .....eliminating my classic fail to wear googles and input wrong passphrase ;)
Failed to connect.
and it kicks me back to prompt
2) 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
hidden agenda.....I forced wicd as a running dep of 8188eu for this reason
thanks for reading
3) the possible reason....if I am right I put in the info file as
https://github.com/lwfinger/rtl8188eu/issues/197
In short, the (sub) driver that rtl8188eu requires to talk with wpa_supplicant (wext) is now deprecated, and NetworkManager apparently ignores all attempts to use wext. The only good long term solution is for rtl8188eu to become compatible with the modern 'nl80211' wpa_supplicant driver.
does this reason seem reasonable?
I am not of course a normal wifi user so rely on my gurus to reveal all.
-
What happens if you try wifi.sh without first having loaded or used wicd?
-
Hi
no change still failed to connect.
no wicd loaded and ethernet cable left intact, no attempt to remove ethernet module either
-
Have you tried to connect manually with wpa_supplicant?
-
Hi
I have attempted to follow the wiki here
http://wiki.tinycorelinux.net/wiki:setting_up_wifi#more_advanced_setupusing_wireless_tools
Connecting to a WPA-PSK secured access point
tce-load -i 8188eu wireless_tools wpa_supplicant-dbus
iwconfig output in quote box
snip
wlan0 unassociated ESSID:"" Nickname:"<WIFI@REALTEK>"
Mode:Auto Frequency=2.412 GHz Access Point: Not-Associated
Sensitivity:0/0
Retry:off RTS thr:off Fragment thr:off
Power Management:off
Link Quality=0/100 Signal level=0 dBm Noise level=0 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0
snip
so we know the kernel module and FW works.....at this point....wicd is not loaded...next
wpa_passphrase lucky2 <my-passphrase>
I then create /opt/wpa_supplicant with disguised contents of
ctrl_interface=/var/run/wpa_supplicant
network={
ssid=lucky2
proto=WPA
key_mgmt=WPA-PSK
pairwise=TKIP
group=TKIP
psk=long-string
}
next
wpa_supplicant -i lucky2 -c/opt/wpa_configure.conf &
tc@box:~$ Successfully initialized wpa_supplicant
Failed to open config file '/opt/wpa_configure.conf', error: No such file or directory
Failed to read or parse configuration '/opt/wpa_configure.conf'.
( it hangs here so I press enter to get prompt back)
[1]+ Done(255) wpa_supplicant -i lucky2 -c/opt/wpa_configure.conf
it claims it can not find my file.
ls -al /opt/wpa_configure.conf
-rw-r--r-- 1 tc staff 223 Jul 22 11:15 /opt/wpa_configure.conf
### Interesting for me....there is no /var/run/wpa_supplicant at this stage
I know I do not always wear my goggles but it looks correct?
I gave up ....loaded wicd as above etc and then the /var/run/wpa_supplicant appears
-
This works for me:
$ sudo wpa_supplicant -B -Dwext -i wlan0 -c/etc/wpa_configure.conf
Successfully initialized wpa_supplicant
$ sudo udhcpc -b -i wlan0 -x hostname:boxdell -p /var/run/udhcpc.wlan0.pid
udhcpc: started, v1.27.2
udhcpc: sending discover
udhcpc: sending select for 192.168.1.105
udhcpc: lease of 192.168.1.105 obtained, lease time 86400
deleting routers
route: SIOCDELRT: No such process
adding dns 192.168.1.1
..but I wonder if you need to replace "-Dwext" with "-Dnl80211"?
-
reply part one
you have used sudo....sudo appears not required in the wiki unless I run the diagnostic and here that is
sudo wpa_supplicant -i lucky2 -c/opt/wpa_configure.conf -d
wpa_supplicant v2.6
random: Trying to read entropy from /dev/random
Successfully initialized wpa_supplicant
Initializing interface 'lucky2' conf '/opt/wpa_configure.conf' driver 'default' ctrl_interface 'N/A' bridge 'N/A'
Configuration file '/opt/wpa_configure.conf' -> '/opt/wpa_configure.conf'
Reading configuration file '/opt/wpa_configure.conf'
Failed to open config file '/opt/wpa_configure.conf', error: No such file or directory
Failed to read or parse configuration '/opt/wpa_configure.conf'.
Failed to add interface lucky2
: Cancelling scan request
: Cancelling authentication timeout
####################################################
part two
using sudo now gives better info?
sudo wpa_supplicant -i lucky2 -c/opt/wpa_configure.conf &
tc@box:/opt$ Successfully initialized wpa_supplicant
Line 5: failed to parse ssid 'lucky2'.
Line 5: failed to parse ssid 'lucky2'.
Line 12: failed to parse network block.
Failed to read or parse configuration '/opt/wpa_configure.conf'
EDIT part three
the wiki in one section showed mynetwork with quotes but the conf without it
just amended conf and now I get
sudo wpa_supplicant -i lucky2 -c/opt/wpa_configure.conf &
tc@box:/opt$ Successfully initialized wpa_supplicant
Could not read interface lucky2 flags: No such device
nl80211: Driver does not support authentication/association or connect commands
nl80211: deinit ifname=lucky2 disabled_11b_rates=0
Could not read interface lucky2 flags: No such device
lucky2: Failed to initialize driver interface
-
part 4 reply so now attempting your other way
sudo wpa_supplicant -B -Dnl80211 -i wlan0 -c/opt/wpa_configure.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
nl80211: Driver does not support authentication/association or connect commands...does not look promising.
In my OP....I claimed the reason for using wicd is because
In short, the (sub) driver that rtl8188eu requires to talk with wpa_supplicant (wext) is now deprecated, and NetworkManager apparently ignores all attempts to use wext. The only good long term solution is for rtl8188eu to become compatible with the modern 'nl80211' wpa_supplicant driver.
are you now in agreement?
-
..and "sudo wpa_supplicant -B -Dwext -i wlan0 -c/opt/wpa_configure.conf" doesn't work either?
-
tce-load -i 8188eu wireless_tools wpa_supplicant-dbus
8188eu.tcz: OK
libiw.tcz: OK
wireless-4.14.10-tinycore64.tcz: OK
wireless_tools.tcz: OK
ncursesw.tcz: OK
readline.tcz: OK
libnl.tcz: OK
wpa_supplicant-dbus.tcz: OK
tc@box:~$ sudo wpa_supplicant -B -Dwext -i wlan0 -c/opt/wpa_configure.conf
Successfully initialized wpa_supplicant
rfkill: Cannot get wiphy information
ioctl[SIOCSIWAP]: Operation not permitted
tc@box:~$ tce-load -i rfkill
rfkill.tcz: OK
tc@box:~$ sudo wpa_supplicant -B -Dwext -i wlan0 -c/opt/wpa_configure.conf
Successfully initialized wpa_supplicant
rfkill: Cannot get wiphy information
ioctl[SIOCSIWAP]: Operation not permitted
ctrl_iface exists and seems to be in use - cannot override it
Delete '/var/run/wpa_supplicant/wlan0' manually if it is not used anymore
Failed to initialize control interface '/var/run/wpa_supplicant'.
You may have another wpa_supplicant process already running or the file was
left by an unclean termination of wpa_supplicant in which case you will need
to manually remove this file before starting wpa_supplicant again.
ioctl[SIOCSIWAP]: Operation not permitted
tc@box:~$ ls /var/run/
klogd.pid udhcpc.eth0.pid wpa_supplicant/
syslogd.pid utmp
tc@box:~$ sudo rm -rf /var/run/wpa_supplicant/wlan0
tc@box:~$ sudo wpa_supplicant -B -Dwext -i wlan0 -c/opt/wpa_configure.conf
Successfully initialized wpa_supplicant
rfkill: Cannot get wiphy information
ioctl[SIOCSIWAP]: Operation not permitted
EDIT
in at least one post I confused interface with router name
forgot to start rfkill done now
sudo /usr/local/etc/init.d/rfkill start
Unblocking rfkill device: all
done.
-
no more edits above so after rfkill I try
sudo rm -rf /var/run/wpa_supplicant/
tc@box:~$
tc@box:~$ sudo wpa_supplicant -B -Dwext -i wlan0 -c/opt/wpa_configure.conf
Successfully initialized wpa_supplicant
rfkill: Cannot get wiphy information
ioctl[SIOCSIWAP]: Operation not permitted
tc@box:~$ sudo wpa_supplicant -B -Dnl80211 -i wlan0 -c/opt/wpa_configure.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
edit
ethernet is still up....is that interfering?
sudo udhcpc -b -i wlan0 -x hostname:box -p /var/run/udhcpc.wlan0.pid
udhcpc: started, v1.27.2
udhcpc: sending discover
udhcpc: sending discover
udhcpc: sending discover
udhcpc: no lease, forking to background
tc@box:~$ ls /var/run
klogd.pid udhcpc.eth0.pid utmp
syslogd.pid udhcpc.wlan0.pid wpa_supplicant/
-
no rush to reply with any suggestions as its bed time for me
-
I think the title is misleading as wifi.sh works fine for all my systems with only wifi.tcz, deps and appropriate firmware extensions..
-
FYI: "wpa_configure.conf" is usually called "wpa_supplicant.conf"
Try adding "nl80211,wext" to /etc/sysconfig/wifi-wpadrv
-
@ coreplayer2
the title area does not give me enough room to provide a more friendly description of the issue.
and I said ME in the subject line.....so not sure why you inferring that I think you are are unable to use wifi.sh?
roughly its this
title=
I normally have no trouble using ethernet to get net, I can get wicd with no issues for my module 8188eu, but if I try to use wifi.sh I get "failed to connect"
also a long time ago I had a dongle that did work with wifi.sh so I have nothing personal against wifi.sh
if you read my OP
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
I would appreciate it, if you have time to answer that question and the other question as my attempt to explain why I am using wicd
so from my OP
3) the possible reason....if I am right I put in the info file as
https://github.com/lwfinger/rtl8188eu/issues/197
Quote
In short, the (sub) driver that rtl8188eu requires to talk with wpa_supplicant (wext) is now deprecated, and NetworkManager apparently ignores all attempts to use wext. The only good long term solution is for rtl8188eu to become compatible with the modern 'nl80211' wpa_supplicant driver.
does this reason seem reasonable?
I am not of course a normal wifi user so rely on my gurus to reveal all.
-
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
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.
-
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
-
I deleted all wicd persistent files and the /opt wpa config and set up in my router a very simple temporary password by
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) 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
-
have not got around to -D wext but wish to report a quirk???
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?
-
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
wpa_passphrase ssid-name passphrase > wpa.confresolves making copy and paste errors
-
Why remove the thread - there's useful information in it.
-
@ 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
-
@ 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
-
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"