Recent content by prox145

  1. P

    Receiving traffic not meant for my IP addresses.

    Hi, no, not Hetzner, much smaller provider I'll try bridge-disable-mac-learning and see if it works. Thanks
  2. P

    Receiving traffic not meant for my IP addresses.

    Hi, I have a server co-located at a datacenter and IP addresses rented from the hosting provider. I've been having an issue for a while where I'm receiving traffic that is not intended for my IPs, but instead for other IPs owned by my hosting provider. The source IP addresses are random...
  3. P

    Live-migrate outside of cluster

    How about now? Unsure how to navigate the mailing list.
  4. P

    Fresh Install Of 7.1 Disk Is Showing 100 percent utilization

    Yeah that is correct, it'll show 100% under there, but then under local and local-lvm you'll see the true usage. Example:
  5. P

    Proxmox showing incorrect usage for Ubuntu VM

    I came across this thread: https://forum.proxmox.com/threads/memory-usage-not-same-as-in-vm.82640/ which is the exact same issue I have, however the guy didn't end up replying back. I'm running Ubuntu 20.04.3 with PVE 6.4-4, Ballooning device is enabled in the Memory Settings: Doing info...
  6. P

    Best way to reinstall proxmox and keep everything as is?

    Much appreciated, seems to be working so far.
  7. P

    Best way to reinstall proxmox and keep everything as is?

    Which version would you recommend? 2.0 or 1.1, I am running pve 6.2-9
  8. P

    Best way to reinstall proxmox and keep everything as is?

    Hey, what's the best way to reinstall proxmox, and keep all vms, configs(firewall,etc.) as is?
  9. P

    Networking works for existing containers and VMs but not newly created ones.

    root@testnet1235:~# ip r default via 185.189.48.1 dev eth0 185.189.48.0/22 dev eth0 proto kernel scope link src 185.189.50.20
  10. P

    Networking works for existing containers and VMs but not newly created ones.

    @Moayad Do you have any suggestions on how I could possibly solve it?
  11. P

    Networking works for existing containers and VMs but not newly created ones.

    It is not a fix, if you had paid attention to my post it says the one with the Firewall has working networking, the other does not.
  12. P

    Networking works for existing containers and VMs but not newly created ones.

    That does not work, no. It gets stuck and then after a short while this appears
  13. P

    Networking works for existing containers and VMs but not newly created ones.

    Hi, the /etc/network/interfaces config is the following: auto lo iface lo inet loopback iface eno1 inet manual auto vmbr0 iface vmbr0 inet static address 185.189.50.190 netmask 255.255.252.0 gateway 185.189.48.1 bridge_ports eno1 bridge_stp off...
  14. P

    Networking works for existing containers and VMs but not newly created ones.

    Sorry for the late response, I will post in one minute.