Wirnet™ i-series

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== Wirnet™ iFemtoCell: Connect to the gateway ======

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 704BEc**1234AB** as board ID, the host name will be:

  * ''klk-wifc-**1234AB**''

===== Ethernet or WiFi =====

==== Before firmware 3.3.3 ====

The first time the gateway is used, an Ethernet cable must be used.

==== From firmware 3.3.3 ====

Ethernet 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. ''7076FF**YYYYYY**''.

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.

===== Discovery =====

==== Before firmware 3.3.3 ====

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.

==== From firmware 3.3.3 ====
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 ([[https://tools.ietf.org/html/rfc6762|RFC 6762]]) or LLMNR ([[https://tools.ietf.org/html/rfc4795|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''

===== Wirnet iFemtoCell login/password =====
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 704BEc**1234AB** 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**''\\

<note important>For security reasons, it is strongly recommended to change the default password.</note>

===== SSH connection =====

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

===== Debug probe =====

<note warning>
The Wirnet iFemtocell has a proprietary serial debug interface available only inside the enclosure.// 
The Wirnet iFemtocell is not warranted by KERLINK in case the enclosure is opened by customer.// 
Therefore, debug interface is only for specific customer needs, it is intended to be used by authorized and qualified personnel only.
</note>

<note important>
When the switch is positioned on the left, the CPU is in reset mode.

When the switch is positioned again to the right, the reset is released and the Wirnet iFemtocell starts booting.

  * Reference document: [[resources_ifemto:resources#wirnet_ifemtocell_installation_and_maintenance|Wirnet iFemtoCell Installation and Maintenance guide]] .
</note>

==== Windows installation ====

  - Download the [[http://www.ftdichip.com/Drivers/VCP.htm|ftdi drivers]] for the debug probe 
  - Install the drivers

==== Linux installation ====

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

++++ If it didn't work |

You may need to tell the Kernel to load the proper [[http://www.ftdichip.com/Support/Documents/AppNotes/AN_220_FTDI_Drivers_Installation_Guide_for_Linux.pdf|FTDI driver]] when the debug probe is plugged.

To do so, list the USB devices and see the product and vendor IDs:

<code text>
$ 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
</code>

Here the debug probe is located on the 1st bus, device ''039''. The device should be automatically recognized, provided you have the FTDI kernel module loaded. To check this, you can run the following command:

<code>
$ lsmod | grep ftdi
ftdi_sio               53248  1
usbserial              53248  3 ftdi_sio
</code>

Next, create a udev rule matching this, and place it in a file called ''/etc/udev/rules.d/99-usbftdi.rules'' (for example):

<code>
# 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"
</code>

Be sure to replace the product/vendor IDs if they need to be changed.
This will have the FTDI Kernel module loaded when the debug probe is plugged.

Next, reload the device tree: ''udevadm control --reload-rules && udevadm trigger'' (run as root).

If you will, you could rename the device in ''/dev''. To do so, add '', SYMLINK+="debug_probe"'' to your udev rule.

Here's the result:

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

++++

{{ :images:hw_probe_wiring.jpg|}}

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

User Tools

Site Tools

Page Tools
