FOR TIPS, gUIDES & TUTORIALS

subscribe to our Youtube

GO TO YOUTUBE

12681 questions

15064 answers

24132 comments

47091 members

0 votes
129 views 3 comments
by
Hi,

I've just started to exercise with data transfer channel consisting of:

- PC with static IP: 192.168.1.100/24

- RUTX11 configured as SPOKE according the article https://wiki.teltonika-networks.com/view/RUTX_DMVPN

  (Router B - SPOKE - LAN IP:192168.1.1/24 - GRE:10.1.1.2/32)

- RUTX11 configured as HUB according the same article https://wiki.teltonika-networks.com/view/RUTX_DMVPN

  (Router A - HUB - LAN IP:192.168.5.1/24 - GRE:10.1.1.3/24)

- PC with static IP: 192.168.5.200/24

Both RUTX11 have RUTX_R_00.07.02.2, both are used as GSM/LTE routers - HUB router has static WAN Ip

Configuration test for both routers seems to be OK - routes exists.

There is an entry 10.1.1.3 in SPOKE routes table and in HUB routes table one can see entry 10.1.1.2

Pings from address 192.168.1.100 to 192.168.1.1, 10.1.1.2, 10.1.1.3 are OK

Pings from address 192.168.5.200 to 192.168.5.1, 10.1.1.3, 10.1.1.2 are OK too.

However there is no connection  between PC's

Pings from 192.168.1.100 to 192.168.5.1 and 192.168.5.200 are negative

Pings from 192.168.5.200 to 192.168.1.1 and 192.168.1.100 are negative too.

Any guidelines how to fix it?

1 Answer

0 votes
by
Hello,

Have you tried to check if disabling firewall in your PCs help?

Best regards,
by
Hi again,

I disabled the firewall in both PCs before starting the testing tunnel.

Both RUTX11 were reset to factory settings at the beginning. Then start setup including APNs and LAN addresses has been done. Then DMVPN setup for HUB and SPOKE has been performed. No additional, manually entered settings (concerning - for example - both RUTX11 firewalls or static routes). I've assumed that the Teltonika procedure (described in the article https://wiki.teltonika-networks.com/view/RUTX_DMVPN), is all to be done to achieve a working tunnel (working means able to be pinged successfully from any end of the tunnel).

Best regards
by
Could you explain if the procedure (described in the article https://wiki.teltonika-networks.com/view/RUTX_DMVPN) allow and gives finally the possibility to ping successfully, a computer on each end of the tunnel? In other words - can user expect that all needed routes are automatically written to the routing tables? Or is this the user responsibility to enter manually routes needed to connect PCs on each end of the tunnel. I'm asking this way because all I've been able to achieve was a successful ping from the PC at the one end of the tunnel to the GRE address on the opposite end of the tunnel. Successful pinging of the PCs was only possible after manual insertion of lacking routes (it seems to be something against the concept of DMVPN in my opinion).
Best regards
by

RUTX11 - BGP configuration for Spoke 

According to information given here: https://wiki.teltonika-networks.com/view/RUTX_DMVPN, field BGP router ID (field numb 5) should be the HUB GRE Tunnel IP, field Network (field numb 6) should be the HUB LAN network IP with subnet mask. 

Is this correct? 

Why does Spoke advertise (to HUB) HUB's data instead of its own LAN IP and LAN Network? 

Let compare it with routers RUT9xx Spoke BGP configuration (see https://wiki.teltonika-networks.com/view/DMVPN_configuration) 

Configuring procedure - step: Network > Routing > Dynamic Routes > BGP 

Maintained part of BGP configuration for routers RUT9xx is different than for RUTX11 

                                                                                            RUT9xx (Config Step 2)      RUTX11 (Config Step 3) 

Spoke config: BGP, configure BGP instance: BGP router ID -----> Spoke LAN IP                    HUB GRE Tunnel IP 

Spoke config: BGP, configure BGP instance: Network ------------> Spoke LAN Network           HUB LAN network IP with subnet mask) 

Which way of BGP configuring is correct? 

This one for RUT9xx or this for RUTX11? Both are correct? Routers firmware performs in different way for these two routers types? 

Please explain.