You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Today I test the Access Point feature and feel that it is weird:
Have to manually type 10.0.0.1:5000 in browser. I think it should provide a Captive Portal, so that Android will automatically show a login page upon connecting to the SUSI.AI wifi.
After visiting 10.0.0.1:5000, I only get a blank page (with 1 line of title). No link, no form. I expect that there are some links or a form to guide me what to do.
All the suppages (/wifi_credentials, /config) contain no form. It instead requires user to manually add data to the URL.
I found that, to activate the Access Point, our script wap.sh directly edit /etc/network/interfaces files. I think that this approach is dangerous and error-prone. If a mistake is made, our RPI can be bricked. We should call some network management tool and let that tool handle all the network config files.
Describe the solution you'd like
I found a software, https://github.com/resin-io/resin-wifi-connect, which serves the same purpose (configure Wifi for RPi, by creating an Access Point from RPi), which is more complete than ours. I think we can reuse it in our project.
What I concern is that, it seems to require NetworkManager installed on RPi. But NetworkManager (in full form) is a desktop app and will pull a lot of GUI dependencies.
But maybe it only requires a minimal form of NetworkManager (no GUI). Need to check if Debian allows to install that form.
Btw, I propose to name this feature (create AP to configure wifi for RPi) as Wifi WebConfig, because the access point created here is not to share internet to other machines like a typical access point does.
The text was updated successfully, but these errors were encountered:
@mariobehling Yes. And it is possible that our access point server is designed to work with an Android app, not for direct use in browser. I'm not sure because I haven't tested enough.
Is your feature request related to a problem? Please describe.
Today I test the Access Point feature and feel that it is weird:
Describe the solution you'd like
I found a software, https://github.com/resin-io/resin-wifi-connect, which serves the same purpose (configure Wifi for RPi, by creating an Access Point from RPi), which is more complete than ours. I think we can reuse it in our project.
What I concern is that, it seems to require NetworkManager installed on RPi. But NetworkManager (in full form) is a desktop app and will pull a lot of GUI dependencies.
But maybe it only requires a minimal form of NetworkManager (no GUI). Need to check if Debian allows to install that form.
Btw, I propose to name this feature (create AP to configure wifi for RPi) as Wifi WebConfig, because the access point created here is not to share internet to other machines like a typical access point does.
The text was updated successfully, but these errors were encountered: