GUI
The OSDx Web GUI is a modern web-based management interface for OSDx routers. It provides a comprehensive set of tools for monitoring, configuring, diagnosing, and administering the router through an intuitive graphical interface accessible from any standard web browser.
The Web GUI is organized into the following sections:
Status – real-time monitoring and read-only information about the router.
Dashboard
ARP Table
DHCP Leases
NTP
Interfaces
DNS
IP Routes
Traffic
NAT
Configuration – allows admin users to modify router settings.
General Settings
NTP Service
Syslog
Static Routing
Traffic Policy
Services (SSH, Telnet, Web, DNS)
NAT
Users Administration
Interfaces
Diagnostics – network troubleshooting tools with real-time streaming output.
Ping
Traceroute
DNS Lookup
Traffic Monitor
Administration – system management tools for admin users.
Software Upgrade
Restart Device
Tech Support
Logging
Configuration
This is the syntax to set up service web:
set service web [ ... ]
To enable the web interface, you must configure at least one of the following protocols:
http, to enable the HTTP server (unencrypted, port 80 by default).https, to enable the HTTPS server (encrypted, port 443 by default).
The available options for http are:
host, to specify the bind address for the server.port, to specify the port for the server.
The available options for https are:
host, to specify the bind address for the server.port, to specify the port for the server.ssl-ciphers, to specify the allowed SSL cipher suites (OpenSSL cipher string format).ssl-protocol, to specify the allowed SSL/TLS protocol version.x509, to configure the X.509 certificate (required for HTTPS).
Troubleshooting
This section covers common issues and their solutions when using the OSDx Web GUI.
Connection issues
Cannot access the web interface
Verify the router IP address is correct and reachable (ping from your computer). Check that the web service is enabled. Ensure the correct protocol is being used (HTTPS on port 443 by default). Check for firewalls blocking the management port. Try HTTP on port 80 if HTTPS is not configured.
SSL/TLS certificate warning in browser
The router uses a self-signed certificate by default. Click “Advanced” > “Proceed to site” to continue. For production environments, install a valid SSL certificate via Configuration > Services > Web.
Page loads but shows blank or broken content
Clear browser cache (Ctrl+Shift+Delete). Disable interfering browser extensions. Ensure JavaScript is enabled. Try a different browser or incognito/private window.
Authentication issues
Login fails with “Invalid username or password”
Verify correct credentials and check Caps Lock. Ensure the user account exists on the system. Contact an administrator if you forgot your password.
Account is locked after failed login attempts
Wait for the auto-unlock timeout (configured in Users Administration > Unlock Time). An administrator can reset the account. If Unlock Time is 0, only an admin can unlock it manually.
Session expires unexpectedly
Check the Idle Timeout setting in Users Administration. A value of 0 disables the timeout. Increase the value if sessions expire too quickly.
“Insufficient privileges” error on a page
Your account role does not have access to this section. Configuration and Administration require the Admin role. Contact an administrator to upgrade your permissions.
Configuration issues
“Router configuration is not available at this moment”
Another session or process holds the configuration lock. Wait a few seconds and retry. If persistent, check if another admin is making changes. As a last resort, restart the web service from CLI.
Changes not taking effect after saving a form
You must click “Commit” in the sidebar to apply changes to the running configuration. Form save only stages the changes. After committing, click “Save” to persist changes across reboots.
Yellow warning icons on sidebar items
These indicate uncommitted (pending) configuration changes in that section. Click “Commit” to apply all pending changes, or “Discard” to revert them.
Lost connectivity after committing changes
If you changed the management IP or web service port, the browser can no longer reach the router at the old address. Connect to the new IP/port. If the change was a mistake, access the router via console (serial/SSH) and revert the configuration.