Commit Graph

19 Commits

Author SHA1 Message Date
Marek Marczykowski-Górecki
919f2ed17e
Merge branch 'master' into spelling-grammar-fixes
Resolved conflicts in:
      basics_user/doc-guidelines.md
      basics_user/reporting-bugs.md
      common-tasks/backup-restore.md
      common-tasks/software-update-dom0.md
      common-tasks/software-update-vm.md
      common-tasks/usb.md
      configuration/disk-trim.md
      configuration/external-audio.md
      configuration/network-printer.md
      configuration/resize-disk-image.md
      configuration/resize-root-disk-image.md
      customization/fedora-minimal-template-customization.md
      managing-os/hvm.md
      managing-os/templates/archlinux.md
      privacy/whonix-install.md
      security/yubi-key.md
      troubleshooting/install-nvidia-driver.md
      troubleshooting/macbook-troubleshooting.md
2018-02-10 16:46:43 +01:00
Andrew David Wong
bddcd0cad2
Replace absolute with relative paths for Qubes URLs 2018-02-03 14:51:06 -06:00
Peter Gerber
6b3eb8fd71 clarify description for randomizing MAC addresses 2018-01-28 23:14:56 +01:00
Peter Gerber
2d84312ac5 Improve instructions for randomizing MAC addresses
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
2018-01-22 02:27:09 +01:00
Miguel Jacq
408aef3941
Fix conflicts introduced from new changes in master branch 2017-11-01 14:00:00 +11:00
Michael Carbone
2f9bc4bbab added Fedora 25 mention 2017-08-04 19:25:04 -04:00
Miguel Jacq
db13ef5a33
Various minor spelling and grammar fixes 2017-05-11 18:48:59 +10:00
tasket
107bdd769a Fix keywork (again)
See https://mail.gnome.org/archives/networkmanager-list/2016-October/msg00019.html
2016-12-16 01:43:02 -05:00
qubenix
a9a82bedf0
Change deprecated *.cloned-mac-address to *.assigned-mac-address. 2016-11-21 03:45:06 +00:00
Andrew David Wong
4eb23c0e09
Update MAC address randomization for NetworkManager instructions
* Settings affect Ethernet in addition to Wi-Fi
* Explain `stable` and `random`

From @tasket:
https://github.com/QubesOS/qubes-doc/pull/221#issuecomment-261710939
2016-11-19 04:49:16 -08:00
Rusty Bird
3466bbe86a
Save in conf.d/ instead of modifying NetworkManager.conf 2016-11-16 18:23:30 +00:00
Rusty Bird
91d3abac15
Also randomize MAC address per Ethernet connection profile 2016-11-16 18:23:30 +00:00
Rusty Bird
82809af961
[device-scan] -> [device]
It only worked because 'wifi.scan-rand-mac-address=yes' is already the
default anyway.
2016-11-16 17:30:25 +00:00
Michael Carbone
435599eed0 fix typo 2016-11-14 12:47:11 -05:00
Andrew David Wong
af4b8ac2e4
Fix formatting 2016-10-14 20:33:02 -07:00
tasket
0fb17b62ba Change section titles to match macchanger 2016-10-13 15:47:53 -04:00
tasket
27dcc6f142 Update anonymizing-your-mac-address.md 2016-10-13 15:39:30 -04:00
tasket
bd8765f1a4 Add section for Network Manager on Debian 9 2016-10-13 12:06:16 -04:00
Andrew David Wong
417664d660
Follow our file naming conventions 2016-05-16 04:01:50 -07:00