routes

I have an issue with two Proxmox hosts which are misbehaving when establishing connections with pretty much anything. My own applications, apt, curl, ping, you name it. Both on the host and within LXC containers, things keep attempting to connect via IPv6, even though no IPv6 service is...

Vorab, ich bin kein Profi und habe mir bisher praktisch alles selbst angeeignet! Erstmal eine Beschreibung wie aktuell alles konfiguriert ist: - eno5 (10 Gbit/s) - eno6 (10Gbit/s) - bond0 (bond eno5 & eno6) - vmbr0 (Bridge für normale VMs, nicht weiter wichtig) - vmbr1 (Bridge in ein Vlan (ID...

Hello! So to make some things clear firstly, `192.99.xxx.xxx` is my Failover IP and associated subnet (`255.255.255.248`) that I'm trying to use with Proxmox on the OVH network, for which I have also already created Virtual MAC addresses for, with each being unique. This here is my...

Hi together, currently I'm trying to migrate to proxmox 4. I successfully converted my OpenVZ container to LXC. Now I need to point my failover IP to this LXC container. The failover IP is without a dedicated MAC address, which means my proxmox host must route the IP to the LXC container...

Hi, is there any way to safely add static routes via the Debian interfaces file as proxmox overwrites the interfaces file on startup I have several setups where we have internal / external Interface, external gets default, internal gets all RFC1918 routes set. Of course I could do this via...

Hi, I recently installed Proxmox 4 on a dedicated OVH server and then created a container like this: pct create 200 /var/lib/vz/template/cache/debian-8.0-standard_8.4-1_amd64.tar.gz -rootfs 25 -hostname myhost.mydomain.com -memory 1024 -nameserver 213.186.33.99 -net0...

I've got several Proxmox 3.1 machines that have a peculiar problem. After booting them up, an extra route is created that has to be deleted before the machine can talk to others on the same subnet. After booting, the routes look like this (public IPs masked): # route Kernel IP routing table...