How does remote access via web.direct link work?

Remote access to the web interface of a router and its terminal devices can be done via web.direct. The respective web.direct link allows users to log in to the web interface of a router (WebUI) or an end device from any location to make settings, perform diagnostics, or carry out other administrative tasks. Further information on the specifications of the web.direct link can be found here

Contents:
Requirements
Perform remote access via web.direct link
web.direct Security
 

Requirements

To have access to web.direct, you need the appropriate permission, for example 'mdex fixed.IP+' or in SIMPro the option DevicePro with the corresponding web.direct licence.

  • The web.direct link must be activated, for more details see here.
  • For remote access to a cellular router, it is necessary that "HTTPS Remote Access" is activated in the router, see here.
  • For remote access to a connected end device, an appropriate port forwarding of the respective TCP port to the end device must be set up in the cellular router. 

 

Perform remote access via web.direct link

In mCOP 2.0, or SIMPro -> DevicePro, the desired SIM device usually already has web.direct links preset in the tile web.direct, such as "Default (HTTP)" and "Router" (HTTPS Port 4444). To use these web.direct links, the web.direct function must be activated.

The respective web.direct links can be individually adjusted by clicking on the 'Edit' icon, see here.

By clicking on 'Call' , the web.direct link opens to access the web interface of the respective device:

The URL of the web.direct link can also be used directly in a web browser without being logged into the portal. You can copy the URL of the web.direct link to the clipboard by clicking on the 'Copy' icon.

 

web.direct Security

For security reasons, authentication is enabled by default for all web.direct links. An overview of the available web.direct authentication methods can be found here. Below are some examples of using web.direct links with the respective authentication methods. 

Example 1: Authentication "Portal Account (OTP required)

With the authentication method 'Portal Account (OTP required)', web.direct access upon clicking 'Call' goes directly to the device's web server without additional authentication. 

 

Only when using the URL of the web.direct link outside the portal does an authentication window first open. The user must log in here with their portal login data (username and password) as well as two-factor authentication before the web.direct link works and the device's web server is accessible. Further informations about the authentication methods can be found here.

 

Example 2: Authentication "Link Password"

For the "Link Password" methods, the respective link password must always be entered for authentication when calling the web.direct link, regardless of whether you are logged into the portal or want to use the URL of the web.direct link outside the portal. Before calling the web.direct link, the password can be copied to the clipboard using the copy icon: 

In the subsequent authentication window, this link password can then simply be pasted by clicking "right mouse button -> Paste". Then click the 'Log in' button:

If the SIM card is online and reachable, the web interface of the cellular router or the end device will now open. A cookie is stored on the computer so that re-authentication is only required if the cookie has expired or has been deleted.

 

 

Was this article helpful?
0 out of 0 found this helpful

Articles in this section