Tiny Core Base > TCB Bugs

TinyCore64 14.0 wifi.sh failures

<< < (2/5) > >>

Rich:
Hi jim
I did a little more digging. This worked:

--- Code: ---tc@box:~$ wpa_passphrase "Baymont Inn & Suites" PASSWORD | sudo tee -a /etc/wpa_supplicant.conf
network={
        ssid="Baymont Inn & Suites"
        #psk="PASSWORD"
        psk=66e49fe73d49ee76ac368db3afcdd2b52f0634127b5c257b907f8efaa72e9367
}
tc@box:~$ sudo wpa_supplicant -B -i wlan0 -c /etc/wpa_supplicant.conf
Successfully initialized wpa_supplicant
nl80211: kernel reports: Match already configured
nl80211: kernel reports: Match already configured
nl80211: kernel reports: Match already configured
nl80211: kernel reports: Match already configured
nl80211: kernel reports: Match already configured
nl80211: kernel reports: Match already configured
nl80211: kernel reports: Match already configured
nl80211: kernel reports: Match already configured
nl80211: kernel reports: Match already configured
nl80211: kernel reports: Match already configured
nl80211: kernel reports: Match already configured
nl80211: kernel reports: Match already configured
nl80211: kernel reports: Match already configured
nl80211: kernel reports: Match already configured
nl80211: kernel reports: Match already configured
nl80211: kernel reports: Match already configured
nl80211: kernel reports: Match already configured
nl80211: kernel reports: Match already configured
nl80211: kernel reports: Match already configured
nl80211: kernel reports: Match already configured
nl80211: kernel reports: Match already configured
tc@box:~$ iwconfig
lo        no wireless extensions.

dummy0    no wireless extensions.

tunl0     no wireless extensions.

wlan0     IEEE 802.11  ESSID:"Baymont Inn & Suites" 
          Mode:Managed  Frequency:2.462 GHz  Access Point: 54:B7:BD:DC:32:76   
          Bit Rate=1 Mb/s   Tx-Power=15 dBm   
          Retry short limit:7   RTS thr:off   Fragment thr:off
          Power Management:off
          Link Quality=48/70  Signal level=-62 dBm 
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:1   Missed beacon:0

eth0      no wireless extensions.

tc@box:~$
--- End code ---

So my guess is something in wifi.sh is tripping on the ampersand.

Rich:
Hi jim
The following 2 changes fix it.

Change this:

--- Code: --- gsub(" ","\\ ",sid[i])
--- End code ---
To this:

--- Code: --- gsub(" ","\\ ",sid[i])
gsub("&","\\\\&",sid[i])
--- End code ---

Change this:

--- Code: --- gsub(" ","\\ ",sid[selection])
--- End code ---
To this:

--- Code: --- gsub(" ","\\ ",sid[selection])
gsub("&","\\\\&",sid[selection])
--- End code ---

Makes me wonder what other legal characters can cause trouble.

    [Edit]: Fixed typo. Changed sid[ i] to sid[selection] in last line.  Rich

CentralWare:
"Illegal" characters for a network ID are: ?  "  $  [  \  ]  + so these should be ignore-able
I would ESTIMATE problems MAY exist with * % @ = / depending on the circumstance, platform and operating system.

CentralWare:
ADDN: ...and possibly `ticks and 'single-quotes'??

Rich:
Hi CentralWare
So I guess the question is, how many of those should
we allow for?
Space: The average user wants to insert field separators in names.
Ampersand: I get it, Ben & Jerry, Barnes & Noble, Punch & Judy, etc.

Do we want to accommodate every "genius" who wants to deviate
from using 0-9, A-Z, and a-z by using "clever" punctuation?

Navigation

[0] Message Index

[#] Next page

[*] Previous page