-
Notifications
You must be signed in to change notification settings - Fork 24
Description
mod-ui works well enough with the pistomp as wifi (or ethernet) client. However, after enabling hotspot mode, I noticed that - though the UI rendered well and appeared to be functioning - button presses on the hardware were not reflected in the UI, and changes to the signal chain generated an error in the web browser UI. There were no new errors in the web browser console or pistomp journal.
As a workaround, I added this to the end of both /usr/lib/pistomp-wifi/{enable_wifi_hotspot.sh, disable_wifi_hotspot.sh}:
systemctl restart mod-ui.service 2> /dev/null
and now mod-ui works well in hotspot mode, as well as toggling between hotspot/non-hotspot modes.
Before that, I would have expected errors to be in the pistomp journal, but did not see anything. My default assumption was that some service was bound to a particular interface and needed to bind to a different interface. This was surprising to me because it remains wlan0/eth0, though the IP did change, and ss shows that the binds are to 0:0:0:0.
LISTEN 0 4096 0.0.0.0:5555 0.0.0.0:* users:(("mod-host",pid=2580,fd=18))
LISTEN 0 4096 0.0.0.0:5556 0.0.0.0:* users:(("mod-host",pid=2580,fd=19))
LISTEN 0 128 0.0.0.0:22 0.0.0.0:* users:(("sshd",pid=679,fd=3))
LISTEN 0 128 0.0.0.0:80 0.0.0.0:* users:(("mod-ui",pid=3442,fd=9))
LISTEN 0 128 0.0.0.0:8081 0.0.0.0:* users:(("browsepy",pid=552,fd=3))
LISTEN 0 32 127.0.0.1:53 0.0.0.0:* users:(("dnsmasq",pid=1226,fd=5))
LISTEN 0 128 [::]:22 [::]:* users:(("sshd",pid=679,fd=4))```
Thoughts?