XUELK-TN-001: Configuring SBC Lynx as industrial router

From DAVE Developer's Wiki
Revision as of 15:00, 9 August 2016 by U0001 (talk | contribs) (Implementation)

Jump to: navigation, search

Introduction[edit | edit source]

Nowadays IP networks are become popular in industrial environments. To limit infrastructure costs, these networks are often built ased on-trivial routing configurations are needed

This article shows how to configure SBC Lynx to implement a router that manages data packet forwarding between two different LANs.

Network topology[edit | edit source]

The following image shows a simplified block diagram of the network topology that has been used for testing this configuration.

There are two LANs:

  • main LAN (
  • secondary LAN (

The following devices are connected to these LANs:

  • a PC connected to the main LAN (IP address =

2) main LAN switch 3) SBC Lynx equipped with two Ethernet interfaces a) primary interface (eth0) connected to main LAN (IP address = b) secondary interface (eth1) connected to secondary LAN (IP address = [1] 4) secondary LAN managed switch (IP address = 5) WiFi access point connected to secondary LAN (IP address =

Secondary LAN managed switch and access point integrate a web server, accessible at port 80. Two IP forwarding rules have been be set up in order to make web servers accessible at and

  • <->
  • <->

[1] For simplicity, secondary interface has been implemented with an USB/Ethernet adapter (TBD) connected to USB port. For a real-world production environment, it is recommended the use of both iMX6UL Ethernet MAC controllers. To do that, a plugin board connected to the one piece connector (J45/J52) can be used. For more details please refer to sales department.

Implementation[edit | edit source]

To enable routing functionality, the well known netfilter/iptables packet filtering framework has been added and configured to default software provided along with XUELK.


Enabling logging[edit | edit source]