mirror of
https://github.com/QubesOS/qubes-doc.git
synced 2024-12-28 16:59:40 -05:00
All Qubes OS Project documentation pages are stored as plain text files in this dedicated repository. By cloning and regularly pulling from this repo, users can maintain their own up-to-date offline copy of all Qubes documentation rather than relying solely on the Web.
2d84312ac5
NetworkManager, by default, uses a connection ID and a per-host random and secret key to generate `stable` MAC addresses. The intention is to keep a connection's MAC address stable indefinitely but for it to be different on every host. The current instruction mention that "`stable` generates a random address that persists for each boot session". This is indeed true for AppVMs using stock TemplateVMs. The reason is that the secret key doesn't exist in the template and thus is only created when the AppVM starts. This, however, may not be true for other VMs. In order to ensure that MACs are always only `stable` during one boot session, `stable-id`, which is used to generate MACs, can be adjusted. NetworkManager's documentation suggests to use `${CONNECTION}/${BOOT}` to ensure generated MACs are unique to a boot session and connection [1]. [1]: https://developer.gnome.org/NetworkManager/stable/nm-settings.html |
||
---|---|---|
_dev | ||
about | ||
basics_dev | ||
basics_user | ||
building | ||
common-tasks | ||
configuration | ||
customization | ||
debugging | ||
hardware | ||
installing | ||
managing-os | ||
privacy | ||
reference | ||
releases | ||
security | ||
security-info | ||
services | ||
system | ||
troubleshooting | ||
.travis.yml | ||
CONTRIBUTING.md | ||
doc.md | ||
README.md |
Qubes OS Documentation
Canonical URL: https://www.qubes-os.org/doc/
All Qubes OS Project documentation pages are stored as plain text files in this dedicated repository. By cloning and regularly pulling from this repo, users can maintain their own up-to-date offline copy of all Qubes documentation rather than relying solely on the Web.
For more information about the documentation, including how to contribute, please see the Documentation Guidelines.