Wirnet iFemtoCell is named after its serial number, as described below, with XXXXXX replaced by the six hexadecimal digits from the serial number, which are also the last six hexadecimal digits of the “Board ID”. The case is not important, as the DNS is case-insensitive.

• klk-wifc-XXXXXX

For example, if an iFemtoCell has 704BEc1234AB as board ID, the host name will be:

• klk-wifc-1234AB

Wirnet iFemtocell has no default IP address, the gateway needs to be connected to a network using DHCP.

• Most of the time, the DHCP is associated to a DNS server. In that case, the Wirnet iFemtoCell can be accessed by its hostname.
• If not, the IP address must be used. Contact your network administrator, he/she will be able to retrieve it.

If the gateway is connected to a network using DHCP, then the behavior is the same as in previous firmware

If not (e.g if a Wirnet iFemtoCell is directly connected to a computer), the Wirnet iFemtoCell can be simply discovered on the network through local name resolution. This means that it can be addressed by name instead of by IP address, in any application using standard name resolution techniques. The OS implements the specific standard, either Multicast DNS (RFC 6762) or LLMNR (RFC 4795), the former being more common on Linux and Mac OS, and the latter on Windows.

local name:

• klk-wifc-XXXXXX (for LLMNR)
• klk-wifc-XXXXXX.local (for Multicast DNS)

The name resolution is done on all the interfaces, i.e. Ethernet, WiFi client, and WiFi access point. The latter interface also offers the shortened version klk-wifc

login: root

To prevent Web robots from attacking the gateway with standard login/password “root/root”, default password is built using the last 6 characters of the board ID : pdmk-$serialno.

For example, if an iFemtoCell has 704BEc1234AB as board ID, then the root password will be pdmk-1234AB (case sensitive).

This last 6 characters can also be retrieved within the host name displayed in the shell prompt:
klk-wifc_1234AB login: root
Password: pdmk-1234AB

1. Start an ssh client (TeraTerm or Putty on Windows) using:
   • IP address, local name or host name
   • port 22
2. Connect with the following information:
   • login: root
   • password: pdmk-$serialno

The first time the gateway is used, SSH connection must be used, WiFi access point is not available.

SSH and WiFi can be used.
A WiFi access point is available at boot time on each Wirnet iFemtoCell for one hour, broadcasting an SSID named after its serial number (klk-wifc-XXXXXX). It can only be used to access the Wirnet iFemtoCell itself, as it does not route traffic to anywhere and does not serve as an Internet wireless access point.

The passphrase to connect to this WiFi network is the Ethernet MAC address (it can be found on the Wirnet iFemtoCell label), in uppercase, without spaces between the digits, e.g. 7076FFYYYYYY.

Note that this interface does not come with a DHCP server, it is only meant to be used for the Wirnet iFemtoCell configuration. Your computer may take some time to get the “connected” status, and the interface will have a “limited connectivity”, which is normal.

1. Download the ftdi drivers for the debug probe
2. Install the drivers

On Linux, everything should work out of the box. The serial port will be located in /dev/ttyUSB*.

If it didn't work

$ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 039: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC
Bus 001 Device 005: ID 0461:0010 Primax Electronics, Ltd HP PR1101U / Primax PMX-KPR1101U Keyboard
Bus 001 Device 045: ID 18d1:4ee7 Google Inc. 
Bus 001 Device 003: ID 0424:2512 Standard Microsystems Corp. USB 2.0 Hub
Bus 001 Device 002: ID 045e:07fd Microsoft Corp. Nano Transceiver 1.1

$ lsmod | grep ftdi
ftdi_sio               53248  1
usbserial              53248  3 ftdi_sio

# Added on xx/yy/zzzz for Kerlink debug probe by foobar
# For FTDI FT232 & FT245 USB devices with Vendor ID = 0x0403, Product ID = 0x6001
ATTR{idProduct}=="6001", ATTR{idVendor}=="0403", RUN+="/sbin/modprobe ftdi_sio product=0x6001 vendor=0x0403"

$ ls -l /dev/debug_probe
lrwxrwxrwx 1 root root 15 04-06 16:05 /dev/debug_probe -> ttyUSB0

1. Open a serial terminal (HyperTerminal, PuTTY, GNU screen, minicom, etc.)
2. Select the serial port created by the FTDI driver (usually: COM3 on Windows, /dev/ttyUSB0 on Linux)
3. Apply the following parameters to use your serial connection:
   • baud rate : 115200
   • data length : 8
   • parity : none
   • stop bit : 1
   • flow control : none
4. Connect with the prompt :
   • login: root
   • password: pdmk-$serialno