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
810 views 2 comments
by anonymous

Hi,
I'm tryng to setup a LAN device access as descibed in https://wiki.teltonika.lt/view/How_to_configure_remote_access_to_LAN_devices_in_RMS%3F that report this example:

but in my UI mask there isn't any field for the external port, so I get an error related to the source port

I'm using a RUT950 with firmware version RUT9XX_R_00.06.04
Thanks for the support.
Gianluigi

1 Answer

+1 vote
by anonymous
Hello,

Thank you for informing us, we already forwarded this information to RND. Soon this issue should be resolved, we will inform you.
by anonymous
Hello,

This issue if resolved. Make sure device is using latest available firmware version.
by anonymous

Thanks for the update.
I'm now able to connect to a rasperry device connected to the router LAN. Its running openhab that is listenting on port 8080.

I instead have a strange problem with another LAN device (lorank) listening on port 80.
This is the device acces configuration related to RUT950 with firmware version RUT9XX_R_00.06.04

I'm able to connect to the lorank login page

but when I try to login, it always show me the same login page as if the cedential were wrong.
I tested the credential inserting them when the lorank is connected to home LAN, and in that case all works fine.

Some additional aspect:
- Even if I didn't select the option "Use custom basic-auth" when I create the device access rule, this option is always activated.
What does it mean and why it's always acitvated ?
-  In the "https://wiki.teltonika.lt/view/How_to_configure_remote_access_to_LAN_devices_in_RMS%3F" page, the values in the last rows are probably inverted

Gianluigi

P.S.
I discovered later that the lorank login page is managed by BoneScript that is a node.js library, it could be the problem is related to this component..