Re: vmd: routing problem

2017-07-25 Thread R0me0 ***
Hetzner routes additional subnets through a specified mac address on robots page. ( Some cases you need to open a trouble ticket ) Also, all related information is provided there. Cheers, 2017-07-25 10:26 GMT-03:00 Stuart Henderson : > On 2017-07-20, Mike Larkin

Re: vmd: routing problem

2017-07-25 Thread Stuart Henderson
On 2017-07-20, Mike Larkin 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

Re: vmd: routing problem

2017-07-20 Thread Mike Larkin
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

Re: vmd: routing problem

2017-07-20 Thread Denis Fondras
> What would be the difference to your version where i use vether instead of > an alias? Or did i missunderstand you? > The difference is broadcast trafic won't be sent over your provider network.

Re: vmd: routing problem

2017-07-20 Thread Leo Unglaub
Hey, On 07/20/17 09:46, Denis Fondras wrote: Can you people see something that i might missed? The easy way would be enable forwarding, add a vether(4) on the host, bridge it with tap0 and configure it with an IP in the 136.243.186.160/29 subnet. Use that IP as the gateway in your VMs. i did

Re: vmd: routing problem

2017-07-20 Thread Leo Unglaub
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,

Re: vmd: routing problem

2017-07-20 Thread Mischa Peters
Hi Leo, Can you ask them how they route the separate subnet to you? Mischa > On 20 Jul 2017, at 12:59, Leo Unglaub wrote: > > Hey, > >> On 07/20/17 06:25, Mike Larkin wrote: >> sysctl net.inet.ip.forwarding=1 ? >> I'm not a networking expert but I think your VM's subnet mask

Re: vmd: routing problem

2017-07-20 Thread Leo Unglaub
Hey, On 07/20/17 06:25, Mike Larkin wrote: sysctl net.inet.ip.forwarding=1 ? I'm not a networking expert but I think your VM's subnet mask is wrong for the gateway you are trying to use. thank you for your response. I tryed it with net.inet.ip.forwarding being 1 and 0. Both don't work.

Re: vmd: routing problem

2017-07-20 Thread Denis Fondras
Hello, > Can you people see something that i might missed? The easy way would be enable forwarding, add a vether(4) on the host, bridge it with tap0 and configure it with an IP in the 136.243.186.160/29 subnet. Use that IP as the gateway in your VMs.

Re: vmd: routing problem

2017-07-20 Thread Karsten Horsmann
Hi List, Hetzner has like other dedicated hosting providers an "crazy" looking network setup for ipv4. Here point to point for the default gw in a different network segment. So it's important also to keep that in mind. Maybe this document helps a bit, need to adapt to Openbsd.

Re: vmd: routing problem

2017-07-19 Thread Mike Larkin
On Thu, Jul 20, 2017 at 04:23:40AM +0200, Leo Unglaub wrote: > Hey friends, > i am trying out vmd and I have a little problem getting networking going > inside the guest machine. I am not sure if this is a problem in vmd or > simply my misconfiguration. > > From my datacenter i got the following

vmd: routing problem

2017-07-19 Thread Leo Unglaub
Hey friends, i am trying out vmd and I have a little problem getting networking going inside the guest machine. I am not sure if this is a problem in vmd or simply my misconfiguration. From my datacenter i got the following data: Main Server (OpenBSD GENERIC.MP#99 amd64)