Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • T tails
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 974
    • Issues 974
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 26
    • Merge requests 26
  • 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
  • #7338
Closed
Open
Issue created May 29, 2014 by intrigeri@intrigeriMaintainer1 of 1 checklist item completed1/1 checklist item

NetworkManager persistence setting is not migrated

Originally created by @intrigeri on #7338 (Redmine)

When migrating to Tails/Wheezy a Tails/Squeeze with NM persistence enabled, one “loses” their persistent networks. I think that’s acceptable. What is not acceptable is that if one then re-creates their network, and reboots, their settings are lost: we keep persisting the old location, but don’t start persisting the new one.

When the /home/amnesia/.gconf/system/networking/connections persistence preset is enabled, live-persist should automatically make /etc/NetworkManager/system-connections persistent.

Feature Branch: bugfix/7338-migrate-nm-persistence-setting

Related issues

  • Blocked by #7343 (closed)
Edited May 15, 2020 by intrigeri
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking