Recent content by inDane

  1. I

    VM as Gateway. NAT for local IPs

    The culprit was rx-gro-hw ... generic-receive-offload on BROADCOM NICs (latest Firmware 22.92.07.50) with Kernel 6.8 Here is what I guess happend: I did not realize the bad RX Performance after Upgrading to PVE 8, because the problems shows only in specific conditions. 1. Docker inside VM ->...
  2. I

    VM as Gateway. NAT for local IPs

    OK, thanks and sorry for being judgemental. This is exactly what im doing. But they need a route to the outside world again. Thats where my gateway comes in. I dont think the SDN approach will solve this. I currently suspect something wonky in our backbone-network or the ISPs network. I will...
  3. I

    VM as Gateway. NAT for local IPs

    Hey Juliosene, the motivation is to use a lower amount of public IPv4 addresses. I have got a /25 net with public addresses and it is getting full. 1. Yes 2. No 3. VLAN 100 Private (192.168.1.0/24) and VLAN 999 is public from my /25 net. 1. There is no dual WAN, nor is it needed! 2. I dont...
  4. I

    VM as Gateway. NAT for local IPs

    Thanks for your input anyway! :)
  5. I

    VM as Gateway. NAT for local IPs

    Bond mode is LACP with layer 2+3 Unfortunately there is no such thing state in the log. Neither "duplicated" nor anything mentioning "mac" or mac adresses. :-(
  6. I

    VM as Gateway. NAT for local IPs

    Hey Proxmoxers, im facing a weird problem. Proxmox Version 8.2.4. I have a bond0, which is split into vlans. I have vmbr0 which is VLAN aware. Lets say i have a private network 192.168.1.0/24 and some VMs there with a virtio NIC with vlan tag 100. Now I am adding another VM, that has two...
  7. I

    No matching key exchange method found.

    it was an ip address conflict... It was a IP on the switch itself for debugging purposes in that network, that hasnt been removed by the network-admin after the debugging....
  8. I

    No matching key exchange method found.

    i cant really narrow down to what it is. We've redone the switch config and the local network configs. Sometimes ssh just works and other times it doesnt. When it works, its says debug2: peer server KEXINIT proposal debug2: KEX algorithms...
  9. I

    No matching key exchange method found.

    Thanks for your input! Yes, this is what I initially thought too. But no, unfortunately not. At this point I'm glancing towards broken tranceivers/nics/switchports... I've had this problem before with the same node. I did a fresh reinstall and the same problem is coming up again. I am going...
  10. I

    No matching key exchange method found.

    that is odd, they are allowed and its only one out of 8 identical installations, that shows this behavior. And also, it is not permanently, sometimes it works, sometimes it doesn't.
  11. I

    No matching key exchange method found.

    Hey all, one of my nodes is causing my cluster to break sync every now and then. When that is happening, it usually does not want me to access it via SSH and gives this error: Unable to negotiate with 10.168.61.21 port 22: no matching key exchange method found. Their offer...
  12. I

    Abysmal IO delay inside containers

    on the network device you mean? How should that affect the underlying NFS? Client -> SSH -> Container -> fio-command -> IOs towards NFS. If you are talking about the network device, then it would only affect the "client -> ssh" part.
  13. I

    Abysmal IO delay inside containers

    i can reliably crash my system if i put IO load inside a container that has its image as raw on the nfs share...
  14. I

    Abysmal IO delay inside containers

    Dear Proxmoxers, i have two boxes, one is running truenas with ZFS RaidZ1 and exporting via NFS. The other one is running Proxmox 7.2. (pve-host) If I am running i.e. fio --randrepeat=1 --ioengine=libaio --direct=1 --gtod_reduce=1 --name=test --bs=4k --iodepth=64 --readwrite=randrw...
  15. I

    Is It possible to boot directly from a NVMe that is passed-through ?

    Hi, I accidentally found a workaround. Usually there is a regular disk created with the VM. The default size for a Win10 VM is 32GB. Delete/Detach this disk. Boot the machine, go into the EFI settings, change the boot order again and voilá, it works. Best regards inDane