SolusVM+OpenVZ internal IP's any work arounds?
As a fairly recent adopter of OpenVZ myself I may be missing something silly or obvious here, I am a little stumped on how to work with internal IP's with OpenVZ in conjunction with solusvm.
If I just do it manually obviously no problem with that however solusvm (despite it being available in the back end) simply does not work with internal IP's I was just wondering if any hosts have come up with any work arounds they may be willing to share?
I have scripted something to handle it however its not ideal and not scale-able.
Before anyone asks I have asked solusvm, they don't know how to make it work and they have been getting the same request for 4 years so I don't think it will ever be supported directly by them.
Anyway, the only one I have come up with via solusvm it to add internal IP's as externals do not assign them to any node and manually enable the range for the node, assign the IP then remove the assignment from the node but obviously long term that wont work and you cannot leave it pinned to a node or clients will get internal instead of external half the time.
Any providers have any bright ideas I would love to hear how you have worked this out?
(yes moving away from solusvm is a very valid one but I have already considered that) )
I am no longer active here, find me at https://talk.lowendspirit.com