FOR TIPS, gUIDES & TUTORIALS

subscribe to our Youtube

GO TO YOUTUBE

14455 questions

17168 answers

28195 comments

0 members

We are migrating to our new platform at https://community.teltonika.lt. Moving forward, you can continue discussions on this new platform. This current platform will be temporarily maintained for reference purposes.
0 votes
162 views 0 comments
by anonymous

Hallo, i hope someone can help me.

I try to make a openVPN connection  between two RUTX-14 routers.

- Router0 (ovpnServer)
  on the RUTX's WAN-port connectet to my home DSL-Router (FritzBox)
  and forwarded the Port specified in the Server configuration to the Server-Router.
- Router1 (ovpn Client)
  connected to a Mobilenetwork (SIM1, Vodafone).

I created all Certificates arcording to the openVPN tutorial and now client says "Connected".

In the Server WebUI (Router0) i can find the client's IP address which is something like "IP-XXX-XX-XX-XXX-web.vodafone.com:PORTNUMBER".
but the LAN-Networks are still not connected (no new entry in Status-->Netwotrk-->LAN, no response to a ping on 192.168.1.1)

Routing on Router0:

root@Teltonika-RUTX14:~# route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
default         192.168.178.1   0.0.0.0         UG    2      0        0 eth1
0.144.241.6     *               255.255.255.255 UH    2      0        0 eth1
128.0.0.0       *               128.0.0.0       U     2      0        0 eth1
172.16.1.0      172.16.1.2      255.255.255.0   UG    0      0        0 tun_s_BritzF
ox
172.16.1.2      *               255.255.255.255 UH    0      0        0 tun_s_BritzF
ox
192.168.1.0     *               255.255.255.0   U     1      0        0 br-lan
192.168.11.0    172.16.1.2      255.255.255.0   UG    0      0        0 tun_s_BritzF
ox
192.168.178.0   *               255.255.255.0   U     2      0        0 eth1
255.255.255.0   *               255.255.255.0   U     0      0        0 eth1

 Routing on Router 1 is more or less similar, only 172.16.1.2 is turned to 172.16.1.5 for the virtual network.

Do i have to make some changes in the routing?
Im unfortunately running out of ideas.

Thanks and all the Best,
Benjamin

1 Answer

0 votes
by anonymous

Hello,

Could you double check if the Common name in the client's certificate is really the same as the one you have entered in server's TLS clients section?

Also, in server's configuration try replacing Virtual local endpoint IP with 172.16.1.6 in TLS clients section.

Best regards,