Description
@rickgurmet reports that he's tried running sudo iiab-network in many different ways. It is not working as expected. I don't know if this is a bug or a question so for now this ticket is tagged as both, until we figure it out.
He wants the WiFi AP (Access Point) to handle more WiFi client devices than just the very meager (maximum of 12?) offered by the NUC's internal WiFi AP.
The WiFi AP device (not much of a router) has only 1 Ethernet port, as does the IIAB/NUC — so there's only 1 way to connect the Ethernet cable between the 2 devices — which greatly simplifies things thankfully.
He's tried running sudo iiab-network both with the Ethernet cable plugged into the NUC and also with the NUC's Ethernet port completely empty.
Then he runs brctl show and the Ethernet interface (eno1) is unfortunately not added to the "bridge" (for LAN-side WiFi AP hotspots).
On the side he discovered that he can temporarily add eno1 under the bridge by running brctl addif br0 eno1 — but unfortunately this setting does not survive reboots:
/opt/iiab/iiab/iiab-network.log (3.2 MB, 53018 lines) is attached here, hoping this might help us all understand better:
iiab-network.log
BACKGROUND: He installed the latest IIAB onto this NUC on Sept ~16, and more recently git pull was run to update /opt/iiab/iiab to the latest code there just in case.
iiab-diagnostics: http://sprunge.us/3fyNhH?bash
Quick Questions for @rickgurmet ...that might possibly shed more light:
- Is the WiFi AP device running DHCP yes or no?
- What's the make and model of this WiFi AP device?
Thanks @rickgurmet if you can explain more detail (and other things you've tried) to help everyone try to resolve this efficiently in coming days. 👍
Umbrella ticket, covering networking issues: