On 2017-07-20, Mike Larkin <mlar...@azathoth.net> wrote:
> On Thu, Jul 20, 2017 at 02:19:29PM +0200, Leo Unglaub wrote:
>> Hey,
>>
>> On 07/20/17 13:05, Mischa Peters wrote:
>> > Can you ask them how they route the separate subnet to you?
>>
>> as far as i understand it they route the subnet on my main ip address.
>>
>>
>> From there documentation:
>> > Newly assigned IPv4 subnets are statically routed on the main IP address
>> > of the server, so no gateway is required.
>>
>> I hope that answers your question.
>> Thanks and greetings
>> Leo
>
>
> Like I said before, I'm not a networking expert, but what you've said there
> doesn't make sense (at least to me). You'll probably need to explain to them
> what you are trying to do and have them help you. I don't think this is a vmd
> related network issue.
It's a common setup at large-scale colo hosts to conserve IP addresses while
still keeping each customer on their own L2 network. Given a gateway address
of 192.0.2.1 you should be able to use something like this:
route add -inet 192.0.2.1/32 -link -iface em0
route add -inet default 192.0.2.1
To run these commands automatically at boot, you can prefix the lines
with ! and add them to hostname.em0.
