Edgerouter 4 S2S & Client VPN config files: what's the best way to replace (overwrite) the Public IP address?
set vpn ipsec site-to-site peer 1.2.3.4 authentication mode pre-shared-secret
set vpn ipsec site-to-site peer 1.2.3.4 authentication pre-shared-secret "shared-secret"
set vpn ipsec site-to-site peer 1.2.3.4 description ipsec
set vpn l2tp remote-access outside-address 5.6.7.810 "old" vm's, Lenovo host w Fedora 32
XP = 2 vm's
2003R2 = 2 vm's
2008 = 6 vm's
RAID controller = LSI 9260-8i w 2 virtual drives (RAID 1 - o/s & R 10 - vm's)
R10 is lvm2 & qcow2 files are at /mnt/data
I shutdown all the vm's and scp'd the qcow2 files to a file share on 2nd server. (Just in case something went wrong)
Installed Proxmox 6.2 on the R1 array.
Added the existing r10 lvm2 into Proxmox.
Added the existing /mnt/data as a directory to Proxmox.
I could now go into the Proxmox shell & all my qcow2 files showed up!
Time to create 10 "new" vm's (each with 1gb disk)
The disks were located at /mnt/data/images/100/vm-100-disk-1.qcow2 (100 is the ID of the vm, each vm has a different ID)
I mv'd all the qcow2 files from /mnt/data to /mnt/data/images/"vm-ID"/your_vm.qcow2
Back to the shell, run cmd qm rescan
Back to the gui, in each vm, detach the vm-100-disk-1.qcow2, add your original qcow2 file
Boot up the vm!
All in all, pretty damn easy & painless!!
@PhlipElder said in Password manager for ordinary users?:
KeePass. Been using it for years.
It's simple, great for organizing, and the auto-type just works.
Sorry, that UI looks like something from the '60's!
Have you looked at https://1password.com/
Btw, I tried (actually paid for it) Dashlane...no thanks. Terrible, gawd awful support!
Must have been a problem with the backend servers.
Yesterday, I re-tried the updates & all is good.
@black3dynamite I'm using 1.1.1.1 & 9.9.9.9, but it's worth taking a look & changing!
After adding the fastestmirror=true
determining the fastest mirror (95 hosts).. done.
[MIRROR] anaconda-install-env-deps-32.24.7-2.fc32.x86_64.rpm: Interrupted by header callback: Server reports Content-Length: 7624 but expected size is: 134600
[MIRROR] kernel-core-5.6.14-300.fc32.x86_64.rpm: Curl error (28): Timeout was reached for https://mirror.atl.genesisadaptive.com/fedora/linux/updates/32/Everything/x86_64/Packages/k/kernel-core-5.6.14-300.fc32.x86_64.rpm [Operation timed out after 30001 milliseconds with 0 out of 0 bytes received]
[MIRROR] kernel-modules-5.6.14-300.fc32.x86_64.rpm: Curl error (28): Timeout was reached for https://mirror.atl.genesisadaptive.com/fedora/linux/updates/32/Everything/x86_64/Packages/k/kernel-modules-5.6.14-300.fc32.x86_64.rpm [Operation timed out after 30000 milliseconds with 0 out of 0 bytes received]
[MIRROR] anaconda-install-env-deps-32.24.7-2.fc32.x86_64.rpm: Curl error (28): Timeout was reached for http://mirror.atl.genesisadaptive.com/fedora/linux/updates/32/Everything/x86_64/Packages/a/anaconda-install-env-deps-32.24.7-2.fc32.x86_64.rpm [Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds]
(54/132): anaconda-install-env-deps-32.24.7-2.fc32.x86_64.rpm 1.7 kB/s | 131 kB 01:16
[MIRROR] kernel-core-5.6.14-300.fc32.x86_64.rpm: Curl error (28): Timeout was reached for http://mirror.atl.genesisadaptive.com/fedora/linux/updates/32/Everything/x86_64/Packages/k/kernel-core-5.6.14-300.fc32.x86_64.rpm [Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds]
[MIRROR] anaconda-live-32.24.7-2.fc32.x86_64.rpm: Curl error (28): Timeout was reached for https://mirror.atl.genesisadaptive.com/fedora/linux/updates/32/Everything/x86_64/Packages/a/anaconda-live-32.24.7-2.fc32.x86_64.rpm [Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds]
[MIRROR] kernel-core-5.6.14-300.fc32.x86_64.rpm: Curl error (28): Timeout was reached for http://mirrors.kernel.org/fedora/updates/32/Everything/x86_64/Packages/k/kernel-core-5.6.14-300.fc32.x86_64.rpm [Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds]
(55/132): anaconda-live-32.24.7-2.fc32.x86_64.rpm 2.8 kB/s | 143 kB 00:51
[MIRROR] kernel-modules-5.6.14-300.fc32.x86_64.rpm: Curl error (28): Timeout was reached for http://mirror.atl.genesisadaptive.com/fedora/linux/updates/32/Everything/x86_64/Packages/k/kernel-modules-5.6.14-300.fc32.x86_64.rpm [Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds]
[MIRROR] anaconda-tui-32.24.7-2.fc32.x86_64.rpm: Curl error (28): Timeout was reached for http://mirrors.kernel.org/fedora/updates/32/Everything/x86_64/Packages/a/anaconda-tui-32.24.7-2.fc32.x86_64.rpm [Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds]
(56/132): anaconda-tui-32.24.7-2.fc32.x86_64.rpm 2.1 kB/s | 223 kB 01:46
[MIRROR] kernel-core-5.6.14-300.fc32.x86_64.rpm: Curl error (28): Timeout was reached for https://mirrors.xmission.com/fedora/linux/updates/32/Everything/x86_64/Packages/k/kernel-core-5.6.14-300.fc32.x86_64.rpm [Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds]
(57/132): anaconda-widgets-32.24.7-2.fc32.x86_64.rpm 4.1 kB/s | 165 kB 00:40
(58/132): blivet-data-3.2.2-1.fc32.noarch.rpm 36 kB/s | 96 kB 00:02
[MIRROR] kernel-core-5.6.14-300.fc32.x86_64.rpm: Curl error (28): Timeout was reached for https://pubmirror1.math.uh.edu/fedora-buffet/fedora/linux/updates/32/Everything/x86_64/Packages/k/kernel-core-5.6.14-300.fc32.x86_64.rpm [Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds]
(59/132): cups-client-2.3.3-2.fc32.x86_64.rpm 1.8 kB/s | 70 kB 00:38
(60/132): ghostscript-9.52-2.fc32.x86_64.rpm 76 kB/s | 38 kB 00:00
[MIRROR] kernel-modules-5.6.14-300.fc32.x86_64.rpm: Curl error (28): Timeout was reached for https://mirrors.xmission.com/fedora/linux/updates/32/Everything/x86_64/Packages/k/kernel-modules-5.6.14-300.fc32.x86_64.rpm [Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds]
[MIRROR] kernel-core-5.6.14-300.fc32.x86_64.rpm: Curl error
Trying to do "dnf upgrade -y" on a F32 xfce desktop.
For the past 2 days, I see a lot of this:
How to solve?
@CCWTech said in Associate existing drive with new Proxmox VM:
@scottalanmiller said in Associate existing drive with new Proxmox VM:
@Pete-S said in Associate existing drive with new Proxmox VM:
You have that info in the thread below from the other day:
https://mangolassi.it/topic/21751/import-a-qcow2-into-proxmoxBasically you need to put it in the right place and it has to have the right name (depending on config file, what filesystem, VM ID)
Right, it seems that you just go into the config and edit the name of the drive to point to the correct volume name and ta da.
What do you need to do in order to change the boot order?
You can do this in the GUI.