public:networking_tools
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
public:networking_tools [2020/10/10 10:34] – lstolp | public:networking_tools [2020/10/18 13:24] – lstolp | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== Linux Network Testing Tools ====== | ====== Linux Network Testing Tools ====== | ||
- | ==== Multipath Network Testing ==== | + | ===== Multipath |
- | To test different network paths from ship to shore using each WAN option directly. | + | To test different network paths from ship to shore using each WAN option directly. For this test we used a [[https:// |
- | ===== tcpdump | + | === Hardware Used === |
- | + | ||
+ | fitlet2 J3455 Barebone | ||
+ | 16 GB RAM for Fitlet2 | ||
+ | 512 GB SATA SSD for fitlet2 | ||
+ | FC-M2LAN FACET-Card (2x Gbit Ethernet) | ||
- | If you ssh into a computer and want to use tcpdump to view traffic, ssh (22) can be excluded | + | === Operating System === |
- | tcpdump -I [interface] -n ' | + | |
- | 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/ | + | |
- | ===== NMAP ===== | + | |
+ | ==== Magic Sauce ==== | ||
+ | Edit **/// | ||
- | To see what computers are up, what OS they are running and what ports are open: | + | auto eth0 |
- | | + | |
+ | address | ||
+ | netmask [[255.255.255.0]] | ||
+ | network [[KA network IP]] | ||
+ | broadcast [[KA Broadcast]] | ||
+ | |||
+ | |||
+ | Edit **/// | ||
+ | # | ||
+ | # 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 | ||
+ | 2 ka | ||
+ | 3 | ||
+ | 4 | ||
+ | |||
+ | Create **/// | ||
| | ||
+ | The multipath script needs to be run as sudo, so have installed it in /root/bin | ||
+ | |||
+ | # multipath.sh | ||
+ | # script to add routes out each WAN using tables created above | ||
+ | ip route add default via [[ka static ip]] dev [[ka eth]] table ka | ||
+ | ip route add default via [[sealink static ip]] dev [[sealink eth]] table hsn | ||
+ | ip route add default via [[cell static ip]] dev [[cell eth]] table cell | ||
+ | ip route add default via [[ship static ip]] dev [[cell eth]] table ship | ||
+ | | ||
+ | # Add rules to the rules | ||
+ | ip rule add from [[ka static ip]] table ka | ||
+ | ip rule add from [[sealink static ip]] table hsn | ||
+ | ip rule add from [[cell static ip]] table cell | ||
+ | ip rule add from [[ship static ip]] table ship | ||
+ | ip rule list | ||
+ | |||
+ | ==== Other Useful Commands ==== | ||
+ | [[public: | ||
- | ===== iftop ===== | + | [[public: |
- | To look at https traffic on the science network: | + | [[public: |
- | iftop -i [interface] -f "dst port 443" | + | |
- | ===== iPerf ===== | + | |
- | Need to setup a server (sender) and client (listener) | + | [[public: |
- | On shore just listen | + | |
- | iperf -s -u | + | |
- | On shore listen on a certain port | + | |
- | iperf -s -u -p 55437 | + | |
- | From ship, send 7 M | + | [[public: |
- | iperf -c [shoreip number] -u -t 120 -b 7M | + | |
public/networking_tools.txt · Last modified: 2024/01/25 03:31 by 127.0.0.1