WiFi Revisited

snickerdoodle general
1
Apparently others are having far more success at establishing a WiFi connection than myself.

I've attached an entire session, perhaps there is a wizard out there who can help? Sure hope so !!!!

Hopefully before I go blind from frustration.

I'm running a WRT54G.

Chuck


2
What does the output of iw wlan0 link give you?

On Wednesday, July 13, 2016 at 10:20:15 AM UTC-7, Charles Glasser wrote:
Apparently others are having far more success at establishing a WiFi connection than myself.

I've attached an entire session, perhaps there is a wizard out there who can help? Sure hope so !!!!

Hopefully before I go blind from frustration.

I'm running a WRT54G.

Chuck


3
It's looks like wpa_supplicant is crashing which is not good behavior.
Take a careful look the wpa_supplicant.conf file. It seems like the wpa_supplicant program may be choking on it and crashing instead of doing something sensible.

In terms of making this easier from the terminal, we are working on seeing if we can get this utility to work:

https://packages.debian.org/sid/net/wicd-curses

If anyone wants to lend a hand in terms of patching it we would be extremely grateful.

-Jamil


On Wednesday, July 13, 2016 at 10:20:15 AM UTC-7, Charles Glasser wrote:
Apparently others are having far more success at establishing a WiFi connection than myself.

I've attached an entire session, perhaps there is a wizard out there who can help? Sure hope so !!!!

Hopefully before I go blind from frustration.

I'm running a WRT54G.

Chuck


4
be sure to check out the sdconnect utility script that was posted:

https://github.com/krtkl/snickerdoodle-utilities
5
It's unclear to me exactly where it is hanging up so we will need to make sure to eliminate some of the possible culprits.

1. Can you confirm that the wlan0 interface is being brought up (ifconfig wlan0 up). The first command you send is ifconfig wlan0 which will not bring up the interface on it's own.
2. Your wpa_supplicant.conf file references proto=WPA RSN which should be proto=RSN for WPA2 networks.
3. After running the wpa_supplicant, make sure to run iw wlan0 link and/or wpa_cli status to check the state of the interface/connection before asking the DHCP server for an IP address with dhclient

On Wednesday, July 13, 2016 at 10:20:15 AM UTC-7, Charles Glasser wrote:
Apparently others are having far more success at establishing a WiFi connection than myself.

I've attached an entire session, perhaps there is a wizard out there who can help? Sure hope so !!!!

Hopefully before I go blind from frustration.

I'm running a WRT54G.

Chuck


6


On Wednesday, July 13, 2016 at 11:25:01 AM UTC-7, Bush wrote:
It's unclear to me exactly where it is hanging up so we will need to make sure to eliminate some of the possible culprits.

1. Can you confirm that the wlan0 interface is being brought up (ifconfig wlan0 up). The first command you send is ifconfig wlan0 which will not bring up the interface on it's own.
2. Your wpa_supplicant.conf file references proto=WPA RSN which should be proto=RSN for WPA2 networks.
3. After running the wpa_supplicant, make sure to run iw wlan0 link and/or wpa_cli status to check the state of the interface/connection before asking the DHCP server for an IP address with dhclient

On Wednesday, July 13, 2016 at 10:20:15 AM UTC-7, Charles Glasser wrote:
Apparently others are having far more success at establishing a WiFi connection than myself.

I've attached an entire session, perhaps there is a wizard out there who can help? Sure hope so !!!!

Hopefully before I go blind from frustration.

I'm running a WRT54G.

Chuck

The segmentation fault is caused by running wpa_supplement a second time.
Running it fresh after a reboot gives Daemonize.. at the last line
Running iw wlan0 link gives back a wpa_state=SCANNING
running ifconfig wlan0 up doesn't return with anything but a prompt

I recaptured everything with a fresh boot but there doesn't appear to be a way to attach the file. Curious.

Regards,
Chuck

7
In the editor (after you click "Post reply"), "Attach a file" is one of the links just above the formatting menu. It took me a while to find it, too.

-Nick

On Wednesday, July 13, 2016 at 3:40:22 PM UTC-7, Charles Glasser wrote:


On Wednesday, July 13, 2016 at 11:25:01 AM UTC-7, Bush wrote:
It's unclear to me exactly where it is hanging up so we will need to make sure to eliminate some of the possible culprits.

1. Can you confirm that the wlan0 interface is being brought up (ifconfig wlan0 up). The first command you send is ifconfig wlan0 which will not bring up the interface on it's own.
2. Your wpa_supplicant.conf file references proto=WPA RSN which should be proto=RSN for WPA2 networks.
3. After running the wpa_supplicant, make sure to run iw wlan0 link and/or wpa_cli status to check the state of the interface/connection before asking the DHCP server for an IP address with dhclient

On Wednesday, July 13, 2016 at 10:20:15 AM UTC-7, Charles Glasser wrote:
Apparently others are having far more success at establishing a WiFi connection than myself.

I've attached an entire session, perhaps there is a wizard out there who can help? Sure hope so !!!!

Hopefully before I go blind from frustration.

I'm running a WRT54G.

Chuck

The segmentation fault is caused by running wpa_supplement a second time.
Running it fresh after a reboot gives Daemonize.. at the last line
Running iw wlan0 link gives back a wpa_state=SCANNING
running ifconfig wlan0 up doesn't return with anything but a prompt

I recaptured everything with a fresh boot but there doesn't appear to be a way to attach the file. Curious.

Regards,
Chuck

8
Rob:
THAT'S A GREAT UTILITY!!!!!!

Amazing how one simple little test reveals so much. Actually it wasn't quite that simple as I had to type it in a debug it, not knowing if it was already in the file system, looked didn't find it, The experience was worthwhile as that's more shell scripting than I've ever debugged - OK I admit it I've never debugged a shell script before:) Mighty touchy!

For wpa2
Setting proto to RSN
FAIL
Setting auth_alg to OPEN
FAIL
Setting key_mgmt to WPA-PSK
FAIL

OK on everything else for WPA2

For WPA
Setting auth_alg to OPEN
FAIL
Setting key_mgmt to WPA-PSK
FAIL
OK on everything else for WPA

For WEP
Invalid password -- I've no idea

Perhaps now it will be possible to focus in on the specific mechanism causing the problem

Regards,

Chuck



On Wednesday, July 13, 2016 at 11:18:13 AM UTC-7, Rob Barris wrote:
be sure to check out the sdconnect utility script that was posted:

9
To use the sdconnect script you will need to bring the wireless up and initialize the wpa_supplicant. The steps are as follows:

1. Remove any networks from /etc/wpa_supplicant.conf
2. After booting, bring up the wireless interface with ifconfig wlan0 up
a. Run ifconfig after bringing up the interface and confirm it is in the interface table
3. Start the wpa_supplicant using wpa_supplicant -Dnl80211 -c/etc/wpa_supplicant.conf -iwlan0 -B
a. The wpa_supplicant must be running for the wpa_cli utility to be used (referenced in the script)
4. Run the sdconnect script
./sdconnect wpa "Network" "Password"
for known network SSID password combinations or
./sdconnect
for interactive

Hopefully, this is helpful. I will be documenting this further so please post any results you have.

On Wednesday, July 13, 2016 at 7:40:39 PM UTC-7, Charles Glasser wrote:
Rob:
THAT'S A GREAT UTILITY!!!!!!

Amazing how one simple little test reveals so much. Actually it wasn't quite that simple as I had to type it in a debug it, not knowing if it was already in the file system, looked didn't find it, The experience was worthwhile as that's more shell scripting than I've ever debugged - OK I admit it I've never debugged a shell script before:) Mighty touchy!

For wpa2
Setting proto to RSN
FAIL
Setting auth_alg to OPEN
FAIL
Setting key_mgmt to WPA-PSK
FAIL

OK on everything else for WPA2

For WPA
Setting auth_alg to OPEN
FAIL
Setting key_mgmt to WPA-PSK
FAIL
OK on everything else for WPA

For WEP
Invalid password -- I've no idea

Perhaps now it will be possible to focus in on the specific mechanism causing the problem

Regards,

Chuck



On Wednesday, July 13, 2016 at 11:18:13 AM UTC-7, Rob Barris wrote:
be sure to check out the sdconnect utility script that was posted:

10
For setting up my WiFi on my snickerdoodle I followed the instructions from Adam Talyor's MicroZed Chronicles found here:

It worked for me. I hope it helps someone else.

Tom Olenik

On Thursday, July 14, 2016 at 1:17:54 AM UTC-4, Bush wrote:
To use the sdconnect script you will need to bring the wireless up and initialize the wpa_supplicant. The steps are as follows:

1. Remove any networks from /etc/wpa_supplicant.conf
2. After booting, bring up the wireless interface with ifconfig wlan0 up
a. Run ifconfig after bringing up the interface and confirm it is in the interface table
3. Start the wpa_supplicant using wpa_supplicant -Dnl80211 -c/etc/wpa_supplicant.conf -iwlan0 -B
a. The wpa_supplicant must be running for the wpa_cli utility to be used (referenced in the script)
4. Run the sdconnect script
./sdconnect wpa "Network" "Password"
for known network SSID password combinations or
./sdconnect
for interactive

Hopefully, this is helpful. I will be documenting this further so please post any results you have.

On Wednesday, July 13, 2016 at 7:40:39 PM UTC-7, Charles Glasser wrote:
Rob:
THAT'S A GREAT UTILITY!!!!!!

Amazing how one simple little test reveals so much. Actually it wasn't quite that simple as I had to type it in a debug it, not knowing if it was already in the file system, looked didn't find it, The experience was worthwhile as that's more shell scripting than I've ever debugged - OK I admit it I've never debugged a shell script before:) Mighty touchy!

For wpa2
Setting proto to RSN
FAIL
Setting auth_alg to OPEN
FAIL
Setting key_mgmt to WPA-PSK
FAIL

OK on everything else for WPA2

For WPA
Setting auth_alg to OPEN
FAIL
Setting key_mgmt to WPA-PSK
FAIL
OK on everything else for WPA

For WEP
Invalid password -- I've no idea

Perhaps now it will be possible to focus in on the specific mechanism causing the problem

Regards,

Chuck



On Wednesday, July 13, 2016 at 11:18:13 AM UTC-7, Rob Barris wrote:
be sure to check out the sdconnect utility script that was posted:

11
I may have spoke too soon. Those instructions certainly worked yesterday. I was accessing the snickerdoodle over WiFi via SSH from three difference computers and OS successfully. I did a power cycle and was going to record a video of the process and now it seems like everything is working except I can't get an IP address assigned at the end. wlan0 sees the router and seems to communicate with it, but there is problem down stream from there. I think this section of the log from running wpa_supplicant gives the clue of what is happening. I'd like to know why:

ctrl_interface_group=0
ctrl_iface bind(PF_UNIX) failed: Address already in use
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.

Failed to add interface wlan0
wlan0: Request to deauthenticate - bssid=00:00:00:00:00:00 pending_bssid=00:00:D
TDLS: Tear down peers
wlan0: No keys have been configured - skip key clearing
wlan0: State: DISCONNECTED -> DISCONNECTED

Any ideas for the non-expert Linux user? Also is it possible to add the sdconnect script to the microSD card in a host machine then reinstall it into the snickerdoodle. Seems like it could be easier. I tried it but got a permission denied error.

On Thursday, July 14, 2016 at 9:56:34 AM UTC-4, Tom Olenik wrote:
For setting up my WiFi on my snickerdoodle I followed the instructions from Adam Talyor's MicroZed Chronicles found here:

It worked for me. I hope it helps someone else.

Tom Olenik


12
Thanks Tom, now I don't feel so alone. I tried what you had suggested. There seem to be configurations files scattered around everywhere. Even after tracking down and clearing out the ones I know about. Same result.

On Thursday, July 14, 2016 at 8:35:26 AM UTC-7, Tom Olenik wrote:
I may have spoke too soon. Those instructions certainly worked yesterday. I was accessing the snickerdoodle over WiFi via SSH from three difference computers and OS successfully. I did a power cycle and was going to record a video of the process and now it seems like everything is working except I can't get an IP address assigned at the end. wlan0 sees the router and seems to communicate with it, but there is problem down stream from there. I think this section of the log from running wpa_supplicant gives the clue of what is happening. I'd like to know why:

ctrl_interface_group=0
ctrl_iface bind(PF_UNIX) failed: Address already in use
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.

Failed to add interface wlan0
wlan0: Request to deauthenticate - bssid=00:00:00:00:00:00 pending_bssid=00:00:D
TDLS: Tear down peers
wlan0: No keys have been configured - skip key clearing
wlan0: State: DISCONNECTED -> DISCONNECTED

Any ideas for the non-expert Linux user? Also is it possible to add the sdconnect script to the microSD card in a host machine then reinstall it into the snickerdoodle. Seems like it could be easier. I tried it but got a permission denied error.

On Thursday, July 14, 2016 at 9:56:34 AM UTC-4, Tom Olenik wrote:
For setting up my WiFi on my snickerdoodle I followed the instructions from Adam Talyor's MicroZed Chronicles found here:

It worked for me. I hope it helps someone else.

Tom Olenik


13
I deleted the file suggested by the log snippet I posted above then rebooted and went through the process again. Similar result although the message above is not there anymore. I've attached the entire wpa_supplicant log and the result from ifconfig following it. Its odd this was working perfectly yesterday. I have another snickerdoodle with a fresh image I'm going to try next.

If I understand the log at all (and I'm only guessing) its almost like the issue is somewhere around assigning the IP address. There are a few packets reported going both ways. So a connection is made. It runs into a problem though and disconnects. That is what it seems like anyway.

Tom Olenik

On Thursday, July 14, 2016 at 11:51:24 AM UTC-4, Charles Glasser wrote:
Thanks Tom, now I don't feel so alone. I tried what you had suggested. There seem to be configurations files scattered around everywhere. Even after tracking down and clearing out the ones I know about. Same result.

On Thursday, July 14, 2016 at 8:35:26 AM UTC-7, Tom Olenik wrote:
I may have spoke too soon. Those instructions certainly worked yesterday. I was accessing the snickerdoodle over WiFi via SSH from three difference computers and OS successfully. I did a power cycle and was going to record a video of the process and now it seems like everything is working except I can't get an IP address assigned at the end. wlan0 sees the router and seems to communicate with it, but there is problem down stream from there. I think this section of the log from running wpa_supplicant gives the clue of what is happening. I'd like to know why:

ctrl_interface_group=0
ctrl_iface bind(PF_UNIX) failed: Address already in use
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.

Failed to add interface wlan0
wlan0: Request to deauthenticate - bssid=00:00:00:00:00:00 pending_bssid=00:00:D
TDLS: Tear down peers
wlan0: No keys have been configured - skip key clearing
wlan0: State: DISCONNECTED -> DISCONNECTED

Any ideas for the non-expert Linux user? Also is it possible to add the sdconnect script to the microSD card in a host machine then reinstall it into the snickerdoodle. Seems like it could be easier. I tried it but got a permission denied error.

On Thursday, July 14, 2016 at 9:56:34 AM UTC-4, Tom Olenik wrote:
For setting up my WiFi on my snickerdoodle I followed the instructions from Adam Talyor's MicroZed Chronicles found here:

It worked for me. I hope it helps someone else.

Tom Olenik


Attached Files:
wpa_supplicant log.pdf
14
Ok so I just tried the same process I used yesterday to successfully connect snickerdoodle to WiFi on another snickerdoodle with a freshly imaged microSD card. Same result. Very odd. I am wondering if it might be an IP address allocation or security issue with the router.


On Thursday, July 14, 2016 at 12:12:43 PM UTC-4, Tom Olenik wrote:
I deleted the file suggested by the log snippet I posted above then rebooted and went through the process again. Similar result although the message above is not there anymore. I've attached the entire wpa_supplicant log and the result from ifconfig following it. Its odd this was working perfectly yesterday. I have another snickerdoodle with a fresh image I'm going to try next.

If I understand the log at all (and I'm only guessing) its almost like the issue is somewhere around assigning the IP address. There are a few packets reported going both ways. So a connection is made. It runs into a problem though and disconnects. That is what it seems like anyway.

Tom Olenik


15


On Wednesday, July 13, 2016 at 10:20:15 AM UTC-7, Charles Glasser wrote:
Apparently others are having far more success at establishing a WiFi connection than myself.

I've attached an entire session, perhaps there is a wizard out there who can help? Sure hope so !!!!

Hopefully before I go blind from frustration.

I'm running a WRT54G.

Chuck
I've turned off all the security and now have a dotted quad. Not ideal by any stretch, but I guess it's progress of some kind. Of course I'd rather be running with a WEP.

cg

cg