Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • T tails
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 1,013
    • Issues 1,013
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 25
    • Merge requests 25
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • tails
  • tails
  • Issues
  • #18443
Closed
Open
Issue created Jun 22, 2021 by intrigeri@intrigeriMaintainer

veth* interfaces should be ignored by NetworkManager and MAC spoofing

While working on another topic I've read the Journal and noticed 2 things:

  • MAC spoofing is attempted for veth0, and fails. IMO we should not even try. This is bound to cause trouble later down the road, when we improve our user story for MAC spoofing failures.
  • NetworkManager seems to manage veth-*. I hope it's not a big deal but it still might cause trouble at some point to have 2 systems trying to manage the same devices. On my system I'm using unmanaged-devices for such things, but I'm using the keyfile plugin, and I did not check if the config plugin we're using in Tails supports this parameter.

cc @boyska

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking