We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I've observed on my desk at LBL that occasionally the pi will lose the wifi connection, even though lbnl-visitor is still good.
lbnl-visitor
A simple solution is to restart the network connection using:
sudo ifdown wlan1 sudo ifup wlan1
These can be run from NetworkStatus with a subprocess.call or .check_output (link).
NetworkStatus
subprocess.call
.check_output
But there should also be some checking on whether the pi is actually using wifi, e.g. do a quick check on /etc/network/interfaces.
/etc/network/interfaces
The text was updated successfully, but these errors were encountered:
Merge pull request #47 from tybtab/memory-#13
db9d357
Closes #13, #42, #43
See issue #52. This may recover the network but it might also crash the subprocesses.
Sorry, something went wrong.
alihanks
No branches or pull requests
I've observed on my desk at LBL that occasionally the pi will lose the wifi connection, even though
lbnl-visitor
is still good.A simple solution is to restart the network connection using:
These can be run from
NetworkStatus
with asubprocess.call
or.check_output
(link).But there should also be some checking on whether the pi is actually using wifi, e.g. do a quick check on
/etc/network/interfaces
.The text was updated successfully, but these errors were encountered: