[Stuck]Use IPv4 subnet for VMs remotely

FlorinMarian

I've followed this tutorial https://lowendtalk.com/discussion/156850/howto-tunnel-ddos-protected-ovh-ip-to-vms-in-other-datacenter

Commands used both servers:

Server 1
ip tunnel add gre1 mode gre remote 9.176.110.209 local 212.188.100.58 ttl 255
ip link set gre1 up
ip route add 212.188.103.64/30 dev gre1

Server 2
ip tunnel add gre1 mode gre remote 212.188.100.58 local 9.176.110.209 ttl 255
ip link set gre1 up
ip rule add from 212.188.103.64/30 table 666
ip route add default dev gre1 table 666
ip route add 212.188.103.64/30 dev br0 table 666
ip addr add 212.188.103.65/30 dev br0

My intention it's to use 212.188.103.64/30 (.66 / .67 usable) for VMs, at SolusVM (9.176.110.209).

Maybe it's important: IPs 212.188.100.58 and 212.188.103.64/30 are from same subnet for my hosting provider (this means I can use all of them if I choose netmask /22 at IP config).

Actually I can't ping and can't be pinged outside of VM.

Thank you!

** IP addresses are fake!

Edit:
Network configuration used for VM:
IP address: 212.188.103.66
Netmask: 255.255.255.252
Gateway: 212.188.103.65

I can ping internally those 3 servers (nodes + VPS) but nothing outside.
I guess it's something wrong with routing somewhere because it takes about 20 seconds to connect from any node with telnet to VM ssh port.

RickBakkr

Are the IPs actually routed by your provider? If not, you might want to work around that by enabling proxy_arp. Furthermore, make sure to disable rp_filter and enable ip_forward.

FlorinMarian

I've added both server
echo 0 > /proc/sys/net/ipv4/conf/all/rp_filter
echo 1 > /proc/sys/net/ipv4/ip_forward
but nothing changed actually.

I don't know how my provider route things but in static IP configuration I have to use just /22 netmask and 212.188.100.1 as gateway (doesn't matter if I use 212.188.100.58 or 212.188.103.XX)