search

wifinigel / wiperf

Utility to run various UX perf tests from an RPi/WLAN Pi and send results to various data repos
Other
26 stars 15 forks source link

wiperf does not connect to SSID #13

Closed credmond06 closed 4 years ago

credmond06 commented 4 years ago

wiperf does not connect to ssid. Will boot into wiperf mode, (once I disconnect the adapter), but once I plug in the adapter, the wlanpi freezes, or goes into a watchdog loop. I have followed the troubleshooting steps, upgraded the wiperf version etc. Below is the settings and logs. I must be missing something, but cant seem to see it. I have also tried different adapters with no change.

wiperf settings: ; ==================================================================== ; General settings - any changes to this section should only be ; made when in classic mode (not while in Wipef mode) on the WLAN Pi ; ==================================================================== [General] ; wlan interface name set this as per the output of an iwconfig command (usually wlan0) wlan_if: wlan0

; interface name over which mgt traffic is sent (i.e. how we get to Splunk) - options: wlan0, eth0, zt mgt_if: zt

; Platform architecture - choices: 'wlanpi' (WLPC WLAN-Pi),'rpi' (Raspberry Pi) platform: wlanpi

; Splunk host IP/name data_host: 10.147.xx.xx

; Splunk event collector port (8088 by default) data_port: 8088

; Splunk token to access Splunk server created by Splunk (example token: 84adb9ca-071c-48ad-8aa1-b1903c60310d) splunk_token: f9dd1431-d1fd-4819-a4b4-xxxxxxxxxxxx

; test interval (mins) - how often we want to run the tests (5 is the recommended minimum) test_interval: 5

; test offset from top of hour (must be less than test interval) - 0 = top of hour, 1 = 1 min after top of hour etc. test_offset: 0

; connectivity DNS lookup - site used for initial DNS lookup when assessing if DNS working OK connectivity_lookup: google.com

; location label for report filtering (if required) location:

wpa_supplicant: ap_scan=1

WPA2 PSK Network sample (highest priority - joined first)

network={ ssid="test_network" psk="password123" priority=10 }

2020-06-14 19:50:05,150 - Probe_Log - ERROR - Returning error... 2020-06-14 19:50:05,150 - Probe_Log - ERROR - Unable to get wireless info due to failure with ifconfig command 2020-06-14 19:50:05,152 - Probe_Log - ERROR - Attempting to recover by bouncing wireless interface... 2020-06-14 19:50:05,153 - Probe_Log - ERROR - Bouncing WLAN interface 2020-06-14 19:50:05,153 - Probe_Log - INFO - Bouncing interface wlan0 (platform type = wlanpi) 2020-06-14 19:50:05,527 - Probe_Log - ERROR - if bounce command appears to have failed. Error: ifdown: interface wlan0 not configured wpa_supplicant: /sbin/wpa_supplicant daemon failed to start run-parts: /etc/network/if-pre-up.d/wpasupplicant exited with return code 1 ifup: failed to bring up wlan0

2020-06-14 19:50:05,528 - Probe_Log - ERROR - Returning error... 2020-06-14 19:50:05,529 - Probe_Log - ERROR - Bounce completed. Exiting script. 2020-06-14 19:50:05,530 - Probe_Log - INFO - removing lock file 2020-06-14 19:55:05,291 - Probe_Log - INFO - 2020-06-14 19:55:05,292 - Probe_Log - INFO - Starting logging... 2020-06-14 19:55:05,292 - Probe_Log - INFO - 2020-06-14 19:55:05,315 - Probe_Log - INFO - No lock file found. Creating lock file. 2020-06-14 19:55:05,316 - Probe_Log - INFO - ########## wireless connection checks ########## 2020-06-14 19:55:05,317 - Probe_Log - INFO - Checking wireless connection available. 2020-06-14 19:55:05,329 - Probe_Log - ERROR - Issue getting interface info using iwconfig command: wlan0 No such device

2020-06-14 19:55:05,330 - Probe_Log - ERROR - Returning error... 2020-06-14 19:55:05,331 - Probe_Log - ERROR - Unable to get wireless info due to failure with ifconfig command 2020-06-14 19:55:05,333 - Probe_Log - ERROR - Attempting to recover by bouncing wireless interface... 2020-06-14 19:55:05,334 - Probe_Log - ERROR - Bouncing WLAN interface 2020-06-14 19:55:05,334 - Probe_Log - INFO - Bouncing interface wlan0 (platform type = wlanpi) 2020-06-14 19:55:05,525 - Probe_Log - ERROR - if bounce command appears to have failed. Error: ifdown: interface wlan0 not configured wpa_supplicant: /sbin/wpa_supplicant daemon failed to start run-parts: /etc/network/if-pre-up.d/wpasupplicant exited with return code 1 ifup: failed to bring up wlan0

2020-06-14 19:55:05,526 - Probe_Log - ERROR - Returning error... 2020-06-14 19:55:05,527 - Probe_Log - ERROR - Bounce completed. Exiting script. 2020-06-14 19:55:05,527 - Probe_Log - INFO - removing lock file 2020-06-14 20:15:05,814 - Probe_Log - INFO - 2020-06-14 20:15:05,815 - Probe_Log - INFO - Starting logging... 2020-06-14 20:15:05,816 - Probe_Log - INFO - 2020-06-14 20:15:05,841 - Probe_Log - INFO - No lock file found. Creating lock file. 2020-06-14 20:15:05,842 - Probe_Log - INFO - ########## wireless connection checks ########## 2020-06-14 20:15:05,843 - Probe_Log - INFO - Checking wireless connection available. 2020-06-14 20:15:05,923 - Probe_Log - INFO - Checking we're connected to the network 2020-06-14 20:15:05,924 - Probe_Log - INFO - Checking we have an IP address. 2020-06-14 20:15:05,942 - Probe_Log - ERROR - Problem with wireless connection: no valid IP address 2020-06-14 20:15:05,944 - Probe_Log - ERROR - Attempting to recover by bouncing wireless interface... 2020-06-14 20:15:05,945 - Probe_Log - ERROR - Bouncing WLAN interface 2020-06-14 20:15:05,946 - Probe_Log - INFO - Bouncing interface wlan0 (platform type = wlanpi) 2020-06-14 20:16:38,827 - Probe_Log - ERROR - Bounce completed. Exiting script. 2020-06-14 20:16:38,828 - Probe_Log - INFO - removing lock file 2020-06-14 20:20:04,602 - Probe_Log - INFO - 2020-06-14 20:20:04,604 - Probe_Log - INFO - Starting logging... 2020-06-14 20:20:04,604 - Probe_Log - INFO - 2020-06-14 20:20:04,625 - Probe_Log - INFO - No lock file found. Creating lock file. 2020-06-14 20:20:04,626 - Probe_Log - INFO - ########## wireless connection checks ########## 2020-06-14 20:20:04,627 - Probe_Log - INFO - Checking wireless connection available. 2020-06-14 20:20:04,709 - Probe_Log - INFO - Checking we're connected to the network 2020-06-14 20:20:04,711 - Probe_Log - INFO - Checking we have an IP address. 2020-06-14 20:20:04,727 - Probe_Log - ERROR - Problem with wireless connection: no valid IP address 2020-06-14 20:20:04,730 - Probe_Log - ERROR - Attempting to recover by bouncing wireless interface... 2020-06-14 20:20:04,730 - Probe_Log - ERROR - Bouncing WLAN interface 2020-06-14 20:20:04,731 - Probe_Log - INFO - Bouncing interface wlan0 (platform type = wlanpi) 2020-06-14 20:21:37,132 - Probe_Log - ERROR - Bounce completed. Exiting script. 2020-06-14 20:21:37,134 - Probe_Log - INFO - removing lock file 2020-06-14 20:25:04,869 - Probe_Log - INFO - 2020-06-14 20:25:04,870 - Probe_Log - INFO - Starting logging... 2020-06-14 20:25:04,870 - Probe_Log - INFO - 2020-06-14 20:25:04,891 - Probe_Log - INFO - No lock file found. Creating lock file. 2020-06-14 20:25:04,893 - Probe_Log - INFO - ########## wireless connection checks ########## 2020-06-14 20:25:04,893 - Probe_Log - INFO - Checking wireless connection available. 2020-06-14 20:25:04,970 - Probe_Log - INFO - Checking we're connected to the network 2020-06-14 20:25:04,971 - Probe_Log - INFO - Checking we have an IP address. 2020-06-14 20:25:04,988 - Probe_Log - ERROR - Problem with wireless connection: no valid IP address 2020-06-14 20:25:04,990 - Probe_Log - ERROR - Attempting to recover by bouncing wireless interface... 2020-06-14 20:25:04,991 - Probe_Log - ERROR - Bouncing WLAN interface 2020-06-14 20:25:04,991 - Probe_Log - INFO - Bouncing interface wlan0 (platform type = wlanpi) 2020-06-14 20:25:16,499 - Probe_Log - ERROR - if bounce command appears to have failed. Error: Killed old client process Internet Systems Consortium DHCP Client 4.3.5 Copyright 2004-2016 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/

/etc/dhcp/dhclient.conf line 21: semicolon expected.

}

^ Listening on LPF/wlan0/20:0d:b0:36:c3:42 Sending on LPF/wlan0/20:0d:b0:36:c3:42 Sending on Socket/fallback DHCPRELEASE on wlan0 to 10.0.1.1 port 67 wpa_supplicant: /sbin/wpa_supplicant daemon failed to start run-parts: /etc/network/if-pre-up.d/wpasupplicant exited with return code 1 ifup: failed to bring up wlan0

2020-06-14 20:25:16,500 - Probe_Log - ERROR - Returning error... 2020-06-14 20:25:16,501 - Probe_Log - ERROR - Bounce completed. Exiting script. 2020-06-14 20:25:16,502 - Probe_Log - INFO - removing lock file 2020-06-14 20:30:05,284 - Probe_Log - INFO - 2020-06-14 20:30:05,285 - Probe_Log - INFO - Starting logging... 2020-06-14 20:30:05,286 - Probe_Log - INFO - 2020-06-14 20:30:05,306 - Probe_Log - INFO - No lock file found. Creating lock file. 2020-06-14 20:30:05,307 - Probe_Log - INFO - ########## wireless connection checks ########## 2020-06-14 20:30:05,308 - Probe_Log - INFO - Checking wireless connection available. 2020-06-14 20:30:05,385 - Probe_Log - INFO - Checking we're connected to the network 2020-06-14 20:30:05,386 - Probe_Log - INFO - Checking we have an IP address. 2020-06-14 20:30:05,403 - Probe_Log - ERROR - Problem with wireless connection: no valid IP address 2020-06-14 20:30:05,405 - Probe_Log - ERROR - Attempting to recover by bouncing wireless interface... 2020-06-14 20:30:05,406 - Probe_Log - ERROR - Bouncing WLAN interface 2020-06-14 20:30:05,406 - Probe_Log - INFO - Bouncing interface wlan0 (platform type = wlanpi) 2020-06-14 20:31:25,740 - Probe_Log - ERROR - Bounce completed. Exiting script. 2020-06-14 20:31:25,742 - Probe_Log - INFO - removing lock file 2020-06-14 20:35:05,740 - Probe_Log - INFO - 2020-06-14 20:35:05,742 - Probe_Log - INFO - Starting logging... 2020-06-14 20:35:05,742 - Probe_Log - INFO - 2020-06-14 20:35:05,763 - Probe_Log - ERROR - Watchdog count exceeded...rebooting 2020-06-14 20:36:37,842 - Probe_Log - ERROR - Reboot output: 2020-06-14 20:36:37,843 - Probe_Log - INFO - No lock file found. Creating lock file. 2020-06-14 20:36:37,844 - Probe_Log - INFO - ########## wireless connection checks ########## 2020-06-14 20:36:37,845 - Probe_Log - INFO - Checking wireless connection available. 2020-06-14 20:36:37,925 - Probe_Log - INFO - Checking we're connected to the network 2020-06-14 20:36:37,926 - Probe_Log - INFO - Checking we have an IP address. 2020-06-14 20:36:37,943 - Probe_Log - ERROR - Problem with wireless connection: no valid IP address 2020-06-14 20:36:37,946 - Probe_Log - ERROR - Attempting to recover by bouncing wireless interface... 2020-06-14 20:36:37,947 - Probe_Log - ERROR - Bouncing WLAN interface 2020-06-14 20:36:37,950 - Probe_Log - INFO - Bouncing interface wlan0 (platform type = wlanpi) 2020-06-14 20:45:04,925 - Probe_Log - INFO - 2020-06-14 20:45:04,926 - Probe_Log - INFO - Starting logging... 2020-06-14 20:45:04,927 - Probe_Log - INFO - 2020-06-14 20:45:04,949 - Probe_Log - INFO - No lock file found. Creating lock file. 2020-06-14 20:45:04,950 - Probe_Log - INFO - ########## wireless connection checks ########## 2020-06-14 20:45:04,951 - Probe_Log - INFO - Checking wireless connection available. 2020-06-14 20:45:04,963 - Probe_Log - ERROR - Issue getting interface info using iwconfig command: wlan0 No such device

2020-06-14 20:45:04,964 - Probe_Log - ERROR - Returning error... 2020-06-14 20:45:04,965 - Probe_Log - ERROR - Unable to get wireless info due to failure with ifconfig command 2020-06-14 20:45:04,966 - Probe_Log - ERROR - Attempting to recover by bouncing wireless interface... 2020-06-14 20:45:04,967 - Probe_Log - ERROR - Bouncing WLAN interface 2020-06-14 20:45:04,968 - Probe_Log - INFO - Bouncing interface wlan0 (platform type = wlanpi) 2020-06-14 20:45:05,336 - Probe_Log - ERROR - if bounce command appears to have failed. Error: ifdown: interface wlan0 not configured wpa_supplicant: /sbin/wpa_supplicant daemon failed to start run-parts: /etc/network/if-pre-up.d/wpasupplicant exited with return code 1 ifup: failed to bring up wlan0

2020-06-14 20:45:05,338 - Probe_Log - ERROR - Returning error... 2020-06-14 20:45:05,339 - Probe_Log - ERROR - Bounce completed. Exiting script. 2020-06-14 20:45:05,340 - Probe_Log - INFO - removing lock file

wifinigel commented 4 years ago

Hiya,

I think the issue is that your wireless adapter never gets an IP address. The wireless connection seems to come up, but then the logs say that there is no IP address received. Is there a DHCP server on the network that you are joining?

Thanks Nigel.

credmond06 commented 4 years ago

Nigel,

Yes the DHCP server is running and working. Other devices get an IP address. I thought that weird also. I'm wondering if the Comfast adapter has issues with Meraki networks.

Thanks -Chris

On Mon, Jun 15, 2020, 08:23 Nigel Bowden notifications@github.com wrote:

Hiya,

I think the issue is that your wireless adapter never gets an IP address. The wireless connection seems to come up, but then the logs say that there is no IP address received. Is there a DHCP server on the network that you are joining?

Thanks

Nigel.

Nigel Bowden | Wireless Mobility Consultant

E: mailto:wifinigel@gmail.com wifinigel@gmail.com | M: <tel:+44%207592%20050459> +44 (0) 7592 050459 | Skype: ncbowden

W: http://wifinigel.com/ http://wifinigel.com | Twitter: @WifiNigel | LinkedIn: http://bit.ly/nigelbowden http://bit.ly/nigelbowden

From: credmond06 notifications@github.com Sent: 15 June 2020 03:10 To: wifinigel/wiperf wiperf@noreply.github.com Cc: Subscribed subscribed@noreply.github.com Subject: [wifinigel/wiperf] wiperf does not connect to SSID (#13)

wiperf does not connect to ssid. Will boot into wiperf mode, (once I disconnect the adapter), but once I plug in the adapter, the wlanpi freezes, or goes into a watchdog loop. I have followed the troubleshooting steps, upgraded the wiperf version etc. Below is the settings and logs. I must be missing something, but cant seem to see it. I have also tried different adapters with no change.

wiperf settings: ; ==================================================================== ; General settings - any changes to this section should only be ; made when in classic mode (not while in Wipef mode) on the WLAN Pi ; ==================================================================== [General] ; wlan interface name set this as per the output of an iwconfig command (usually wlan0) wlan_if: wlan0

; interface name over which mgt traffic is sent (i.e. how we get to Splunk) - options: wlan0, eth0, zt mgt_if: zt

; Platform architecture - choices: 'wlanpi' (WLPC WLAN-Pi),'rpi' (Raspberry Pi) platform: wlanpi

; Splunk host IP/name data_host: 10.147.xx.xx

; Splunk event collector port (8088 by default) data_port: 8088

; Splunk token to access Splunk server created by Splunk (example token: 84adb9ca-071c-48ad-8aa1-b1903c60310d) splunk_token: f9dd1431-d1fd-4819-a4b4-xxxxxxxxxxxx

; test interval (mins) - how often we want to run the tests (5 is the recommended minimum) test_interval: 5

; test offset from top of hour (must be less than test interval) - 0 = top of hour, 1 = 1 min after top of hour etc. test_offset: 0

; connectivity DNS lookup - site used for initial DNS lookup when assessing if DNS working OK connectivity_lookup: google.com

; location label for report filtering (if required) location:

wpa_supplicant: ap_scan=1

WPA2 PSK Network sample (highest priority - joined first)

network={ ssid="test_network" psk="password123" priority=10 }

2020-06-14 19:50:05,150 - Probe_Log - ERROR - Returning error... 2020-06-14 19:50:05,150 - Probe_Log - ERROR - Unable to get wireless info due to failure with ifconfig command 2020-06-14 19:50:05,152 - Probe_Log - ERROR - Attempting to recover by bouncing wireless interface... 2020-06-14 19:50:05,153 - Probe_Log - ERROR - Bouncing WLAN interface 2020-06-14 19:50:05,153 - Probe_Log - INFO - Bouncing interface wlan0 (platform type = wlanpi) 2020-06-14 19:50:05,527 - Probe_Log - ERROR - if bounce command appears to have failed. Error: ifdown: interface wlan0 not configured wpa_supplicant: /sbin/wpa_supplicant daemon failed to start run-parts: /etc/network/if-pre-up.d/wpasupplicant exited with return code 1 ifup: failed to bring up wlan0

2020-06-14 19:50:05,528 - Probe_Log - ERROR - Returning error... 2020-06-14 19:50:05,529 - Probe_Log - ERROR - Bounce completed. Exiting script. 2020-06-14 19:50:05,530 - Probe_Log - INFO - removing lock file 2020-06-14 19:55:05,291 - Probe_Log - INFO -

2020-06-14 19:55:05,292 - Probe_Log - INFO - Starting logging... 2020-06-14 19:55:05,292 - Probe_Log - INFO -

2020-06-14 19:55:05,315 - Probe_Log - INFO - No lock file found. Creating lock file. 2020-06-14 19:55:05,316 - Probe_Log - INFO - ########## wireless connection checks ########## 2020-06-14 19:55:05,317 - Probe_Log - INFO - Checking wireless connection available. 2020-06-14 19:55:05,329 - Probe_Log - ERROR - Issue getting interface info using iwconfig command: wlan0 No such device

2020-06-14 19:55:05,330 - Probe_Log - ERROR - Returning error... 2020-06-14 19:55:05,331 - Probe_Log - ERROR - Unable to get wireless info due to failure with ifconfig command 2020-06-14 19:55:05,333 - Probe_Log - ERROR - Attempting to recover by bouncing wireless interface... 2020-06-14 19:55:05,334 - Probe_Log - ERROR - Bouncing WLAN interface 2020-06-14 19:55:05,334 - Probe_Log - INFO - Bouncing interface wlan0 (platform type = wlanpi) 2020-06-14 19:55:05,525 - Probe_Log - ERROR - if bounce command appears to have failed. Error: ifdown: interface wlan0 not configured wpa_supplicant: /sbin/wpa_supplicant daemon failed to start run-parts: /etc/network/if-pre-up.d/wpasupplicant exited with return code 1 ifup: failed to bring up wlan0

2020-06-14 19:55:05,526 - Probe_Log - ERROR - Returning error... 2020-06-14 19:55:05,527 - Probe_Log - ERROR - Bounce completed. Exiting script. 2020-06-14 19:55:05,527 - Probe_Log - INFO - removing lock file 2020-06-14 20:15:05,814 - Probe_Log - INFO -

2020-06-14 20:15:05,815 - Probe_Log - INFO - Starting logging... 2020-06-14 20:15:05,816 - Probe_Log - INFO -

2020-06-14 20:15:05,841 - Probe_Log - INFO - No lock file found. Creating lock file. 2020-06-14 20:15:05,842 - Probe_Log - INFO - ########## wireless connection checks ########## 2020-06-14 20:15:05,843 - Probe_Log - INFO - Checking wireless connection available. 2020-06-14 20:15:05,923 - Probe_Log - INFO - Checking we're connected to the network 2020-06-14 20:15:05,924 - Probe_Log - INFO - Checking we have an IP address. 2020-06-14 20:15:05,942 - Probe_Log - ERROR - Problem with wireless connection: no valid IP address 2020-06-14 20:15:05,944 - Probe_Log - ERROR - Attempting to recover by bouncing wireless interface... 2020-06-14 20:15:05,945 - Probe_Log - ERROR - Bouncing WLAN interface 2020-06-14 20:15:05,946 - Probe_Log - INFO - Bouncing interface wlan0 (platform type = wlanpi) 2020-06-14 20:16:38,827 - Probe_Log - ERROR - Bounce completed. Exiting script. 2020-06-14 20:16:38,828 - Probe_Log - INFO - removing lock file 2020-06-14 20:20:04,602 - Probe_Log - INFO -

2020-06-14 20:20:04,604 - Probe_Log - INFO - Starting logging... 2020-06-14 20:20:04,604 - Probe_Log - INFO -

2020-06-14 20:20:04,625 - Probe_Log - INFO - No lock file found. Creating lock file. 2020-06-14 20:20:04,626 - Probe_Log - INFO - ########## wireless connection checks ########## 2020-06-14 20:20:04,627 - Probe_Log - INFO - Checking wireless connection available. 2020-06-14 20:20:04,709 - Probe_Log - INFO - Checking we're connected to the network 2020-06-14 20:20:04,711 - Probe_Log - INFO - Checking we have an IP address. 2020-06-14 20:20:04,727 - Probe_Log - ERROR - Problem with wireless connection: no valid IP address 2020-06-14 20:20:04,730 - Probe_Log - ERROR - Attempting to recover by bouncing wireless interface... 2020-06-14 20:20:04,730 - Probe_Log - ERROR - Bouncing WLAN interface 2020-06-14 20:20:04,731 - Probe_Log - INFO - Bouncing interface wlan0 (platform type = wlanpi) 2020-06-14 20:21:37,132 - Probe_Log - ERROR - Bounce completed. Exiting script. 2020-06-14 20:21:37,134 - Probe_Log - INFO - removing lock file 2020-06-14 20:25:04,869 - Probe_Log - INFO -

2020-06-14 20:25:04,870 - Probe_Log - INFO - Starting logging... 2020-06-14 20:25:04,870 - Probe_Log - INFO -

2020-06-14 20:25:04,891 - Probe_Log - INFO - No lock file found. Creating lock file. 2020-06-14 20:25:04,893 - Probe_Log - INFO - ########## wireless connection checks ########## 2020-06-14 20:25:04,893 - Probe_Log - INFO - Checking wireless connection available. 2020-06-14 20:25:04,970 - Probe_Log - INFO - Checking we're connected to the network 2020-06-14 20:25:04,971 - Probe_Log - INFO - Checking we have an IP address. 2020-06-14 20:25:04,988 - Probe_Log - ERROR - Problem with wireless connection: no valid IP address 2020-06-14 20:25:04,990 - Probe_Log - ERROR - Attempting to recover by bouncing wireless interface... 2020-06-14 20:25:04,991 - Probe_Log - ERROR - Bouncing WLAN interface 2020-06-14 20:25:04,991 - Probe_Log - INFO - Bouncing interface wlan0 (platform type = wlanpi) 2020-06-14 20:25:16,499 - Probe_Log - ERROR - if bounce command appears to have failed. Error: Killed old client process Internet Systems Consortium DHCP Client 4.3.5 Copyright 2004-2016 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/

/etc/dhcp/dhclient.conf line 21: semicolon expected.

}

^ Listening on LPF/wlan0/20:0d:b0:36:c3:42 Sending on LPF/wlan0/20:0d:b0:36:c3:42 Sending on Socket/fallback DHCPRELEASE on wlan0 to 10.0.1.1 port 67 wpa_supplicant: /sbin/wpa_supplicant daemon failed to start run-parts: /etc/network/if-pre-up.d/wpasupplicant exited with return code 1 ifup: failed to bring up wlan0

2020-06-14 20:25:16,500 - Probe_Log - ERROR - Returning error... 2020-06-14 20:25:16,501 - Probe_Log - ERROR - Bounce completed. Exiting script. 2020-06-14 20:25:16,502 - Probe_Log - INFO - removing lock file 2020-06-14 20:30:05,284 - Probe_Log - INFO -

2020-06-14 20:30:05,285 - Probe_Log - INFO - Starting logging... 2020-06-14 20:30:05,286 - Probe_Log - INFO -

2020-06-14 20:30:05,306 - Probe_Log - INFO - No lock file found. Creating lock file. 2020-06-14 20:30:05,307 - Probe_Log - INFO - ########## wireless connection checks ########## 2020-06-14 20:30:05,308 - Probe_Log - INFO - Checking wireless connection available. 2020-06-14 20:30:05,385 - Probe_Log - INFO - Checking we're connected to the network 2020-06-14 20:30:05,386 - Probe_Log - INFO - Checking we have an IP address. 2020-06-14 20:30:05,403 - Probe_Log - ERROR - Problem with wireless connection: no valid IP address 2020-06-14 20:30:05,405 - Probe_Log - ERROR - Attempting to recover by bouncing wireless interface... 2020-06-14 20:30:05,406 - Probe_Log - ERROR - Bouncing WLAN interface 2020-06-14 20:30:05,406 - Probe_Log - INFO - Bouncing interface wlan0 (platform type = wlanpi) 2020-06-14 20:31:25,740 - Probe_Log - ERROR - Bounce completed. Exiting script. 2020-06-14 20:31:25,742 - Probe_Log - INFO - removing lock file 2020-06-14 20:35:05,740 - Probe_Log - INFO -

2020-06-14 20:35:05,742 - Probe_Log - INFO - Starting logging... 2020-06-14 20:35:05,742 - Probe_Log - INFO -

2020-06-14 20:35:05,763 - Probe_Log - ERROR - Watchdog count exceeded...rebooting 2020-06-14 20:36:37,842 - Probe_Log - ERROR - Reboot output: 2020-06-14 20:36:37,843 - Probe_Log - INFO - No lock file found. Creating lock file. 2020-06-14 20:36:37,844 - Probe_Log - INFO - ########## wireless connection checks ########## 2020-06-14 20:36:37,845 - Probe_Log - INFO - Checking wireless connection available. 2020-06-14 20:36:37,925 - Probe_Log - INFO - Checking we're connected to the network 2020-06-14 20:36:37,926 - Probe_Log - INFO - Checking we have an IP address. 2020-06-14 20:36:37,943 - Probe_Log - ERROR - Problem with wireless connection: no valid IP address 2020-06-14 20:36:37,946 - Probe_Log - ERROR - Attempting to recover by bouncing wireless interface... 2020-06-14 20:36:37,947 - Probe_Log - ERROR - Bouncing WLAN interface 2020-06-14 20:36:37,950 - Probe_Log - INFO - Bouncing interface wlan0 (platform type = wlanpi) 2020-06-14 20:45:04,925 - Probe_Log - INFO -

2020-06-14 20:45:04,926 - Probe_Log - INFO - Starting logging... 2020-06-14 20:45:04,927 - Probe_Log - INFO -

2020-06-14 20:45:04,949 - Probe_Log - INFO - No lock file found. Creating lock file. 2020-06-14 20:45:04,950 - Probe_Log - INFO - ########## wireless connection checks ########## 2020-06-14 20:45:04,951 - Probe_Log - INFO - Checking wireless connection available. 2020-06-14 20:45:04,963 - Probe_Log - ERROR - Issue getting interface info using iwconfig command: wlan0 No such device

2020-06-14 20:45:04,964 - Probe_Log - ERROR - Returning error... 2020-06-14 20:45:04,965 - Probe_Log - ERROR - Unable to get wireless info due to failure with ifconfig command 2020-06-14 20:45:04,966 - Probe_Log - ERROR - Attempting to recover by bouncing wireless interface... 2020-06-14 20:45:04,967 - Probe_Log - ERROR - Bouncing WLAN interface 2020-06-14 20:45:04,968 - Probe_Log - INFO - Bouncing interface wlan0 (platform type = wlanpi) 2020-06-14 20:45:05,336 - Probe_Log - ERROR - if bounce command appears to have failed. Error: ifdown: interface wlan0 not configured wpa_supplicant: /sbin/wpa_supplicant daemon failed to start run-parts: /etc/network/if-pre-up.d/wpasupplicant exited with return code 1 ifup: failed to bring up wlan0

2020-06-14 20:45:05,338 - Probe_Log - ERROR - Returning error... 2020-06-14 20:45:05,339 - Probe_Log - ERROR - Bounce completed. Exiting script. 2020-06-14 20:45:05,340 - Probe_Log - INFO - removing lock file

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub < https://github.com/wifinigel/wiperf/issues/13> , or unsubscribe < https://github.com/notifications/unsubscribe-auth/AEXGPJHXDWJADKAKVZ6J75DRWV7G5ANCNFSM4N5XRBNA> . < https://github.com/notifications/beacon/AEXGPJD6KSK45UAHEQSL5YTRWV7G5A5CNFSM4N5XRBNKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4JQOR53A.gif>

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/wifinigel/wiperf/issues/13#issuecomment-644099617, or unsubscribe https://github.com/notifications/unsubscribe-auth/AOVCZ4BJUSQBWECXUBEIDKTRWYHENANCNFSM4N5XRBNA .

wifinigel commented 4 years ago

Chris, sorry for the delay in responding. Can you try it on another (non-Meraki) network?

credmond06 commented 4 years ago

No Problem Nigel. I know we are all busy with many projects. I will try to set up a different network. I will also try to move the DHCP server from the Meraki MX.

On Thu, Jun 18, 2020 at 9:47 AM Nigel Bowden notifications@github.com wrote:

Chris, sorry for the delay in responding. Can you try it on another (non-Meraki) network?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/wifinigel/wiperf/issues/13#issuecomment-646027598, or unsubscribe https://github.com/notifications/unsubscribe-auth/AOVCZ4AZ5GQNHWC5ZIZCOXLRXILGJANCNFSM4N5XRBNA .

credmond06 commented 4 years ago

Nigel,

I was able to get it to connect to a non-Meraki network and switched back to the Meraki network. Both networks pulled an IP address. I had a little issue with it connecting to the Splunk server running on my windows machine on port 8088. But, once I added the port to my inbound rules of the windows machine, it began working and testing and sending data to the Splunk Server. However, the Splunk Server is not showing any received data. Both the WLAN Pi and Splunk are in the same time zone, and port 8088 has been added to the Meraki Firewall. I've noticed that the Splunk server URL is localhost:8000. Would this make a difference?

On Fri, Jun 19, 2020 at 6:27 PM Chris Redmond credmond06@gmail.com wrote:

No Problem Nigel. I know we are all busy with many projects. I will try to set up a different network. I will also try to move the DHCP server from the Meraki MX.

On Thu, Jun 18, 2020 at 9:47 AM Nigel Bowden notifications@github.com wrote:

Chris, sorry for the delay in responding. Can you try it on another (non-Meraki) network?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/wifinigel/wiperf/issues/13#issuecomment-646027598, or unsubscribe https://github.com/notifications/unsubscribe-auth/AOVCZ4AZ5GQNHWC5ZIZCOXLRXILGJANCNFSM4N5XRBNA .

wifinigel commented 4 years ago

Chris,

No, as long as the WLAN Pi can hit port 8088 on the Splunk server you should be good to go.

If you take a look in /home/wlanpi/logs/agent.log, see if there are any messages about comms issues to the Splunk server.

credmond06 commented 4 years ago

Nigel,

There is nothing I can tell from the agent.log. I even changed the splunk token just to be sure.

2020-06-20 08:46:57,063 - Probe_Log - INFO - ########## end ########## 2020-06-20 08:50:05,015 - Probe_Log - INFO -

2020-06-20 08:50:05,016 - Probe_Log - INFO - Starting logging... 2020-06-20 08:50:05,017 - Probe_Log - INFO -

2020-06-20 08:50:05,039 - Probe_Log - INFO - No lock file found. Creating lock file. 2020-06-20 08:50:05,041 - Probe_Log - INFO - ########## wireless connection checks ########## 2020-06-20 08:50:05,042 - Probe_Log - INFO - Checking wireless connection available. 2020-06-20 08:50:05,117 - Probe_Log - INFO - Checking we're connected to the network 2020-06-20 08:50:05,118 - Probe_Log - INFO - Checking we have an IP address. 2020-06-20 08:50:05,135 - Probe_Log - INFO - Checking we can do a DNS lookup to google.com 2020-06-20 08:50:05,171 - Probe_Log - INFO - Checking port connection to server 10.147.17.100, port: 8088 2020-06-20 08:50:05,192 - Probe_Log - INFO - Port connection to server 10.147.17.100, port: 8088 checked OK. 2020-06-20 08:50:05,194 - Probe_Log - INFO - Wireless connection: SSID:DINC, BSSID:C8:67:5E:3B:DE:65, Freq:5.2, Center Freq:5.2, Channel: 40, Channel Width: 20, Tx Phy rate:174.0, Rx Phy rate:False, Tx MCS: False, Rx MCS: False, RSSI:-66.0, Tx retries:0, IP address:10.10.10.76 2020-06-20 08:50:05,195 - Probe_Log - INFO - ########## speedtest ########## 2020-06-20 08:50:05,196 - Probe_Log - INFO - Starting speedtest... 2020-06-20 08:50:06,218 - Probe_Log - INFO - Checked interface route to : 8.8.8.8. Result: wlan0 2020-06-20 08:50:06,220 - Probe_Log - INFO - Speedtest in progress....please wait. 2020-06-20 08:50:28,858 - Probe_Log - INFO - ping_time: 39, download_rate: 28.54, upload_rate: 6.89, server_name: tampp-speedtest-01.noc.bhn.net:8080 2020-06-20 08:50:28,870 - Probe_Log - INFO - Speedtest ended. 2020-06-20 08:50:28,872 - Probe_Log - INFO - HEC update: wiperf-speedtest-splunk, source=Speedtest 2020-06-20 08:50:28,873 - Probe_Log - INFO - Sending event to HEC: wiperf-speedtest-splunk (dest host: 10.147.17.100, dest port: 8088) 2020-06-20 08:50:32,682 - Probe_Log - INFO - ########## ping tests ########## 2020-06-20 08:50:32,685 - Probe_Log - INFO - Starting ping test... 2020-06-20 08:50:33,745 - Probe_Log - INFO - DNS hostname lookup : bbc.co.uk. Result: 151.101.0.81 2020-06-20 08:50:33,777 - Probe_Log - INFO - Checked interface route to : 151.101.0.81. Result: wlan0 2020-06-20 08:50:33,926 - Probe_Log - INFO - ping_host: bbc.co.uk, pkts_tx: 1, pkts_rx: 1, pkt_loss: 0, rtt_avg: 29.012 2020-06-20 08:50:33,958 - Probe_Log - INFO - DNS hostname lookup : cisco.com. Result: 72.163.4.185 2020-06-20 08:50:33,989 - Probe_Log - INFO - Checked interface route to : 72.163.4.185. Result: wlan0 2020-06-20 08:50:34,212 - Probe_Log - INFO - ping_host: cisco.com, pkts_tx: 1, pkts_rx: 1, pkt_loss: 0, rtt_avg: 94.888 2020-06-20 08:50:34,252 - Probe_Log - INFO - DNS hostname lookup : google.com. Result: 64.233.185.100 2020-06-20 08:50:34,282 - Probe_Log - INFO - Checked interface route to : 64.233.185.100. Result: wlan0 2020-06-20 08:50:34,401 - Probe_Log - INFO - ping_host: google.com, pkts_tx: 1, pkts_rx: 1, pkt_loss: 0, rtt_avg: 30.216 2020-06-20 08:50:43,508 - Probe_Log - INFO - ping_host: bbc.co.uk, pkts_tx: 10, pkts_rx: 10, pkt_loss: 0, rtt_avg: 25.665 2020-06-20 08:50:43,510 - Probe_Log - INFO - HEC update: wiperf-ping-splunk, source=Ping 2020-06-20 08:50:43,512 - Probe_Log - INFO - Sending event to HEC: wiperf-ping-splunk (dest host: 10.147.17.100, dest port: 8088) 2020-06-20 08:50:47,504 - Probe_Log - INFO - Ping test ended. 2020-06-20 08:50:56,722 - Probe_Log - INFO - ping_host: cisco.com, pkts_tx: 10, pkts_rx: 10, pkt_loss: 0, rtt_avg: 69.070 2020-06-20 08:50:56,725 - Probe_Log - INFO - HEC update: wiperf-ping-splunk, source=Ping 2020-06-20 08:50:56,726 - Probe_Log - INFO - Sending event to HEC: wiperf-ping-splunk (dest host: 10.147.17.100, dest port: 8088) 2020-06-20 08:51:00,523 - Probe_Log - INFO - Ping test ended. 2020-06-20 08:51:09,639 - Probe_Log - INFO - ping_host: google.com, pkts_tx: 10, pkts_rx: 10, pkt_loss: 0, rtt_avg: 31.369 2020-06-20 08:51:09,641 - Probe_Log - INFO - HEC update: wiperf-ping-splunk, source=Ping 2020-06-20 08:51:09,643 - Probe_Log - INFO - Sending event to HEC: wiperf-ping-splunk (dest host: 10.147.17.100, dest port: 8088) 2020-06-20 08:51:13,436 - Probe_Log - INFO - Ping test ended. 2020-06-20 08:51:13,438 - Probe_Log - INFO - ########## dns tests ########## 2020-06-20 08:51:13,439 - Probe_Log - INFO - Starting DNS tests... 2020-06-20 08:51:14,483 - Probe_Log - INFO - DNS results: bbc.co.uk: 40ms 2020-06-20 08:51:14,485 - Probe_Log - INFO - HEC update: wiperf-dns-splunk, source=DNS 2020-06-20 08:51:14,486 - Probe_Log - INFO - Sending event to HEC: wiperf-dns-splunk (dest host: 10.147.17.100, dest port: 8088) 2020-06-20 08:51:18,272 - Probe_Log - INFO - DNS test ended. 2020-06-20 08:51:18,307 - Probe_Log - INFO - DNS results: cisco.com: 33ms 2020-06-20 08:51:18,309 - Probe_Log - INFO - HEC update: wiperf-dns-splunk, source=DNS 2020-06-20 08:51:18,310 - Probe_Log - INFO - Sending event to HEC: wiperf-dns-splunk (dest host: 10.147.17.100, dest port: 8088) 2020-06-20 08:51:22,117 - Probe_Log - INFO - DNS test ended. 2020-06-20 08:51:22,149 - Probe_Log - INFO - DNS results: google.com: 30ms 2020-06-20 08:51:22,150 - Probe_Log - INFO - HEC update: wiperf-dns-splunk, source=DNS 2020-06-20 08:51:22,152 - Probe_Log - INFO - Sending event to HEC: wiperf-dns-splunk (dest host: 10.147.17.100, dest port: 8088) 2020-06-20 08:51:25,952 - Probe_Log - INFO - DNS test ended. 2020-06-20 08:51:25,954 - Probe_Log - INFO - ########## http tests ########## 2020-06-20 08:51:25,955 - Probe_Log - INFO - Starting HTTP tests... 2020-06-20 08:51:26,959 - Probe_Log - INFO - Starting http test to : https://ebay.co.uk 2020-06-20 08:51:28,146 - Probe_Log - INFO - HTTP results: https://ebay.co.uk: 1184ms (status code: 200) 2020-06-20 08:51:28,148 - Probe_Log - INFO - HEC update: wiperf-http-splunk, source=HTTP 2020-06-20 08:51:28,149 - Probe_Log - INFO - Sending event to HEC: wiperf-http-splunk (dest host: 10.147.17.100, dest port: 8088) 2020-06-20 08:51:31,936 - Probe_Log - INFO - HTTP test ended. 2020-06-20 08:51:31,938 - Probe_Log - INFO - Starting http test to : http://twitter.com 2020-06-20 08:51:32,366 - Probe_Log - INFO - HTTP results: http://twitter.com: 426ms (status code: 200) 2020-06-20 08:51:32,367 - Probe_Log - INFO - HEC update: wiperf-http-splunk, source=HTTP 2020-06-20 08:51:32,368 - Probe_Log - INFO - Sending event to HEC: wiperf-http-splunk (dest host: 10.147.17.100, dest port: 8088) 2020-06-20 08:51:36,129 - Probe_Log - INFO - HTTP test ended. 2020-06-20 08:51:36,131 - Probe_Log - INFO - Starting http test to : https://facebook.com 2020-06-20 08:51:36,763 - Probe_Log - INFO - HTTP results: https://facebook.com: 629ms (status code: 200) 2020-06-20 08:51:36,764 - Probe_Log - INFO - HEC update: wiperf-http-splunk, source=HTTP 2020-06-20 08:51:36,766 - Probe_Log - INFO - Sending event to HEC: wiperf-http-splunk (dest host: 10.147.17.100, dest port: 8088) 2020-06-20 08:51:40,559 - Probe_Log - INFO - HTTP test ended. 2020-06-20 08:51:40,561 - Probe_Log - INFO - Starting http test to : https://instagram.com 2020-06-20 08:51:41,302 - Probe_Log - INFO - HTTP results: https://instagram.com: 740ms (status code: 200) 2020-06-20 08:51:41,303 - Probe_Log - INFO - HEC update: wiperf-http-splunk, source=HTTP 2020-06-20 08:51:41,304 - Probe_Log - INFO - Sending event to HEC: wiperf-http-splunk (dest host: 10.147.17.100, dest port: 8088) 2020-06-20 08:51:45,070 - Probe_Log - INFO - HTTP test ended. 2020-06-20 08:51:45,072 - Probe_Log - INFO - Starting http test to : https://amazon.com 2020-06-20 08:51:45,563 - Probe_Log - ERROR - HTTP error occurred: 503 Server Error: Service Unavailable for url: https://www.amazon.com/ 2020-06-20 08:51:45,566 - Probe_Log - INFO - HTTP results: https://amazon.com: 491ms (status code: 503) 2020-06-20 08:51:45,567 - Probe_Log - INFO - HEC update: wiperf-http-splunk, source=HTTP 2020-06-20 08:51:45,569 - Probe_Log - INFO - Sending event to HEC: wiperf-http-splunk (dest host: 10.147.17.100, dest port: 8088) 2020-06-20 08:51:49,338 - Probe_Log - INFO - HTTP test ended. 2020-06-20 08:51:49,339 - Probe_Log - INFO - ########## iperf3 tcp test ########## 2020-06-20 08:51:49,341 - Probe_Log - INFO - Iperf3 tcp test not enabled in config file (or previous tests failed), bypassing this test... 2020-06-20 08:51:49,342 - Probe_Log - INFO - ########## iperf3 udp test ########## 2020-06-20 08:51:49,344 - Probe_Log - INFO - Iperf3 udp test not enabled in config file (or previous tests failed), bypassing this test... 2020-06-20 08:51:49,345 - Probe_Log - INFO - ########## dhcp test ########## 2020-06-20 08:51:49,346 - Probe_Log - INFO - Starting DHCP renewal test... 2020-06-20 08:51:50,350 - Probe_Log - INFO - Renewing dhcp address...(mode = passive, interface= wlan0) 2020-06-20 08:51:50,916 - Probe_Log - INFO - Address renewed. 2020-06-20 08:51:50,918 - Probe_Log - INFO - Renewal time: 565mS 2020-06-20 08:51:50,919 - Probe_Log - INFO - HEC update: wiperf-dhcp-splunk, source=DHCP 2020-06-20 08:51:50,920 - Probe_Log - INFO - Sending event to HEC: wiperf-dhcp-splunk (dest host: 10.147.17.100, dest port: 8088) 2020-06-20 08:51:54,704 - Probe_Log - INFO - DHCP test ended. 2020-06-20 08:51:55,708 - Probe_Log - INFO - removing lock file 2020-06-20 08:51:55,709 - Probe_Log - INFO - ########## end ##########

On Sat, Jun 20, 2020 at 2:44 AM Nigel Bowden notifications@github.com wrote:

Chris,

No, as long as the WLAN Pi can hit port 8088 on the Splunk server you should be good to go.

If you take a look in /home/wlanpi/logs/agent.log, see if there are any messages about comms issues to the Splunk server.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/wifinigel/wiperf/issues/13#issuecomment-646952650, or unsubscribe https://github.com/notifications/unsubscribe-auth/AOVCZ4F6VES54FQ3ZYB4GUTRXRLEBANCNFSM4N5XRBNA .

wifinigel commented 4 years ago

Chris:

Looks like everything is OK. Can you go to the search page and enter a wildcard search to see if the data is getting in to the DB. Here is a screenshot: image

credmond06 commented 4 years ago

Nigel,

Apologies for not responding. I'm not showing anything on the Splunk server under the search section.

On Sun, Jun 21, 2020 at 2:48 AM Nigel Bowden notifications@github.com wrote:

Looks like everything is OK. Can you go to the search page and enter a wildcard search to see if the data is getting in to the DB. Here is a screenshot: [image: image] https://user-images.githubusercontent.com/19818404/85218583-8455c780-b393-11ea-9209-801f42611984.png

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/wifinigel/wiperf/issues/13#issuecomment-647086739, or unsubscribe https://github.com/notifications/unsubscribe-auth/AOVCZ4GOJKRKLDTCLL56FZTRXWUK7ANCNFSM4N5XRBNA .

credmond06 commented 4 years ago

Nigel,

I was able to achieve data collection and display on the Splunk Server. I eliminated the Zerotier One connection and went directly to my local splunk server using the LAN IP vs the Zerotier One IP.

Now I know it works, and I can begin working to get it to use Zerotier One for remote logging.

v/r Chris

On Sat, Jun 27, 2020 at 10:02 AM Chris Redmond credmond06@gmail.com wrote:

Nigel,

Apologies for not responding. I'm not showing anything on the Splunk server under the search section.

On Sun, Jun 21, 2020 at 2:48 AM Nigel Bowden notifications@github.com wrote:

Looks like everything is OK. Can you go to the search page and enter a wildcard search to see if the data is getting in to the DB. Here is a screenshot: [image: image] https://user-images.githubusercontent.com/19818404/85218583-8455c780-b393-11ea-9209-801f42611984.png

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/wifinigel/wiperf/issues/13#issuecomment-647086739, or unsubscribe https://github.com/notifications/unsubscribe-auth/AOVCZ4GOJKRKLDTCLL56FZTRXWUK7ANCNFSM4N5XRBNA .