Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

[Stuck]Use IPv4 subnet for VMs remotely
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.

[Stuck]Use IPv4 subnet for VMs remotely

FlorinMarianFlorinMarian Member, Host Rep
edited September 2020 in Tutorials

I've followed this tutorial

Commands used both servers:

Server 1
ip tunnel add gre1 mode gre remote local ttl 255
ip link set gre1 up
ip route add dev gre1

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

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

Maybe it's important: IPs and 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!

Network configuration used for VM:
IP address:

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.


  • RickBakkrRickBakkr Member, Patron Provider, LIR

    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.

  • FlorinMarianFlorinMarian Member, Host Rep

    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 as gateway (doesn't matter if I use or 212.188.103.XX)

Sign In or Register to comment.