wiki:systeme_mana:webui
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
|
wiki:systeme_mana:webui [2019/09/25 15:36] ghi created |
wiki:systeme_mana:webui [2023/10/12 16:23] (current) ehe |
||
|---|---|---|---|
| Line 3: | Line 3: | ||
| ===== Connect to the web interface ===== | ===== Connect to the web interface ===== | ||
| - | To connect to the web interface, enter the IP address of your gateway into your browser’s URL bar (Make sure your computer is on the same local network).\\ | + | The easiest way to connect to your gateway is to address it by name. Wirnet gateways are named after their serial number, as described below, with XXXXXX replaced by the six hexadecimal digits from the serial number; these digits are taken from the last six hexadecimal digits of the “CPU module ID” for iBTS, and the last six hexadecimal digits of the “Board ID” for iFemtoCell and iStation. The prefix depends on the gateway type, and is of the form “klk-GGGG-”. |
| + | |||
| + | |||
| + | ^ Gateway model ^ URL template ^ | ||
| + | | **Wirnet iFemtoCell** | ''http://klk-wifc-XXXXXX/'' | | ||
| + | | **Wirnet iStation** | ''http://klk-wiis-XXXXXX/'' | | ||
| + | | **Wirnet iFemtoCell-evolution** | ''http://klk-fevo-XXXXXX/'' | | ||
| + | | **Wirnet iBTS** | ''http://klk-lpbs-XXXXXX/'' | | ||
| + | | **Wirnet iZeptoCell Ethernet** | ''http://klk-zeth-XXXXXX/'' | | ||
| + | | **Wirnet iZeptoCell Cellular** | ''http://klk-zcel-XXXXXX/'' | | ||
| + | |||
| + | |||
| + | For example, for the Wirnet iBTS with 729ATf061ECD as CPU module ID, the hostname will be: **klk-lpbs-061ECD**. | ||
| + | |||
| + | For the Wirnet iFemtoCell with 704BEc1234AB as board ID, the hostname will be: **klk-wifc-1234AB**. | ||
| + | |||
| + | |||
| + | It is also possible to enter the IP address of your gateway into your browser’s URL bar (Make sure your computer is on the same local network).\\ | ||
| + | |||
| The default credentials are:\\ | The default credentials are:\\ | ||
| Login:''admin''\\ | Login:''admin''\\ | ||
| Line 16: | Line 35: | ||
| <note important>When changing the IP of the gateway, or when switching from DHCP to fix IP and vice versa, connection to the web interface will be lost. This is __not__ a bug. As the IP changed, the IP used in the browser’s URL bar is no longer up-to-date. Update it to recover the web interface</note> | <note important>When changing the IP of the gateway, or when switching from DHCP to fix IP and vice versa, connection to the web interface will be lost. This is __not__ a bug. As the IP changed, the IP used in the browser’s URL bar is no longer up-to-date. Update it to recover the web interface</note> | ||
| + | ==== HTTPS Web Interface ==== | ||
| + | |||
| + | === Self-signed certificate procedure === | ||
| + | |||
| + | This procedure will enable HTTPS access to HTTP REST API and web user interface of the product but using self-signed certificate. It's an easy way but at least with 2 drawbacks: | ||
| + | * web navigators will ask for a security exception | ||
| + | * certificates are valid only for 365 days | ||
| + | |||
| + | **Procedure:** | ||
| + | - Activate the configuration with self-signed certificates: | ||
| + | * ''mv /etc/lighttpd.d/ssl-selfsigned.conf.disabled /etc/lighttpd.d/ssl-selfsigned.conf'' | ||
| + | - Apply this configuration : | ||
| + | * ''/etc/init.d/lighttpd restart'' | ||
| + | - Connect to the web interface: https://your_product_name/ | ||
| + | * ex: ''https://klk-wifc-020003/'' | ||
| + | |||
| + | === Full chained certificate support === | ||
| + | |||
| + | The integrated lighttpd is able to support full chained certificate but procedure will depend on the certificate authority used. | ||
| ===== Overview menu ===== | ===== Overview menu ===== | ||
| Line 28: | Line 66: | ||
| ==== Network configuration ==== | ==== Network configuration ==== | ||
| - | The network can be easily configured thanks to the web interface. | + | The network can be easily configured thanks to the web interface.\\ |
| + | After cellular configuration has been set, a reboot of the gateway is required to take into account the new APN configuration. | ||
| === Ethernet === | === Ethernet === | ||
| Line 83: | Line 122: | ||
| A reboot is required to finalize the update, click on //REBOOT GATEWAY//.\\ | A reboot is required to finalize the update, click on //REBOOT GATEWAY//.\\ | ||
| {{:images:update-reboot_webui.png?nolink&400|}} | {{:images:update-reboot_webui.png?nolink&400|}} | ||
| + | |||
| ==== Gateway administration menu ==== | ==== Gateway administration menu ==== | ||
| - | Several actions can be triggered from the Gateway tab: | + | === Get logs from gateway === |
| + | |||
| + | Logs can be retrieved from the web interface in Administration -> Gateway | ||
| + | |||
| + | - Click on **START LOG COLLECTION** button to create the log archive \\ {{:images:get_logs1.jpg?nolink&400|}} | ||
| + | - Once created, the button **GET LOG FILE** turns active. Click on it to download the log archive \\ {{:images:get_logs2.jpg?nolink&400|}} | ||
| + | |||
| + | The logs archive is downloaded on your computer and then deleted from the gateway. | ||
| + | |||
| + | |||
| + | === Other administration possibility === | ||
| + | |||
| + | Some other actions can be triggered from the Gateway tab: | ||
| * Web interface password change. | * Web interface password change. | ||
wiki/systeme_mana/webui.1569418564.txt.gz · Last modified: 2019/09/25 15:36 by ghi
