FLUIDMESH ACADEMY

A New Standard for Wireless Connectivity in IOT and Machine Automation

Layer 3 Fluidity

POWERFUL WIRELESS BACKHAULING Copyright © 2005-2020 Fluidmesh Networks, LLC.

 FLUIDITY LAYER 3

Layer 3 Fluidity

• Fluidity Layer 3 enables seamless handoff between a vehicle and wayside base stations / radios that belong to different subnets.
• A vehicle would be able to move between multiple wayside network clusters, each cluster belonging to a different network /
subnet, without losing end to end connectivity to the core network during handoff.
• This is achieved with the use of L2TP tunnels between the Mesh End at each network cluster/site, and a Fluidmesh Gateway
device located at the network core called a Global Gateway.
• Each Global Gateway has a L2TP tunnel connection to each Mesh End at each network cluster / subnet, which allows MPLS
routing to take place at the Global Gateway rather than conventional layer 3 routing.

POWERFUL WIRELESS BACKHAULING Copyright © 2005-2020 Fluidmesh Networks, LLC.

 Onboard Server
Layer 3 Fluidity enables full scalability across multiple Onboard Router 172.30.128.1/29 IP: 172.30.128.2/29
networks deployments/sites that are miles apart, Default Route: DG: 172.30.128.1
whether connected by private fiber optic or crossing 0.0.0.0 -> 10.42.0.6
10
.42
.0.
Vehicle
1/
public domain (ISP). Fluidity Layer 3 sits on top of 29
existing networks and ‘flattens’ subnets via L2TP
Onboard Switch
encapsulations between the Global Gateways and
the Mesh Ends at each site, allowing seamless routing FM4500 FM4500
and end to end connectivity for a vehicle moving IP: 10.42.0.2/29 IP: 10.42.0.3/29
between multiple networks back to the core network. DG: 10.42.0.1 DG: 10.42.0.1
Static Route: Static Route:
172.30.128.0/29 Virtual IP: 10.42.0.6 172.30.128.0/29

Wayside Subnet A
DG: 10.42.0.1 DG: 10.42.0.1
Wayside Subnet (n)
FM3500 Mesh End FM3500 Mesh End FM3500 Mesh Point FM3500 Mesh Point FM3500 Mesh End FM3500 Mesh End FM3500 Mesh Point FM3500 Mesh Point
IP: 192.168.200.10/24 IP: 192.168.200.12/24 IP: 192.168.200.15/24 IP: 192.168.200.16/24 IP: 192.168.201.10 IP: 192.168.201.12 IP: 192.168.201.15 IP: 192.168.201.16
DG: 192.168.200.1 DG: 192.168.200.1 DG: 192.168.200.1 DG: 192.168.200.1 DG: 192.168.201.1 DG: 192.168.201.1 DG: 192.168.201.1 DG: 192.168.201.1
L2TP: 192.168.200.210 L2TP: 192.168.200.212 L2TP: 192.168.201.210 L2TP: 192.168.201.212
Virtual IP: 192.168.201.14
Virtual IP: 192.168.200.13

18 FM10000 FM10000
2.0/ IP: 192.168.20.2/24 IP: 192.168.20.3/24
.19
.168 DG: 192.168.20.1 DG: 192.168.20.1
Core Router 2
19 L2TP: 192.168.20.12 L2TP: 192.168.20.13

172.20.128.1 192.168.20.1
Core
Core Server Routes:
IP: 172.20.128.2/29 Static Route: 172.30.128.0/29 -> 192.168.20.4
DG: 172.20.128.1 Static Route: 10.42.0.1 -> 192.168.20.4 Virtual IP: 192.168.20.4

POWERFUL WIRELESS BACKHAULING Copyright © 2005-2020 Fluidmesh Networks, LLC.

 FLUIDITY LAYER 3

Layer 3 Fluidity Key Concepts

• Communication between Wayside subnets and Global Gateway network is provided by the customer routed IP network.
• Communication between Global Gateway network and vehicle networks goes through the MPLS and L2TP tunnels.
• Each radio network on the wayside needs at least a Mesh End. These networks shall be configured on different broadcast
domains.
• Fluidmesh Radios onboard the vehicle should be configured with a static route of each local subnet on the vehicle. This allows the
vehicle to advertise these addresses back to the network core (Global Gateway) for network convergence.
• The IP address of the on-board router should be used to configure the default gateway of the vehicle radios.
• Each Global Gateway, Mesh End, and Vehicle Radio should be configured with TITAN to enable redundancy at the core and
prevent network outage in case on of the units has a failure.
• Each Global Gateway should be configured to connect to the L2TP WAN address of each Mesh End.

POWERFUL WIRELESS BACKHAULING Copyright © 2005-2020 Fluidmesh Networks, LLC.

 FLUIDITY LAYER 3

Layer 2 Tunneling Protocol Encapsulation

Layer 2 Tunneling Protocol (L2TP) wraps around

or encapsulates the original IP payload, creating
what is referred to as a tunnel – because it
creates a new end to end connection within an
existing network. As seen in the illustration, the
packet highlighted in blue is encapsulated by L2TP,
creating a tunnel. With Fluidity Layer 3, this new
end to end connection is created between the
Global Gateways and the Mesh Ends.

POWERFUL WIRELESS BACKHAULING Copyright © 2005-2020 Fluidmesh Networks, LLC.

 RACER Configuration – Global Gateway

FM10000

POWERFUL WIRELESS BACKHAULING Copyright © 2005-2020 Fluidmesh Networks, LLC.

Layer 3 Fluidity RACER Configuration – Global Gateway

Create a name for the Template, usually a name that relates

to device network role / function.

Select device type. In this case the FM1000/FM10000 for

Global Gateway role

Create a configuration template for the device. Templates are configuration settings that will be applied to the respective devices.

POWERFUL WIRELESS BACKHAULING Copyright © 2005-2020 Fluidmesh Networks, LLC.

Layer 3 Fluidity RACER Configuration – Global Gateway

For a layer 3 Fluidity Network, configure the FM10000 /

FM1000 as a Global Gateway.

Shared passphrase should be the same across all Fluidmesh

Devices.

Configure the IP Address and subnet for the device

Configure the default gateway for traffic being routed to and

from the gateway.

Enter DNS Address for the network if applicable

POWERFUL WIRELESS BACKHAULING Copyright © 2005-2020 Fluidmesh Networks, LLC.

Layer 3 Fluidity RACER Configuration – Global Gateway

VLAN should be disabled for Layer 3 Fluidity

Applications. Packets are expected to be sent with no
.1q tagging.

Configure unit as an infrastructure device

Configure network type as multiple subnet to enable

Layer 3 Fluidity Function

Disable it if the radios within the subnets are daisy-chained

(ring topology) otherwise LNO can be enabled.

POWERFUL WIRELESS BACKHAULING Copyright © 2005-2020 Fluidmesh Networks, LLC.

Layer 3 Fluidity RACER Configuration – Global Gateway

Set Enable L2TP to the ON option to activate the L2TP Feature

This is the unique WAN IP Address of the local device that will
be used when forming a L2TP Tunnel with the Mesh End.

IP Address of the Default Gateway

Maximum number of L2TP Tunnels

Enter the WAN IP Address and port number of each Mesh

End device. A pop out window will appear.

POWERFUL WIRELESS BACKHAULING Copyright © 2005-2020 Fluidmesh Networks, LLC.

Layer 3 Fluidity RACER Configuration – Global Gateway

Enter the WAN IP Address and port number of each Primary

and Secondary Mesh End device on each subnet.

POWERFUL WIRELESS BACKHAULING Copyright © 2005-2020 Fluidmesh Networks, LLC.

Layer 3 Fluidity RACER Configuration – Global Gateway

To enable the failover redundancy function, Fast Failover should be

enabled. A TITAN License is required for this feature.

Configure timeout for the gateway failure detection in milliseconds

Configure the virtual IP. Use the same address for the primary and the
secondary gateway. The virtual IP must be different from the
management IP and the L2TP WAN IP addresses chosen for the devices.

The Preempt Delay prevents the primary gateway to come back online
after a failure as soon as it is booted. This delay allows the primary
gateway to learn network information (ARP, IPs, …) from the active
secondary gateway before being back as primary gateway of the
network.

POWERFUL WIRELESS BACKHAULING Copyright © 2005-2020 Fluidmesh Networks, LLC.

Layer 3 Fluidity: Global Gateway

Wayside
Key Parameters
Device Mode: Global Gateway
Fluidity Role: Infrastructure
FM TITAN: Enabled
Virtual IP: 192.168.20.4
L2TP IP: 192.168.20.12
Default Gateway: 192.168.20.1 Mesh Point Radios

Both Global Gateways should be configured with FM TITAN enabled, allowing the use of a Virtual IP to be configured. This allows the network to stay converged in the event of a hardware
failure of one of the devices, the secondary Mesh End will seamlessly take over. Additionally, the L2TP address of each Mesh End should be entered in list format on each Global Gateway to
build the L2TP tunnel from the Global Gateway to each site.

POWERFUL WIRELESS BACKHAULING Copyright © 2005-2020 Fluidmesh Networks, LLC.

 RACER Configuration – Mesh End

FM1000

POWERFUL WIRELESS BACKHAULING Copyright © 2005-2020 Fluidmesh Networks, LLC.

Layer 3 Fluidity RACER Configuration – Mesh End

Create a name for the Template, usually a name that

relates to device network role / function.

Select device type. In this case the FM1000/FM10000 for

Mesh End role

POWERFUL WIRELESS BACKHAULING Copyright © 2005-2020 Fluidmesh Networks, LLC.

Layer 3 Fluidity RACER Configuration – Mesh End

For a layer 3 Fluidity Network, configure the FM1000 as

a Mesh End for the different cluster.

Configure the IP Address and subnet for the device

Configure the default gateway for traffic being routed

to and from the Mesh End.

Enter DNS Address for the network if applicable

Shared passphrase should be the same across all

Fluidmesh Devices.

POWERFUL WIRELESS BACKHAULING Copyright © 2005-2020 Fluidmesh Networks, LLC.

Layer 3 Fluidity RACER Configuration – Mesh End

VLAN should be disabled for Layer 3 Fluidity

Applications. Packets are expected to be sent with no
.1q tagging.

Configure unit as an infrastructure device

Configure network type as multiple subnet to enable

Layer 3 Fluidity Function

Enable if (and only if) the cluster units or subnets are daisy-
chained (ring topology), Otherwise LNO must be disabled.

POWERFUL WIRELESS BACKHAULING Copyright © 2005-2020 Fluidmesh Networks, LLC.

Layer 3 Fluidity RACER Configuration – Mesh End

To enable the failover redundancy function, Fast Failover should be

enabled. A TITAN License is required for this feature.

Configure timeout for the Mesh End failure detection in milliseconds

Configure the virtual IP. Use the same address for the primary and the
secondary Mesh End. The virtual IP must be different from the
management IP and the L2TP WAN IP addresses chosen for the devices.

The Preempt Delay prevents the primary Mesh End to come back online
after a failure as soon as it is booted. This delay allows the primary Mesh
End to learn network information (ARP, IPs, …) from the active secondary
Mesh End before being back as primary Mesh End of the subnet.

If enabled forces on-board client devices to be reached via the mobile

master. If disabled allows on-board client devices to be connected
directly to mobile slaves.

POWERFUL WIRELESS BACKHAULING Copyright © 2005-2020 Fluidmesh Networks, LLC.

Layer 3 Fluidity RACER Configuration – Mesh End

Set Enable L2TP to the ON option to activate the L2TP Feature

This is the unique WAN IP Address of the local device that will
be used when forming a L2TP Tunnel with the Mesh End.

IP Address of the Default Gateway

Maximum number of L2TP Tunnels

Enter the WAN IP Address and port number of each Global

Gateway. A pop out window will appear.

POWERFUL WIRELESS BACKHAULING Copyright © 2005-2020 Fluidmesh Networks, LLC.

Layer 3 Fluidity RACER Configuration – Mesh End

Enter the WAN IP Address and port number of each Primary and Secondary
Global Gateway Device

POWERFUL WIRELESS BACKHAULING Copyright © 2005-2020 Fluidmesh Networks, LLC.

Layer 3 Fluidity: Mesh End

Wayside
Key Parameters
Device Mode: Mesh End
Fluidity Role: Infrastructure
FM TITAN: Enabled
Virtual IP: 192.168.200.13
L2TP IP: 192.168.200.210
Mesh Point Radios
Default Gateway: 192.168.200.1

Both Mesh Ends should be configured with FM TITAN enabled, allowing the use of a Virtual IP to be configured. This allows the network to stay converged in the event of a hardware failure of
one of the devices, the secondary Mesh End will seamlessly take over. Additionally, the L2TP address of each Global Gateway should be entered in list format on each Mesh End to form the
L2TP Tunnel from the site to the Global Gateway.

POWERFUL WIRELESS BACKHAULING Copyright © 2005-2020 Fluidmesh Networks, LLC.

 RACER Configuration – Wayside

FM3200/3500/4200/4500

POWERFUL WIRELESS BACKHAULING Copyright © 2005-2020 Fluidmesh Networks, LLC.

Layer 3 Fluidity RACER Configuration – Wayside AP

Create a name for the Template, usually a name that relates

to device network role / function.

Select device type. In this case the FM3500/FM4500 for

wayside AP role

POWERFUL WIRELESS BACKHAULING Copyright © 2005-2020 Fluidmesh Networks, LLC.

Layer 3 Fluidity RACER Configuration – Wayside AP

For a layer 3 Fluidity Network, configure the wayside radio as

a Mesh Point.

Configure the IP Address and subnet for the device

Configure the default gateway for traffic being routed to and

from the Mesh Point.

Enter DNS Address for the network if applicable

Shared passphrase should be the same across all Fluidmesh

Devices.

POWERFUL WIRELESS BACKHAULING Copyright © 2005-2020 Fluidmesh Networks, LLC.

Layer 3 Fluidity RACER Configuration – Wayside AP

VLAN should be disabled for Layer 3 Fluidity Applications

Configure unit as an infrastructure device

Configure network type as multiple subnet to enable

Layer 3 Fluidity Function

POWERFUL WIRELESS BACKHAULING Copyright © 2005-2020 Fluidmesh Networks, LLC.

 RACER Configuration – Vehicle

FM4200/4500

POWERFUL WIRELESS BACKHAULING Copyright © 2005-2020 Fluidmesh Networks, LLC.

Layer 3 Fluidity RACER Configuration – Vehicle

Create a name for the Template, usually a name that relates

to device network role / function.

Select device type. In this case the FM3500/FM4500 for

vehicle role

POWERFUL WIRELESS BACKHAULING Copyright © 2005-2020 Fluidmesh Networks, LLC.

Layer 3 Fluidity RACER Configuration – Vehicle

For a layer 3 Fluidity Network, configure the wayside radio as

a Mesh Point.

Configure the IP Address and subnet for the device

Configure the default gateway for traffic being routed to and

from the vehicle network.

Enter DNS Address for the network if applicable

Shared passphrase should be the same across all Fluidmesh

Devices.

POWERFUL WIRELESS BACKHAULING Copyright © 2005-2020 Fluidmesh Networks, LLC.

Layer 3 Fluidity RACER Configuration – Vehicle

VLAN should be disabled for Layer 3 Fluidity Applications

Configure unit role as a vehicle

Toggle Automatic Vehicle ID to Disable when deploying

a Fluidity Layer 3 Network

Create a Vehicle ID that is unique to each vehicle but the

same for the radios onboard the same vehicle.

Configure network type as multiple subnet to enable

Layer 3 Fluidity Function

POWERFUL WIRELESS BACKHAULING Copyright © 2005-2020 Fluidmesh Networks, LLC.

Layer 3 Fluidity RACER Configuration – Vehicle

To enable the failover redundancy function, Fast Failover should be

enabled. A TITAN License is required for this feature.

Configure timeout for FM1000 failure detection in milliseconds

Configure the virtual IP. Use the same address for the primary and the
secondary vehicle radios. The virtual IP must be different from the
management IP and the L2TP WAN IP addresses chosen for the devices.

The Preempt Delay prevents the primary Vehicle Radio to come back
online after a failure as soon as it is booted. This delay allows the primary
Vehicle Radio to learn network information (ARP, IPs, …) from the active
secondary Vehicle Radio before being back as primary gateway of the on-
board network.

If enabled forces on-board client devices to be reached via the mobile

master. If disabled allows on-board client devices to be connected
directly to mobile slaves.

POWERFUL WIRELESS BACKHAULING Copyright © 2005-2020 Fluidmesh Networks, LLC.

Layer 3 Fluidity RACER Configuration – Vehicle

Configure static routes for networks onboard the vehicle to be

routed/advertised to the Global Gateway. This is essential in ensuring
end to end reachability to the network onboard the vehicles and the
Global Gateways.

POWERFUL WIRELESS BACKHAULING Copyright © 2005-2020 Fluidmesh Networks, LLC.

Layer 3 Fluidity: Vehicle

Virtual IP: 10.42.0.6/29

Key Parameters
Radio Mode: Mesh Point
Fluidity Role: Vehicle
172.30.128.2 FM TITAN: Enabled
Virtual IP: 10.42.0.6/29
10.42.0.5
10.42.0.2 Static Route: 172.30.128.0/29
Default Gateway: 10.42.0.1

CAR CAR

In order for networks onboard the vehicle to be advertised to the Global Gateway, it is important that static routes of the network/networks onboard the vehicle are added to the
Fluidmesh Radios onboard. Additionally the Virtual IP should be set on both Fluidmesh Radios to ensure routing stays consistent in the event of a radio outage or hardware failure.

POWERFUL WIRELESS BACKHAULING Copyright © 2005-2020 Fluidmesh Networks, LLC.

Layer 3 Fluidity RACER Configuration – Applying a Template

To apply a template to a device or set of devices, click on the Configure

Templates tab. A list of all devices related to the project will be listed. Here you
will be able to select devices and apply the relevant template configurations to
each device.

With the device/devices selected, click Apply Template and

select the requisite template that needs to be applied.

Once the template has been fully configured, select the

devices that the template settings will be applied to. It is
important to note that unique settings such as IP Address
will have to be configured in each row according to device
allocation.

POWERFUL WIRELESS BACKHAULING Copyright © 2005-2020 Fluidmesh Networks, LLC.

 L2TP Tunnel Verification & Troubleshooting

POWERFUL WIRELESS BACKHAULING Copyright © 2005-2020 Fluidmesh Networks, LLC.

L2TP PLUGIN

After the template has been

applied to a device, a
dedicated menu will appear
in the navigation pane on
the left side of the radio’s
web interface that shows
L2TP configuration details
on that device.

POWERFUL WIRELESS BACKHAULING Copyright © 2005-2020 Fluidmesh Networks, LLC.

L2TP Tunnel Verification – Web GUI

This table shows the

current L2TP tunnels
and their status (CONN,
WAIT, IDLE).

From here it’s possible

to check the current
status and remove the
L2TP tunnels already
installed if needed.

POWERFUL WIRELESS BACKHAULING Copyright © 2005-2020 Fluidmesh Networks, LLC.

L2TP Tunnel Verification – Mesh End

Different WAN IP Address for the two Mesh Ends

POWERFUL WIRELESS BACKHAULING Copyright © 2005-2020 Fluidmesh Networks, LLC.

L2TP Tunnel Verification – Mesh End

Same entry that points to the same Remote WAN IP

address (Global Gateways WAN IP address)

When both Mesh End’s are up and running , on primary Mesh End the L2TP status will be in status
CONN while on secondary Mesh End the L2TP status will be in status IDLE.

POWERFUL WIRELESS BACKHAULING Copyright © 2005-2020 Fluidmesh Networks, LLC.

L2TP Status Summarization
q Each Global Gateway establishes a L2TP tunnel with each remote Mesh End
q Each cluster Mesh End establishes a L2TP tunnel with the Global Gateways

With the system in normal condition (all devices up and running), this is the expected scenario between the global
gateways and each L3 Fluidity trackside cluster:
Ø L2TP Tunnel between Primary Global Gateway and Primary Mesh End – CONN
Ø L2TP Tunnel between Primary Global Gateway and Secondary Mesh End – IDLE
Ø L2TP Tunnel between Secondary Global Gateway and Primary Mesh End – IDLE
Ø L2TP Tunnel between Secondary Global Gateway and Secondary Mesh End – IDLE

L2TP Redundancy:
Global Gateway: In case of failure of Primary Global Gateway, the L2TP tunnels between itself and the primary Mesh End
of each cluster will become IDLE, while the L2TP tunnels between the secondary Global Gateway (elected the new
Primary) and the primary Mesh End of each cluster will become CONN

Mesh End: In case of failure of Primary Mesh End in a cluster, the L2TP tunnels between itself and the primary Global
Gateway will become IDLE, while the L2TP tunnels between the secondary Mesh End (elected the new Primary) and the
primary Global Gateway will become CONN

POWERFUL WIRELESS BACKHAULING Copyright © 2005-2020 Fluidmesh Networks, LLC.

Troubleshooting & Common Mistakes
In a Fluidity L3 network scenario, the L2TP tunnels status is one of the most important settings to check; in fact a L2TP
tunnel toward a cluster that is in IDLE or WAIT status or not properly configured, prevents the communication between the
vehicle and backbone when the vehicle is connected to that specific cluster.

MESH-ID ping test

A simple way to check the tunnel status via CLI is trying to ping the MESH-ID of the remote peer (ping the Mesh-Id of the
Global Gateway from the Mesh-End CLI and ping the Mesh-Id of the Mesh-End from the Global Gateway CLI).
Unsuccessfully ping means L2TP tunnel not established and a situation to investigate…

Typical configuration issues / Things to check

1) IP / WAN IP / Virtual IP misconfiguration (use of the same IP on the same device)

2) Incorrect Remote IP Address (a device is pointing to an IP that is not the correct WAN IP of the remote device)
3) Duplicated WAN IP (two Mesh End’s on the same cluster configured with the same WAN IP)
4) Incorrect interface (device is configured to establish the tunnel with an ethernet port that is not the one connected to
the network)
5) UDP port mismatch with the remote peer (local device and remote peer are using different UDP port to encapsulate
the traffic)

POWERFUL WIRELESS BACKHAULING Copyright © 2005-2020 Fluidmesh Networks, LLC.

HEADQUARTERS, 81 PROSPECT ST. (9TH FLOOR) - BROOKLYN, NY 11201 - USA