Peplink + Rajant

Hi,

I have the following setup:

  • A mobile unit, with a BR2 with 2 cellular WANs and a LAN side with multiple devices
  • A mothership unit, with a BR1 with 1 cellular WAN (which can have a public IP) and a LAN side with multiple devices

I want to connect both using a high-speed long-range mesh network using Rajant Breadcrump devices. This mesh path should be the preferred path for all data, whilst a Speedfusion tunnel to the BR1’s public IP could be a fallback path for some limited outbound policy selected traffic flows.

Currently, I would think of having two different subnets and having a dedicated route over the Rajant and some outbound policy rules with priorities. What would you recommend? Thanks.

Setup is working now, having the BR1 and BR2 connected to the Rajant breadcrumps and using them as a WAN interface, in a separate IP range for the Rajant part. Using outbound policies, the remote Pepwave devices are used as gateways for their LAN networks. It works, but it’s very ugly, as it’s not scalable to multiple mobile units now.

Instead of having a “default gateway” for a “WAN interface”, I would prefer to setup my routing table myself and have different gateways for different subnets on one particular interface.

Hi Peter. I am running this configuration with USV’s with a customer. USVs travel over a significant distance at very high speed. I can say no more. literally we have two peplink units on the vessel in HA. Rajant operates at Layer 2. Routes are dynamically assessed on each node and utilise a costing algorithm. Sounds like you aren’t using a Rajant Partner here which means you probably are missing out on a great deal of information. I have asked our Sales Engineer based in Spain to make contact.

1 Like

Hi Peter,
What you’re doing sounds similar to what I did for this project from a topology perspective (I used Doodle Labs here but same concept).

Keep the breadcrumbs on the WANs of the Peplinks, use OSPF so that each Peplink learns the routes available across that L2 segment, job done.

Shout if I can assist.

3 Likes

Great and very cool video! This is indeed exactly the setup as I have put it up until now, except that my Rajant devices are all on the WAN (or WAN over VLAN) ports of the Peplinks, with a fixed IP, as you suggest. In your setup, the BR1’s in the different cars get their WAN IP address through DHCP from the follower cars’ DHCP server on the BR1’s LAN interface, which sets the default gateway to this BR1 LAN IP address. In my static IP configuration, I also set the WAN IP and default gateway, whilst in a scaled solution this default gateway is not always the same. There OSPF has to kick in. Thanks!

Nice of you to help the little productions make a name for themselves !

3 Likes

I have a problem enabling OSPF on the Rajant network.

On the BR1, I have connected the Rajant on the LAN1 port, where I use VLAN WAN and this port being configured as access port in this VLAN:

The connection is alive:

Although, when enabling OSPF, I cannot select the VLAN WAN interface as broadcast interface for OSPF:

I would expect to see the VLAN WAN (VLAN 172) interface in this list. How can I advertise the networks on the LAN part over this VLAN WAN interface to the other side over the Rajant link? Thanks.

Also, it seems routes are not correctly advertised the other way around as well.

On the USV I have this OSPF config:

With this config I should expect the two networks “Drone LAN” and “test VLAN” are advertised over the WAN 2 - Rajant link/interface.

When I do a PCAP on the other side, I see indeed OSPF Hello packets coming in originating from this device. However, the selected networks are not advertised:

I guess I’m doing something wrong, but don’t see what.

For the announcements over the VLAN WAN I expect this to be a bug, or has anyone experience with that? Thanks.