Good Morning, My application listens on port 80, for the usual local services. I also want to use WiFi Connect. When the network is unavailable, port 80 needs to go to the WiFi Connect captive authentication portal. Any suggestions on how to handle these situations? I am also wondering if access …

Hi there, the change to PORTAL_LISTENING_PORT would need to be coupled with an iptables rule to forward packets from port 80 (default) to appropriate non-default port where the portal is listening. This can be done in a privileged container with host networking.

[image] jtonello: One of my colleagues did a couple tests running a container on a balenaOS device (his was a NUC, but this procedure should work regardless of hardware): balena-engine run -it --privileged ubuntu /bin/bash balena-engine run -it --privileged --network host ubuntu /bin/bash W…

Hi, The commands launch a simple Ubuntu container in privileged mode, which means they have access to hostOS stuff. The first example uses the “Docker” network addressing (usually 172.x.x.x.). The second uses your device’s host networking (something like 192.x.x.x). One thing you might try is addin…

But I can’t/shouldn’t be using those commands myself, on my macOS workstation. [image] jtonello: One thing you might try is adding network_mode: host to your frontend: stanza. The frontend has nothing to do with the wifi-connect container, it’s a placeholder for the UI that needs to run on p…

Right, those commands are run on balenaOS. They’re very much like “docker exec -it…” Re: frontend: I understand. John

I’m running my commands ssh’d into the host OS and the container.

Just found this while searching for something else: [image] Balena application iptables no longer propagating to host BalenaOS balenaOS Hi all, Hoping I can get both some suggestion and insight into a mechanism that was previously working (and has been suggested elsewher…

Ah, this seems to be the critical bit: iptables /usr/sbin/iptables-legacy

So I tried adding: RUN update-alternatives --set iptables /usr/sbin/iptables-legacy At the top of the docker-compose.yml, but I don’ t fully know how this interacts with dockerize: Any advice? FROM balenalib/%%BALENA_ARCH%%-python as builder RUN install_packages dnsmasq wireless-tools git rsync…

Oops, forgot to say what the current stumbling block was! In the WiFi Connect container, this is what I get: # iptables -nL Fatal: can't open lock file /run/xtables.lock: No such file or directory Thoughts?

What container does your frontend: app run in? If it’s a Debian balena image there isn’t much value in using the balenablocks version and you could get much greater control and tools for port forwarding by using the original. Including a working iptables.

WiFi Connect and Port 80

Product support

crbn60 December 16, 2020, 12:06am 27

Just found this while searching for something else:

Topic		Replies	Views
WiFi-connect installation in Raspberry Pi Docker container Project help	62	6392	January 21, 2021
What labels are needed for Balena Wifi-Connect? balenaOS	9	865	November 13, 2019
Wifi-Connect sends out wifi but the webpage doesn't show up Product support	20	2022	October 31, 2019
How would one customize wifi-connect UI? balenaOS raspberrypi3	22	2933	January 29, 2020
[WiFiConnect] Extend captive portal with a URL callback / redirect after successfully connected to the internet Project help wifi	6	1074	March 15, 2022

WiFi Connect and Port 80

Related topics