Recent content by c24
-
C
[SOLVED] HOST / VM & Container config only works partially
SOLVED myself,.. Obviously, my config is complete BS. Here is how it should look like in a routed-configuration: auto lo iface lo inet loopback iface eno2 inet manual auto eno1 iface eno1 inet static address 168.xxx.yyy.aaa/25 gateway 168.xxx.yyy.zzz pointopoint...- c24
- Post #2
- Forum: Proxmox VE: Networking and Firewall
-
C
[SOLVED] HOST / VM & Container config only works partially
Hello everyone, Hetzner Dedicated Server 168.xxx.yyy.aaa / Main Server IP 168.xxx.yyy.zzz / Main Server Gateway 168.xxx.yyy.111-333 / additional IPs (3 single) On Proxmox i have a VM install in which Proxmox Back Server runs - using vmbr0 / 168.xxx.yyy.111 And that works perfectly (IN/OUT)...- c24
- Thread
- additional ips hetzner not working
- Replies: 1
- Forum: Proxmox VE: Networking and Firewall
-
C
2 nodes, 1 VM on each node. Cannot ping each other.
Hello everybody, I have two dedi's at Hetzner, on each Proxmox. One VM runs on each Proxmox node (Debian 10) The VMs can ping each of the following: - oneself - the own host node - the other host node BUT they cannot ping the other VM on the other host node. (Destination Host Unreachable)...- c24
- Thread
- destination host unreachable hetzner vm to vm vswitch
- Replies: 1
- Forum: Proxmox VE: Networking and Firewall
-
C
2 Nodes, 1 VM auf jedem Node. Können sich nicht gegenseitig pingen.
Hallo zusammen, Ich habe bei Hetzner zwei dedi's, auf jedem Proxmox. Auf jedem Proxmox-Node läuft jeweils eine VM (Debian 10) Nun können die VMs jeweils folgendes anpingen: - sich selbst - den eigenen Host-Node - den anderen Host-Node ABER Sie können nicht die andere VM auf dem anderen...- c24
- Thread
- destination host unreachable hetzner vm to vm vswitch
- Replies: 1
- Forum: Proxmox VE (Deutsch/German)