-
Notifications
You must be signed in to change notification settings - Fork 12
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
Make maia startup optional #23
Comments
Maia is working in parallel and thus does not disturb iio. So accessing it is not an issue, isnt it ? |
well, not exactly. Several time I had an issue that I'm receiving just noise on a pc, with no signal at all. Probably maia shifting frequency or uploads something to fpga that conflicts with whatever pc is requesting via iio. |
Maia could change eventually frequency if it is the first time your browser is connected to ip of your sdr. After that a cookie is set not to disturb and set any variable. Need to double check this. |
I am also not sure about root cause, but even in home/local network virtually anything can make a request via HTTP to port 8000, just as a part of auto-discovery. Prevent maia from firing up on first request to front page is a minimum precaution for predictable behavior. Something like "start radio" button. More advanced mechanism would be login page or optional service startup. |
If maiasdr is exposed to any local network, things like homeassistant can open port 8000 to scan network device and, a result, get maiasdr running radio, which results in iio interface behaving in a strange way.
One of the options is to make maiasdr startup an option, another is to make maia interface protected by password, or at least require a button press to start signal acquisition.
The text was updated successfully, but these errors were encountered: