-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
check whether network/password authenticate and whether the Tessel connects #395
Comments
I'll take a stab at this |
Relevant docs: |
dterm'd into T2, in a giving it the creds for a network that doesn't exist (after it was on a network):
giving it the right creds:
(it's not always this clean, sometimes you get deauthentication events and reauthentications mixed in) giving it a real network but the wrong password:
|
no such network & real network but wrong password have the same output, so this does not produce a complete solution. However, we could do a quick & dirty listen for "ifup" within a certain timeframe after setting credentials to determine if the network is providing a connection. |
Instead of listening for "ifup", wouldn't it be better to just run/output |
@Frijol I think the question is how long to wait after setting credentials. For example, if a wifi signal is relatively weak, the connection may not happen on the first or second attempt but maybe the third. |
Currently
t2 wifi
sets credentials in a file, but it doesn't do anything to check whether the network/password authenticate or connection is successful.moved from #82
The text was updated successfully, but these errors were encountered: