This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
wiki:systeme_mana:connection_credentials [2020/07/03 16:33] ghi |
wiki:systeme_mana:connection_credentials [2022/04/15 11:44] gat [root] |
||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== Web interface ====== | + | ====== Connection, login and credentials ====== |
- | ===== Connect to the web interface ===== | + | To log into the gateway, you will need to connect to it either through the network (through SSH) or sometimes through the debug interface (for [[wiki:ibts:connect_ibts|iBTS]] and [[wiki:istation:connect_istation|iStation]]). The remote SSH access is available on several network interfaces, depending on the gateway: either through its main Ethernet interface, or by the [[wiki:ibts:connect_ibts#local_connection|local Ethernet port for iBTS]], or the [[wiki:ifemtocell:connect_ifemto#wifi_ap_connection|iFemtoCell local Wifi Access Point]]. |
- | 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-”. | + | To access remotely the gateway, you will have to [[#addressing_the_gateway|discover it on the network]], either through its name or its IP address. |
+ | For all those access methods, you will need to choose a [[#user_accounts|user account]] with its corresponding [[#default_password|password]]. | ||
- | ^ Gateway model ^ URL template ^ | + | ===== Addressing the gateway ===== |
- | | **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/'' | | + | |
+ | 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-”. The case is not important, as the DNS is case-insensitive. This gives: | ||
+ | * ''klk-lpbs-**XXXXXX**'' for iBTS | ||
+ | * ''klk-wifc-**XXXXXX**'' for iFemtoCell | ||
+ | * ''klk-wiis-**XXXXXX**'' for iStation | ||
+ | * ''klk-fevo-**XXXXXX**'' for iFemtoCell-Evolution | ||
+ | * ''klk-zeth-**XXXXXX**'' for iZeptoCell Ethernet | ||
- | For example, for the Wirnet iBTS with 729ATf061ECD as CPU module ID, the hostname will be: **klk-lpbs-061ECD**. | + | For example, |
+ | * if a Wirnet iBTS has 729ATf**1234AB** as CPU module ID, the hostname will be: | ||
- | For the Wirnet iFemtoCell with 704BEc1234AB as board ID, the hostname will be: **klk-wifc-1234AB**. | + | ''klk-lpbs-**1234AB**'' |
+ | * if a Wirnet iFemtoCell has 704BEc**1234AB** as board ID, the hostname will be: | ||
- | 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).\\ | + | ''klk-wifc-**1234AB**'' |
+ | * if a Wirnet iZeptoCell Ethernet has 7076FF0078**1234AB** as gateway EUI, the hostname will be: | ||
+ | | ||
+ | ''klk-zeth-**1234AB**'' | ||
+ | | ||
+ | Please note that these names are resolvable when your gateway is connected to your network through its main Ethernet interface, and when your network has a standard way of linking DHCP leases to the local DNS zone. If you do not have this kind of standard network setup, you may have to rely on another way of addressing your gateway, .e.g. checking your DHCP server to get the gateway’s IP, or using a static IP configuration on the gateway. | ||
- | The default credentials are:\\ | + | ++++ Alternative naming and addressing | |
- | Login:''admin''\\ | + | |
- | Password:''pwd4admin'' | + | |
- | The web interface allows to: | + | If the above way of addressing your gateway does not work, you may rely (for firmware version 4.1 and above, or starting 4.0 for iFemtoCell) on autonomous addressing and local name resolution, sometimes called “Zeroconf” or “Bonjour”. This way of addressing it also necessary when the gateway is directly connected to a computer, i.e. not through a network switch or router. |
- | * Trigger upgrade/update on the gateway. | + | |
- | * Manage the network connectivity. | + | |
- | * Trigger actions on the gateway: Turn off, reboot, factory reset. | + | |
+ | This works in any application using standard name resolution techniques. The OS implements the specific standard, either [[https://en.wikipedia.org/wiki/Multicast_DNS|Multicast DNS]] or [[https://en.wikipedia.org/wiki/Link-Local_Multicast_Name_Resolution|LLMNR]], the former being more common on Linux and Mac OS, and the latter on Windows. | ||
- | <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> | + | The local name is then (replacing GGGG with the gateway type and XXXXXX with the serial): |
+ | * ''klk-**GGGG**-**XXXXXX**'' (for LLMNR) | ||
+ | * ''klk-**GGGG**-**XXXXXX**.local'' (for Multicast DNS) | ||
- | ===== Overview menu ===== | + | The name resolution is done on all the interfaces, i.e. backhaul Ethernet port, LOCAL Ethernet port (for iBTS), WiFi client and WiFi access point (for iFemtoCell). |
- | The overview menu provides the network connectivity status as well as the firmware version, the hardware serial number, and the system status. | + | Otherwise, you can also address the gateway by IP address. You can do so by looking at the leases given by your DHCP server. Please contact your local network administrator for more information. |
- | | **Wirnet iBTS Web_UI** | **Wirnet iFemtoCell Web_UI** | | + | For iBTS, in case you use the LOCAL Ethernet port, the default IP address of the gateway is 192.168.1.1. |
- | |{{:images:overview_webui_ibts.png?nolink&750|}}|{{:images:overview_webui_femto.png?nolink&760|}}| | + | |
- | ===== Administration menu ===== | + | ++++ |
+ | ===== Network shell access (SSH) ===== | ||
- | ==== Network configuration ==== | + | Start an SSH client (typically Putty on Windows) using the gateway’s name or IP address (the port is the standard 22). |
- | The network can be easily configured thanks to the web interface. | + | After getting a prompt: enter login/password (e.g. “''root'' / ''pdmk-**$serialno**''”). See [[#default_password|below for other login and credentials]]. In case of failure, request password to Kerlink support team. |
- | === Ethernet === | ||
- | Two parameters can be configured: | + | ===== User accounts ===== |
- | * If the Ethernet connection should be enabled/disabled. | + | |
- | * Which IPv4 configuration should be used. | + | |
- | * DHCP. | + | |
- | * Manual: Use a static IP. | + | |
- | * OFF: Will turn OFF the IPv4 configuration. You will be disconnected from the web interface. | + | |
- | <note important> | + | By default different accounts are available on the system: |
- | On 4.0.X firmwares, if there is a configuration file named ''lan.config'' in the ''/etc/network/connman/'' directory, this configuration file will prevail, and will prevent the web interface to modify the IPv4 configuration. \\ | + | * ''root'' with full access to any tools, files and devices. |
- | Once a manual configuration file is present, the only way to modify the configuration is: | + | * ''support'' with limited access. |
- | * by editing the file. | + | * ''usbuser'' with full access to any tools, files and devices. ''usbuser'' has no ''/home'' directory, it is dedicated to protecting the USB access. |
- | * by removing the file. <code> | + | * ''admin'' dedicated to web interface access, SMS commands and RESTAPI. |
- | rm /etc/network/connman/lan.config | + | |
- | /etc/init.d/connman restart | + | ===== Default password ===== |
+ | |||
+ | ==== root ==== | ||
+ | |||
+ | To prevent Web robots to attack the gateway with standard login/password such as ''root''/''root'', default password is built using the last 6 digits of the serial number, __CPU module S/N__ for Wirnet iBTS, __EUI__ for Wirnet iZeptoCell and __board ID__ for other Wirnet Gateways: ''pdmk-**$serialno**''. | ||
+ | |||
+ | For example, if the serial number of a CPU module is ''641ATe0507DD'', then the root password will be ''pdmk-0507DD'' (case sensitive). | ||
+ | |||
+ | This 6 digits number can also be retrieved in the hostname. It is displayed in the shell prompt: | ||
+ | <code> | ||
+ | klk-lpbs_0507DD login: root | ||
+ | Password: pdmk-0507DD | ||
</code> | </code> | ||
- | Starting with 4.1.2 firmware, modifications done in ''/etc/network/connman/*.config'' files are seen on web interface and modification done in web interface will be written in ''/etc/network/connman/*.config'' files. | ||
- | </note> | ||
- | === GSM === | + | ==== support ==== |
- | The GSM access can be configured in the web interface. | + | Default ''support'' password is: ''fd!15d4gd#''. |
- | A list of Mobile Network Code / Mobile Country Code can be found on [[http://mcc-mnc.com/|mcc-mnc.com]]. | ||
- | <note important> | + | ==== usbuser ==== |
- | * If a Roaming SIM card is inserted in the gateway, the **MCC/MNC** codes to configure should be those ones of the SIM and not those of the local operator. | + | |
- | * The **APN** to configure is the one of the SIM provider also, not the one of the local operator. | + | Default ''usbuser'' password is ''USBklkPassword''. |
+ | |||
+ | ==== admin ==== | ||
+ | |||
+ | Default ''admin'' password is ''pwd4admin''. | ||
+ | |||
+ | |||
+ | ===== How to change the passwords ===== | ||
+ | |||
+ | <note warning> | ||
+ | For security reasons, it is strongly recommended to change the default passwords. | ||
</note> | </note> | ||
- | === WiFi (Wirnet iFemtoCell only) === | + | Use the following command to change the password: |
+ | |||
+ | <code bash> | ||
+ | passwd <account> | ||
+ | </code> | ||
+ | |||
+ | <note important>The support account can't modify passwords.</note> | ||
+ | |||
+ | ===== File transfer (SFTP/SCP) ===== | ||
- | To connect to a Wi-Fi network: | + | Start an SFTP client (typically WinSCP on Windows) using the gateway’s name or IP address. |
- | * Choose your Wi-Fi access point in the list. | + | |
- | * Click on the access point name. | + | |
- | * For passphrase-protected WiFi, fill the passphrase in the newly opened window and click “Connect”. | + | |
- | * For WPS-enabled Access Point, or if your WiFi AP is open, just click “Connect”. | + | |
- | * The Wi-Fi network will appear connected in front of the network name. | + | |
- | {{:images:femto_wifimenu.png?nolink&400|}} | + | Enter a login and password (“''root'' / ''pdmk-**$serialno**''”). See [[#default_password|below for other login and credentials]]. In case of failure, request password to Kerlink support team. |
- | <note important>If this feature is enabled or disabled, don't forget to save the modification.</note> | + | ==== WinSCP on Windows ==== |
- | Starting with 4.1.6 firmware, you can also configure a not detected WiFi network (give SSID and passphrase). | + | To retrieve files easily with a graphical interface, WinSCP can be used: [[https://winscp.net/eng/index.php|Download link]].\\ |
- | ==== Update ==== | + | WinSCP acts as the Linux ''scp'' or ''sftp'' command, allowing to retrieve file with a copy/paste or drag'n'drop from a distant server to a computer.\\ |
- | Drag & drop your ''ipk'' file and click on //UPDATE GATEWAY//. \\ | + | Install WinSCP as a classic Windows program and run it. |
- | {{:images:update_webui.png?nolink&600|}} | + | |
- | A reboot is required to finalize the update, click on //REBOOT GATEWAY//.\\ | + | **<fc #ff0000>1</fc>** - **Configure** the protocol. Here, ''Secured File Transfer Protocol'' is required.\\ |
- | {{:images:update-reboot_webui.png?nolink&400|}} | + | **<fc #ff0000>2</fc>** - **Configure** the gateway's IP address.\\ |
+ | **<fc #ff0000>3</fc>** - **Enter** username : default is root.\\ | ||
+ | **<fc #ff0000>4</fc>** - **Enter** password : default is the following pattern ''pdmk-**XXXXXX**'' where XXXXXX are hexadecimal digits from the serial number. More informations [[#default_password|here]].\\ | ||
+ | **<fc #ff0000>5</fc>** - **Click** to login. | ||
- | ==== Gateway administration menu ==== | + | {{:images:winscp-login.png?| }} |
- | Several actions can be triggered from the Gateway tab: | + | ==== Send/Retrieve files ==== |
- | * Web interface password change. | + | **<fc #ff0000>1</fc>** - **Copy/paste or drag'n'drop** the file on computer's side window.\\ |
- | * Time settings change. | + | **<fc #ff0000>2</fc>** - A window will appear - **Click OK** - to confirm the transfer.\\ |
- | * Gateway shutdown (halt command). | + | **<fc #ff0000>3</fc>** - **Check** the folder where the file has been downloaded. It is now on the computer's folder.\\ |
- | * Gateway reboot. | + | |
- | * Gateway factory reset (a gateway reboot is required to initiate the factory reset). | + | |
+ | {{:images:winscp-getfile.png?| }} |