New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Comments
The interesting thing is that, even here on LET, we've not gotten anywhere.
OP ain't getting anywhere with OVH.
He ain't getting anywhere here on LET.
Conculusion, OVH = LET? Are we just as incompetent as OVH? Does this mean perhaps OVH is actually good?
The end must be nigh.
@FlorinMarian
From whois your IP, I guess you have a 51.195.48.96/28 subnet, with its gateway is 51.195.48.110.
From your data, I assume your host gateway is 51.195.61.254.
You have 2 ways to config your VM guests:
Florin is trying to use the first IP .96 on a VM.
Would it ever work?
I think it's possible to get it working, given that it works when configured on the host.
@bsh @yoursunny thank you for help!
You figured our correctly, that's the FO allocation but I main server has different IP than 51.195.48.XXX.
You said correctly, .110 will be gateway for .224 subnet but I use exactly same DHCP configuration for 51.75.158.48-63 (again /28) and have 4/4 successfully sent requests to all IPs within this range.
Best regards, Florin.
Sigh
Yes, it works if using with virtual MAC. For guest machines, OVH /28 has 15 usable IP's (need to create virtual MAC), except the gateway. For just IP-aliasing on the host machine, OVH /28 has 16 usable IP's (no need to create virtual MAC).
You mean that you have one (1) dedi with two (2) subnets of /28 size, and I guess it's a SyS server, not OVH.
OpenStack seems not to support fragmented subnets, unfortunately. If so, you would have to create a virtual network for bridging your two subnets to the host. Otherwise saying, try creating multiple floating IP pools on your neutron router and bridge your virtual network to the physical network to enable connectivity to and from virtual instances.
Conclusion
OVH really does a blunder when changing your hardware, because it's not the hardware-related issue.
SYS is not ideal for running OpenStack when comparing to OVH on the cost-effective side (16 free IPs vs 254 free IPs).
I did say IMHO, if you don't agree with opinion then no problem, it's your right. Now, name calling other people just because they have different opinion than yours is not. Imagine what becomes of this community, when people name calling each other just because the opinion difference.
Everyone is entitled of their own opinion. Perhaps you think Linus is bad. But I still think he's good. It's literally impossible to please everyone. Maybe you are just not his target demographic.
My fav episode would be the taze each other with electroboom. While the science content is very negligible, the experiment is failed, their objective is to break a component, and then failed breaking even one of them. I still think, it's a good content.
Hahaha, I like this too, I lost count how many Electroboom shot Linus
Thank you for your time, dude
Just few minutes ago OVH sent me an internal comment sayin' that they're still working on this issue even they don't update my ticket daily.
Regarding server, it is pure OVH, not SyS.
Best regards, Florin.