To test different network paths from ship to shore using each WAN option directly. For this test we used a fitlet2 computer with 4 Gigibit Ethernet ports.

fitlet2 J3455 Barebone
16 GB RAM for Fitlet2
512 GB SATA SSD for fitlet2
FC-M2LAN FACET-Card (2x Gbit Ethernet)

Ubuntu Mint 20 was used.

Edit /etc/network/interfaces and add a static IP for each WAN

auto eth0
iface eth0 inet static
    address [[KA]]
    netmask [[255.255.255.0]]
    network [[KA network IP]]
    broadcast [[KA Broadcast]]
    
    

Edit /etc/iproute2/rt_tables to create local tables

#
# reserved values
#
255    local
254    main
253    default
0    unspec
#
# local
# Create multipath routing tables for Sealink and KA and Cell if available
# A table can also be created to send traffic out the regular ship (via cyberoam and peplink)
1   sealink
2   ka
3   cell
4   ship    

If you ssh into a computer and want to use tcpdump to view traffic, ssh (22) can be excluded

tcpdump -I [interface] -n 'port!22'

Capture traffic leaving a host

tcpdump -pi [interface] src host [hostname]

Watch for traffic leaving one network and entering two other networks

tcpdump -pi [interface] src net [network] and dst net [network2] or [network3]
tcpdump -pi [interface] src net 128.128.252.0/28 and dst 192.168.11.0/24 or 192.168.12/24

To see what computers are up, what OS they are running and what ports are open:

nmap -sS -O [network]    ie: nmap -sS -O 192.168.11.0

To look at https traffic on the science network:

iftop -i [interface] -f "dst port 443" 

Need to setup a server (sender) and client (listener)

On shore just listen
       iperf -s -u
On shore listen on a certain port    
    iperf -s -u -p 55437

From ship, send 7 M
   iperf -c [shoreip number]  -u -t 120 -b 7M