Changes

Jump to: navigation, search

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

1,581 bytes added, 14:41, 9 August 2016
Created page with "==Introduction== Nowadays IP networks are become popular in industrial environments. To limit infrastructure costs, these networks are often built ased on-trivial routing con..."
==Introduction==
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==
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 (192.168.0.0/24)
* secondary LAN (192.168.11.0/24).

The following devices are connected to these LANs:
*a PC connected to the main LAN (IP address = 192.168.0.28)
2) main LAN switch
3) SBC Lynx equipped with two Ethernet interfaces
a) primary interface (eth0) connected to main LAN (IP address = 192.168.0.209)
b) secondary interface (eth1) connected to secondary LAN (IP address = 192.168.11.209) [1]
4) secondary LAN managed switch (IP address = 192.168.11.239)
5) WiFi access point connected to secondary LAN (IP address = 192.168.11.241)

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 192.168.0.209:80 and 192.168.0.209:8080:
*192.168.0.209:80 <-> 192.168.11.241:80
*192.168.0.209:8080 <-> 192.168.11.239:80

[1] For simplicity, secondary interface has been implemented with an USB2Ethernet adapter (TBD). For a real-world production environment it is recommended the use of the iMX6UL

==Implementation==
===Enabling logging===
4,650
edits

Navigation menu