-
-
Notifications
You must be signed in to change notification settings - Fork 0
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
Extend configure_isolated_interface to support more network stacks #8
Comments
The current plan is to wait for the upcoming point release (12.7, planned tomorrow) to get fresh images, and use “debian-installer test laptops” as generic machines. |
First things first: netinst, no desktop, therefore In this scenario, we have everything configured via In passing, if we end up making it possible to toggle between interfaces, we might have some interfaces configured via snippets, some others via Edit: In any case, the code isn't/wasn't crazy: it relies on the output of Proposed change: Run |
Call `ifquery --list` twice, once with `--all` and once with `--allow hotplug`. The former works for /e/n/i as set up in Debian/PTS Raspberry Pi images, the latter is required to spot allow-hotplug interfaces set up by debian-installer. [ Best viewed with -b due to indentation changes. ] Link: #8
This seems unlikely but ifquery /could/ change behaviour over time. Plus we'll probably want to make it possible to update the config, e.g. for interfaces that are coming and going (e.g. a USB/Ethernet or USB/Wi-Fi dongle, or tethering, etc.), so we might end up with several interfaces being configured via /e/n/i at a given time. Link: #7 Link: #8
It seems NetworkManager doesn't want to let us set up just an IP address as we would do in the ifupdown case, if the interface is configured with mode=ap. Go with the flow, and include as many settings as needed to make the connection usable from a test phone. Link: #8
If NM manages our network, we have to fully configure the Wi-Fi interface when it comes to the isolated network. That means hostapd isn't required, and it couldn't deal with the interface anyway, as it's already configured by NM. Link: #8
This adds support for APPLIANCE mode, when the isolated interface is an Ethernet one (APPLIANCE mode): - Create/update pirogue-isolated-network.nmconnection via nmcli, with fewer parameters than in the Wi-Fi case (AP mode). Link: #8
Let's make extra sure it cannot be enabled/started accidentally. Link: PiRogueToolSuite/pirogue-admin#8
Marking with
Most desktop environments use This can be closed once tests have been documented in a dedicated page. |
At the moment, we only support
IFUPDOWN
andNETWORKD_RESOLVED
, we'll want to support more use cases so that the APPLIANCE mode can be used with a Debian system set up with other network stacks (e.g. NetworkManager).See also #7 regarding reverting such modifications.
The text was updated successfully, but these errors were encountered: