Recent content by gusto

When I try tracert, I see tracert 192.168.100.2 Tracing route to 192.168.100.2 over a maximum of 30 hops 1 <1 ms <1 ms <1 ms 10.10.8.1 2 1 ms <1 ms <1 ms 192.168.100.2 Trace complete. I removed the 192.168.100.0/24 subnet from AllowedIPs to see if that was the cause. thx

Route table Active Routes: Network Destination Netmask Gateway Interface Metric 0.0.0.0 0.0.0.0 192.168.100.1 192.168.100.8 25 10.10.8.0 255.255.255.0 On-link 10.10.8.10 5 10.10.8.10 255.255.255.255...

There is a bridge between the physical LAN and the VM. The gateway is 192.168.100.1. I cannot even ping the gateway.

Maybe I didn't need to mention WG, but since I use WG as well, I mentioned it. My WG setup on Win 11 is [Interface] PrivateKey = GOFhaxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxiMeXAFE= Address = 10.10.8.10/32 [Peer] PublicKey = fdjMhZ9GzxxxxxxxxxxxxxxxxxxxxxxxSRhlfjslR00= AllowedIPs = 192.168.100.0/24...

Apologies—this topic relates to networking, but specifically within the Windows 11 OS. I know many people also use Windows 11 in a VM, so perhaps you can offer some advice. This is my configuration for QM (on Proxmox VE 9.1.2) qm config 100 agent: 1 bios: ovmf boot: order=scsi0;ide0;ide2;net0...

Sorry, yes, that was a question. However, I tried to create LXC several times. Sometimes it takes 50-70 seconds until LXC starts. Today I tried again and LXC was created and started in 10 seconds (like in the old days). Here is the script how I create LXC pct create 114 \...

I don't really mind. I don't create and restore LXC that often. I just wanted to know why it behaves like that in PVE9, when it was OK in PVE8. The HW is exactly the same. I accidentally installed PVE8 in ZFS RAID0. Now in PVE9 I have it installed in ZFS RAID1 It is possible that stripping was...

According to AI, my SSD patriot P200 are old disks and not very suitable for ZFS. They have 39000 hours of operation which is more than 4 years (that's true). I had Proxmox 8 on ZFS RIAD0 and now I have Proxmox 9 on ZFS RAID1 (mirror). Could this be the problem? AI advised me to use this zfs set...

I tried watch -cd -n1 "zpool iostat -vyl 1 1", but I'm not an expert, I can't judge if it's okay. I also tried pveperf 3x pveperf /var/lib/vz CPU BOGOMIPS: 69597.24 REGEX/SECOND: 4606004 HD SIZE: 205.62 GB (rpool/var-lib-vz) FSYNCS/SECOND: 41.41 DNS EXT: 28.69...

Today I updated Proxmox to 9.1.4 and rebooted. I still have problems. LXC (debian 13) takes 70-90 seconds to create. Restoring takes the same amount of time. It's pure LXC (the compressed backup is not even 250MB). zpool status -v pool: datapool state: ONLINE scan: scrub repaired 0B in...

I don't like it at all. If I backup LXC (zstd), the size is 250MB. If I do a restore via the web gui, it takes 70 seconds. Something is definitely wrong there. In Proxmox 8, backup and restore were in the order of seconds. Graphs during LXC manipulation (creation, backup, restoration).

NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS FSTYPE MODEL sda 8:0 0 238.5G 0 disk Patriot P200 256GB ├─sda1 8:1 0 1007K 0 part ├─sda2 8:2 0 1G 0 part vfat └─sda3 8:3 0 237G 0...

When I was using proxmox 8, creating LXC debian 12 took very fast (5-10 seconds). Now I'm using Proxmox 9 and creating LXC debian 13 takes more than a minute. See graphs of what happens when creating LXC Is this a bug? pct create 114 \ local:vztmpl/debian-13-standard_13.1-2_amd64.tar.zst...

There is criticism of the new installer everywhere. Offline installation was 1000x better. That's why I used the 2.7.2 ISO image for installation and then updated to 2.8.1

I use pfsense as the only router/firewall in the network (there is a gpon modem in bridge mode in front of it). pfSense from ver. 2.8.0 does not use the regular ISO installation, but online installation. After booting the ISO, you need to configure the WAN (IP static/dynamic, PPPoE, VLAN ....)...