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
At the moment, the focus is implementing autodetection, using it to apply an initial configuration that works for the various use cases.
But we already know that switching between modes is going to be problematic: at least on the system configuration side, we will need to clean up static configuration set up for the isolated interface in the APPLIANCE mode to avoid IP-related conflicts when setting up the wg0 interface in the VPN mode.
One way to address that might be to leave breadcrumbs when setting things up, so that it can be reverted/cancelled when switching to another mode.
The text was updated successfully, but these errors were encountered:
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
At the moment, the focus is implementing autodetection, using it to apply an initial configuration that works for the various use cases.
But we already know that switching between modes is going to be problematic: at least on the system configuration side, we will need to clean up static configuration set up for the isolated interface in the APPLIANCE mode to avoid IP-related conflicts when setting up the
wg0
interface in the VPN mode.One way to address that might be to leave breadcrumbs when setting things up, so that it can be reverted/cancelled when switching to another mode.
The text was updated successfully, but these errors were encountered: