How to configure NAT 1to1 on the OpenBAT - 1
How to configure NAT 1to1 on the OpenBAT
[19.11.2015]
This lesson describes step by step how to configure NAT 1to1 on OpenBAT frequently used in
several train to ground applications.
We'll use for that a simple example:
A BAT configured as Access Client (Train) connected on a BAT configured as Access point
(Ground).
On the BAT client (Train) Laptop1 is connected to ETH-1
IP address: 192.168.1.29 | Mask: 255.255.255.0 | GW: 192.168.1.1
On THE BAT AP Laptop2 is connected to ETH-1
IP address: 10.3.110.19 | Mask: 255.255.255.0 | No gateway
When devices in the train communicates with devices on the Ground, there address is translated
into the ground IP range.
In our example, 192.168.1.29 is tranlated into 10.3.110.29
As the NAT configuration is done on the client only, this lesson describes only the client
configuration
LANconfig is used as configuration tool.
Rel 9.10 at least is required on the OpenBAT client
Representation
How to configure NAT 1to1 on the OpenBAT - 2
System Design OpenBAT
The scheeme above represents the internal system design of the HilCOS products.
NAT is only possible between a LAN and a WAN interface. Given that the OpenBAT doesn't have a
dedicated WAN interface (a physical DSL port for example) we'll have to define a physical LAN or
WLAN interface as WAN interface assigning it a DSL usage.
Without this system design view, the configuration may seem tricky (why go in DSL settings to
configure NAT ???) but actually it is logical if we have in mind this view similar to all HiLCOS
products, knowing that the OpenBAT doesn't have a fixed WAN interface.