Network Performance Knowledge Base

perfSONAR Firewall Requirements

perfSONAR Port Requirements / Firewall Rules

perfSONAR includes many services, each of which requires one or more open ports. If you are deploying perfSONAR behind a firewall you will need to change your firewall configuration to allow the following incoming and outgoing ports. Note that in general it is not recommended to run a 10G perfSONAR server behind a firewall, as many firewalls can not do full 10G flows. Blocking outgoing connections is particularly problematic, as described in the perfSONAR FAQ. Also note that bwctl and owamp provide their own mechanisms to limit what can connect.

A sample iptables configuration for Linux is available here (and an ip6tables configuration can be found here). A script to check your firewall configuration is available here.

perfSONAR tool requirements

  • bwctl --  By default bwctl uses random ports, so you must set  peer_port in if behind a firewall. Edit bwctld.conf, and set peer_port to a specific port range (default peer_port is 6001-6200), and open those tcp ports. Also set iperf_port and nuttcp_port , and open TCP and UDP for that range. (default iperf_port is 5001-5200). The number of ports needed depends on how many tests are configured. We recommend at least 25 ports for each range.
  • owamp -- By default owamp uses random ports, so you must set testports if behind a firewall. Edit owampd.conf, and set testports to a range of ports (default testports is 8760-8960), and open those udp ports.The size of the range needs to be the maximum possible number of simultaneous owamp tests you wish to allow. (ESnet sets this to a range of 100 ports).

A summary of all required ports for perfSONAR Toolkit operation can be found on the perfSONAR website:

ESnet's perfSONAR hosts are in subnets on this page