I'm still waiting to be solved, so I bought another server RBX. Last response i got from support was 5 days ago:
The problem seems to be somewhere between the hub SBG-4ab-a72 and routers Strasbourg SBG-4ab-a9 . The strange thing is that only affects certain servers ( Like yours ) and not all.
While I'm still waiting OVH support, i'm trying to find where is the problem, and i found that if you move the failover IP to a second server and then move again to the first server, the speed is normal during five to ten minutes, so the isn't a problem with the server i think the problem is in...
@PhilV I have exactly the same issue on a server in OVH in GRA datacenter, another server in the cluster that is in RBX is not having the problem. What is your datacenter??
Fuck! i'ts a noob thing! i make a script to automate the migration process, and i removed /etc/netwok/interfaces to regenerate from venetX to ethX, but iface "lo" is not regenerated in the new interfaces by proxmox
Sorry, but the more obvious thing is always the harder thing to find!
Yes i tried vía CLI:
pct set CT -net0 name=eth0,bridge=vmbr0,ip=IP/32,gw=GW,hwaddr=MAC
And via web
After that i can ping external IP's like Google DNS 8.8.8.8, but any local ip
In the config file of the containers, the net0: line is the same in the container that works and in the container...
I just followed https://pve.proxmox.com/wiki/Convert_OpenVZ_to_LXC but after start i have strange networs issues, for example i cannot ping the ip of the container and cannot ping 127.0.0.1 too
This problem doesn't appear if i create a container in LXC instead of import it
Anyone can point me...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.