Tunnel Gre problem between two hosts (vps and dedicated server)

[AleDevite]

I'm still following this. Are you on the Italian or German end of this connection? The 169 address is a Windows ad hoc service address. It won't pass every protocol.

TC

"ip rout show" outuput:
This is the output of console vps in Italy i.imgur.com/zJRXjIP.png and this is his ip 185.xx.xxx.xxx; This the output of dedicated server in germany i.imgur.com/jiFHFFL.png and his ip is 148.251.127.xx; These are the command i.imgur.com/hoOn7cE.png i tried with another guide https://www.tldp.org/HOWTO/Adv-Routing-HOWTO/lartc.tunnel.gre.html, if I have understood well the guide then they have not worked. @trinidad

[trinidad]

I'm still following this. Are you on the Italian or German end of this connection? The 169 address is a Windows ad hoc service address. It won't pass every protocol.

TC

[AleDevite]

@kpanic i'm using this guide for create a gre tunnel https://wiki.buyvm.net/doku.php/gre_tunnel , i'm not creating a vpn system.

Console image with full command output:

[kpanic]

@AleDevite ,

Ok, which VPN service do you use, if any?

[AleDevite]

@kpanic
I need to communicate internally the VPS (in Italy) and Dedicated Server (in Germany), but they do not communicate and i can not understand why.

In other attempts (by this i mean that i managed to successfully create the GRE Tunnel between these machines):
- The VPS (in France) and VPS (in Italy) communicate internally (ping and ssh command tests)
- The VPS (in France) and Dedicated Server (in Germany) communicate internally (ping and ssh command tests)

Problem (by this i mean that i could not successfully create the GRE Tunnel between these machines):
- The VPS (in Italy) and Dedicated Server (in Germany) do not communicate internally (ping and ssh command tests). I also asked hosting services if they had any restrinzione but nothing.

[kpanic]

@AleDevite ,

May I ask what are you trying to achieve with this?
Before you mess up more with the routing tables...

[AleDevite]

192.168.*.* is a local or intrAnet (not intErtnet) address issued from your router. Is not a server public address except on a local network. Somewhere in your PC client configuration (not your router other than port designation) you must connect actual public server addresses. You will need server public address somewhere when you are doing inter-country connections. That aside maybe I misunderstand your question. Below is a somewhat informative link for setting up the tunnel. Cisco should also have helpful information on this subject.

https://wiki.buyvm.net/doku.php/gre_tunnel
https://serverfault.com/questions/663259/multicraft-port-forwarding-through-a-gre-tunnel

TC

I've also tried this internal IP 10.10.10.1/24 and 10.10.10.2/24 but nothing.

I'm using the same guide you sent: https://wiki.buyvm.net/doku.php/gre_tunnel

[trinidad]

192.168.*.* is a local or intrAnet (not intErtnet) address issued from your router. Is not a server public address except on a local network. Somewhere in your PC client configuration (not your router other than port designation) you must connect actual public server addresses. You will need server public address somewhere when you are doing inter-country connections. That aside maybe I misunderstand your question. Below is a somewhat informative link for setting up the tunnel. Cisco should also have helpful information on this subject.

https://wiki.buyvm.net/doku.php/gre_tunnel
https://serverfault.com/questions/663259/multicraft-port-forwarding-through-a-gre-tunnel

TC

[AleDevite]

See here:

https://www.tecmint.com/find-linux-server-public-ip-address/

TC

Thanks for your reply, how can help me the guide for find the public ip? I have already the ip public of all server i using.

[trinidad]

See here:

https://www.tecmint.com/find-linux-server-public-ip-address/

TC

[AleDevite]

Hello guys i need to resolve this problem (all server have installed centos 7): i'm trying to create a gre tunnel through vps (in Italy - OpenVZ)
and a dedicated server (in Germany), but they do not communicate internally (ping and ssh command tests).
Next i create a gre tunnel trought vps (in Italy - OpenVZ) and vps (in France - KVM OpenStack) and their communicate, i next i had create a tunnel trought vps (in France - KVM OpenStack) and a dedicated server (in Germany) their communicate.
I can not understand why the vps (in Italy - OpenVZ) and the dedicated server (in Germany) do not communicate,
ideas on how I can fix (I also tried with iptables disabled, firewalld is not enable)? Thanks

1. VPS command for tunnel:

echo 'net.ipv4.ip_forward=1' >> /etc/sysctl.conf
       iptunnel add gre1 mode gre local VPS_IP remote DEDICATED_SERVER_IP ttl 255
       ip addr add 192.168.168.1/30 dev gre1 ip link set gre1 up

 2. Dedicated server command for tunnel:

iptunnel add gre1 mode gre local DEDICATED_SERVER_IP remote VPS_IP ttl 255
       ip addr add 192.168.168.2/30 dev gre1
       ip link set gre1 up

[root@VPS ~]# ping 192.168.168.2
PING 192.168.168.2 (192.168.168.2) 56(84) bytes of data.
^C
--- 192.168.168.2 ping statistics ---
89 packets transmitted, 0 received, 100% packet loss, time 87999ms

[root@DE ~]# ping 192.168.168.1
PING 192.168.168.1 (192.168.168.1) 56(84) bytes of data.
^C
--- 192.168.168.1 ping statistics ---
92 packets transmitted, 0 received, 100% packet loss, time 91001ms

[root@VPS ~]# lsmod | grep gre
ip_gre                  4242  -2
ip_tunnel               4242  -2 sit,ip_gre
gre                     4242  -2 ip_gre


[root@DE ~]# lsmod | grep gre
ip_gre                 22707  0
ip_tunnel              25163  1 ip_gre
gre                    13144  1 ip_gre