EnBoard1

EnBoard1 is an embedded processor board

with popular network and I/O interface support.
Leveraging existing industry ecosystem,
customer will be able to launch its own product
in shortest timewith minimum effort. With on
board dual mini-PCI slots, 802.2af PoE and
serial port,
EnBoard1 is perfect choice for enterprise-level
dual-band AP/Router supporting Wi-Fi, WiMAX
and Mesh.
The combination of EnBoard1 and IkarusOS,
makes this a powerful WiFi device for WISP.

 IkarusOS is a network services operating

system which turns an embedded based system
into a dedicated (WI-FI) router.
IkarusOS enabled deployments are easily
configured provisioned and monitored through
IkarusOS Manager which is a software
application that provides real-time visibility and
control of all IkarusOS based systems of the
network.
The complete administration and configuration
of IkarusOS systems is done through IkarusOS
Manager executed from any platform that
support Java

Step by Step Wireless Bridge Setup

Below you can see a picture of the INMS user interface

Q&A

Step 1: Create a new bridge with name br0.

Step 2: Select interface eth0, add eth0 to br0.

Step 3: Select interface ath0, add ath0 to br0.

Step 4: Submit your changes.

Step 5: Save your configuration.

Note: After the base station is configured, the configuration parameters are
stored in RAM (volatile memory). If the base station is powered down the
configuration will be lost unless you Save Configuration to the base stations
permanent memory.

Simple Wireless Point to Point Scenario

Prerequisites
You will need 2 devices with IkarusOS loaded.

Configuration Steps
Step 1: Follow the Step By Step Wireless Bridge Setup example and create 2 wireless bridges.
Step 2: Configure the 1st device to operate in Access Point Mode.

Select Access Point from the Select Operational Mode Drop Down Menu.
Insert an essid string in the SSID box.

Click the Submit button

Step 3: Configure the 2nd device to operate in Access Point Client Mode and perform a Site Survey
action.
Select Access Point Client from the Select Operational Mode Drop Down Menu.
Click the Site Survey button

Step 4: Connect with the desired Access Point.

Select the desired ESSID from the Site Survey Pop-up Menu.
Click the Connect button.

As soon as the devices get connected the connection status bar inform you about the link's quality and
the Signal's Level.

Firewall Scenarios

Example: Forward Reject

You will need 2 devices setted up with latest Ikarus O.S version. Beside each node a PC should exist.

Host PC1: ip1

AP Mode:ip2

Host PC2:ip3

AP Client Mode:ip4
1.
2.
3.
4.
5.
6.

7.
8.
9.

Open the INMS

Right click to the AP node and choose "Advanced node configuration"
Choose "Firewall" tab from the horizontal third row of tabs
From the top pane next to labels "Chain" and "Policy" select "FORWARD" and "ACCEPT"
respectively.
Press the button with the "+" sign.
In the pop-up window Insert in textboxes "Source IP", "Destination IP"

Source IP: ip1

Destination IP: ip3

From dropdown list next to "ACTION" select "REJECT".

Go to "Advanced" Tab and from the dropdown list next to "Protocol" label select "UDP"
protocol.
Select all the checkboxes in "Connection State" panel
Click the button with "check" sign.

Example: Input Drop

You will need 2 devices setted up with latest Ikarus O.S version.
You will also need to install the latest INMS Manager version.
1.
Open the INMS
2.
Right click to the AP node and choose "Advanced node configuration"
3.
Choose "Firewall" tab from the horizontal third row of tabs
4.
From the top pane next to labels "Chain" and "Policy" select "INPUT" and
"ACCEPT" respectively.
5.
Press the button with the "+" sign.
6.
In the pop-up window Insert in textboxes "Source IP", "Destination IP" the IPs of AP
client and AP respectively and from dropdown list next to "ACTION" select "DROP".
7.
From the "advanced" tab next to protocol dropdown list select "protocol" ICMP
8.
Click the button with "check" sign.
Example: Output Reject
You will need 2 devices setted up with latest Ikarus O.S version.
You will also need to install the latest INMS Manager version.
1.
Open the INMS
2.
Right click to the AP node and choose "Advanced node configuration"
3.
Choose "Firewall" tab from the horizontal third row of tabs
4.
From the top pane next to labels "Chain" and "Policy" select "OUTPUT" and
"ACCEPT" respectively.
5.
Press the button with the "+" sign.

6.

7.

In the pop-up window Insert in textboxes "Source IP", "Destination IP" the IPs of AP and of the
subnet the network is setted up (e.g. 192.168.1.0/24) respectively and from dropdown list next
to "ACTION" select "REJECT".
Go to "Advanced" Tab and from the dropdown list next to "Protocol" label select "TCP" protocol

8.

Click the button with "check" sign.

NAT Scenarios

Prerequisite Steps

Make the configuration of the above image.

Setup HTTP Server
Setup FTP Server
Setup SIP Server

From any PC of Private Subnet 192.168.5.x/24 you should be able to ping eth0 of AP Mode.

Start Ikarus OS Manager and Insert AP in the Topology Map.

Right click to the Access Point node of the network topology and choose from the arised list
Advanced Network Configuration

From the third row of tabs choose "NAT"

SNAT Configuration

From the top frame next to label "NAT kind" choose "SNAT" and click to the button with the "+"
sign.

Fill the fields as below.

Click the "submit" button and then the "tick" button to apply changes.
Try to ping from any Server behind the switch to ath0 of AP Mode.
Try to ping from any Server behind the switch to any HOST PC which is connected to AP Client
Mode.
The connection is established although you can not ping from any HOST PC to any Server.
In order to make this happen, we need the appropriate DNAT rule.

DNAT Configuration

Right click to the Access Point node of the network topology and choose from the arised list
Advanced Network Configuration

From the third row of tabs choose "NAT"

From the top frame next to label "NAT kind" choose "DNAT" and click to the button with the "+"
sign.

Fill the fields as below.

Click the "submit" button and then the "tick" button to apply changes.
Try to ping from any Host PC behind the switch to any Server.
The connection is established
For HTTP you should add another DNAT rule and specify in "Traslate Dest IP To" the ip of HTTP
Server, Destination Port 80 and in "Translate Port To" 80-80.
For FTP you should add another DNAT rule and specify in "Traslate Dest IP To" the ip of FTP
Server, Destination Port 22 and in "Translate Port To" 22-22.
For SIP you should add another DNAT rule and specify in "Traslate Dest IP To" the ip of SIP
Server, Destination Port 5060 and in "Translate Port To 5060-5060.