WIKIABOUT

FOR TIPS, gUIDES & TUTORIALS

subscribe to our Youtube

GO TO YOUTUBE

14455 questions

17168 answers

28195 comments

0 members

Most popular tags

rut955 rut240 rut950 rutx11 rms vpn to openvpn wifi not sms trb140 firmware connection - ipsec on rutx12 rutx09 modbus
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.

Connection problems with the RUT360 in connection DDNS via NoIp.com (ddns.net)

0 votes
614 views 11 comments
by anonymous
hello supporter,

according to the instructions (but with the latest firmware) we have tried to address the router RUT360 with GSM or the PC's behind the router in the LAN, unfortunately without success.

We have followed the instructions see... https://wiki.teltonika-networks.com/view/Noip.com_DDNS_configuration held.

First we created an account at Noip.com, then we assigned a domain name and stored the access data in the router.

Then we changed the interface in the router to public and activated the remote access of the router for the internet.

In the dashboard of NoIp.com you can see that the router has logged in correctly.

Also in the router you can see that the router connects to NOIP.com properly.

With nslookup meinedomaine.ddns.net you can also see the assigned IP of the GSM connection.

Only via http://meinedomaine.ddns.net you can't get to the web interface of the router.

What am I doing wrong here?

regards

Alexander

Since the firmware update to the current version, you can no longer access the weblogin of the router via the IP 192.168.1.1, but must explicitly specify the 192.168.1.1 /index.html behind it... this is new!!
by anonymous

Hi - I'm just a passer-by, but I noticed you having the same problem I had.

My carrier (EE, in the UK) is using CGNAT, which presents exactly the same symptoms as you are having.  

Could that be your problem?  If it is, then I'm afraid there isn't really a way around it.  sad

1 Answer

0 votes
by anonymous

Hello,

It would be helpful if you could share your complete configuration or a troubleshoot file. 

You can also check if you have enabled remote HTTP access in System -> Administration -> Access control section.

Regarding the web interface login issue, it is known and should be solved in the 7.02.4 firmware. We apologize for any inconvenience.

Best regards,

by anonymous

yes, I had activated HTTP remote access

is there a possibility that I upload a backup file?

have not found a way to attach files

Backupfile

here is in the attachment the Backupfile from the RUT360, is this private??

regards

Alexander

by anonymous
You can attach the file by editing your question.
by anonymous
The file you attached is a backup, not troubleshoot, and it does not contain the information I need. However, the thing I wanted to check was the IP address assigned to you mobile interface by the service provider, as there is a likelihood that you have an IP from private addresses pool dedicated to you. In this case, DDNS will simply not work.

Also, are you able to access your router via WAN with the same IP and remote HTTP access enabled?

Best regards,
by anonymous

we have a test network with the router RUT360 and a laptop.

The router has the LAN IP 192.168.230.1 and is only connected to the Internet via GSM (Vodafone), the WAN interface is not occupied.

Laptop IP 192.168.230.223 Gateway 192.168.230.1

my.noip.com/dynamic-dns gives us as xxxxxxx.ddns.net

returns the following temporary IP, see screenshot.

also from our normal network we can resolve the xxxxxxx.ddns.net with nslookup and also get back the same IP (from the Vodafone GSM connection).

but we cannot access the router in the test LAN via remote access...

If the basic setup works, we will access various Wallboxes in the network of the RUT360 router via the Internet using port forwarding.

Is there also a possibility to switch off the WLAN or at least to control it via firewall so that users of the WLAN cannot surf the Internet via the GSM connection and can only access the internal LAN?

Regards

Alexander

by anonymous

Could you connect to the router via CLI (In the WebUI navigate to System -> CLI) or SSH (via PuTTy), login using root as username and your router's password, and send me a screenshot of the output of the following command in a private message:

  • ifconfig

You can disable wireless interface in Network -> Wireless section in the web interface.

by anonymous

here is the current ifconfig !!

root@Teltonika-RUT360:~# ifconfig

br-lan    Link encap:Ethernet  HWaddr 00:1E:42:3A:8F:98

          inet addr:192.168.230.1  Bcast:192.168.230.255  Mask:255.255.255.0

          inet6 addr: fe80::21e:42ff:fe3a:8f98/64 Scope:Link

          inet6 addr: fd4d:e91d:20a4::1/60 Scope:Global

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:278250 errors:0 dropped:0 overruns:0 frame:0

          TX packets:351288 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000

          RX bytes:43925462 (41.8 MiB)  TX bytes:321893745 (306.9 MiB)

eth0      Link encap:Ethernet  HWaddr 00:1E:42:3A:8F:98

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:302167 errors:0 dropped:85 overruns:0 frame:0

          TX packets:428770 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000

          RX bytes:47586761 (45.3 MiB)  TX bytes:435093627 (414.9 MiB)

          Interrupt:5

eth1      Link encap:Ethernet  HWaddr 00:1E:42:3A:8F:99

          UP BROADCAST MULTICAST  MTU:1500  Metric:1

          RX packets:0 errors:0 dropped:0 overruns:0 frame:0

          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000

          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

          Interrupt:4

lo        Link encap:Local Loopback

          inet addr:127.0.0.1  Mask:255.0.0.0

          inet6 addr: ::1/128 Scope:Host

          UP LOOPBACK RUNNING  MTU:65536  Metric:1

          RX packets:16547 errors:0 dropped:0 overruns:0 frame:0

          TX packets:16547 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000

          RX bytes:1479145 (1.4 MiB)  TX bytes:1479145 (1.4 MiB)

wlan0     Link encap:Ethernet  HWaddr 00:1E:42:3A:8F:9A

          inet6 addr: fe80::21e:42ff:fe3a:8f9a/64 Scope:Link

          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1

          RX packets:14361 errors:0 dropped:0 overruns:0 frame:0

          TX packets:31057 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000

          RX bytes:3855934 (3.6 MiB)  TX bytes:12275768 (11.7 MiB)

wwan0     Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00

          inet addr:100.97.244.62  P-t-P:100.97.244.62  Mask:255.255.255.255

          inet6 addr: fe80::bd88:bcd1:1001:d73f/64 Scope:Link

          UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1500  Metric:1

          RX packets:345275 errors:0 dropped:0 overruns:0 frame:0

          TX packets:209065 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000

          RX bytes:412490174 (393.3 MiB)  TX bytes:33957713 (32.3 MiB)

root@Teltonika-RUT360:~#

by anonymous

I would like you to attach a troubleshoot file to your question. Please, replicate the issue, then access router's WebUI, go to System -> Administration > Troubleshoot section and download troubleshoot file from there.

 

by anonymous
by anonymous
good day,

have you already found a solution to the problem for me?

I had sent you the file

Regards

Alexander
by anonymous

The IPv4 address of wwan0 is 100.97.244.62 this is not a public address it is a carrier grade NAT one and isn't reachable from the external world. The IP address you have registered on no-ip.com (109.42.179.158) is the address of some router belonging the mobile provider.

You may have a solution if you enable IPv4+IPv6 in the PDP (go to Network->Interfaces->mob1s1a1 edit it with the pen set the PDP type there) there is no guarantee that 1) the provider will give you a public IPv6 address 2) ports are open on this address.