diff options
| author | uvok cheetah | 2021-09-22 21:03:25 +0200 |
|---|---|---|
| committer | uvok cheetah | 2021-09-22 21:03:25 +0200 |
| commit | 0816a55f39f6752e8491e691a2e0da6a26019bda (patch) | |
| tree | 8655430e9d078478b79f0c5ba5c7d63869ca3805 /_posts/2021-09-22-problems-updating-proxmox.md | |
| parent | 7f78f0e1f68411174ed8bf0447eedcfdacc638a2 (diff) | |
Add article
Diffstat (limited to '_posts/2021-09-22-problems-updating-proxmox.md')
| -rw-r--r-- | _posts/2021-09-22-problems-updating-proxmox.md | 17 |
1 files changed, 17 insertions, 0 deletions
diff --git a/_posts/2021-09-22-problems-updating-proxmox.md b/_posts/2021-09-22-problems-updating-proxmox.md new file mode 100644 index 0000000..3885b79 --- /dev/null +++ b/_posts/2021-09-22-problems-updating-proxmox.md @@ -0,0 +1,17 @@ +--- +layout: post +title: Network gone after updating Proxmox +date: 2021-09-22 20:59 +0200 +--- + +So, after upgrading Proxmox from version 6.x to 7.x, the network +was suddenly gone. Turns out, the network service wasn't started anymore. + +According to `systemctl`, it was disabled. +After some googling, it seemed to be that this was because +I was doing was the Debian docs were saying, performing +an `apt purge`, deleting the `ifupdown` configuration. This seemingly +disabled `networking.service`. + +So I symlinked the unit into `/etc/systemd/system/default.target.wants`, rebooted +and everything was fine again. Thank godness for physical access to hardware. |