Frequently Asked Questions

Most LigoWave devices have the dual firmware image feature.

If a device fails to perform a firmware boot from an active partition 3 times, it will set the second partition as the active one and will boot from the backup partition.

If a device fails to perform a firmware boot from both partitions 3 times, it will enter recovery mode. Then it will wait 5 minutes for a new firmware image via TFTP.

If no image is supplied to the device, it will try to boot images from both partitions again.

The following devices support the dual firmware image feature:

– LigoPTP RapidFire
– LigoDLB
– LigoDLB PRO
– LigoDLB ac
– Infinity

The following devices do not support this feature:

– NFT 2AC
– LigoDLB 5-15ac
– LigoDLB 5-20ac
– LigoDLB 5-90ac
– LigoDLB 5ac
– LigoDLB 6-15ac
– LigoDLB 6-20ac
– LigoDLB 6-90ac
– LigoDLB 6ac

Follow these steps to check the active and backup firmware versions on the devices:

Step 1. Log in into the device via SSH.
Step 2. Run the following command: /usr/share/lua/system_info.lua | grep fw

Information about how to check active firmware or how to activate backup firmware on the RapidFire device can be found here:
https://www.ligowave.com/wiki/faq/ligoptp-rapidfire-active-and-backup-firmwares/

LigoDLB ac series can be powered with 100Mbps or 1000Mbps speed 24V passive PoE adapter.
LigoDLB n series can be powered with 100Mbps or 1000Mbps speed 24V passive PoE adapter.

Missed beacon limit – This advanced parameter controls CPE side. When defined count of beacons is lost, CPE understands that AP is gone and simply disconnects. In a very noisy areas higher value of missed beacon keeps wireless session longer and ensures better stability.

• Parameter is visible when wireless operating mode is Station(WDS/iPoll 3) or Station(ARPNAT).
• Parameter values: 1-60, default 2

The main iPoll 3 proprietary protocol and the standard 802.11n protocol on LigoDLB devices with firmware version 7.53 or later are compatible with the new LigoDLB ac series of protocols—iPoll 3 and 802.11ac.

Introduction

There may be cases when it is beneficial or even necessary to update the firmware on a device without using the web browser. It is possible to update the firmware by using SSH and the fwupdate command. This article serves as a walk-through for getting the image onto the device and then flashing it.

Getting the image onto the device

The first step of flashing an image in the shell is getting the firmware image onto the device. There are two easy ways to do this: using SFTP to upload the image onto the device, or using wget from the device to download the image from an external source.

Instructions for Windows users

Step 1. Run WinSCP. Fill out the following fields:

Host name – device IP address (default 192.168.2.66)
Username – admin
Password – device login password (default: admin01)
Press Login to initiate an SSH connection to the device.

Step 2. In the next window, go to the /tmp directory. Then copy the PTP.MA-1.v7.51.13476.img file to the /tmp directory.

Step 3. Run PuTTY. In the Host Name field, type the device’s IP address and press Open.

Step 4. Type in the username and the password in the next window.

Username – admin
Password – device’s password (default: admin01)

Step 5. Navigate to the /tmp directory.

cd /tmp

Step 6. Rename the previously uploaded file to fwupdate.bin.

mv PTP.MA-1.v7.51.13476.img fwupdate.bin

Step 7. Type the command fwupdate –m to start the firmware upgrade.

fwupdate -m

Step 8. If PuTTY closes automatically, this confirms the successful start of the upgrade.

Step 9. Once the firmware upgrade is complete, the device should respond to a ping using the configured IP address.

Instructions for Linux users

Download the latest firmware and open the Terminal.

Step 1. Rename the downloaded firmware to fwupdate.bin.

mv PTP.MA-1.v7.51.13476.img fwupdate.bin

Step 2. Copy the firmware image to the device’s /tmp directory.

scp /home/fwupdate.bin [email protected]:/tmp

Step 3. Log onto the device using SSH.

ssh [email protected]

Username – admin

Password – device’s password (default: admin01)

Step 4. Type in the command fwupdate –m to start the firmware upgrade.

fwupdate -m

Step 5. Once the firmware upgrade is complete, the device should respond to a ping using the configured IP address.

LigoPTP RapidFire supports packet sizes of up to 2184 bytes without any external configuration.

The following steps should be performed to identify the maximum packet size that can be sent between devices:

Equipment for testing:

Linux PC 1 and Linux PC 2 (Cisco switches can also be used instead of PCs).

Once the wireless link is connected, make sure that the ping works by sending small packets using the following command:

ping remote_device_ip

If a ping response is received, change the Linux PC Ethernet interface MTU size with the following command:

ifconfig eth0 mtu 3500

In the provided example, the network interface is called eth0. However, it can be named eth1 or any similar name on other machines.

Once the MTU value is changed on both Linux PCs, run the ping command with the attributes -M do to send the packet without any fragmentation because the ping function performs fragmentation by default.

ping remote_device_ip -s 3500 -M do

-s indicates the packet size. The example is for 3,500 bytes.

When using a remote Linux PC, you can run the tcpdump tool. See the screenshot below:

How to reset the RapidFire unit to its default settings via LAN

Follow these steps to run the LigoWave Reset Tool and reset the device to its default factory settings:

Linux OS

The package should be installed by running the following command (Ubuntu/Debian version):

   sudo apt-get install sun-java6-jre

Afterwards, click the right mouse button on the Reset Tool and select Open with Sun Java 6 Runtime or via the following command line:

sudo java -jar /home/reset-tool.ligowave.en.v1.2.55051.20170126.1017.jar

Once the Reset Tool starts, follow the steps as shown in the example with Windows 7.

Windows 7 OS

Provided bellow is an example on how to run the Reset Tool with an elevated access command prompt.

Download the Reset Tool locally to your computer from this link: reset-tool.ligowave.en.v1.2.55051.20170126.1017.jar

Create the Reset Tool folder on drive C:

Copy the Reset Tool executable into this folder:

Click on Start, select All Programs and then choose Accessories:

Click the right mouse button on Command Prompt to call out the context menu and choose Run as administrator:

Command Prompt should now be running with administrator privileges:

Type in the command cd c:\Reset Tool and hit the Enter key:

Type in the command java -jar reset-tool.ligowave.en.v1.2.52133.20150721.1615.jar –V:

If done successfully, the Reset Tool should launch with administrator privileges enabled:

Steps to reset the device to its default settings:

Step 1. Once the Reset Tool starts, reboot the device (physically turn off and turn on the device) and wait until it automatically appears in the list.

Select the device and press Reset:

Step 2. For a full device reset, the 4 last symbols of the serial number have to be entered.

Step 3. The serial number can be found on the device’s casing, the box, using the device discovery, and in the UI status menu.

Step 4. Status: Resetting indicates that the RapidFire device is being reset to the default settings:

Step 5. Status: Booting device indicates that the RapidFire device has been successfully reset to the default factory settings and that it is starting to boot:

Step 6. When the status Reset complete appears, you will be able to log into device:

N connector polarizations

It is important not to mix up V and H polarity when the external MiMo antenna is connected to the LigoPTP RapidFire device. The H polarity port is on the ETH2 side and the V polarity port is on the ETH1 PoE IN port side. Once the RF cable is connected, both N connectors have to be well isolated from water.

Active and Backup firmware

LigoPTP units have factory-installed default dual-boot firmware. With each new firmware upgrade, the backup firmware is overwritten.

If the current firmware is experiencing problems, click on Activate to enable the backup firmware. The Backup firmware will be activated after a reboot.

Antenna alignment using sound

The Antenna Alignment tool measures signal quality between the Master and Slave. To achieve the best results during antenna alignment, turn off all wireless networking equipment within range of the device, except for the device(s) with which you are trying to align the antenna. Watch the perpetually-updated signal strength as you adjust the antenna.

Start/Stop – press this button to start or to stop antenna alignment.
Sound – once this option is enabled, a sound (beeping) will be produced during the aligning process, if the browser allows this. The device itself does not have an integrated speaker. The sound will play through the speakers of the PC or any other device that is running the Antenna Alignment tool.
Averaging – if this option is enabled, the graph will display the average signal strength of both vertical and horizontal polarities.

Site survey

The Site Survey tool provides an overview of the wireless networks found within a local geographic area. With this tool, an administrator can scan for active wireless devices that are operating in Master or AP mode, check their operating protocol, frequency, bandwidth, and see the signal/noise levels, either listed in a table or represented by a graph.
To perform a site survey, click Start:

Graph Data – choose which site data to display in the graphs:

• only local site
• only remote site
• combine both sites

The Graph Data option is hidden, if the Master device receives no data from the Slave unit or if the unit is operating as a Slave device.

Below is an illustration of an Only local site graph.

The following illustration shows a site survey graph with combined Master and Slave device results:

The illustration below shows a list of scanned wireless networks:

Spectrum analyzer

The Spectrum Analyzer tool provides detailed information about the signal levels of each LigoPTP unit antenna on every available frequency. This allows the administrator to choose the best available frequency/channel for unit operation. The frequency list depends on the country that the unit is operating in and the selected channel width. The Spectrum Analyzer also shows the noise levels in the available spectrum.

Click Start to perform the test:

The Spectrum Analyzer only runs on local devices. The spectrum graph looks as follows:

Ethernet port speed and PoE passthrough configuration

ETH port speed – select the ETH1 and/or ETH2 ports speeds:

• Auto
• 100Mbps Full Duplex
• 100Mbps Half Duplex
• 10Mbps Full Duplex
• 10Mbps Half Duplex

PoE passthrough to ETH2 – if enabled, the ETH2 interface becomes a 48V PoE source device.

LED configuration

LED – choose LED operation mode:
Always off – LED indication will be permanently disabled.
Always on – LED indication will be permanently enabled.
Auto off – LED will be disabled upon timeout.

Ethernet traffic control

Configure the Ethernet traffic control on both Ethernet ports:

Enable speed limit – slide to enable speed limitation on both Ethernet ports.
Incoming speed – use the slider or specify manually the maximum speed in megabits per second for incoming traffic. Traffic is shared among ETH1 and ETH2 ports, e.g. 120Mbps.

QoS configuration

LigoPTP RapidFire 5 supports Layer 2 (802.1p) and Layer 3 (DSCP) QoS. With L2 QoS, data are prioritized based on VLANs, while with L3, data are prioritized based on IP addresses. Both types of QoS can run together or independently and traffic can be mapped onto 4 different queues for each type by applying strict or WRR policies. By having QoS in the link, users can prioritize mission-critical data and real time data that requires more capacity and a higher PPS rate. Maximum capacity for each queue is calculated dynamically according to the wireless link.

QoS policy – choose the prioritization method: Strict or WRR.

Strict – if this scheduling policy is enabled, higher priority data are transmitted before transmitting any data from the lower priority queues. The value of this type of scheduling is that high priority packets are always handled before low priority packets, which is required for voice or video data.

WRR – if this scheduling policy is enabled, a set number of data packets is transmitted from each queue based on the round-robin algorithm. The higher the queue priority, the more packets are transmitted as the algorithm cycles through the queues in turn. This policy guarantees that every queue receives some attention from the port for transmitting packets.

QoS mapping precedence – select the QoS mapping priority: either L2 (802.1p) or L3 (DSCP). This option is available only if both types of QoS are enabled.

802.1p settings – enable L2 QoS and specify the priority queue [0–4] for each CoS value (0-7):

DSCP settings – enable L3 QoS and specify the priority queue [0–4] for each DSCP value (0-63):

Link quality is a connection quality index that is expressed in percentages. It shows how effectively the system is running at the current time compared to the maximum theoretical system capacity. The link quality calculation also includes the percentages of transmitted packet retries and received packet drop. Link quality shows how many packets underwent transmission retries at the current data rate.

Public status page – enable or disable the permission for users, who are not logged-in, to view the status page.

There are a few simple steps for testing device configurations indoors or at very short distances between radios.

To test devices with N connectors, use RF cables with 50–60dB attenuators.

If the devices have integrated antennas, indoor tests should not be performed due to bad results from signal reflections. When choosing to test indoors, minimize possible damage by following these guidelines:

Set Tx power to 0.

Have both units facing the ceiling or ground. Check the signal levels which should be around -50dBm.

The recommended signal level range for optimum performance is from –35dBm to –55dBm. Links may also work with lower signal level modulations ranging from –56dbm to –85dBm.

The troubleshooting file contains valuable information about the device’s configuration, log files, command outputs, and other data. The device automatically gathers troubleshooting information rather than requiring the user to gather each piece of information manually. This is helpful when submitting problems to the support team. Follow these steps to download the troubleshooting file via the GUI:

Step 1. Login to the LigoPTP RapidFire 5 GUI via a web browser:

Step 2. To download the troubleshooting file, navigate to the Maintenance tab, click on Troubleshooting in the side-bar menu, and then click Download:

During the gathering of statistical data, the wireless link will be interrupted for a short period of time because the radio will be performing a site survey in the background.

Step 3. The troubleshooting file has been successfully downloaded to your computer:

The firmware upgrade is compatible with all of the configuration settings. When the device is upgraded to a newer version or the same version build, all of the system’s configuration are preserved after the upgrade.

Follow these steps to upgrade your device’s firmware:

Step 1. Click Update and select the proper firmware image in the Firmware Update pop-up window:

Step 2. Click Browse and select a file to upload:

Step 3. Once the firmware image is successfully uploaded, the Firmware Update window will display a table showing LigoPTP RapidFire 5 devices. It will now be possible to choose devices to upgrade. Both linked devices (i.e. Master and Slave) will be upgraded by default.

 Step 4. Click on Update to upgrade the device using the uploaded image. Both devices will be upgraded automatically. The Slave device is upgraded first.

The default IP address is 192.168.2.66 with a subnet mask of 255.255.255.0.

The LigoPTP unit’s remote wireless management interface is accessible only through HTTPS and SSH via IP: 192.168.111.1.

How to back up the configuration from Master and Slave devices

The LigoPTP RapidFire Master device provides an option to back up the configurations of both devices onto one file.

Click Backup to download the configuration files of the entire LigoPTP link. The downloaded file will contain two configurations: the Master’s and the Slave’s.

Read the full article on how to restore devices from a network configuration backup file here: Slave and Master Device Configuration from Network Configuration Backup.

How to reset the LigoPTP RapidFire device using the reset button?

LigoPTP RapidFire devices have a reset button next to the Ethernet port. To reset the device, press and hold the reset button for 6 seconds until all of the LED lights turn on and begin blinking. Then release the button.

Auto data rate

Auto data rate algorithm – a data rate is automatically selected by the mechanism that evaluates the current performance of the device based on the current signal level, data packet retry rate, and other parameters. The data rate fallback drops the MCS step by step until the data can be transferred. The auto data rate algorithm is not configurable and is always enabled.

This is a list of device bit rates:

How to discover all LigoPTP RapidFire devices in a network?

Device discovery – a feature that allows the LigoPTP unit to discover other devices within reach of a single multicast packet. Bonjour provides a simpler way of discovering devices in a local area network. If the device discovery feature is enabled, the unit will periodically multicast Bonjour service records using the SSDP protocol to the entire local network so as to notify of its presence. This allows the user to find devices without any external tools or programs.

Follow these steps to discover LigoPTP devices within the network:

Step 1.1. Enable the network discovery function on your Windows PC. Open Windows Explorer, enter the Network section and follow the automatic pop-up at the top of the screen:

Step 1.2. To enable, click Yes, turn on network discovery and file sharing for all public networks.

Users can also enable the network discovery function manually:

Step 2.1. go to Control Panel and click Choose homegroup and sharing options under the Network and Internet section:

Step 2.2. Proceed to Change advanced sharing settings:

Step 2.3. Select Turn on network discovery:

Step 3. All of the available devices should appear in the Network devices section. The scanned devices should now be ready for management:

Right click on the device to open the context menu and select Properties to check the IP address and serial number. Users can also reach the device’s web page directly:

MAX OS X

Step 1. Enable the Bonjour service in the Safari browser under Preferences → Advanced (the location depends on the version of the operating system).

Step 2. Go to Bookmarks → Bonjour → Web-pages.

Step 3. Click on the name of the radio (look for a friendly device name).

Public status page – enable or disable the permission for users, who are not logged in, to view the status page.

Configure the additional management interface for easy access to the device’s web management interface after newly installing or rebooting a LigoPTP unit. Once the unit is turned on, it will switch to the remote wireless management mode.

SSID – assign the SSID for remote wireless management interface (default: LigoPTP-mng-[last 3 MAC octets]).
Security – choose the security options for remote wireless management access.
Passphrase – specify the passphrase for WPA/WPA2 personal security.
Activity interval – indicate the period of remote wireless management interface activity. If no user logs on to the LigoPTP web management interface for a specified amount of time, the remote wireless access mode will be automatically switched off (default: 5 minutes).

Channel width – select the width of the operating radio channel. LigoPTP RapidFire supports 5, 10, 20, 40 and 80MHz channel widths.

Connection via LAN cable

Follow these steps to access the LigoPTP RapidFire device for the first time:

Step 1. Configure the PC LAN card using a static IP address on the 192.168.2.0 subnet (e.g. 192.168.2.10 with mask 255.255.255.0).

Step 2. Open a web browser and enter the default IP address of the AP device—192.168.2.66:

Step 3. Once the login page is loaded, agree to the LigoPTP disclaimer. Regulatory domain settings may differ depending on the selected operating country. Users are not allowed to select radio channels and RF output power values other than the permitted values for their respective country and regulatory domain:

Connection via the wireless management interface

Configure the additional management interface for easy access to the device’s web management interface after newly installing or rebooting a LigoPTP unit. Once the unit is turned on, it will switch to the remote wireless management mode.

How to configure the SSID failover

The SSID failover option is used to add a backup access point SSID to the station.

The SSID failover section is only available in station mode (iPoll and 802.11n) in firmware version 7.00 or later.

Go to Configuration → Wireless and put a check mark next to Enable SSID failover in the SSID failover section.

Use the Scan function to search for nearby devices. Once the scan is complete, select the relevant device from the drop-down list below the SSID field, and, if necessary, select the security protocol and enter the passphrase of the selected device.

How SSID failover operates:

• After reboot, the station always attempts to connect to the primary SSID first and then to the secondary one.
• While in operation, the station connects to the secondary SSID when the connection with the primary one is lost.
• If the Return to primary SSID function is turned off, the station will keep working on the secondary SSID.
• If the Return to primary SSID function is turned on with a timer (Failover timeout, default—720 minutes), the station will attempt to connect to the primary SSID after the set time.
• If the station is operating on the secondary SSID and loses connection with it, it will try to reconnect to the primary and then to the secondary SSID (e.g. after reboot).

Sensitivity and noise balance

The Sensitivity/Noise balance slider lets users balance between signal sensitivity and noise immunity.

If the sensitivity and noise balance value is decreased, the device becomes more sensitive, thus allowing it to detect lower signals. However, this also means that it will experience more interference.

If this value is increased, the level of interference and noise is reduced, but this also means that the device will only be able to scan the main signal.

The value should be set to approx. 50–60 so as to not lose the connection with the main signal.

Block Acknowledgements (BLOCK ACK)
Rather than sending an individual acknowledgement following each data frame, 802.11n introduces a technique of confirming a burst of up to 64 frames using a single Block ACK (BA) frame. Block ACK even contains a bitmap to selectively acknowledge individual frames of a burst (comparable to selective TCP acknowledgements). The use of combined acknowledgments can be requested by sending a Block ACK Request (BAR). Block ACK options are negotiated and confirmed using Action frames defined in 802.11e (WLAN QoS).

Usage: AutoBA should be enabled by default. The only time when AutoBA should be disabled is when a decrease in performance and in stability with smart phones is identified.

Quality of Service (QoS) in detail

Firmware version x.95 and later have granted the Deliberant APC series of devices QoS functionality for the iPoll proprietary protocol. It is a major improvement in the quality control applicable to the different kinds of traffic.

QoS allows users to adjust the distribution of the 4 different types of traffic.  The process places the data into 4 queues that are then processed based on their priority levels. The prioritization policy is strict, which means that higher-priority data is sent first and lower priority is sent afterwards. Packets are prioritized using VLAN/CoS (layer 2) or IP/ToS/DSCP (layer 3) marks.

QoS allows LigoWave’s customers to provide higher-quality services with multiple types of traffic (data, voice, video, etc.) on the same network.

Figure 1. QoS graph

QoS can be adjusted using three sliders for the different kinds of traffic: voice, video, and best effort.

Voice traffic has the highest priority and will always be added to the queue first. Background traffic, which is without priority (priority 0) by default, is adjusted according to your preferences applicable to the other kinds of traffic. The background traffic margin is controlled by an algorithm that takes into account both the CPE currently connected to the access point and the current link capacity. The algorithm also automatically adjusts the values in accordance with the changing environments and user increase or decrease probability. The main control window is displayed in the picture below:

Figure 2. QoS control window

QoS is controlled over the access point, after which the settings are applied to all connected CPE.

A SISO antenna should be connected to the main N connector that is marked V.

A 50 ohm terminator should be mounted onto the secondary N connector.

In the device wireless configuration section, select the SISO 1×1 mode.

Command Line Interface Management

The Command Line Interface, or CLI, software is a configuration shell for DLB-based devices. CLI is an alternative way of configuring the device. It is not intended to be the main device management method. Using CLI, the operator can test the authentication parameters, change the administrator’s password, reboot the device, reset the device to its default settings, see the device configuration, or view the device status.

All of the key shortcuts available in the CLI mode are listed in the table below:

CLI access

Use the SSH client application (e.g. Putty) to access the CLI of the WILI-S-based device.

Login

Enter the administrator login information as displayed in the command prompt.

Default administrator login information:

• User Name: admin
• Password: admin01

After a successful login, enter the help command to get the list of available CLI commands:

help

List of all CLI commands:

logout
reboot
reset-to-defaults
ping <ip>
telnet <ip>
show config
save config
show gateway
set gateway <gateway>
set user <user> password <encrypted_password> 
show software version
shell
linktest [frames <packet count>] [pkt-size <packet size>] [sessions <session count>] [peer <peer number>] [ip <remote IP>]
set virtual-ap <interface>
no virtual-ap <interface>
show interface list
show interface <interface> mac
show interface <interface> ip
set interface <interface> ip <ip/subnet mask>
show interface <interface> wireless-mode
set interface <interface> wireless-mode <ap, ipoll-ap, repeater, station, statio n-auto-ipoll> [peer-mac <MAC>]
set interface <interface> wds <on, off>
show interface <interface> ssid
set interface <interface> ssid <ssid>
show interface <interface> ssid-broadcast
set interface <interface> ssid-broadcast
no interface <interface> ssid-broadcast
show interface <interface> security
set interface <interface> security <open, wep64, wep128, wpa-psk, wpa2-psk, wpa-ent, wpa2-ent>
        wep64 key <1,2,3,4> pass <pass>
        wpa-psk/wpa2-psk encr <tkip, aes, auto> pass <pass>
        wpa-ent/wpa2-ent encr <tkip, aes, auto> pass <pass> radius <radius ip> port <radius port>
show interface <interface> ieee-mode
set interface <interface> ieee-mode <11a, 11b, 11bg, 11g, 11n, 11gn, 11an, 11bgn, 11n5>
show interface <interface> channel
set interface <interface> channel <channel>
set interface <interface> channel-auto <channel,channel,...>
set interface <interface> txpower <txpower>
set interface <interface> up
set interface <interface> down
show interface <interface> peers
show interface <interface> vlan-to-ssid
set interface <interface> vlan-to-ssid <vlan id>
no interface <interface> vlan-to-ssid <vlan id>
set interface <interface> vlan <vlan id>
no interface <interface> vlan <vlan id>

Examples of how to use CLI commands:

To change the wireless security setting, type the following command and press the Enter key:

set interface ra0 security open

To review the list of stations connected to the radio, type the following command and press Enter:

show interface ra0 peers

To check the current radio SSID, type the following command and press Enter:

show interface ra0 ssid

Type logout to leave the CLI mode:

logout

This article provides information on how to create a bridged Point to Multi-Point link using iPoll or 11n.

Step 1. Configure the network settings on the master (AP) device: change the device’s IP address (can be static or dynamic) and enable IP alias, if necessary:

Step 2. Configure the wireless settings for iPoll Master:

– set the Wireless Mode to Access Point iPoll

– define the SSID

– set the Channel to Auto

– enable Security, if necessary

All other settings should be kept as default values:

Configure the wireless settings for an 11n AP:

– set the Wireless Mode to Access Point (auto WDS)

– define the SSID

– choose the IEEE mode:

     N for 802.11n compatible radios

     A/N mixed or B/G/N mixed for legacy radios in the network

– set the Channel to Auto

– enable Security, if necessary

– set the ACK timeout in accordance with the maximum distance from the station using the slider:

Step 3. Configure the network settings on the station: change the device’s IP address (can be static or dynamic) and enable IP alias, if necessary:

Step 4. Configure the wireless settings for the station:

– select the country code

– set the wireless mode to Station (auto iPoll)

According to the access point:

– define the SSID

– enable Security if necessary

Step 5. Monitor the connection.

On the access point: navigate to Status > Wireless:

On the station: navigate to the Status > Information page:

If it is a MIMO device, there will be two signal streams: one will be the Main and the other—the Aux.

Follow these steps to run the Deliberant Reset Tool and to reset the device to its default factory settings:

Linux OS

The package should be installed by running the following command (Ubuntu/Debian version):

sudo apt-get install sun-java6-jre

Afterwards, click the right mouse button on the Reset Tool file and select Open with Sun Java 6 Runtime from the context menu.

Windows 7 OS

A shortcut with the following data must be created on the Windows 7 operating system:

General path: %ProgramFiles%Javajre6binjava.exe" -jar "%HOMEPATH%/Desktop/reset-tool.en.v1.2.45019.20121109.2143.jar

Example: "C:Program Files (x86)Javajre7binjava.exe" -jar "C:UserstesterDesktopreset-tool.en.v1.2.45019.20121109.2143.jar

Once the shortcut is created, it must be executed with administrative privileges enabled by right-clicking on it and selecting the option Run as Administrator from the context menu.

Step 1. Download the Reset Tool to your computer from this link.

Step 2. Run the executable file. The Reset Tool will launch:

Step 3. Click Scan to search for all Deliberant devices available on the network:

Step 4. Select the necessary device and press Reset:

Step 5. The Reset Tool will notify the administrator when to physically turn off and turn on the device:

Step 6. Physically turn off and then turn on the device.

Step 7. The device will now wait for the special reset packet. Once the special reset packet is received, the APC device will wait for 300 seconds to verify the reset procedure:

Step 8. Physically turn off and then turn on the device once more.

Step 9. The APC device will reboot and reset to its default settings:

Step 10. The APC device has now successfully been reset to its default factory settings.

Step 11. The APC device should now be configured under its default factory settings. Click the right mouse button on the appropriate device and launch the GUI:

The following steps should be performed to identify the maximum packet size that can be sent between devices:

Equipment for testing:

Linux PC 1 and Linux PC 2 (Cisco switches can also be used instead of PCs).

Once the wireless link is connected, make sure that the ping works by sending small packets using the following command:

ping remote_device_ip

If a ping response is received, change the Linux PC Ethernet interface MTU size with the following command:

ifconfig eth0 mtu 3500

In the provided example, the network interface is called eth0. However, it can be named eth1 or any similar name on other machines.

Once the MTU value is changed on both Linux PCs, run the ping command with the attributes -M do to send the packet without any fragmentation because the ping function performs fragmentation by default. The user can run the tcpdump tool on the remote Linux PC. See the screenshot below:

Internet Group Management Protocol (IGMP) snooping is the process of listening in to IGMP network traffic. IGMP snooping can significantly reduce traffic in cases of media streaming and other bandwidth-intensive IP multicast applications. With IGMP snooping, devices can make intelligent multicast forwarding decisions by reducing network capacity requirements.

When is it necessary to enable IGMP snooping?

Example:

Imagine a network that has an AP and several CPEs. An IPTV service is being provided to the clients. When a client decides to watch IPTV, the multicast traffic carrying TV data travels to the subscriber as well as to the rest of the CPEs connected to the AP. Such multicast flooding will reduce network bandwidth for the clients behind other CPEs. To avoid flooding the entire network, enable IGMP snooping on the AP (under Configuration > Network). Once the setting is enabled, multicast data will be sent to the specific subscribers only.

Intelligent Polling (or the iPoll Protocol) is a proprietary wireless mechanism customized for best performance in harsh environments.

Bandwidth allocation between the Master and the Slave devices is managed by the Master device. The Master device polls each Slave device sequentially. The Slave device only transmits the data “upstream” to the Master device when the Master device gives authorization via a “transmit grant”.

On iPoll, slower connections will not limit the speed for users who have better options to receive maximum throughput. The reason for this is the mechanism that works in multi-point scenarios.  When there are clients who have no or very few packets to send, the AP skips them and moves to the faster clients (those who have more data to send). Thus, users that have better signal levels (and less interference) maximize their performance, while others, who run on low modulations, are limited by the AP.

iPoll implements the airtime fairness mechanism by letting faster users to send more data than slower users, which means that faster users will usually have more time for sending and receiving data. The total throughput will therefore be higher. This is achieved by using a token mechanism between the AP and the Station. Tokens includes all of the sensitive control data for each device connected to the AP.

Follow these steps to run the Deliberant Reset Tool and to reset the device to its default factory settings:

Linux OS

The package should be installed by running the following command (Ubuntu/Debian version):

sudo apt-get install sun-java6-jre

Afterwards, click the right mouse button on the Reset Tool file and select Open with Sun Java 6 Runtime from the context menu.

Windows 7 OS

A shortcut with the following data must be created on the Windows 7 operating system:

General path: %ProgramFiles%Javajre6binjava.exe" -jar "%HOMEPATH%/Desktop/reset-tool.en.v1.2.45019.20121109.2143.jar

Example: "C:Program Files (x86)Javajre7binjava.exe" -jar "C:UserstesterDesktopreset-tool.en.v1.2.45019.20121109.2143.jar

Once the shortcut is created, it must be executed with administrative privileges enabled by right-clicking on it and selecting the option Run as Administrator from the context menu.

The Reset Tool allows administrators to easily restore the default configurations of the devices. Follow these steps to reset the device to its default settings:

Step 1. Download the Reset Tool to your computer from reset-tool.en.v1.2.45019.20121109.2143.

Step 2. Run the executable file. The Reset Tool will launch:

Step 3. Click Scan to search for all Deliberant devices available on the network:

Step 4. Select the necessary device and press Reset:

Step 5. The Reset Tool will notify the administrator when to physically turn off and turn on the device:

Step 6. Physically turn off and then turn on the device.

Step 7. The device will now wait for the special reset packet. Once the special reset packet is received, the APC device will wait for 300 seconds to verify the reset procedure:

Step 8. Physically turn off and then turn on the device once more.

Step 9. The APC device will reboot and reset to its default settings:

Step 10.  The APC device has now successfully been reset to its default factory settings.

Step 11.  The APC device should now be configured under its default factory settings. Click the right mouse button on the appropriate device and launch the GUI:

The Reset Tool allows administrators to discover all Deliberant devices present in the local area network and to easily restore the default configurations of these devices.

Follow these steps to discover Deliberant device in the network:

Step 1. Download the Reset Tool to your computer from reset-tool.en.v1.2.45019.20121109.2143.

Step 2. Run the executable file. The Reset Tool will launch:

Step 3. Click Scan to search for all Deliberant devices available on the network:

Step 4. The Reset Tool will now display all Deliberant devices available on your network. The scanned devices will now be ready to be managed:

The troubleshooting file is an extremely useful resource for the technical support team as it contains valuable information about the device’s configuration, routes, log files, command outputs, and other important information.

Follow these steps to download the troubleshooting file via the GUI:

Step 1. Log in to the APC GUI via a web browser:

Step 2. To download the troubleshooting file, navigate to System > Administration:

Step 3. Click the Download button next to Download troubleshooting file:

Step 4. The troubleshooting file should now be downloaded to your computer:

This article explains how to properly upgrade an APC device’s firmware.

Follow these steps to upgrade your device:

Step 1. Launch the device’s GUI and navigate to System > Firmware upgrade:

Step 2. Press Upload firmware and select the firmware file from your computer:

Step 3. Once the firmware is successfully uploaded on to the APC device, click Upgrade:

Follow these steps to access the Deliberant APC device for the first time:

Step 1. Configure your PC using a static IP address on the 192.168.2.0 subnet (e.g. 192.168.2.10 with mask 255.255.255.0).

Step 2. Open a web browser and enter the default IP address of the AP device—192.168.2.66:

Step 3. Once the login page is loaded, enter the default administrator login information (login: admin; password: admin01) and click Login:

Step 4. Agree to the disclaimer of the Deliberant APC device. Regulatory domain settings may differ depending on the selected operating country. Users are not allowed to select radio channels and RF output power values other than the permitted values for their respective country and regulatory domain:

The signal-to-noise ratio (SNR) is a measure that compares the signal level to the amount of noise present in the medium of transmission. The value is expressed in Decibel (dB).

The range of SNR may vary between 1dB and 30dB. The optimum SNR range is 18–30dB. 18dB is the minimum value at which the device can still operate and deliver relatively optimum performance. Values lower than 18dB can drastically reduce the performance.

SNR is reported for each chain (V and H polarities). If only one antenna is connected, the reported SNR values will show up as 20/1 or 1/20. The maximum SNR value is 30dB, which indicates the best link quality. Anything that is above 18-20dB means that the link is working properly. Anything below those values may indicate that there is interference or that the selected settings are not suited for the current radio environment.

If one of the SNR values is equal to 1, it usually means that no data is passing through the second antenna’s polarity (this usually happens when there is no traffic present on the link) or when the RSSI is very bad on that polarity.

Example of a bad link quality and SNR:

Dynamic algorithm

A dynamic algorithm (or auto data rate) is when a data rate is selected automatically by the mechanism that evaluates the performance of the device based on the current signal level, rate of data packet retry, and other relevant parameters.

Data rate fallback is the reduction of the data rate. When it is operating in Normal mode, it gradually reduces the modulation and coding scheme (MCS) until the data can pass through. When the data rate fallback is set to Aggressive, the MCS is decreased by 2 steps until it can pass the data through. The dynamic algorithm and aggressive fallback have to be used in noisy environments.

Fixed algorithm

A fixed algorithm is when a data rate is a fixed value (MCS).

The main difference between the dynamic algorithm and the fixed algorithm is that the fixed algorithm will always try to send data under the selected MCS rather then decreasing the currently selected MCS to the value at which the retry rate is lower.

The fixed algorithm does not take into account signal level or the amount of retried packets.  The data rate is only decreased when the device cannot send the current data at the fixed data rate. The data rate fallback mechanism turns on in such a case.

Data rate fallback operating in Normal mode gradually reduces the MCS until the data can pass through. When the data rate fallback is set to Aggressive, the MCS is decreased by 2 steps until it can pass the data through. A fixed data rate is best suited for operation in clean radio environments.

For Windows users

Step 1. Download it from the Net-SNMP website and install.

Step 2. Open the cmd command prompt window and run the following command:

snmpwalk.exe -c public -v2c -On 192.168.2.66

Step 3. There is also a command for using external MIBs:

snmpwalk.exe -c public -v2c 192.168.2.66 MIB [MIB name]

Download Deliberant MIBs from here.

For Linux users

Step 1. Install the SNMP packages:

apt-get install snmp

Step 2. Open the terminal and run the following command:

snmpwalk 192.168.2.66 -c public -v2c

Step 3. To add external MIBs, use the provided command:

snmpwalk 192.168.2.66 -c public -v2c -m /home/DELIBERANT-MIB

Download Deliberant MIBs from here.

How to configure the DMZ

Step 1. Set up the wireless mode. The provided example is for the Access Point (Auto WDS) wireless mode.

Step 2. Set the network mode to Router and then set the IP addresses for the DHCP server as well as the addresses for the wired WAN.

Step 3. Under Port Forwarding, tick the Enable DMZ option. Then, in the IP address field, enter the LAN IP that you wish to reach via the DMZ.

The main function is to provide reachability to the LOCAL LAN devices from the WAN when all ports are redirected to one IP address (I.E. 192.168.3.1).

How to test:

Step 1. Two computers are needed in order to test the DMZ function. In this case, they will be referred to as PC1 and PC2.

Step 2. PC1 should be connected to the WAN port of the device with an IP from subnet 2. In this case, it was 192.168.2.90. PC2’s LAN IP address will be provided from the device’s DHCP server from subnet 3. In this case, it is 192.168.3.1.

Step 3. Once the first two steps are completed, try to enter the access point from PC1 using 192.168.2.66. The DMZ function should apply and the user should be redirected to the LAN subnet IP address 192.168.3.1—the one that was entered into the IP address field.

A bridge is a device that separates two or more network segments within one logical network (e.g. a single IP subnet). The job of the bridge is to examine the destination of the data packets one at a time and to decide whether or not to pass the packets to the other side of the Ethernet segment. The result is a faster and quieter network with less collisions. In the OSI model, bridging acts in the first two layers, below the network layer.

The principle of ARPNAT is similar to NAT regarding IP networks, except that NAT works one layer deeper. Instead of translating the IP address, the router translates between the MAC hardware address on its side. If something on the wired side of the router makes an ARP request for the MAC address of an IP on the wireless side, then the router forwards the request as if it came from the router. When the response comes back, it mangles that too. Instead of passing back the real MAC (which lives on the wireless network), the router gives its own wired MAC address. Then, when it receives the frames for the IP addresses on the wireless network, it forwards them through. It does this to both sides of the bridge.

The following is an example of ARPNAT:

1. The Client PC asks what the MAC address of 192.168.1.67 is and asks to tell this to 192.168.1.5. This is a broadcast ARP request over wired Ethernet.
2. APC 5M (works as a STA) sees the ARP request and forwards the broadcast onto the wireless network as “What is the MAC address of 192.168.1.67. Tell it to 192.168.1.66” (this is APC 5M’s IP; remember that the Client was 192.168.1.5, so it is changed now).
3. APC 5M (works as an AP), which has the IP 192.168.1.67, responds with a result that is sent to 192.168.1.66. For example, the result is 00:19:23:66:12:56.
4. APC 5M (works as a STA) receives the response. It does some modifications and sends that request back to the Client PC as “192.168.1.67 is at 00:12:23:55:66:77“. This MAC is the MAC address of the APC 5M (STA) itself.
5. So, if the Client wants to talk to the AP, it will talk to APC 5M (STA), which will forward those frames to the AP.

When a bridge is installed between two networks, it gathers the packets from one network and repeats them to the other and vice-versa. This way, the nodes on one network can talk to the nodes on the other. Bridges also have features such as broadcast filtering, allowing for greater efficiency and reduced traffic. Therefore, in its most simple form, a bridge is a two-port network device that connects two network segments. Some advanced implementation of bridging can monitor traffic and determine which nodes are on which segment and later use this information while forwarding packets. The main factor to note is the fact that bridging takes place in the data-link layer of the OSI reference model.

There are some fundamental rules in wireless network planning for hotspots.  In the case of 2.4GHz, there are only 3 non-overlapping channels: 1, 6, and 11.

All large wireless networks can be built from many clusters.  One network cluster is formed from 3 different frequency cells. One cell is served by one access point.

Adjacent frequencies have to be different and separated by one neighboring frequency. This is an important aspect in wireless network planning. This type of network planning helps to avoid interference and improves link quality.

In the case of a 5GHz Wi-Fi network, more frequency channels are used. It helps to choose adjacent frequencies that are separated by two or three neighboring frequencies because this improves the quality of the network. 5Ghz network clusters could be formed from 7 or more different frequency cells.

It is necessary to know the required throughput when choosing the number of users to be managed by one AP. Throughput is dependent on the number of users connected to the base station. Ideally, an AP could provide 180Mbps with 30 connected stations. The throughput per station would be a 6Mbps simplex and a 3Mbps duplex.

The power source LED light typically blinks when there is a problem with the radio circuit. If a new PoE does not solve the problem, change the radio to a new one. Contact your distributor regarding unit repair.

There are a few simple steps for testing device configurations indoors or at very short distances between radios.

To test devices with N connectors, use RF cables with 50–60dB attenuators.

If the devices have integrated antennas, indoor tests should not be performed due to bad results from signal reflections. When choosing to test indoors, minimize possible damage by following these guidelines:

Set Tx power to 0. Signal levels should be set to approx. –50dBm.

If signal levels at 0 Tx power are still too high, place the devices out of clear line of sight. Putting cardboard or foam between the devices or pointing both devices at the ceiling may also help.

The default IP address is 192.168.2.66 with a subnet mask of 255.255.255.0.

The default username is admin and the default password is admin01.

Devices that are missing the reset button and devices with a reset button that is only accessible by disassembling the housing require an external process for easy reset to default factory settings.

The discovery daemon is launched during device startup—once the Ethernet interface drivers are loaded. The daemon suspends the startup process for 3 seconds and waits for the ICMP echo request packet of 369 bytes. If the packet is received, the discovery daemon resets the device to its default configuration.

For Linux users, follow these steps in order to reset to the device to its default settings:

Step 1. Turn the device off.

Step 2. Obtain the device’s MAC address.

Step 3. Connect a PC to the same physical subnet as the device.

Step 4. Execute the arp -s command to assign the IP address (the IP address should be from the same subnet as the PC) to the device’s MAC address:

arp -s <IP address to assign> <device MAC address>

Step 5. Start pinging the device:

ping <IP address> -s 369

For Windows users:

ping <IP address> -l 369 -t -w 200

Step 6. Power up the device and wait for about 1 minute or more (depending on the device hardware).

Step 7. Stop pinging the device and let it boot up as usual. The device should boot with its default settings.

Introduction

There may be cases when it is beneficial or even necessary to update a device’s firmware without using the web browser. It is possible to update the firmware using SSH and the fwupdate command. This article is a walk-through for getting the image onto the device and then flashing it.

Getting the image on to the device

The first step of flashing an image using shell is getting the firmware image onto the device. There are two easy ways to do this: to SFTP the image onto the device or to use wget from the device to download the image from an external source.

Instructions for Windows users

Step 1. Run WinSCP. Fill in the following fields in the window:

Host name – device’s IP address (default 192.168.2.66)
Username – admin
Password – device’s password (default: admin01)
Press Login to initiate an SSH connection with the device.

Step 2. Once a new window appears, navigate to the TMP directory. Then copy the file fwupdate.bin to the TMP directory.

Step 3. Run PuTTY. In the Host Name field, type in the device’s IP address and press Open.

Step 4. Type in the username admin and the password into the new window.

Username – admin
Password – device’s password (default: admin01)

 Step 5. Type in the command shell and press enter. The hardware should now be ready to start with the firmware upgrade.

Step 6. Navigate to the /tmp directory

cd /tmp

Step 7. Rename the previously uploaded file to fwupdate.bin.

mv DLB-CPE_24.v5.23.20642.080822.164518.img fwupdate.bin

Step 8. Type in the command fwupdate –m to start the firmware upgrade.

fwupdate -m

 Step 9. A message will confirm a successful upgrade.

/sbin/fwupdate: About to run firmware update

Step 10. Once the firmware upgrade is complete, the device should respond to a ping under its configured IP address.

Instructions for Linux users

Download the latest firmware and open the Terminal.

Step 1. Rename the downloaded firmware to fwupdate.bin.

mv DLB_APC-5M.FWBD-0100.v5.94-2.rt2880.Deliberant.APC.en_US.47825.130819.212805_Deliberant.5.94-2.47839.FWBD-0100.cfg.img fwupdate.bin

Step 2. Copy the firmware image to the device’s /tmp directory.

scp /home/fwupdate.bin [email protected]:/tmp

Step 3. Log on to the device via SSH.

ssh [email protected]

Username – admin

Password – device’s password (default: admin01)

Step 4. Type in the command shell and press Enter.

shell

Step 5. Type in the command fwupdate –m to start the firmware upgrade.

fwupdate -m

Step 6. Once firmware recovery is complete, the device should respond to a ping under its configured IP address.

The APC 5M V2 and V3 series of products support packet sizes of up to 3,790 bytes without any external configuration.

The APC 5M series of products support packet sizes of up to 1,532 bytes without any external configuration.

The APC 2M series of products support packet sizes of up to 1,532 bytes without any external configuration.

Introduction

Starting with firmware version 5.93, DLB APC devices will be equipped with firmware recovery functionality. Only newly purchased products with firmware version 5.93 or later will have firmware recovery via TFTP functionality. APC upgrades from older versions to 5.93 will not support the recovery feature. As of firmware version 5.94-6, the recovery feature is introduced with the firmware upgrade. This applies only to the APC 5M V2 and 2M series.

Products that may need a firmware recovery procedure:

• DLB APC 2M series
• DLB APC 5M V2 series

Other new products (the APC Propeller, APC Button, and APC ECHO 5) have dual-firmware image support, so it is very difficult to damage both firmware images.

When is recovery required?

Recovery is required when the firmware installed on the device’s flash memory becomes corrupted. This happens when the device is turned off during a firmware upgrade (e.g. power cuts, cable problems, etc). When the device cannot boot, it goes into recovery mode.

If the device is not accessible over the web, there is no ping response, and the Reset Tool cannot find the device, perform the firmware recovery procedure.

Firmware recovery using TFTP

Step 1. Download, install, and run a TFTP server on your PC.

TFTP for Windows:

TFTPD-HPA for Linux:

Use a command from the Linux shell:

 sudo apt-get install tftpd-hpa

Step 2. Download the newest appropriate firmware from the LigoWave website here.

Step 3. Rename the downloaded firmware file to fwupdate.bin and move it to the TFTP server directory.

Step 4. Turn the device off.

Step 5. Connect the device to a PC directly or through a switch using a cable.

Step 6. Set the PC network adapter IP address to 192.168.2.1 (it must be a TFTP server address).

Step 7. Turn on the device. If everything is configured correctly, the TFTP server will notify about the firmware transfer.

Step 8. Wait 5 minutes or less until the firmware is properly flashed.

Step 9. Once firmware recovery is complete, the device should respond to a ping under its configured IP address.

All products within the APC series that are running in Access Point (Auto WDS) mode support a maximum of 127 CPEs.

The recommended maximum number of CPEs is 70.

All products within the APC series that are running in Access Point iPoll mode support a maximum of 127 stations.

The recommended maximum number of stations is 70.

The Statistics page is divided into two sections. It displays the network interface counters as well as the traffic graphs of the wired and wireless interfaces.

The interface counters display a table of interface statistics.

Interface – displays the radio interfaces, VAPs, and SSIDs (in brackets)
MAC address – displays the MAC address of a particular interface.
Tx data – displays the amount of transmitted data.
Rx data – displays the amount of received data.
Tx packets – displays the number of transmitted packets.
Rx packets – displays the number of received packets.
Tx errors – displays the number of TX errors.
Rx errors – displays the number of RX errors.

The Wireless page displays the receive/transmit statistics for the APs and the successfully-linked wireless clients (click the Counters tab to view the Rx/Tx information of the connected clients):

If the access point has more than one wireless interface (VAPs), the appropriate number of tables with the information about the connected wireless clients will be displayed.

Station – displays the MAC address and the friendly name of the successfully connected wireless client.
IP address – displays the IP address of the wireless client.
Signal – displays the signal strength of the access point’s main and auxiliary antennas that the station communicates with (in dBm).
Tx/Rx rate – displays the transmit/receive data rates (in Mbps).
Tx/Rx CCQ, % – displays the wireless Client Connection Quality (CCQ). The value (in percentages) shows how effectively the bandwidth is used with respect to the maximum possible bandwidth.
Protocol – displays the protocol, under which the access point communicates with a particular station.
Link uptime – displays the duration of a particular session.

Detailed Radio statistics per Peer:

Station – displays the MAC address and the friendly name of the successfully connected wireless client.
IP address – displays the IP address of the wireless client.
Tx data – displays the amount of transmitted data.
Rx data – displays the amount of received data.
Tx packets – displays the number of transmitted packets.
Rx packets – displays the number of received packets.
Tx retry, % – displays the amount of retried packets (in percentages).
Rx drop, % – displays the amount of dropped packets (in percentages).

Introduction

There may be cases when it is beneficial or even necessary to update the firmware on a device without using the web browser. It is possible to update the firmware by using SSH and the fwupdate command. This article serves as a walk-through for getting the image onto the device and then flashing it.

Getting the firmware onto the device

The first step of flashing an image in the shell is getting the firmware image onto the device. There are two easy ways to do this: using SFTP to upload the image onto the device, or using wget from the device to download the image from an external source.

Instructions for Windows users

Step 1. Run WinSCP. Fill out the following fields:

Host name – device IP address (default 192.168.2.66)
Username – admin
Password – device login password (default: admin01)
Press Login to initiate an SSH connection to the device.

Step 2. In the next window, go to the /tmp directory. Then copy the fwupdate.bin file to the /tmp directory.

Step 3. Run PuTTY. In the Host Name field, type the device’s IP address and press Open.

Step 4. Type in the username and the password in the next window.

Username – admin
Password – device’s password (default: admin01)

Step 5. Navigate to the /tmp directory.

cd /tmp

Step 6. Rename the previously uploaded file to fwupdate.bin.

mv AP.QD-1.v7.50.7780.img fwupdate.bin

Step 7. Type the command fwupdate –m to start the firmware upgrade.

fwupdate -m

Step 8. If PuTTY closes automatically, this confirms the successful start of the upgrade.

Step 9. Once the firmware upgrade is complete, the device should respond to a ping using the configured IP address.

Instructions for Linux users

Download the latest firmware and open the Terminal.

Step 1. Rename the downloaded firmware to fwupdate.bin.

mv AP.QD-1.v7.50.7780.img fwupdate.bin

Step 2. Copy the firmware image to the device’s /tmp directory.

scp /home/fwupdate.bin [email protected]:/tmp

Step 3. Log onto the device via SSH.

ssh [email protected]

Username – admin

Password – device’s password (default: admin01)

Step 4. Type in the command fwupdate –m to start the firmware upgrade.

fwupdate -m

Step 5. Once the firmware upgrade is complete, the device should respond to a ping using the configured IP address.

BA window size (found under Wireless configuration > Advanced radio settings) specifies the size of the Block ACK window. Individual acknowledgements are transmitted after every MPDU packet. The BA window size value allows to acknowledge multiple MPDUs together as a single BA frame.

Block ACK has a bitmap size of 64×16 bits. If the level of interference is high, it is recommended to set the BA window size to 8 to reduce packet loss and the amount of retries. If the environment is clean, it is recommended to set the BA window size to 64 for maximum performance.

The power source LED light typically blinks when there is a problem with the radio circuit. If a new PoE does not solve the problem, change the radio to a new one. Contact your distributor regarding unit repair.

This article discusses how to properly upgrade the firmware on NFT equipment. Follow these steps to upgrade your device’s firmware:

Step 1. The current version of the device’s firmware is shown in the upper left corner of the web interface. To update the device’s firmware, click the Update link found at the name of the current firmware:

Step 2. Select the firmware file from your computer and press Upload:

Wait until the firmware is uploaded:

Step 3. Once the firmware is successfully uploaded onto the NFT device, click Upgrade:

Step 4. The upgrade should take approx. 2 minutes. The device will reboot at the end.

The troubleshooting file contains valuable information about the device’s configuration, log files, command outputs, and other data. The device automatically gathers troubleshooting information rather than requiring the user to gather each piece of information manually. This is helpful when submitting problems to the support team. Follow these steps to download the troubleshooting file via the GUI:

Step 1. Login to the NFT GUI via a web browser:

Step 2. To download the troubleshooting file, navigate to the Maintenance tab, click on Troubleshooting in the side-bar menu, and then click Download:

Step 3. The troubleshooting file has been successfully downloaded to your computer:

NFT 1Ni devices have a reset button near the Ethernet port. To reset the device, hold the button for 5 seconds and then release it. When the reset process starts, the device’s LEDs will begin blinking.

Follow these steps to run the LigoWave Reset Tool and to reset the device to its default factory settings:

Linux OS

The package should be installed by running the following command (Ubuntu/Debian version):

sudo apt-get install sun-java6-jre

Afterwards, click the right mouse button on the Reset Tool file and select Open with Sun Java 6 Runtime from the context menu.

Windows 7 OS

A shortcut with the following data must be created on the Windows 7 operating system:

General path: %ProgramFiles%\Java\jre6\bin\java.exe" -jar "%HOMEPATH%/Desktop/reset-tool.en.v1.2.45019.20121109.2143.jar

Example: "C:\Program Files (x86)\Java\jre7\bin\java.exe" -jar "C:\Users\tester\Desktop\reset-tool.en.v1.2.45019.20121109.2143.ja

Once the shortcut is created, it must be executed with administrative privileges enabled by right-clicking on it and selecting the option Run as Administrator from the context menu.

Step 1. Download the Reset Tool to your computer from reset-tool.ligowave.en.v1.2.55051.20170126.1017.jar.

Step 2. Run the executable file. The Reset Tool will launch:

Step 3. Once the Reset Tool launches, reboot the device (physically turn off and turn on the device) and wait until it automatically appears. Then select the device and press Reset:

Step 4. For a full device reset, the 4 last symbols of the serial number have to be entered.

 Step 5. The serial number can be found on the device’s casing, the box, using the device discovery, and in the UI status menu.

Step 6. Status: Resetting indicates that the NFT device is being reset to the default settings:

Step 7. Status: Booting device indicates that the NFT device has been successfully reset to the default factory settings and that it is starting to boot:

The auto data rate algorithm is when a data rate is selected automatically by the mechanism that evaluates the performance of the device based on the current signal level, rate of data packet retry, and other relevant parameters. This is not configurable.

Introduction

All NFT devices have dual-firmware image support, so it is very difficult to damage both firmware images. In the case that both images are damaged, all NFT devices are equipped with firmware recovery functionality. This applies to all NFT devices.

When is recovery required?

Recovery is required when both of the firmware images installed on the device’s flash memory become corrupted. This happens when the device is turned off during a firmware upgrade (e.g. power cuts, cable problems, etc). When the device cannot boot, it goes into recovery mode.

If the device is not accessible over the web or there is no ping response, follow the firmware recovery procedure.

Firmware recovery using TFTP

Step 1. Download, install, and run a TFTP server on your PC.

TFTP for Windows:

TFTPD-HPA for Linux:

Use a command from the Linux shell:

 sudo apt-get install tftpd-hpa

Step 2. Download the newest appropriate firmware from the LigoWave website here.

Step 3. Rename the downloaded firmware file to fwupdate.bin and move it to the TFTP server directory.

Step 4. Turn the device off.

Step 5. Connect the device to a PC directly or through a switch using a cable.

Step 6. Set the PC network adapter IP address to 192.168.2.254 (it must be a TFTP server address).

Step 7. Turn on the device. If everything is configured correctly, the TFTP server will notify about the firmware transfer.

Step 8. Wait 5 minutes or less until the firmware is properly flashed.

Step 9. Once firmware recovery is complete, the device should respond to a ping under its configured IP address.

How to discover all Infinity devices in a local network?

The NFT series of products support the SSDP protocol (firmware v7.5 and later), which allows users to find devices without any external tools or programs. Follow these steps to discover all NFT devices on the network:

Step 1.1. Enable the network discovery function on your Windows PC. Open Windows Explorer, enter the Network section and follow the automatic pop-up at the top of the screen:

Step 1.2. To enable, click Yes, turn on network discovery and file sharing for all public networks.

Users can also enable the network discovery function manually:

Step 2.1. go to Control Panel and click Choose homegroup and sharing options under the Network and Internet section:

Step 2.2. Proceed to Change advanced sharing settings:

Step 2.3. Select Turn on network discovery:

Step 3. All of the available devices should appear in the Network devices section. The scanned devices should now be ready for management:

Right click on the device to open the context menu and select Properties to check the IP address and serial number. Users can also reach the device’s web page directly:

MAC OS X

Step 1. Enable the Bonjour service in the Safari browser under Preferences → Advanced (the location depends on the version of the operating system).

Step 2. Go to Bookmarks → Bonjour → Web-pages.

Step 3. Click on the name of the radio (look for a friendly device name).

The Client Connection Quality (CCQ) is a connection quality index expressed in percentages. The value shows how effectively the system is running with respect to the maximum possible performance.

The CCQ formula also includes the percentage values of packet re-transmissions and received packet drops. Lastly, the CCQ shows how many packets are retried at the current data rate.

Device discovery – a feature that allows the NFT unit to discover other devices within reach of a single multicast packet. Enable this option to turn on this feature.

Bonjour provides a simpler way of discovering devices in a local area network. If the device discovery feature is enabled, the unit will periodically multicast Bonjour service records to the entire local network so as to notify of its presence. This allows the user to find devices without any external tools or programs.

The Backup configuration function allows users to save a file of the current configuration. The saved configuration file is useful when restoring configuration settings in case of device misconfiguration or when uploading a standard configuration to multiple devices without the need to manually configure each device through the web interface.

Follow these steps to access the NFT device for the first time:

Step 1. Configure the PC using a static IP address on the 192.168.2.0 subnet (e.g. 192.168.2.10 with mask 255.255.255.0).

Step 2. Open a web browser and enter the default IP address of the NFT device—192.168.2.66:

Step 3. Once the login page is loaded, enter the default administrator login and password: admin and admin01 respectively. Click Login.

Step 4. Agree to the NFT disclaimer. Regulatory domain settings may differ depending on the selected operating country. Users are not allowed to select radio channels and RF output power values other than the permitted values for their respective country and regulatory domain:

To enable Telnet, log on to the NFT device’s GUI and navigate to Settings → Services → Remote Management and slide the Enable Telnet slider.

Enable telnet – use to enable or disable Telnet access to the device.
Telnet port – specify the Telnet port. The Telnet port is 23 by default.

The NFT 2N device supports a maximum of 256 clients. Each radio (2.4GHz and 5GHz) supports up to 128 concurrent clients.

The default IP address is 192.168.2.66 with a subnet mask of 255.255.255.0.

The default username is admin and the default password is admin01.

Quality of Service: Traffic Optimization

Quality of Service, or QoS, is of particular importance in ensuring continuous transmission of high-bandwidth video and multimedia information.

The QoS on the LigoDLB unit automatically detects and classifies incoming traffic according to 802.1p or DSCP values to match one of the four queues (lowest → highest), as provided in the following table:

Traffic optimization – select the traffic transmission type for the best data optimization and performance:

• Data/Data+Voip – for data and data + VoIP traffic.
• Data+Video+Voip – for data, video, and VoIP traffic.

Follow these steps to run the LigoWave Reset Tool and reset the device to its default factory settings:

Linux OS

The package should be installed by running the following command (Ubuntu/Debian version):

sudo apt-get install sun-java6-jre

Afterwards, click the right mouse button on the Reset Tool and select Open with Sun Java 6 Runtime or via the following command line:

sudo java -jar /home/reset-tool.ligowave.en.v1.2.55051.20170126.1017.jar

Once the Reset Tool starts, follow the steps as shown in the example with Windows 7.

Windows 7 OS

Provided bellow is an example on how to run the Reset Tool with an elevated access command prompt.

Download the Reset Tool locally to your computer from reset-tool.ligowave.en.v1.2.55051.20170126.1017.jar.

Create the Reset Tool folder on drive C:

Copy the Reset Tool executable into this folder:

Click on Start, select All Programs and then choose Accessories:

Click the right mouse button on Command Prompt to call out the context menu and choose Run as administrator:

Command Prompt should now be running with administrator privileges:

Type in the command cd c:\Reset Tool and hit the Enter key:

Type in the command java -jar reset-tool.ligowave.en.v1.2.52133.20150721.1615.jar –V:

If done successfully, the Reset Tool should launch with administrator privileges enabled:

Steps to reset the device to its default settings:

Step 1. Once the Reset Tool starts, reboot the device (physically turn off and turn on the device) and wait until it automatically appears in the list.

Select the device and press Reset:

Step 2. For a full device reset, the 4 last symbols of the serial number have to be entered.

Step 3. The serial number can be found on the device’s casing, the box, using the device discovery, and in the UI status menu.

Step 4. Status: Resetting indicates that the LigoDLB device is being reset to the default settings:

Step 5. Status: Booting device indicates that the LigoDLB device has been successfully reset to the default factory settings and that it is starting to boot:

Step 6. When the status Reset complete appears, you will be able to log into device:

The following steps are intended for devices that were upgraded to NFT firmware following the HotSpot guide for the LigoDLB (LigoDLB configuration scenarios).

Step 1. Download the latest firmware for the LigoDLB unit from LigoWave’s website here.

Step 2. Download one of the default configuration images:

• LigoDLB 2 series default configuration image
• LigoDLB 5 series default configuration image
• LigoDLB 5 AC series default configuration image
• LigoDLB PRO 2-90 series default configuration image
• LigoDLB PRO 5-90 series default configuration image
• LigoDLB PRO 5 AC series default configuration image

Step 3. Upgrade the LigoDLB unit using the latest firmware twice to set the back-up firmware image for dual-boot.

Note: LigoDLB 5ac series does not have dual-boot, so it is enough to upgrade firmware once.

Step 4. Upgrade the LigoDLB unit using the default configuration image.

Step 5. Perform a reset to default settings.

Smart channel width – select this option to enable smart channel width on the station. The station will automatically connect to an AP in all channel widths. This option allows the LigoDLB station to automatically change the channel width in case of an unsuccessful connection to an AP as long as the connection to the AP is established.

There are a few simple steps for testing device configurations indoors or at very short distances between radios.

To test devices with N connectors, use RF cables with 50–60dB attenuators.

If the devices have integrated antennas, indoor tests should not be performed due to bad results from signal reflections. When choosing to test indoors, minimize possible damage by following these guidelines:

Set Tx power to 0. Signal levels should be set to approx. –50dBm.

If signal levels at 0 Tx power are still too high, place the devices out of clear line of sight. Putting cardboard or foam between the devices or pointing both devices at the ceiling may also help.

An Object Identifier or OIDs is a name that is used to identify a specific object. In order to find all of the OID from a selected device, the Net-SNMP package and the SNMP-walk tool are required.

For Windows users

Step 1. Download it from the Net-SNMP website and install.

Step 2. Open the cmd command prompt window and run the following command:

snmpwalk.exe -c public -v1 -On 192.168.2.66

Step 3. There is also a command for using external MIBs:

snmpwalk.exe -c public -v1 192.168.2.66 MIB [MIB name]

Download the LigoDLB proprietary MIBs from here.

For Linux users

Step 1. Install the SNMP packages:

apt-get install snmp

Step 2. Open the terminal and run the following command:

snmpwalk 192.168.2.66 -c public -v1 . -On

Step 3. To add external MIBs, use the provided command:

snmpwalk 192.168.2.66 -c public -v1 -m /home/ligodlb.mib

Download the LigoDLB proprietary MIBs from here.

Introduction

There may be cases when it is beneficial or even necessary to update the firmware on a device without using the web browser. It is possible to update the firmware by using SSH and the fwupdate command. This article serves as a walk-through for getting the image onto the device and then flashing it.

Getting the image onto the device

The first step of flashing an image in the shell is getting the firmware image onto the device. There are two easy ways to do this: using SFTP to upload the image onto the device, or using wget from the device to download the image from an external source.

Instructions for Windows users

Step 1. Run WinSCP. Fill out the following fields:

Host name – device IP address (default 192.168.2.66)
Username – admin
Password – device login password (default: admin01)
Press Login to initiate an SSH connection to the device.

Step 2. In the next window, go to the /tmp directory. Then copy the fwupade.bin file to the /tmp directory.

Step 3. Run PuTTY. In the Host Name field, type the device’s IP address and press Open.

Step 4. Type in the username and the password in the next window.

Username – admin
Password – device’s password (default: admin01)

Step 5. Navigate to the /tmp directory.

cd /tmp

Step 6. Rename the previously uploaded file to fwupdate.bin.

mv APCPE.QM-1.v7.50.7643.img fwupdate.bin

Step 7. Type the command fwupdate –m to start the firmware upgrade.

fwupdate -m

Step 8. If PuTTY closes automatically, this confirms the successful start of the upgrade.

Step 9. Once the firmware upgrade is complete, the device should respond to a ping using the configured IP address.

Instructions for Linux users

Download the latest firmware and open the Terminal.

Step 1. Rename the downloaded firmware to fwupdate.bin.

mv APCPE.QM-1.v7.50.7643.img fwupdate.bin

Step 2. Copy the firmware image to the device’s /tmp directory.

scp /home/fwupdate.bin [email protected]:/tmp

Step 3. Log onto the device using SSH.

ssh [email protected]

Username – admin

Password – device’s password (default: admin01)

Step 4. Type in the command fwupdate –m to start the firmware upgrade.

fwupdate -m

Step 5. Once the firmware upgrade is complete, the device should respond to a ping using the configured IP address.

A bridge is a device that separates two or more network segments within one logical network (e.g. a single IP subnet). The job of the bridge is to examine the destination of the data packets one at a time and to decide whether or not to pass the packets to the other side of the Ethernet segment. The result is a faster and quieter network with less collisions. In the OSI model, bridging acts in the first two layers, below the network layer.

The principle of ARPNAT is similar to NAT regarding IP networks, except that NAT works one layer deeper. Instead of translating the IP address, the router translates between the MAC hardware address on its side. If something on the wired side of the router makes an ARP request for the MAC address of an IP on the wireless side, then the router forwards the request as if it came from the router. When the response comes back, it mangles that too. Instead of passing back the real MAC (which lives on the wireless network), the router gives its own wired MAC address. Then, when it receives the frames for the IP addresses on the wireless network, it forwards them through. It does this to both sides of the bridge.

The following is an example of ARPNAT:

1. The Client PC asks what the MAC address of 192.168.1.67 is and asks to tell this to 192.168.1.5. This is a broadcast ARP request over wired Ethernet.
2. The DLB unit (works as a STA) sees the ARP request and forwards the broadcast onto the wireless network as “What is the MAC address of 192.168.1.67. Tell it to 192.168.1.66” (this is DLB unit’s IP; remember that the Client was 192.168.1.5, so it is changed now).
3. The DLB unit (works as an AP), which has the IP 192.168.1.67, responds with a result that is sent to 192.168.1.66. For example, the result is 00:19:23:66:12:56.
4. The DLB unit (works as a STA) receives the response. It does some modifications and sends that request back to the Client PC as “192.168.1.67 is at 00:12:23:55:66:77“. This MAC is the MAC address of the DLB unit (STA) itself.
5. So, if the Client wants to talk to the AP, it will talk to the DLB unit (STA), which will forward those frames to the AP.

When a bridge is installed between two networks, it gathers the packets from one network and repeats them to the other and vice-versa. This way, the nodes on one network can talk to the nodes on the other. Bridges also have features such as broadcast filtering, allowing for greater efficiency and reduced traffic. Therefore, in its most simple form, a bridge is a two-port network device that connects two network segments. Some advanced implementation of bridging can monitor traffic and determine which nodes are on which segment and later use this information while forwarding packets. The main factor to note is the fact that bridging takes place in the data-link layer of the OSI reference model.

Due to the changes in the main proprietary protocol mechanism of the LigoDLB, iPoll 2 is not compatible with iPoll 1. To set up iPoll 2 on Deliberant APC and LigoDLB devices, upgrade to the latest firmware, which can be found on LigoWave’s website.

The following steps should be performed to identify the maximum packet size that can be sent between devices:

Equipment for testing:

Linux PC 1 and Linux PC 2 (Cisco switches can also be used instead of PCs).

Once the wireless link is connected, make sure that the ping works by sending small packets using the following command:

ping remote_device_ip

If a ping response is received, change the Linux PC Ethernet interface MTU size with the following command:

ifconfig eth0 mtu 3500

In the provided example, the network interface is called eth0. However, it can be named eth1 or any similar name on other machines.

Once the MTU value is changed on both Linux PCs, run the ping command with the attributes -M do to send the packet without any fragmentation because the ping function performs fragmentation by default.

ping remote_device_ip -s 3500 -M do

-s indicates the packet size. The example is for 3,500 bytes.

When using a remote Linux PC, you can run the tcpdump tool. See the screenshot below:

The power source LED light typically blinks when there is a problem with the radio circuit. If a new PoE does not solve the problem, change the radio to a new one. Contact your distributor regarding unit repair.

Network Address Translation, or NAT, functions first by transforming the private IP address of the packets originating from hosts on the user’s network, so that they appear to be coming from a single public IP address, and second by restoring the destination public IP address to the appropriate private IP address for packets entering the private network. The group of PCs on the user’s network would then appear as a single client to the WAN interface. This is used in Router mode.

All LigoDLB devices have a reset button near the Ethernet port. To reset the device, hold the button for 5 seconds and then release it. When the reset process starts, the device’s LEDs will begin blinking.

The LigoDLB series of products support the SSDP protocol (firmware v7.5 and later), which allows users to find devices without any external tools or programs. Follow these steps to discover all DLB devices on the network:

Step 1.1. Enable the network discovery function on your Windows PC. Open Windows Explorer, enter the Network section and follow the automatic pop-up at the top of the screen:

Step 1.2. To enable, click Yes, turn on network discovery and file sharing for all public networks.

Users can also enable the network discovery function manually:

Step 2.1. go to Control Panel and click Choose homegroup and sharing options under the Network and Internet section:

Step 2.2. Proceed to Change advanced sharing settings:

Step 2.3. Select Turn on network discovery:

Step 3. All of the available devices should appear in the Network devices section. The scanned devices should now be ready for management:

Right click on the device to open the context menu and select Properties to check the IP address and serial number. Users can also reach the device’s web page directly:

MAX OS X

Step 1. Enable the Bonjour service in the Safari browser under Preferences → Advanced (the location depends on the version of the operating system).

Step 2. Go to Bookmarks → Bonjour → Web-pages.

Step 3. Click on the name of the radio (look for a friendly device name).

To enable Telnet, log on to the NFT device’s GUI and navigate to Settings → Services → Remote Management and slide the Enable Telnet slider.

Enable telnet – use to enable or disable Telnet access to the device.
Telnet port – specify the Telnet port. The Telnet port is 23 by default.

Channel width – select the width of the operating radio channel. The LigoDLB device supports 5, 10, 20, and 40MHz channel widths.

Auto data rate algorithm

Auto data rate algorithm – a data rate is automatically selected by the mechanism that evaluates the current performance of the device based on the current signal level, data packet retry rate, and other parameters. The data rate fallback drops the MCS step by step until the data can be transferred. The auto data rate should always be used in noisy environments.

Follow these steps to run the LigoWave Reset Tool and to reset the device to its default factory settings:

Linux OS

The package should be installed by running the following command (Ubuntu/Debian version):

sudo apt-get install sun-java6-jre

Afterwards, click the right mouse button on the Reset Tool file and select Open with Sun Java 6 Runtime from the context menu.

Windows 7 OS

A shortcut with the following data must be created on the Windows 7 operating system:

General path: %ProgramFiles%\Java\jre6\bin\java.exe" -jar "%HOMEPATH%/Desktop/reset-tool.en.v1.2.45019.20121109.2143.jar

Example: "C:\Program Files (x86)\Java\jre7\bin\java.exe" -jar "C:\Users\tester\Desktop\reset-tool.en.v1.2.45019.20121109.2143.jar

Once the shortcut is created, it must be executed with administrative privileges enabled by right-clicking on it and selecting the option Run as Administrator from the context menu.

Step 1. Download the Reset Tool to your computer from reset-tool.ligowave.en.v1.2.51166.20150304.1257.

Step 2. Run the executable file. The Reset Tool will launch:

Step 3. Once the Reset Tool launches, reboot the device (physically turn off and turn on the device) and wait until it automatically appears. Then select the device and press Reset:

Step 4. For a full device reset, the 4 last symbols of the serial number have to be entered.

 Step 5. The serial number can be found on the device’s casing, the box, using the device discovery, and in the UI status menu.

Step 6. Status: Resetting indicates that the DLB device is being reset to the default settings:

Step 7. Status: Booting device indicates that the DLB device has been successfully reset to the default factory settings and that it is starting to boot:

The Backup configuration function allows users to save a file of the current configuration. The saved configuration file is useful when restoring configuration settings in case of device misconfiguration or when uploading a standard configuration to multiple devices without the need to manually configure each device through the web interface.

Restore configuration – click to upload an existing configuration file to the device. Once the configuration file is uploaded, the new configuration will be effective as soon as the Save changes button is pressed.

If necessary, click to save the current configuration file:

Device discovery – select this option to enable the LigoDLB discovery function. This allows the discovery of LigoDLB units within reach of a single multicast packet.

Bonjour provides a generic method for discovering devices on a local area network. When the device discovery feature is enabled, the device periodically multicasts Bonjour service records to the entire local network so as to announce its existence.

Public status page – this option enables or disables the permission for not-logged users to view the status page.

Client Connection Quality (CCQ) is the connection quality index expressed in percentages. It shows the ratio of current system efficiency to the maximum theoretical system capacity.

The CCQ index also indicates the percentage value for transmitted packet retries, received packet drop, and the quantity of packets retried at the current data rate.

Introduction

All LigoDLB devices have dual-firmware image support, so it is very difficult to damage both firmware images. In the case that both images are damaged, all LigoDLB devices are equipped with firmware recovery functionality. This applies to LigoDLB 5 and LigoDLB 2 series of devices.

When is recovery required?

Recovery is required when both of the firmware images installed on the device’s flash memory become corrupted. This happens when the device is turned off during a firmware upgrade (e.g. power cuts, cable problems, etc). When the device cannot boot, it goes into recovery mode.

If the device is not accessible over the web, there is no ping response, and the Reset Tool cannot find the device, follow the firmware recovery procedure.

Firmware recovery using TFTP

Step 1. Download, install, and run a TFTP server on your PC.

TFTP for Windows:

TFTPD-HPA for Linux:

Use a command from the Linux shell:

 sudo apt-get install tftpd-hpa

Step 2. Download the newest appropriate firmware from the LigoWave website here.

Step 3. Rename the downloaded firmware file to fwupdate.bin and move it to the TFTP server directory.

Step 4. Turn the device off.

Step 5. Connect the device to a PC directly or through a switch using a cable.

Step 6. Set the PC network adapter IP address to 192.168.2.254 (it must be a TFTP server address).

Step 7. Turn on the device. If everything is configured correctly, the TFTP server will notify about the firmware transfer.

Step 8. Wait 5 minutes or less until the firmware is properly flashed.

Step 9. Once firmware recovery is complete, the device should respond to a ping under its configured IP address.

All products within the LigoDLB series that are running in Access Point iPoll 2 mode support a maximum of 127 stations.

The recommended maximum number of stations is 70.

All products within the LigoDLB series that are running in Access Point (Auto WDS) mode support a maximum of 127 CPEs.

The recommended maximum number of CPEs is 70.

The LigoDLB 5 series products support packet sizes of up to 3,764 bytes (data payload) without any external configuration.

The LigoDLB 5 ac series products support packet sizes of up to 3,550 bytes (data payload) without any external configuration.

The LigoDLB 2 series products support packet sizes of up to 3,764 bytes (data payload) without any external configuration.

The recommended signal level range for optimum performance is from –35dBm to –60dBm. Links may also work with lower signal level modulations ranging from –60dbm to –85dBm.

On the access point side:

On the station side:

Follow these steps to access the LigoDLB device for the first time:

Step 1. Configure the PC using a static IP address on the 192.168.2.0 subnet (e.g. 192.168.2.10 with mask 255.255.255.0).

Step 2. Open a web browser and enter the default IP address of the AP device—192.168.2.66:

Step 3. Once the login page is loaded, enter the default administrator login and password: admin and admin01 respectively. Click Login.

Step 4. Agree to the LigoDLB disclaimer. Regulatory domain settings may differ depending on the selected operating country. Users are not allowed to select radio channels and RF output power values other than the permitted values for their respective country and regulatory domain:

The troubleshooting file contains valuable information about the device’s configuration, routers, log files, command outputs, and other data. This is helpful when submitting problems to the support team.

Follow these steps to download the troubleshooting file via the GUI:

Step 1. Login to the LigoDLB GUI via a web browser:

Step 2. To download the troubleshooting file, navigate to the Maintenance tab, click on Troubleshooting in the side-bar menu, and then click Download:

Step 3. The troubleshooting file has been successfully downloaded to your computer:

A SISO antenna should be connected to the main N connector that is marked V.

A 50 ohm terminator should be mounted onto the secondary N connector.

In the device wireless configuration section/advanced radio settings section, set the MAX 802.11n MCS Index to MCS7 (150Mbps) to enable the SISO 1×1 mode.

This article discusses how to properly upgrade the firmware on LigoDLB equipment. Follow these steps to upgrade your device’s firmware:

Step 1. The current version of the device’s firmware is shown in the upper left corner of the web interface. To update the device’s firmware, click the Update link found at the name of the current firmware:

Step 2. Select the firmware file from your computer and press Upload:

Wait until the firmware is uploaded:

Step 3. Once the firmware is successfully uploaded onto the LigoDLB device, click Upgrade:

Step 4. The upgrade should take approx. 2 minutes. The device will reboot at the end.

The default IP address is 192.168.2.66 with a subnet mask of 255.255.255.0.

The default username is admin and the default password is admin01.

Quality of Service (QoS) in detail

Firmware version x.95 and later have granted the LigoPTP PRO and LigoPTP MIMO series of devices QoS functionality. It is a major improvement in the quality control applicable to the different kinds of traffic.

QoS allows users to adjust the distribution of the 4 different types of traffic.  The process places the data into 4 queues that are then processed based on their priority levels. The prioritization policy is strict, which means that higher-priority data is sent first and lower priority is sent afterwards. Packets are prioritized using VLAN/CoS (layer 2) or IP/ToS/DSCP (layer 3) marks.

QoS allows LigoWave’s customers to provide higher-quality services with multiple types of traffic (data, voice, video, etc.) on the same network.

Figure 1. QoS graph

QoS can be adjusted using three sliders for the different kinds of traffic: voice, video, and best effort.

Voice traffic has the highest priority and will always be added to the queue first. Background traffic, which is without priority (priority 0) by default, is adjusted according to your preferences applicable to the other kinds of traffic. The background traffic margin is controlled by an algorithm that takes into account both the current priorities for voice, video, and best effort traffic and the current link capacity. The algorithm also automatically adjusts the values in accordance with the changing environments. The main control window is displayed in the picture below:

Figure 2. QoS control window

QoS is controlled on the Master’s side, after which the settings are applied to a remote node (Slave) device. QoS operates on both sides and controls all incoming traffic.

Signal fading is a common issue among links installed over seas and in rainy locations. Due to tidal fading, links are constantly undergoing signal decrease and increase cycles. These events—arbitrarily defined as having fades relative to free space powers in excess of 20dB for a duration of 2 hours or more—are believed to be generally due to extreme subrefractive conditions.

Figure 1. The impact of the tidal fading effect on signal strength [1]

Analysis of synoptic weather conditions and nearby rawinsonde data [1] during four sustained deep fading periods showed atmospheric conditions consistent with extreme subrefraction. A tidal fading effect-based mechanism derived from the research conducted in [2] was therefore constructed.

Figure 2. The effect under the mitigated tidal fading mechanism [2]

The first prototype of the mitigated tidal fading effect mechanism was implemented starting from x.95 firmware, which helps to keep constant signal strength over sustained periods of time by using the slow frequency hopping approach. The frequency that is used by the algorithm is left for the user to choose. The only requirement is to select at least 2 frequencies, preferably with a gap no less than 100MHz between each instance. The signal level threshold must be selected based on the current link conditions.

—

[1] Fade statistics and propagation events at C band for two overwater, line-of-sight propagation paths over a 1-year period – Julius Goldhirsh, G. Daniel Dockery, Bert H. Musiani.

[2] Slow Frequency Hopping for Mitigating Tidal Fading on Rural Long Distance Over-Water Wireless Links – Alex Macmillan, Mahesh K. Marina, and Jhair Tocancipa Triana

In order to find all of the OIDs from a selected device, the Net-SNMP package and the SNMP-walk tool are required.

For Windows users

Step 1. Download it from the Net-SNMP website and install.

Step 2. Open the cmd command prompt window and run the following command:

snmpwalk.exe -c public -v1 -On 192.168.2.66

Step 3. There is also a command for using external MIBs:

snmpwalk.exe -c public -v1 192.168.2.66 MIB [MIB name]

Download the LigoPTP proprietary MIBs from here.

For Linux users

Step 1. Install the SNMP packages:

apt-get install snmp

Step 2. Open the terminal and run the following command:

snmpwalk 192.168.2.66 -c public -v1 . -On

Step 3. To add external MIBs, use the provided command:

snmpwalk 192.168.2.66 -c public -v1 -m /home/LIGO-802DOT11-EXT-MIB.mib

Download the LigoPTP proprietary MIBs from here.

The Statistics page displays detailed statistics on the performance of the LigoPTP link. The Statistics page is divided into two sections: Network statistics and W-Jet statistics

Network statistics displays detailed statistics of the Ethernet and Wireless interfaces:

RX bytes – displays the total number of bytes received through the Ethernet or Wireless interface of the LigoPTP PRO link.
RX packets – displays the total number of packets received through the Ethernet or Wireless interface of the LigoPTP PRO link.
RX errors – displays the total number of corrupted packets received through the Ethernet or Wireless interface of the LigoPTP PRO link.
RX drops – displays the total number of packets dropped by the Ethernet or Wireless interface of the LigoPTP PRO link.
TX bytes – displays the total number of bytes sent through the Ethernet or Wireless interface of the LigoPTP PRO link.
TX packets – displays the total number of packets sent through the Ethernet or Wireless interface of the LigoPTP PRO link.
TX errors – displays the total number of corrupted packets sent through the Ethernet or Wireless interface of the LigoPTP PRO link.
TX drops – displays the total number of packets dropped by the Ethernet or Wireless interface of the LigoPTP PRO link.

W-Jet is an advanced proprietary wireless protocol that combines special techniques to achieve superior performance and reliability, even over long distances. This table displays the statistical counters of the LigoPTP PRO link communication protocol.

MAC address – displays the MAC addresses of the Local and Remote units.
IP address – displays the IP addresses of the Local and Remote units.
TX frames – displays the number of transmitted data frames. The number provided in brackets (+XX) displays the data change since the last page refresh.
RX frames – displays the number of transmitted data frames. The number provided in brackets (+XX) displays the data change since the last page refresh.
TX retry frames % – the percentage of attempts to retransmit data frames. The number provided in brackets (+XX) displays the data change since the last page refresh.

Introduction

New rules

LigoPTP 3 products have been certified under FCC Part 90Z rules. This is a licensed band, which is why the rules differ from Part-15 regarding 900MHz, 2.4GHz, and 5GHz unlicensed radios. First, the power (EIRP) limitations are a little different from part-15. Second, any operators of LigoPTP 3 products must obtain a nationwide 3.65GHz license before operating any equipment. Finally, each individual site must be licensed in the FCC ULS database. For more information on the 3.65GHz licensing process, visit this link.

The main purpose of this article is to outline EIRP restrictions, which LigoPTP 3 products must abide by in order to remain compliant with FCC rules.

Software features

The LigoPTP 3 configuration screen provided below shows a the Antenna Gain (dBi) field. When configuring the LigoPTP 3 radio, the gain of the installed antenna must be entered into this field. Once the gain is entered, the software starts to automatically handle all of the EIRP calculations.

Rules

Maximum values

LigoPTP 3 EIRP rules are based on frequency and channel size. Each combination of the two may have a specific maximum transmit power and EIRP limit that must be complied with. The following is a chart showing the maximum limits based on frequency and channel size.

Following the rules

There are three main rules to keep in mind when changing Tx power and antenna gain.

1. The maximum transmit power cannot exceed the value indicated in the Max Tx Power column provided above, given the frequency and channel size.
2. The EIRP (radio Tx power + antenna gain (dBi) cannot exceed the value indicated in the Max EIRP column provided above, given the frequency and channel size.
3. There is no limit to antenna gain, as long as the EIRP index does not exceed the value the Max EIRP listed above.

The software handles these rules automatically and does not allow the setting of Tx power and/or EIRP higher than what is allowed.

There are two important configuration options used to control these settings: Transmit Power (%), and Antenna Gain (dBi)

When setting the Tx power, the software retrieves the frequency, channel size, and antenna gain and generates a range of valid values from the minimum to the maximum possible. The indicated percentage value will be applied to this range and will output a valid single Tx power setting that will be saved to the configuration.

All of this is performed in the background, automatically eliminating all of the tedious work regarding compliance maintenance.

Introduction

This article is a complete walk-through for users wanting to register and license LigoWave’s 3.65GHz products for use in the United States. The four main steps include:

1. Obtaining an FRN (FCC Registration Number)
2. Obtaining a nationwide 3650 license
3. Examining ULS for nearby 3650 registrations
4. Registering each LigoWave 3.65 radio with ULS

History & rules

In order to stimulate the rapid expansion of broadband services, the FCC has opened the 3650 – 3670 band for terrestrial wireless broadband operations. The band contains a non-exclusive licensing scheme which strikes a balance between an unlicensed approach and an expensive exclusive licensing scheme. Since every fixed station must be licensed, the band will not contain unknown sources of interference (portable phones, SOHO wireless routers, etc). At the same time, the method provides low entry cost and minimal regulatory delay.

For more information on the 3,650–3,670MHz band, follow this link.

Contention-based protocol

LigoPTP 3 products include a restricted contention-based protocol. This means that LigoPTP 3 products are only operable within 3,650–3,675MHz.

3650 cooperation

In order to promote an effective shared use of the spectrum, all 3650 MHz licensees must cooperate and make every effort to avoid harmful interference. There is no first come, first serve rule in this band. If one user has 3650 equipment on a tower, and a competitor wants to install on the same tower, the original user must do what is necessary to work together with the competitor. To facilitate with this process. All radios are licensed in the FCC database (ULS).

Grandfathered satellite earth stations

The 3.65GHz band is also home to a handful of grandfathered FSS (Fixed Satellite Service) operators. In order to protect these band incumbents, then FCC has imposed exclusion zones in which terrestrial broadband operators are not allowed. There are approximately 100 grandfathered earth stations which have 150km circular protection zones. In order to operate these zones approval must be given by the incumbent FSS operator. Additionally, there are three Federal Government radio location stations that have 80km circular protection zones; usage in these zones will only be approved upon successful coordination by the FCC with the NTIA.

The three grandfathered stations are located at:

• St. Inigoes, MD 38 10 00 N 76 23 00 W
• Pascagoula, MS 30 22 00 N 88 29 00 W
• Pensacola, FL 30 21 28 N 87 16 26 W

To see a list of grandfathered stations follow this link.

Obtaining an FRN (FCC Registration Number)

Before applying for a license to operate in the 3.65GHz band in the US, the company or individual applying for the license must obtain an FRN (FCC Registration Number). This is basically the user account for the FCC ULS (Universal Licensing System).

To register an FRN, navigate to the FCC’s official website located here.

Once on the FCC’s website, locate the option FCC Registration Number (FRN) Commission Registration System (CORES) in the main menu (see image). Click on the link to be transferred to the FCC Registration System.

Once in the main menu of the FCC Registration System, select the option to Register and receive your FRN.

In the next form, select the appropriate responses (whether you are filing as an individual or as a corporation). If filing as an individual, you will be required to submit your personal social security number. If filing as a corporation, you will be required to submit your corporate tax identification information.

You will then be directed to a registration form where you will be required to enter registration/contact information for you and/or your organization.

After completing the registration, you will be provided your FRN number. You will need this FRN number in order to apply for licenses, so print or save the form for your records.

 Obtaining a 3.65GHz nationwide license

To apply for a nationwide 3.65GHz license, navigate to the ULS (Universal Licensing System) website located here.

ULS

You will then see the ULS Menu. Since you have already obtained an FRN number, you will want to click the LOG IN option. If you do not have this information, see the section Obtaining an FRN (FCC Registration Number).

On the login screen, enter the FRN number and the password that you have submitted when obtaining the FRN number.

After a successful login, you will be redirected to your license manager. To apply for a new license, click the Apply for a New License option in the menu

New license

The first option asks what type of radio service the new license will accommodate. In this case you need to choose NN – 3650-3700 MHz.

You will then begin the registration process.

Applicant information

The first section requests applicant information. Here you will be asked to enter information such as business/individual information, address, etc.

Contact information

The second section requests corporate/individual contact information.

Application information

The third section marks the beginning of the application information form. In most cases, you will mark no for any exemptions or rule wavers. You also do not need to enter a renewal date, since the 3650 license is good for ten years.

The second part of the third section continues with the application information. On this page, verify that the type of license you are applying for is listed as Nationwide & 3650-3700 MHz.

General information

The fourth section requests general information about the usage of the license. Check each applicable box and continue.

Alien ownership information

The fifth section requests alien ownership information.

Basic qualification information

The sixth section requests basic qualification information.

Summary

The seventh section displays a summary of information provided and displays the fees due to complete the application. Please make sure that all of the information is correct.

Certification

The eighth and final step in the application process is the electronic signature. Make sure you read and understand all of the certification statements before agreeing and signing the document. After signing, press Submit Application to complete the application process.

Confirmation

After submitting the application, continue through the following menus to submit the payment to the FCC. Once the payment is complete, you will be provided with a confirmation of your application’s submission and payment.

You have now completed the application for the 3,650MHz nationwide license. Once the FCC processes and approves the application, you will then be eligible to operate in the 3,650MHz restricted band.

Registering each radio location in ULS

Once the nationwide 3.65GHz license has been obtained, it is then necessary to register each location in the FCC ULS (Universal Licensing System) system.

Logging into the ULS

After logging into the ULS, the Licenses at a Glance section will be displayed. On the right side of the screen, you will see the Work on this License menu. From this menu, select Register Locations.

Locations

Clicking Register Locations will display a list of your current locations. If you are adding a new location, click Add New Location.

Application questions

If you are filing for a waiver of the commission’s rules or need to upload attachments, you can do so here.

Location questions

If there is a possibility that the transmitter may have an environmental effect or if it is located in one of the grandfathered earth station areas, you must enter this info here.

Site data

In this section, you must enter general information about your transmitter’s site and location.

• FCC ASR Number – the antenna structure registration number. If you have already registered this location in the ULS, you can use the previous ASR information you have on file.
• Site Name – a friendly name that you want to have associated with each location.
• Transmitter Latitude – the transmitter’s latitude in minutes-seconds.
• Transmitter Longitude – the transmitter’s longitude in minutes-seconds.
• City – the city that the transmitter resides in.
• County/Borough/Parish – the county, borough or parish that the transmitter resides in.
• State – the state that the transmitter resides in.
• Elevation of the Site AMSL – the elevation of the site (above mean sea level).
• Overall Height AGL Without Appurtenances – the height (above ground level) to the highest point of the supporting structure only (without appurtenances).
• Overall Height AGL With Appurtenances – the overall height (above ground level) of the entire antenna structure to the highest point, including any appurtenances.
• Support Structure Type – the type of structure the transmitter and antenna will be located on.

Transmitter antenna data

This section contains information about the antenna you will be using with LigoPTP 3 products.

• Manufacturer – the manufacturer of the antenna you are using. (If you are using the integrated LigoPTP 3-18, you may indicate LigoWave).
• Model Number – the model number of the antenna you are using. (If you are using the integrated LigoPTP 3-18, you may indicate LigoPTP 3-18).
• Gain – the gain of the antenna you are using (in dBi).
• Beamwidth – the beamwidth of the antenna you are using. For the LigoPTP 3-18, the beamwidth is 22 degrees.
• Center Line – the height (above ground level) of the center of the antenna.
• Azimuth – enter the azimuth of the transmit antenna (in degrees; rounded to one decimal place) clockwise from True North. For omni-directional antennas, indicate the value 360.
• Elevation Angle – the angle of elevation of the antenna.
• Polarization – select from the following values:
  • – E – elliptical
  • – F – 45 degrees
  • – H – horizontal
  • – J – linear
  • – L – left-hand circular
  • – R – right-hand circular
  • – S – horizontal and vertical
  • – T – right and left-hand circular
  • – V – vertical
  • – X – other (provide a description in an attachment)

Equipment data

This section requests more specific information about the radio transmitter.

• FCC ID Number – the FCC ID of the product you are using.
  • For LigoPTP 3 products, it is V2V-PTP3.
  • For LigoPTP 3 R2 products, it is V2V-WMR370.
• Lower/Center Frequency – the lowest frequency you may use at this location.
• Upper Frequency – the highest frequency you may use at this location.
• EIRP – indicate the EIRP (in dBm) radiated by the transmitting antenna.
• Emission Designator – this designates the transmitter bandwidth (5/10/20MHz) and the emission type. Choose from this list of emission designators based on what bandwidth you will be using:
  • For LigoPTP 3 use:
    • 5MHz: 4M14D7D
    • 10MHz: 8M25D7D
    • 20MHz: 16M7D7D
  • For LigoPTP 3 R2 use:
    • 5MHz: 4M24D7D
    • 10MHz: 8M44D7D
    • 20MHz: 17M2D7D
• Modulation Scheme – the modulation scheme you will be implementing (BPSK, QPSK, 16QAM, 64QAM, etc).
• Restricted/Unrestricted protocol – LigoWave LigoPTP 3 uses a restricted protocol, meaning it can only operate in 3,650-3,675MHz.
• Name of transmission protocol – Select Other
• Description of transmission protocol – in this field, you can enter choose one of the following: Dynamic TDD with Selective Repeat ARQ. Carrier Sense Multiple Access with Collision Avoidance for sensing clear wireless medium.

Summary

This section displays a summary of information provided and shows the fees due to complete the application. Please make sure that all of the information is correct.

Confirmation

If everything is accepted, you will see a confirmation page acknowledging that your application has been submitted. Please allow 2–3 days for the registration to be officially complete.

Newest LigoWave PTP models:

• LigoPTP 5 Unity: FWBD-1404
• LigoPTP 5 PRO: FWBD-1400
• LigoPTP 5 MiMo: FWBD-0100

Legacy LigoWave models

Due to hardware revisions, there was few different firmware versions to choose from. Depending on which hardware revision you have, you will want to load the latest appropriate image.

There are two different models of LigoPTP 5 and LigoPTP 5 R2:

• WILIBOARD
• WBD422

Follow these steps to run the LigoWave Reset Tool and to reset the device to its default factory settings:

Linux OS

The package should be installed by running the following command (Ubuntu/Debian version):

sudo apt-get install sun-java6-jre

Afterwards, click the right mouse button on the Reset Tool file and select Open with Sun Java 6 Runtime from the context menu.

Windows 7 OS

A shortcut with the following data must be created on the Windows 7 operating system:

General path: %ProgramFiles%\Java\jre6\bin\java.exe" -jar "%HOMEPATH%/Desktop/reset-tool.en.v1.2.45019.20121109.2143.jar

Example: "C:\Program Files (x86)\Java\jre7\bin\java.exe" -jar "C:\Users\tester\Desktop\reset-tool.en.v1.2.45019.20121109.2143.jar

Once the shortcut is created, it must be executed with administrative privileges enabled by right-clicking on it and selecting the option Run as Administrator from the context menu.

Step 1. Download the Reset Tool to your computer from the official LigoWave website here.

Step 2. Run the executable file. The Reset Tool will launch:

Step 3. Click Scan to search for all LigoWave devices available on the network:

Step 4. Select the necessary device and press Reset:

Step 5. The Reset Tool will notify the administrator when to physically turn off and turn on the device:

Step 6. Physically turn off and then turn on the device.

Step 7. The device will now wait for the special reset packet. Once the special reset packet is received, the LigoWave device will wait for 300 seconds to verify the reset procedure:

Step 8. Physically turn off and then turn on the device once more.

Step 9. The LigoWave device will reboot and reset to its default settings:

Step 10. The LigoWave device has now successfully been reset to its default factory settings.

Step 11. The LigoWave device should now be configured under its default factory settings. Click the right mouse button on the appropriate device and launch the GUI:

Dynamic algorithm

A dynamic algorithm (or auto data rate) is when a data rate is selected automatically by the mechanism that evaluates the performance of the device based on the current signal level, rate of data packet retry, and other relevant parameters.

Data rate fallback is the reduction of the data rate. When it is operating in Normal mode, it gradually reduces the modulation and coding scheme (MCS) until the data can pass through. When the data rate fallback is set to Aggressive, the MCS is decreased by 2 steps until it can pass the data through. The dynamic algorithm and aggressive fallback have to be used in noisy environments.

Fixed algorithm

A fixed algorithm is when a data rate is a fixed value (MCS).

The main difference between the dynamic algorithm and the fixed algorithm is that the fixed algorithm will always try to send data under the selected MCS rather then decreasing the currently selected MCS to the value at which the retry rate is lower.

The fixed algorithm does not take into account signal level or the amount of retried packets.  The data rate is only decreased when the device cannot send the current data at the fixed data rate. The data rate fallback mechanism turns on in such a case.

Data rate fallback operating in Normal mode gradually reduces the MCS until the data can pass through. When the data rate fallback is set to Aggressive, the MCS is decreased by 2 steps until it can pass the data through. A fixed data rate is best suited for operation in clean radio environments.

Follow these steps to access the LigoPTP device for the first time:

Step 1. Configure your PC using a static IP address on the 192.168.2.0 subnet (e.g. 192.168.2.10 with mask 255.255.255.0).

Step 2. Open a web browser and enter the default IP address of the AP device—192.168.2.66:

Step 3. Once the login page is loaded, enter the default administrator login information (login: admin; password: admin01) and click Login:

Step 4. Agree to the disclaimer of the LigoPTP device. Regulatory domain settings may differ depending on the selected operating country. Users are not allowed to select radio channels and RF output power values other than the permitted values for their respective country and regulatory domain:

Follow these steps to upgrade your device’s firmware:

Step 1. To update your device’s firmware, navigate to the Configuration > Maintenance menu:

Step 2. Press Upload firmware and select the firmware file from your computer:

Step 3. Once the firmware is successfully uploaded onto the LigoWave device, click Upgrade:

The troubleshooting file is an extremely useful resource for the technical support team as it contains valuable information about the device’s configuration, routes, log files, command outputs, and other important information.

Follow these steps to download the troubleshooting file via the GUI:

Step 1. Log in to the LigoPTP GUI via a web browser:

Step 2. To download the troubleshooting file, navigate to Configuration > Maintenance:

Step 3. Click the Download button next to Download troubleshooting file:

Step 4. The troubleshooting file should now be downloaded to your computer:

The Reset Tool allows administrators to discover all LigoWave devices present in the local area network and to easily restore the default configurations of these devices.

Follow these steps to discover LigoWave device in the network:

Step 1. Download the Reset Tool to your computer from here.

Step 2. Run the executable file. The Reset Tool will launch:

Step 3. Click Scan to search for all LigoWave devices available on the network:

Step 4. The Reset Tool will now display all LigoWave devices available on your network. The scanned devices will now be ready to be managed:

Command Line Interface Management

The Command Line Interface, or CLI, software is a configuration shell for LigoPTP devices. CLI is an alternative way of configuring the device. It is not intended to be the main device management method. Using CLI, the operator can test the authentication parameters, change the administrator’s password, reboot the device, reset the device to its default settings, see the device configuration, or view the device status.

CLI Access

Use the SSH client application (e.g. Putty) to access the CLI of the WILI-S-based device.

Login

Enter the administrator login information as displayed in the command prompt.

Default administrator login information:

• User Name: admin
• Password: admin01

After a successful login, enter the help command to get the list of available CLI commands:

help

List off all CLI commands:

logout
reboot
reset-to-defaults
ping <ip>
telnet <ip>
show config
save config
show gateway
set gateway <gateway>
show software version
shell
linktest [frames <packet count>] [pkt-size <packet size>] [sessions <sessiont>] [peer <peer number>] [ip <remote IP>]
show interface list
show interface <interface> mac
show interface <interface> ip
set interface <interface> ip <ip/subnet mask>
show interface <interface> wireless-mode
set interface <interface> wireless-mode <ap, station>
show interface <interface> ssid
set interface <interface> ssid <ssid>
show interface <interface> ssid-broadcast
set interface <interface> ssid-broadcast
no interface <interface> ssid-broadcast
show interface <interface> security
set interface <interface> security <open, wpa2-psk>
        wpa2-psk encr aes pass <pass>
show interface <interface> channel
set interface <interface> channel <channel>
set interface <interface> channel-auto <channel,channel,...>
set interface <interface> txpower <txpower>
set interface <interface> up
set interface <interface> down
show interface <interface> peers
set interface <interface> vlan <vlan id>
no interface <interface> vlan <vlan id>

Examples of how to use CLI commands:

To change the wireless security setting, type the following command and press the Enter key:

set interface ra0 security open

To view what channels the radio is working on, type the following command and press Enter:

show interface ra0 channel

To check the current radio SSID, type the following command and press Enter:

show interface ra0 ssid

Type logout to leave the CLI mode:

logout

The following steps should be performed to identify the maximum packet size that can be sent between devices:

Equipment for testing:

Linux PC 1 and Linux PC 2 (Cisco switches can also be used instead of PCs).

Once the wireless link is connected, make sure that the ping works by sending small packets using the following command:

ping remote_device_ip

If a ping response is received, change the Linux PC Ethernet interface MTU size with the following command:

ifconfig eth0 mtu 3500

In the provided example, the network interface is called eth0. However, it can be named eth1 or any similar name on other machines.

Once the MTU value is changed on both Linux PCs, run the ping command with the attributes -M do to send the packet without any fragmentation because the ping function performs fragmentation by default.

When using a remote Linux PC, you can run the tcpdump tool. See the screenshot bellow:

The recommended signal level range for optimum performance is from –35dBm to –60dBm. Links may also work with lower signal level modulations ranging from –60dbm to –85dBm.

The power source LED light typically blinks when there is a problem with the radio circuit. If a new PoE does not solve the problem, change the radio to a new one. Contact your distributor regarding unit repair.

There are a few simple steps for testing device configurations indoors or at very short distances between radios.

To test devices with N connectors, use RF cables with 50–60dB attenuators.

If the devices have integrated antennas, indoor tests should not be performed due to bad results from signal reflections. When choosing to test indoors, minimize possible damage by following these guidelines:

Set Tx power to 0.

Have both units facing the ceiling or ground. Check the signal levels which should be around -50dBm.

The default IP address is 192.168.2.66 with a subnet mask of 255.255.255.0.

The default username is admin and the default password is admin01.

Devices that are missing the reset button and devices with a reset button that is only accessible by disassembling the housing require an external process for easy reset to default factory settings—the ping reset method.

The discovery daemon is launched during device startup—once the Ethernet interface drivers are loaded. The daemon suspends the startup process for 3 seconds and waits for the ICMP echo request packet of 369 bytes. If the packet is received, the discovery daemon resets the device to its default configuration.

For Linux users, follow these steps in order to reset to the device to its default settings:

Step 1. Turn the device off.

Step 2. Obtain the device’s MAC address.

Step 3. Connect a PC to the same physical subnet as the device.

Step 4. Execute the arp -s command to assign the IP address (the IP address should be from the same subnet as the PC) to the device’s MAC address:

arp -s <IP address to assign> <device MAC address>

Step 5. Start pinging the device:

ping <IP address> -s 369

For Windows users:

ping <IP address> -l 369 -t -w 200

Step 6. Power up the device and wait for about 1 minute or more (depending on the device hardware).

Step 7. Stop pinging the device and let it boot up as usual. The device should boot with its default settings.

Introduction

There may be cases when it is beneficial or even necessary to update the firmware on a device without using the web browser. It is possible to update the firmware by using SSH and the fwupdate command. This article serves as a walk-through for getting the image onto the device and then flashing it.

Getting the image onto the device

The first step of flashing an image in the shell is getting the firmware image onto the device. There are two easy ways to do this: using SFTP to upload the image onto the device, or using wget from the device to download the image from an external source.

Instructions for Windows users

Step 1. Run WinSCP. Fill out the following fields:

Host name – device IP address (default 192.168.2.66)
Username – admin
Password – device login password (default: admin01)
Press Login to initiate an SSH connection to the device.

Step 2. In the next window, go to the /tmp directory. Then copy the fwupdate.bin file to the /tmp directory.

Step 3. Run PuTTY. In the Host Name field, type the device’s IP address and press Open.

Step 4. Type in the username and the password in the next window.

Username – admin
Password – device’s password (default: admin01)

 Step 5. Type in the shell command and press Enter. You are now ready to start the firmware upgrade.

shell

Step 6. Navigate to the /tmp directory.

cd /tmp

Step 7. Rename the previously uploaded file to fwupdate.bin.

mv LIGO-PTP.FWBD-1400.v6.94-3.rt3883.LIGO.PTP.en_US.47840.130820.0352.img fwupdate.bin

Step 8. TType the command fwupdate –m to start the firmware upgrade.

fwupdate -m

 Step 9. If the start of the upgrade is successful, a message will appear regarding the start.

/sbin/fwupdate: About to run firmware update

Step 10. Once the firmware upgrade is complete, the device should respond to a ping using the configured IP address.

Instructions for Linux users

Download the latest firmware and open the Terminal.

Step 1. Rename the downloaded firmware to fwupdate.bin.

mv LIGO-PTP.FWBD-1400.v6.94-3.rt3883.LIGO.PTP.en_US.47840.130820.0352.img fwupdate.bin

Step 2. Copy the firmware image to the device’s /tmp directory.

scp /home/fwupdate.bin [email protected]:/tmp

Step 3. Log onto the device using SSH.

ssh [email protected]

Username – admin

Password – device’s password (default: admin01)

Step 4. Type the shell command and press Enter.

shell

Step 5. Type in the command fwupdate –m to start the firmware upgrade.

fwupdate -m

Step 6. Once the firmware upgrade is complete, the device should respond to a ping using the configured IP address.

LigoPTP 5/4/3/2 and LigoPTP 5 MiMo support packet sizes of up to 1,800 bytes without any external configuration.

LigoPTP 5 PRO supports packet sizes of up to 3,794 bytes without any external configuration.

LigoPTP 5 UNITY supports packet sizes of up to 3,734 bytes without any external configuration.

LigoPTP 620 HP supports packet sizes of up to 10,000 bytes.

LigoPTP 620 S supports packet sizes of up to 1,632 bytes without any external configuration.

Introduction

Starting with firmware version 6.93, LigoPTP devices will be equipped with firmware recovery functionality. Only newly purchased products with firmware version 6.93 or later will have firmware recovery via TFTP functionality (note that the usual LigoPTP upgrade from older versions to 6.93 will not add the recovery feature).

As of firmware version 6.94-6, the recovery feature is introduced with the firmware upgrade. This applies only to the PRO series.

Products that may need a firmware recovery procedure:

• LigoPTP PRO series
• LigoPTP UNITY series (it has two firmware images, making it difficult to damage both)

When is recovery required?

Recovery is required when the firmware installed on the device’s flash memory becomes corrupted. This happens when the device is turned off during a firmware upgrade (e.g. power cuts, cable problems, etc). When the device cannot boot, it goes into recovery mode.

If the device is not accessible over the web, there is no ping response, and the Reset Tool cannot find the device, perform the firmware recovery procedure.

Firmware recovery using TFTP

Step 1. Download, install, and run a TFTP server on your PC.

TFTP Windows:

TFTPD-HPA for Linux:

Use a command from the Linux shell:

 sudo apt-get install tftpd-hpa

Step 2. Download the newest appropriate firmware from the LigoWave website here.

Step 3. Rename the downloaded firmware file to fwupdate.bin and move it to the TFTP server directory.

Step 4. Turn the device off.

Step 5. Connect the device to a PC directly or through a switch using a cable.

Step 6. Set the PC network adapter IP address to 192.168.2.1 (it must be a TFTP server address).

Step 7. Turn on the device. If everything is configured correctly, the TFTP server will notify about the firmware transfer.

Step 8. Wait 5 minutes or less until the firmware is properly flashed.

Step 9. Once firmware recovery is complete, the device should respond to a ping under its configured IP address.