Search results

and this config too not working: - VM is not reachable from internet, and additionally too VM cannot reach internet: allow-hotplug ens3 iface ens3 inet static post-up echo 1 > /proc/sys/net/ipv4/ip_forward post-up echo 1 > /proc/sys/net/ipv4/conf/ens3/proxy_arp auto vmbr0 iface...

PVE: root@8900:~# ip route show default via 185.244.30.1 dev ens3 onlink 185.244.30.0/24 dev vmbr0 proto kernel scope link src 185.244.30.26 185.244.30.1 dev ens3 proto kernel scope link src 185.244.30.26 185.244.30.37 dev vmbr0 scope link root@8900:~# route -n Kernel IP routing table...

Good day PVE: allow-hotplug ens3 iface ens3 inet static address 185.244.30.26/24 pointopoint 185.244.30.1 gateway 185.244.30.1 post-up echo 1 > /proc/sys/net/ipv4/ip_forward post-up echo 1 > /proc/sys/net/ipv4/conf/ens3/proxy_arp auto vmbr0 iface...

Hello @shrdlicka By you suggested configuration WORKS fine, thank you (dakujem) one more time!

Hello @shrdlicka . Thank you very much for your suggestion, i will try this config today and then update here if this works Regards Milos

Hello Folks, i have VPS with 2 IPv4s: 1) this is main IP used by PVE node: 46.30.189.229/24 w GW 46.30.189.1 2) additional IP what i wanna use for VM: 5.183.95.30/24 w GW 5.183.95.1 In net config (debian 10) on PVE node (46.30.189.229) i have this config: auto lo iface lo inet...

Hello, @Corwin @polluxtroy3758 thank you very much for all your responses & contributions

and here is (mine) working network log from SYS with PVE6.4 (installed from ISO) with bridged (above mentioned) config, bridge port found and works as should: -- Logs begin at Tue 2021-07-27 20:23:58 CEST, end at Wed 2021-07-28 13:49:12 CEST. -- Jul 27 20:24:03 pve systemd[1]: Starting Raise...

Hello to all, my another update: After discussing about my issue on another forums several ppl confirmed the same issue (after installation or upgrade on v7 they got network UNREACHABLE). BTW: On Reddit also many ppl have reported network issues of PVE7 So imo v7 ISO must still contains bugs..

BTW: DHCP config auto lo iface lo inet loopback iface eno3 inet manual auto vmbr0 iface vmbr0 inet dhcp bridge-ports eno3 bridge-stp off bridge-fd 0 also not works on SoYOuStart with Proxmox 7 (network unrechable)

additional info: when using OVH template Proxmox 6 + static config auto lo iface lo inet loopback iface eno3 inet manual auto vmbr0 iface vmbr0 inet static address 54.38.192.11/24 gateway 54.38.192.254 bridge-ports eno3 bridge-stp off bridge-fd...

Good day, 1) When i tried use control panel template and choose Proxmox VE (6) template, after auto-installation is server reachable and interfaces file contains this default DHCP config: auto lo iface lo inet loopback iface eno3 inet manual auto vmbr0 iface vmbr0 inet dhcp...

Hello, good note. I also found later this option in GUI (but only by chance, because I first look for such an option only under the node because it gave me more logic find it there, not under the data center.) In case if this disable ebtables in kernel (total) that firewalld cannot find and...

UPDATE: ------------ After another day of searching, reading and investigations probably i found probable reason of problem and also usable solution (not quit clean but yet seems all work well) CAUSE: ------------ Seems, when firewalld and Proxmox VE meet self on one host/OS, they compete...

Additionally - here is actual complete iptables content if this can be useful: # iptables -S -P INPUT ACCEPT -P FORWARD ACCEPT -P OUTPUT ACCEPT -N FORWARD_IN_ZONES -N FORWARD_IN_ZONES_SOURCE -N FORWARD_OUT_ZONES -N FORWARD_OUT_ZONES_SOURCE -N FORWARD_direct -N FWDI_public -N FWDI_public_allow...

Good day. I have installed PROXMOX VE on Deb10 host node where has been already running and configured Firewalld & MariaDB & postfix & BIND. It is new fresh installation of PROXMOX where host is currently w no load, no traffic, yet idling. (host node is OVH KVM 2vCPU, nested virtualization...