Recent content by bofh

  1. B

    Proxmox Host Network Issue (Cannot Ping Gateway)

    probably ip is taken, you assign that ip within the dhcp range. or gateway requires ip by dhcp. certainly a gateway issue
  2. B

    PVE firewall with NAT not working

    the config i gave you does work, at least for VM, again i cant speak for lcx at all, i dont use lcx container. but does work def for vm ofc network config needs to be changed on the vm for vmbr0
  3. B

    PVE firewall with NAT not working

    no it is not reread again you confused routed with nat there the nat section even at hetzner (famous for some esoteric shit) it is basicalkly the same as i wrote you they write main interface has the ip, then bridge tget the private subnet, then you nat as it should be. if you need more than...
  4. B

    PVE firewall with NAT not working

    ok i dunno why i did this but i did here a working config auto lo iface lo inet loopback auto enp41s0 iface enp41s0 inet static address publicIP/26 gateway publicGW post-up iptables -w -t nat -A PREROUTING -i enp41s0 -p udp -m tcp -m multiport -d publicIP --dports 443,80...
  5. B

    PVE firewall with NAT not working

    no its not proof of a problem the additional command is nessesary to ad prerouting to the fwbr chain, which normaly is not needed there so it isnt in. if you do nat you need it in so presourting can get filtered by fwbr which in turn allows to set rules via the gui you dont need to add it to...
  6. B

    PVE firewall with NAT not working

    oh hold this is not the proper nat setup youre supposed to give the pubip to your network adapter then make vmbr0 a private network then you can nat to it
  7. B

    PVE firewall with NAT not working

    if firewall is enabled in the vnic but disabled in the firewall panel means the firewall is OFF, if you still having blocking issues it isnt the firewall at all. and i know what it is as i just made a post about it. when you activate the vnic firewall checkmark, regardless if firewall on or...
  8. B

    PVE firewall with NAT not working

    cannot speak of lcx container but it does work with the VM firewall if you put prerouting into the fwbr chain (line2)
  9. B

    VLAN's across hosts in a cluster

    is VLAN 10 enabled on the switch side ? did you test if O2#1 works ? if you test that then you narrow it down to VM level, if that doenst work than its probably switch config
  10. B

    VLAN's across hosts in a cluster

    there are 2 ways todo this We call it Option 1 and 2 (O1, O2) either you want vmbr1 pass VLAN10 as native traffic to the vm. in that case you need todo nothing in the vm except set the interface to vmbr1. with again 2 ways todo that. o1#1 do it on the switch and simply pass VLAN10 as native on...
  11. B

    PVE firewall with NAT not working

    you mean a normal snat?dnat ? echo 1 > /proc/sys/net/ipv4/ip_forward iptables -t raw -I PREROUTING -i fwbr+ -j CT --zone 1 #iptables -t nat -A POSTROUTING -s '10.11.250.0/24' -o eth0 -j MASQUERADE iptables -w -t nat -A POSTROUTING -o eth0 -s 10.11.250.20 -j SNAT --to-source 10.10.250.20...
  12. B

    PVE Firewall and MTU little trap

    I just stumbled across a little nasty trap. When not setting the firewall check mark in the Network adapter, MTU doesnt seem to be set or taken from the Bridge by default. However, the Moment you activate the firewall Check mark MTU will be forced set to 1500 This can be a very nasty trap for...
  13. B

    [SOLVED] After syncing to a new datastore: backup owner check failed (pve-user@pbs != backup@pam)

    let me necro this with a little script change path of directory to your datastore change datastorename and mynamespacename in the path and in the execution line change newowner % #!/bin/bash # Define the directory (current directory by default)...
  14. B

    Nodes lose network connectivity when I reboot the switch and do not get it back after switch reboot is complete

    no sorry iam not italian but i did understand mostly... :) i stole the config from the official proxmox documentation lol
  15. B

    Nodes lose network connectivity when I reboot the switch and do not get it back after switch reboot is complete

    my corosync suggest its really not that complicated, you can set it up within 5 minutes. just define 2 new tagged vlans and add one of each to each of tghe mellanox ports so lets say vlan 100 and 101, you add vlan 100 to all ports using mellanox port1, and 101 to all ports using mellanox 2 (i...