Bypass Tests
The following scenario shows different configuration alternatives to improve the OSDx firewall performance.
Test Local Bypass
Description
Builds a scenario with three DUTs in which a performance test is carried out between DUT1 and DUT2, and DUT0 is the router running the firewall. “Local bypass” is set to allow the firewall to internally skips packets belonging to a flow that must be bypassed. The performance test may produce better results than the general tests.
Scenario
Step 1: Run command file copy http://10.215.168.1/~robot/test-performance.rules running:// force at DUT0 and expect this output:
Show output
% Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 129 100 129 0 0 44162 0 --:--:-- --:--:-- --:--:-- 64500
Step 2: Run command file show running://test-performance.rules at DUT0 and expect this output:
Show output
alert tcp any any -> any 5001 (msg: "Skipping test network performance traffic"; bypass; flow: established, to_server; sid: 40;)
Step 3: Set the following configuration in DUT0 :
set interfaces ethernet eth0 address 10.215.168.64/24 set interfaces ethernet eth0 traffic nat source rule 1 address masquerade set interfaces ethernet eth1 vif 101 address 40.0.0.1/8 set interfaces ethernet eth1 vif 101 traffic policy in FW_PLAN set interfaces ethernet eth1 vif 201 address 20.0.0.1/8 set interfaces ethernet eth1 vif 201 traffic policy in FW_PLAN set protocols static route 0.0.0.0/0 next-hop 10.215.168.1 set service dns static host-name WAN inet 10.215.168.1 set service firewall FW logging level config set service firewall FW logging outputs fast set service firewall FW mode inline queue FW_Q set service firewall FW ruleset file 'running://test-performance.rules' set service firewall FW stream bypass set service firewall FW validator-timeout 20 set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0' set traffic policy FW_PLAN rule 1 action enqueue FW_Q set traffic queue FW_Q elements 1
Step 4: Ping IP address 20.0.0.2 from DUT1:
admin@DUT1$ ping 20.0.0.2 count 1 size 56 timeout 1Show output
PING 20.0.0.2 (20.0.0.2) 56(84) bytes of data. 64 bytes from 20.0.0.2: icmp_seq=1 ttl=63 time=0.682 ms --- 20.0.0.2 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.682/0.682/0.682/0.000 ms
Step 5: Ping IP address 40.0.0.2 from DUT2:
admin@DUT2$ ping 40.0.0.2 count 1 size 56 timeout 1Show output
PING 40.0.0.2 (40.0.0.2) 56(84) bytes of data. 64 bytes from 40.0.0.2: icmp_seq=1 ttl=63 time=0.565 ms --- 40.0.0.2 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.565/0.565/0.565/0.000 ms
Step 6: Initiate a bandwidth test from DUT2 to DUT1
admin@DUT1$ monitor test performance server port 5001 admin@DUT2$ monitor test performance client 40.0.0.2 duration 10 port 5001 parallel 1Expect this output in
DUT2:Connecting to host 40.0.0.2, port 5001 [ 5] local 20.0.0.2 port 52668 connected to 40.0.0.2 port 5001 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 167 MBytes 1.40 Gbits/sec 166 1.86 MBytes [ 5] 1.00-2.00 sec 161 MBytes 1.35 Gbits/sec 0 2.03 MBytes [ 5] 2.00-3.00 sec 165 MBytes 1.38 Gbits/sec 235 1.52 MBytes [ 5] 3.00-4.00 sec 161 MBytes 1.35 Gbits/sec 0 1.61 MBytes [ 5] 4.00-5.01 sec 161 MBytes 1.35 Gbits/sec 0 1.68 MBytes [ 5] 5.01-6.00 sec 85.0 MBytes 718 Mbits/sec 0 1.72 MBytes [ 5] 6.00-7.00 sec 112 MBytes 944 Mbits/sec 0 1.75 MBytes [ 5] 7.00-8.00 sec 70.0 MBytes 587 Mbits/sec 0 1.77 MBytes [ 5] 8.00-9.00 sec 55.0 MBytes 461 Mbits/sec 0 1.79 MBytes [ 5] 9.00-10.00 sec 141 MBytes 1.18 Gbits/sec 0 1.84 MBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-10.00 sec 1.25 GBytes 1.07 Gbits/sec 401 sender [ 5] 0.00-10.01 sec 1.25 GBytes 1.07 Gbits/sec receiver iperf Done.
Step 7: Run command service firewall FW show logging fast | tail at DUT0 and check if output matches the following regular expressions:
(?m)^.+(Skipping test network performance traffic).+$Show output
03/23/2026-11:19:41.299286 [**] [1:40:0] Skipping test network performance traffic [**] [Classification: (null)] [Priority: 3] {TCP} 20.0.0.2:52664 -> 40.0.0.2:5001 03/23/2026-11:19:41.300223 [**] [1:40:0] Skipping test network performance traffic [**] [Classification: (null)] [Priority: 3] {TCP} 20.0.0.2:52668 -> 40.0.0.2:5001
Test Capture Bypass Using Packet Mark
Description
Builds a scenario with three DUTs in which a performance test is conducted between DUT1 and DUT2, and DUT0 is the router running the firewall. “Capture bypass” is set to allow the firewall to mark packets. An external tool can then decide what to do with the flow when the mark is seen. For this example, when packet marks are detected, the traffic is assigned a label, thereby allowing the possibility of classifying traffic. In particular, labeling avoids traffic from entering the firewall.
Performance must improve considerably compared to the Local Bypass test.
The test is extended by using other packet marks that we have customized for the firewall.
Scenario
Step 1: Run command file copy http://10.215.168.1/~robot/test-performance.rules running:// force at DUT0 and expect this output:
Show output
% Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 129 100 129 0 0 28711 0 --:--:-- --:--:-- --:--:-- 32250
Step 2: Run command file show running://test-performance.rules at DUT0 and expect this output:
Show output
alert tcp any any -> any 5001 (msg: "Skipping test network performance traffic"; bypass; flow: established, to_server; sid: 40;)
Step 3: Set the following configuration in DUT0 :
set interfaces ethernet eth0 address 10.215.168.64/24 set interfaces ethernet eth0 traffic nat source rule 1 address masquerade set interfaces ethernet eth1 vif 101 address 40.0.0.1/8 set interfaces ethernet eth1 vif 101 traffic policy in FW_PLAN set interfaces ethernet eth1 vif 101 traffic policy out FW-SKIP set interfaces ethernet eth1 vif 201 address 20.0.0.1/8 set interfaces ethernet eth1 vif 201 traffic policy in FW_PLAN set interfaces ethernet eth1 vif 201 traffic policy out FW-SKIP set protocols static route 0.0.0.0/0 next-hop 10.215.168.1 set service dns static host-name WAN inet 10.215.168.1 set service firewall FW logging level config set service firewall FW logging outputs fast set service firewall FW mode inline queue FW_Q set service firewall FW ruleset file 'running://test-performance.rules' set service firewall FW stream bypass mark 129834765 set service firewall FW stream bypass mask 129834765 set service firewall FW validator-timeout 20 set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0' set traffic label BYPASS set traffic policy FW-SKIP rule 1 log prefix SKIP set traffic policy FW-SKIP rule 1 selector MARKED-PACKETS set traffic policy FW-SKIP rule 1 set label BYPASS set traffic policy FW_PLAN rule 1 action enqueue FW_Q set traffic policy FW_PLAN rule 1 selector FW_SEL_ENQUEUE set traffic queue FW_Q elements 1 set traffic selector FW_SEL_ENQUEUE rule 1 not label BYPASS set traffic selector MARKED-PACKETS rule 1 mark 129834765
Step 4: Ping IP address 20.0.0.2 from DUT1:
admin@DUT1$ ping 20.0.0.2 count 1 size 56 timeout 1Show output
PING 20.0.0.2 (20.0.0.2) 56(84) bytes of data. 64 bytes from 20.0.0.2: icmp_seq=1 ttl=63 time=0.628 ms --- 20.0.0.2 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.628/0.628/0.628/0.000 ms
Step 5: Ping IP address 40.0.0.2 from DUT2:
admin@DUT2$ ping 40.0.0.2 count 1 size 56 timeout 1Show output
PING 40.0.0.2 (40.0.0.2) 56(84) bytes of data. 64 bytes from 40.0.0.2: icmp_seq=1 ttl=63 time=0.613 ms --- 40.0.0.2 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.613/0.613/0.613/0.000 ms
Step 6: Initiate a bandwidth test from DUT2 to DUT1
admin@DUT1$ monitor test performance server port 5001 admin@DUT2$ monitor test performance client 40.0.0.2 duration 10 port 5001 parallel 1Expect this output in
DUT2:Connecting to host 40.0.0.2, port 5001 [ 5] local 20.0.0.2 port 55266 connected to 40.0.0.2 port 5001 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 303 MBytes 2.54 Gbits/sec 6 1.86 MBytes [ 5] 1.00-2.00 sec 304 MBytes 2.55 Gbits/sec 128 1.45 MBytes [ 5] 2.00-3.00 sec 312 MBytes 2.62 Gbits/sec 0 1.59 MBytes [ 5] 3.00-4.00 sec 290 MBytes 2.43 Gbits/sec 0 1.72 MBytes [ 5] 4.00-5.00 sec 320 MBytes 2.68 Gbits/sec 25 1.34 MBytes [ 5] 5.00-6.00 sec 336 MBytes 2.82 Gbits/sec 0 1.51 MBytes [ 5] 6.00-7.00 sec 265 MBytes 2.22 Gbits/sec 31 1.18 MBytes [ 5] 7.00-8.00 sec 312 MBytes 2.62 Gbits/sec 0 1.36 MBytes [ 5] 8.00-9.00 sec 324 MBytes 2.72 Gbits/sec 0 1.52 MBytes [ 5] 9.00-10.00 sec 358 MBytes 3.00 Gbits/sec 0 1.68 MBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-10.00 sec 3.05 GBytes 2.62 Gbits/sec 190 sender [ 5] 0.00-10.00 sec 3.05 GBytes 2.62 Gbits/sec receiver iperf Done.
Step 7: Run command service firewall FW show logging fast | tail at DUT0 and check if output matches the following regular expressions:
(?m)^.+(Skipping test network performance traffic).+$Show output
03/23/2026-11:20:18.503727 [**] [1:40:0] Skipping test network performance traffic [**] [Classification: (null)] [Priority: 3] {TCP} 20.0.0.2:55256 -> 40.0.0.2:5001 03/23/2026-11:20:18.504962 [**] [1:40:0] Skipping test network performance traffic [**] [Classification: (null)] [Priority: 3] {TCP} 20.0.0.2:55266 -> 40.0.0.2:5001
Step 8: Run command system journal show | cat at DUT0 and check if output matches the following regular expressions:
(?m)^.*\[SKIP\-1\].*$Show output
Mar 23 11:20:10.338534 osdx systemd-journald[2086]: Runtime Journal (/run/log/journal/6b3b4e4818aa404284bc644df40f6904) is 1.7M, max 13.8M, 12.0M free. Mar 23 11:20:10.339000 osdx systemd-journald[2086]: Received client request to rotate journal, rotating. Mar 23 11:20:10.339039 osdx systemd-journald[2086]: Vacuuming done, freed 0B of archived journals from /run/log/journal/6b3b4e4818aa404284bc644df40f6904. Mar 23 11:20:10.349640 osdx OSDxCLI[377968]: User 'admin' executed a new command: 'system journal clear'. Mar 23 11:20:10.697114 osdx OSDxCLI[377968]: User 'admin' executed a new command: 'system coredump delete all'. Mar 23 11:20:10.918719 osdx OSDxCLI[377968]: User 'admin' entered the configuration menu. Mar 23 11:20:11.054563 osdx OSDxCLI[377968]: User 'admin' added a new cfg line: 'set interfaces ethernet eth0 address 10.215.168.64/24'. Mar 23 11:20:11.121035 osdx OSDxCLI[377968]: User 'admin' added a new cfg line: 'set interfaces ethernet eth0 traffic nat source rule 1 address masquerade'. Mar 23 11:20:11.227819 osdx OSDxCLI[377968]: User 'admin' added a new cfg line: 'set protocols static route 0.0.0.0/0 next-hop 10.215.168.1'. Mar 23 11:20:11.289334 osdx OSDxCLI[377968]: User 'admin' added a new cfg line: 'set service dns static host-name WAN inet 10.215.168.1'. Mar 23 11:20:11.385148 osdx OSDxCLI[377968]: User 'admin' added a new cfg line: 'set interfaces ethernet eth1 vif 101 address 40.0.0.1/8'. Mar 23 11:20:11.436257 osdx OSDxCLI[377968]: User 'admin' added a new cfg line: 'set interfaces ethernet eth1 vif 201 address 20.0.0.1/8'. Mar 23 11:20:11.557158 osdx OSDxCLI[377968]: User 'admin' added a new cfg line: 'show working'. Mar 23 11:20:11.615587 osdx ubnt-cfgd[378481]: inactive Mar 23 11:20:11.641361 osdx INFO[378487]: FRR daemons did not change Mar 23 11:20:11.670882 osdx kernel: 8021q: adding VLAN 0 to HW filter on device eth1 Mar 23 11:20:11.687650 osdx WARNING[378527]: No supported link modes on interface eth1 Mar 23 11:20:11.689127 osdx modulelauncher[378527]: osdx.utils.xos cmd error: /sbin/ethtool -A eth1 autoneg on Mar 23 11:20:11.689144 osdx modulelauncher[378527]: Command '/sbin/ethtool -A eth1 autoneg on' returned non-zero exit status 76. Mar 23 11:20:11.690293 osdx modulelauncher[378527]: osdx.utils.xos cmd error: /sbin/ethtool -s eth1 autoneg on advertise Pause off Asym_Pause off -- Mar 23 11:20:11.690301 osdx modulelauncher[378527]: Command '/sbin/ethtool -s eth1 autoneg on advertise Pause off Asym_Pause off --' returned non-zero exit status 75. Mar 23 11:20:11.730898 osdx kernel: 8021q: adding VLAN 0 to HW filter on device eth0 Mar 23 11:20:11.777332 osdx WARNING[378607]: No supported link modes on interface eth0 Mar 23 11:20:11.778728 osdx modulelauncher[378607]: osdx.utils.xos cmd error: /sbin/ethtool -A eth0 autoneg on Mar 23 11:20:11.778745 osdx modulelauncher[378607]: Command '/sbin/ethtool -A eth0 autoneg on' returned non-zero exit status 76. Mar 23 11:20:11.779985 osdx modulelauncher[378607]: osdx.utils.xos cmd error: /sbin/ethtool -s eth0 autoneg on advertise Pause off Asym_Pause off -- Mar 23 11:20:11.779994 osdx modulelauncher[378607]: Command '/sbin/ethtool -s eth0 autoneg on advertise Pause off Asym_Pause off --' returned non-zero exit status 75. Mar 23 11:20:11.790697 osdx (udev-worker)[378623]: Network interface NamePolicy= disabled on kernel command line. Mar 23 11:20:11.949554 osdx cfgd[1828]: [377968]Completed change to active configuration Mar 23 11:20:11.960607 osdx OSDxCLI[377968]: User 'admin' committed the configuration. Mar 23 11:20:11.975424 osdx OSDxCLI[377968]: User 'admin' left the configuration menu. Mar 23 11:20:14.145819 osdx OSDxCLI[377968]: User 'admin' executed a new command: 'ping 10.215.168.1 count 1 size 56 timeout 1'. Mar 23 11:20:14.281742 osdx OSDxCLI[377968]: User 'admin' executed a new command: 'ping 40.0.0.2 count 1 size 56 timeout 1'. Mar 23 11:20:14.386839 osdx OSDxCLI[377968]: User 'admin' executed a new command: 'ping 20.0.0.2 count 1 size 56 timeout 1'. Mar 23 11:20:15.064484 osdx file_operation[378802]: using src url: http://10.215.168.1/~robot/test-performance.rules dst url: running:// Mar 23 11:20:15.090845 osdx OSDxCLI[377968]: User 'admin' executed a new command: 'file copy http://10.215.168.1/~robot/test-performance.rules running:// force'. Mar 23 11:20:15.247221 osdx OSDxCLI[377968]: User 'admin' executed a new command: 'file show running://test-performance.rules'. Mar 23 11:20:15.407732 osdx OSDxCLI[377968]: User 'admin' entered the configuration menu. Mar 23 11:20:15.482968 osdx OSDxCLI[377968]: User 'admin' added a new cfg line: 'set service firewall FW ruleset file running://test-performance.rules'. Mar 23 11:20:15.625337 osdx OSDxCLI[377968]: User 'admin' added a new cfg line: 'set service firewall FW mode inline queue FW_Q'. Mar 23 11:20:15.701094 osdx OSDxCLI[377968]: User 'admin' added a new cfg line: 'set service firewall FW logging outputs fast'. Mar 23 11:20:15.795547 osdx OSDxCLI[377968]: User 'admin' added a new cfg line: 'set service firewall FW logging level config'. Mar 23 11:20:15.851721 osdx OSDxCLI[377968]: User 'admin' added a new cfg line: 'set service firewall FW validator-timeout 20'. Mar 23 11:20:15.943180 osdx OSDxCLI[377968]: User 'admin' added a new cfg line: 'set traffic queue FW_Q elements 1'. Mar 23 11:20:16.047766 osdx OSDxCLI[377968]: User 'admin' added a new cfg line: 'set interfaces ethernet eth1 vif 101 traffic policy in FW_PLAN'. Mar 23 11:20:16.123204 osdx OSDxCLI[377968]: User 'admin' added a new cfg line: 'set interfaces ethernet eth1 vif 201 traffic policy in FW_PLAN'. Mar 23 11:20:16.218161 osdx OSDxCLI[377968]: User 'admin' added a new cfg line: 'set service firewall FW stream bypass mark 129834765'. Mar 23 11:20:16.279463 osdx OSDxCLI[377968]: User 'admin' added a new cfg line: 'set service firewall FW stream bypass mask 129834765'. Mar 23 11:20:16.370259 osdx OSDxCLI[377968]: User 'admin' added a new cfg line: 'set traffic label BYPASS'. Mar 23 11:20:16.430368 osdx OSDxCLI[377968]: User 'admin' added a new cfg line: 'set traffic policy FW-SKIP rule 1 log prefix SKIP'. Mar 23 11:20:16.527611 osdx OSDxCLI[377968]: User 'admin' added a new cfg line: 'set traffic policy FW-SKIP rule 1 selector MARKED-PACKETS'. Mar 23 11:20:16.587909 osdx OSDxCLI[377968]: User 'admin' added a new cfg line: 'set traffic policy FW-SKIP rule 1 set label BYPASS'. Mar 23 11:20:16.682898 osdx OSDxCLI[377968]: User 'admin' added a new cfg line: 'set traffic selector MARKED-PACKETS rule 1 mark 129834765'. Mar 23 11:20:16.743234 osdx OSDxCLI[377968]: User 'admin' added a new cfg line: 'set traffic selector FW_SEL_ENQUEUE rule 1 not label BYPASS'. Mar 23 11:20:16.863361 osdx OSDxCLI[377968]: User 'admin' added a new cfg line: 'set traffic policy FW_PLAN rule 1 selector FW_SEL_ENQUEUE'. Mar 23 11:20:16.949705 osdx OSDxCLI[377968]: User 'admin' added a new cfg line: 'set interfaces ethernet eth1 vif 101 traffic policy out FW-SKIP'. Mar 23 11:20:17.043434 osdx OSDxCLI[377968]: User 'admin' added a new cfg line: 'set interfaces ethernet eth1 vif 201 traffic policy out FW-SKIP'. Mar 23 11:20:17.121427 osdx OSDxCLI[377968]: User 'admin' added a new cfg line: 'set traffic policy FW_PLAN rule 1 action enqueue FW_Q'. Mar 23 11:20:17.238140 osdx OSDxCLI[377968]: User 'admin' added a new cfg line: 'show working'. Mar 23 11:20:17.323217 osdx ubnt-cfgd[378850]: inactive Mar 23 11:20:17.412348 osdx INFO[378895]: FRR daemons did not change Mar 23 11:20:17.688463 osdx systemd[1]: Reloading. Mar 23 11:20:17.734893 osdx systemd-sysv-generator[378950]: stat() failed on /etc/init.d/README, ignoring: No such file or directory Mar 23 11:20:17.871113 osdx systemd[1]: Starting suricata@FW.service - Suricata client "FW" service... Mar 23 11:20:17.892191 osdx systemd[1]: Started suricata@FW.service - Suricata client "FW" service. Mar 23 11:20:18.074504 osdx INFO[378932]: Rules successfully loaded Mar 23 11:20:18.075248 osdx cfgd[1828]: [377968]Completed change to active configuration Mar 23 11:20:18.077657 osdx OSDxCLI[377968]: User 'admin' committed the configuration. Mar 23 11:20:18.098267 osdx OSDxCLI[377968]: User 'admin' left the configuration menu. Mar 23 11:20:18.506893 osdx kernel: [SKIP-1] ACCEPT IN=eth1.201 OUT=eth1.101 MAC=de:ad:be:ef:6c:01:de:ad:be:ef:6c:20:08:00:45:00:00:59 SRC=20.0.0.2 DST=40.0.0.2 LEN=89 TOS=0x00 PREC=0x00 TTL=63 ID=3548 DF PROTO=TCP SPT=55256 DPT=5001 WINDOW=502 RES=0x00 ACK PSH URGP=0 MARK=0x7bd1f0d Mar 23 11:20:18.506972 osdx kernel: [SKIP-1] ACCEPT IN=eth1.201 OUT=eth1.101 MAC=de:ad:be:ef:6c:01:de:ad:be:ef:6c:20:08:00:45:00:00:59 SRC=20.0.0.2 DST=40.0.0.2 LEN=89 TOS=0x00 PREC=0x00 TTL=63 ID=14700 DF PROTO=TCP SPT=55266 DPT=5001 WINDOW=502 RES=0x00 ACK PSH URGP=0 MARK=0x7bd1f0d Mar 23 11:20:28.743001 osdx OSDxCLI[377968]: User 'admin' executed a new command: 'service firewall FW show logging fast | tail'.
Note
The following steps are just a reiteration of the previous test, but with the difference that the packet mark is an extra mark.
Step 9: Modify the following configuration lines in DUT0 :
set service firewall FW stream bypass extra-mark 1 mask 3294967295 set service firewall FW stream bypass extra-mark 1 value 3294967295 set traffic policy FW-SKIP rule 1 selector FW_SEL_EXTRA_MARK set traffic selector FW_SEL_EXTRA_MARK rule 1 extra-mark 1 value 3294967295
Step 10: Initiate a bandwidth test from DUT2 to DUT1
admin@DUT1$ monitor test performance server port 5001 admin@DUT2$ monitor test performance client 40.0.0.2 duration 10 port 5001 parallel 1Expect this output in
DUT2:Connecting to host 40.0.0.2, port 5001 [ 5] local 20.0.0.2 port 49722 connected to 40.0.0.2 port 5001 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 324 MBytes 2.72 Gbits/sec 1 1.82 MBytes [ 5] 1.00-2.00 sec 329 MBytes 2.76 Gbits/sec 0 1.97 MBytes [ 5] 2.00-3.00 sec 356 MBytes 2.99 Gbits/sec 272 1.50 MBytes [ 5] 3.00-4.00 sec 330 MBytes 2.77 Gbits/sec 0 1.65 MBytes [ 5] 4.00-5.00 sec 292 MBytes 2.45 Gbits/sec 0 1.78 MBytes [ 5] 5.00-6.00 sec 360 MBytes 3.02 Gbits/sec 0 1.92 MBytes [ 5] 6.00-7.00 sec 209 MBytes 1.75 Gbits/sec 372 1.50 MBytes [ 5] 7.00-8.00 sec 358 MBytes 3.00 Gbits/sec 0 1.65 MBytes [ 5] 8.00-9.00 sec 331 MBytes 2.78 Gbits/sec 0 1.79 MBytes [ 5] 9.00-10.00 sec 345 MBytes 2.89 Gbits/sec 0 1.93 MBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-10.00 sec 3.16 GBytes 2.71 Gbits/sec 645 sender [ 5] 0.00-10.00 sec 3.16 GBytes 2.71 Gbits/sec receiver iperf Done.
Step 11: Run command service firewall FW show logging fast | tail at DUT0 and check if output matches the following regular expressions:
(?m)^.+(Skipping test network performance traffic).+$Show output
03/23/2026-11:20:18.503727 [**] [1:40:0] Skipping test network performance traffic [**] [Classification: (null)] [Priority: 3] {TCP} 20.0.0.2:55256 -> 40.0.0.2:5001 03/23/2026-11:20:18.504962 [**] [1:40:0] Skipping test network performance traffic [**] [Classification: (null)] [Priority: 3] {TCP} 20.0.0.2:55266 -> 40.0.0.2:5001 03/23/2026-11:20:33.344970 [**] [1:40:0] Skipping test network performance traffic [**] [Classification: (null)] [Priority: 3] {TCP} 20.0.0.2:49706 -> 40.0.0.2:5001 03/23/2026-11:20:33.346022 [**] [1:40:0] Skipping test network performance traffic [**] [Classification: (null)] [Priority: 3] {TCP} 20.0.0.2:49722 -> 40.0.0.2:5001
Step 12: Run command system journal show | cat at DUT0 and check if output matches the following regular expressions:
(?m)^.*\[SKIP\-1\].*$Show output
Mar 23 11:20:10.338534 osdx systemd-journald[2086]: Runtime Journal (/run/log/journal/6b3b4e4818aa404284bc644df40f6904) is 1.7M, max 13.8M, 12.0M free. Mar 23 11:20:10.339000 osdx systemd-journald[2086]: Received client request to rotate journal, rotating. Mar 23 11:20:10.339039 osdx systemd-journald[2086]: Vacuuming done, freed 0B of archived journals from /run/log/journal/6b3b4e4818aa404284bc644df40f6904. Mar 23 11:20:10.349640 osdx OSDxCLI[377968]: User 'admin' executed a new command: 'system journal clear'. Mar 23 11:20:10.697114 osdx OSDxCLI[377968]: User 'admin' executed a new command: 'system coredump delete all'. Mar 23 11:20:10.918719 osdx OSDxCLI[377968]: User 'admin' entered the configuration menu. Mar 23 11:20:11.054563 osdx OSDxCLI[377968]: User 'admin' added a new cfg line: 'set interfaces ethernet eth0 address 10.215.168.64/24'. Mar 23 11:20:11.121035 osdx OSDxCLI[377968]: User 'admin' added a new cfg line: 'set interfaces ethernet eth0 traffic nat source rule 1 address masquerade'. Mar 23 11:20:11.227819 osdx OSDxCLI[377968]: User 'admin' added a new cfg line: 'set protocols static route 0.0.0.0/0 next-hop 10.215.168.1'. Mar 23 11:20:11.289334 osdx OSDxCLI[377968]: User 'admin' added a new cfg line: 'set service dns static host-name WAN inet 10.215.168.1'. Mar 23 11:20:11.385148 osdx OSDxCLI[377968]: User 'admin' added a new cfg line: 'set interfaces ethernet eth1 vif 101 address 40.0.0.1/8'. Mar 23 11:20:11.436257 osdx OSDxCLI[377968]: User 'admin' added a new cfg line: 'set interfaces ethernet eth1 vif 201 address 20.0.0.1/8'. Mar 23 11:20:11.557158 osdx OSDxCLI[377968]: User 'admin' added a new cfg line: 'show working'. Mar 23 11:20:11.615587 osdx ubnt-cfgd[378481]: inactive Mar 23 11:20:11.641361 osdx INFO[378487]: FRR daemons did not change Mar 23 11:20:11.670882 osdx kernel: 8021q: adding VLAN 0 to HW filter on device eth1 Mar 23 11:20:11.687650 osdx WARNING[378527]: No supported link modes on interface eth1 Mar 23 11:20:11.689127 osdx modulelauncher[378527]: osdx.utils.xos cmd error: /sbin/ethtool -A eth1 autoneg on Mar 23 11:20:11.689144 osdx modulelauncher[378527]: Command '/sbin/ethtool -A eth1 autoneg on' returned non-zero exit status 76. Mar 23 11:20:11.690293 osdx modulelauncher[378527]: osdx.utils.xos cmd error: /sbin/ethtool -s eth1 autoneg on advertise Pause off Asym_Pause off -- Mar 23 11:20:11.690301 osdx modulelauncher[378527]: Command '/sbin/ethtool -s eth1 autoneg on advertise Pause off Asym_Pause off --' returned non-zero exit status 75. Mar 23 11:20:11.730898 osdx kernel: 8021q: adding VLAN 0 to HW filter on device eth0 Mar 23 11:20:11.777332 osdx WARNING[378607]: No supported link modes on interface eth0 Mar 23 11:20:11.778728 osdx modulelauncher[378607]: osdx.utils.xos cmd error: /sbin/ethtool -A eth0 autoneg on Mar 23 11:20:11.778745 osdx modulelauncher[378607]: Command '/sbin/ethtool -A eth0 autoneg on' returned non-zero exit status 76. Mar 23 11:20:11.779985 osdx modulelauncher[378607]: osdx.utils.xos cmd error: /sbin/ethtool -s eth0 autoneg on advertise Pause off Asym_Pause off -- Mar 23 11:20:11.779994 osdx modulelauncher[378607]: Command '/sbin/ethtool -s eth0 autoneg on advertise Pause off Asym_Pause off --' returned non-zero exit status 75. Mar 23 11:20:11.790697 osdx (udev-worker)[378623]: Network interface NamePolicy= disabled on kernel command line. Mar 23 11:20:11.949554 osdx cfgd[1828]: [377968]Completed change to active configuration Mar 23 11:20:11.960607 osdx OSDxCLI[377968]: User 'admin' committed the configuration. Mar 23 11:20:11.975424 osdx OSDxCLI[377968]: User 'admin' left the configuration menu. Mar 23 11:20:14.145819 osdx OSDxCLI[377968]: User 'admin' executed a new command: 'ping 10.215.168.1 count 1 size 56 timeout 1'. Mar 23 11:20:14.281742 osdx OSDxCLI[377968]: User 'admin' executed a new command: 'ping 40.0.0.2 count 1 size 56 timeout 1'. Mar 23 11:20:14.386839 osdx OSDxCLI[377968]: User 'admin' executed a new command: 'ping 20.0.0.2 count 1 size 56 timeout 1'. Mar 23 11:20:15.064484 osdx file_operation[378802]: using src url: http://10.215.168.1/~robot/test-performance.rules dst url: running:// Mar 23 11:20:15.090845 osdx OSDxCLI[377968]: User 'admin' executed a new command: 'file copy http://10.215.168.1/~robot/test-performance.rules running:// force'. Mar 23 11:20:15.247221 osdx OSDxCLI[377968]: User 'admin' executed a new command: 'file show running://test-performance.rules'. Mar 23 11:20:15.407732 osdx OSDxCLI[377968]: User 'admin' entered the configuration menu. Mar 23 11:20:15.482968 osdx OSDxCLI[377968]: User 'admin' added a new cfg line: 'set service firewall FW ruleset file running://test-performance.rules'. Mar 23 11:20:15.625337 osdx OSDxCLI[377968]: User 'admin' added a new cfg line: 'set service firewall FW mode inline queue FW_Q'. Mar 23 11:20:15.701094 osdx OSDxCLI[377968]: User 'admin' added a new cfg line: 'set service firewall FW logging outputs fast'. Mar 23 11:20:15.795547 osdx OSDxCLI[377968]: User 'admin' added a new cfg line: 'set service firewall FW logging level config'. Mar 23 11:20:15.851721 osdx OSDxCLI[377968]: User 'admin' added a new cfg line: 'set service firewall FW validator-timeout 20'. Mar 23 11:20:15.943180 osdx OSDxCLI[377968]: User 'admin' added a new cfg line: 'set traffic queue FW_Q elements 1'. Mar 23 11:20:16.047766 osdx OSDxCLI[377968]: User 'admin' added a new cfg line: 'set interfaces ethernet eth1 vif 101 traffic policy in FW_PLAN'. Mar 23 11:20:16.123204 osdx OSDxCLI[377968]: User 'admin' added a new cfg line: 'set interfaces ethernet eth1 vif 201 traffic policy in FW_PLAN'. Mar 23 11:20:16.218161 osdx OSDxCLI[377968]: User 'admin' added a new cfg line: 'set service firewall FW stream bypass mark 129834765'. Mar 23 11:20:16.279463 osdx OSDxCLI[377968]: User 'admin' added a new cfg line: 'set service firewall FW stream bypass mask 129834765'. Mar 23 11:20:16.370259 osdx OSDxCLI[377968]: User 'admin' added a new cfg line: 'set traffic label BYPASS'. Mar 23 11:20:16.430368 osdx OSDxCLI[377968]: User 'admin' added a new cfg line: 'set traffic policy FW-SKIP rule 1 log prefix SKIP'. Mar 23 11:20:16.527611 osdx OSDxCLI[377968]: User 'admin' added a new cfg line: 'set traffic policy FW-SKIP rule 1 selector MARKED-PACKETS'. Mar 23 11:20:16.587909 osdx OSDxCLI[377968]: User 'admin' added a new cfg line: 'set traffic policy FW-SKIP rule 1 set label BYPASS'. Mar 23 11:20:16.682898 osdx OSDxCLI[377968]: User 'admin' added a new cfg line: 'set traffic selector MARKED-PACKETS rule 1 mark 129834765'. Mar 23 11:20:16.743234 osdx OSDxCLI[377968]: User 'admin' added a new cfg line: 'set traffic selector FW_SEL_ENQUEUE rule 1 not label BYPASS'. Mar 23 11:20:16.863361 osdx OSDxCLI[377968]: User 'admin' added a new cfg line: 'set traffic policy FW_PLAN rule 1 selector FW_SEL_ENQUEUE'. Mar 23 11:20:16.949705 osdx OSDxCLI[377968]: User 'admin' added a new cfg line: 'set interfaces ethernet eth1 vif 101 traffic policy out FW-SKIP'. Mar 23 11:20:17.043434 osdx OSDxCLI[377968]: User 'admin' added a new cfg line: 'set interfaces ethernet eth1 vif 201 traffic policy out FW-SKIP'. Mar 23 11:20:17.121427 osdx OSDxCLI[377968]: User 'admin' added a new cfg line: 'set traffic policy FW_PLAN rule 1 action enqueue FW_Q'. Mar 23 11:20:17.238140 osdx OSDxCLI[377968]: User 'admin' added a new cfg line: 'show working'. Mar 23 11:20:17.323217 osdx ubnt-cfgd[378850]: inactive Mar 23 11:20:17.412348 osdx INFO[378895]: FRR daemons did not change Mar 23 11:20:17.688463 osdx systemd[1]: Reloading. Mar 23 11:20:17.734893 osdx systemd-sysv-generator[378950]: stat() failed on /etc/init.d/README, ignoring: No such file or directory Mar 23 11:20:17.871113 osdx systemd[1]: Starting suricata@FW.service - Suricata client "FW" service... Mar 23 11:20:17.892191 osdx systemd[1]: Started suricata@FW.service - Suricata client "FW" service. Mar 23 11:20:18.074504 osdx INFO[378932]: Rules successfully loaded Mar 23 11:20:18.075248 osdx cfgd[1828]: [377968]Completed change to active configuration Mar 23 11:20:18.077657 osdx OSDxCLI[377968]: User 'admin' committed the configuration. Mar 23 11:20:18.098267 osdx OSDxCLI[377968]: User 'admin' left the configuration menu. Mar 23 11:20:18.506893 osdx kernel: [SKIP-1] ACCEPT IN=eth1.201 OUT=eth1.101 MAC=de:ad:be:ef:6c:01:de:ad:be:ef:6c:20:08:00:45:00:00:59 SRC=20.0.0.2 DST=40.0.0.2 LEN=89 TOS=0x00 PREC=0x00 TTL=63 ID=3548 DF PROTO=TCP SPT=55256 DPT=5001 WINDOW=502 RES=0x00 ACK PSH URGP=0 MARK=0x7bd1f0d Mar 23 11:20:18.506972 osdx kernel: [SKIP-1] ACCEPT IN=eth1.201 OUT=eth1.101 MAC=de:ad:be:ef:6c:01:de:ad:be:ef:6c:20:08:00:45:00:00:59 SRC=20.0.0.2 DST=40.0.0.2 LEN=89 TOS=0x00 PREC=0x00 TTL=63 ID=14700 DF PROTO=TCP SPT=55266 DPT=5001 WINDOW=502 RES=0x00 ACK PSH URGP=0 MARK=0x7bd1f0d Mar 23 11:20:28.743001 osdx OSDxCLI[377968]: User 'admin' executed a new command: 'service firewall FW show logging fast | tail'. Mar 23 11:20:28.857519 osdx OSDxCLI[377968]: User 'admin' executed a new command: 'system journal show | cat'. Mar 23 11:20:29.045345 osdx OSDxCLI[377968]: User 'admin' entered the configuration menu. Mar 23 11:20:29.104311 osdx OSDxCLI[377968]: User 'admin' added a new cfg line: 'set service firewall FW ruleset file running://test-performance.rules'. Mar 23 11:20:29.200038 osdx OSDxCLI[377968]: User 'admin' added a new cfg line: 'set service firewall FW mode inline queue FW_Q'. Mar 23 11:20:29.255089 osdx OSDxCLI[377968]: User 'admin' added a new cfg line: 'set service firewall FW logging outputs fast'. Mar 23 11:20:29.352305 osdx OSDxCLI[377968]: User 'admin' added a new cfg line: 'set service firewall FW logging level config'. Mar 23 11:20:29.406676 osdx OSDxCLI[377968]: User 'admin' added a new cfg line: 'set service firewall FW validator-timeout 20'. Mar 23 11:20:29.511529 osdx OSDxCLI[377968]: User 'admin' added a new cfg line: 'set traffic queue FW_Q elements 1'. Mar 23 11:20:29.597146 osdx OSDxCLI[377968]: User 'admin' added a new cfg line: 'set interfaces ethernet eth1 vif 101 traffic policy in FW_PLAN'. Mar 23 11:20:29.662497 osdx OSDxCLI[377968]: User 'admin' added a new cfg line: 'set interfaces ethernet eth1 vif 201 traffic policy in FW_PLAN'. Mar 23 11:20:29.755016 osdx OSDxCLI[377968]: User 'admin' added a new cfg line: 'set service firewall FW stream bypass mark 129834765'. Mar 23 11:20:29.810702 osdx OSDxCLI[377968]: User 'admin' added a new cfg line: 'set service firewall FW stream bypass mask 129834765'. Mar 23 11:20:29.904687 osdx OSDxCLI[377968]: User 'admin' added a new cfg line: 'set traffic label BYPASS'. Mar 23 11:20:29.971666 osdx OSDxCLI[377968]: User 'admin' added a new cfg line: 'set traffic policy FW-SKIP rule 1 log prefix SKIP'. Mar 23 11:20:30.064850 osdx OSDxCLI[377968]: User 'admin' added a new cfg line: 'set traffic policy FW-SKIP rule 1 selector MARKED-PACKETS'. Mar 23 11:20:30.134951 osdx OSDxCLI[377968]: User 'admin' added a new cfg line: 'set traffic policy FW-SKIP rule 1 set label BYPASS'. Mar 23 11:20:30.224981 osdx OSDxCLI[377968]: User 'admin' added a new cfg line: 'set traffic selector MARKED-PACKETS rule 1 mark 129834765'. Mar 23 11:20:30.292912 osdx OSDxCLI[377968]: User 'admin' added a new cfg line: 'set traffic selector FW_SEL_ENQUEUE rule 1 not label BYPASS'. Mar 23 11:20:30.382657 osdx OSDxCLI[377968]: User 'admin' added a new cfg line: 'set traffic policy FW_PLAN rule 1 selector FW_SEL_ENQUEUE'. Mar 23 11:20:30.438122 osdx OSDxCLI[377968]: User 'admin' added a new cfg line: 'set interfaces ethernet eth1 vif 101 traffic policy out FW-SKIP'. Mar 23 11:20:30.530581 osdx OSDxCLI[377968]: User 'admin' added a new cfg line: 'set interfaces ethernet eth1 vif 201 traffic policy out FW-SKIP'. Mar 23 11:20:30.583308 osdx OSDxCLI[377968]: User 'admin' added a new cfg line: 'set traffic policy FW_PLAN rule 1 action enqueue FW_Q'. Mar 23 11:20:30.678948 osdx OSDxCLI[377968]: User 'admin' added a new cfg line: 'set service firewall FW stream bypass extra-mark 1 value 3294967295'. Mar 23 11:20:30.731153 osdx OSDxCLI[377968]: User 'admin' added a new cfg line: 'set service firewall FW stream bypass extra-mark 1 mask 3294967295'. Mar 23 11:20:30.826293 osdx OSDxCLI[377968]: User 'admin' added a new cfg line: 'set traffic policy FW-SKIP rule 1 selector FW_SEL_EXTRA_MARK'. Mar 23 11:20:30.886966 osdx OSDxCLI[377968]: User 'admin' added a new cfg line: 'set traffic selector FW_SEL_EXTRA_MARK rule 1 extra-mark 1 value 3294967295'. Mar 23 11:20:30.995775 osdx OSDxCLI[377968]: User 'admin' added a new cfg line: 'show changes'. Mar 23 11:20:31.072168 osdx ubnt-cfgd[379073]: inactive Mar 23 11:20:31.118314 osdx INFO[379093]: FRR daemons did not change Mar 23 11:20:31.363408 osdx systemd[1]: Stopping suricata@FW.service - Suricata client "FW" service... Mar 23 11:20:32.869148 osdx systemd[1]: suricata@FW.service: Deactivated successfully. Mar 23 11:20:32.869276 osdx systemd[1]: Stopped suricata@FW.service - Suricata client "FW" service. Mar 23 11:20:32.869310 osdx systemd[1]: suricata@FW.service: Consumed 1.504s CPU time. Mar 23 11:20:32.883150 osdx systemd[1]: Starting suricata@FW.service - Suricata client "FW" service... Mar 23 11:20:32.924426 osdx systemd[1]: Started suricata@FW.service - Suricata client "FW" service. Mar 23 11:20:33.125517 osdx INFO[379120]: Rules successfully loaded Mar 23 11:20:33.126058 osdx cfgd[1828]: [377968]Completed change to active configuration Mar 23 11:20:33.128317 osdx OSDxCLI[377968]: User 'admin' committed the configuration. Mar 23 11:20:33.143639 osdx OSDxCLI[377968]: User 'admin' left the configuration menu. Mar 23 11:20:33.346898 osdx kernel: [SKIP-1] ACCEPT IN=eth1.201 OUT=eth1.101 MAC=de:ad:be:ef:6c:01:de:ad:be:ef:6c:20:08:00:45:00:00:59 SRC=20.0.0.2 DST=40.0.0.2 LEN=89 TOS=0x00 PREC=0x00 TTL=63 ID=19561 DF PROTO=TCP SPT=49706 DPT=5001 WINDOW=502 RES=0x00 ACK PSH URGP=0 MARK=0x7bd1f0d EMARK1=0xc46535ff Mar 23 11:20:33.347088 osdx kernel: [SKIP-1] ACCEPT IN=eth1.201 OUT=eth1.101 MAC=de:ad:be:ef:6c:01:de:ad:be:ef:6c:20:08:00:45:00:00:59 SRC=20.0.0.2 DST=40.0.0.2 LEN=89 TOS=0x00 PREC=0x00 TTL=63 ID=26111 DF PROTO=TCP SPT=49722 DPT=5001 WINDOW=502 RES=0x00 ACK PSH URGP=0 MARK=0x7bd1f0d EMARK1=0xc46535ff Mar 23 11:20:40.032043 osdx systemd[1]: systemd-timedated.service: Deactivated successfully. Mar 23 11:20:43.524678 osdx OSDxCLI[377968]: User 'admin' executed a new command: 'service firewall FW show logging fast | tail'.
Test Capture Bypass Using Conntrack Mark
Description
Builds a scenario with three DUTs in which a performance test is conducted between DUT1 and DUT2, and DUT0 is the router running the firewall. This test sets the conntrack mark directly, thus skipping all the steps required to set it later.
Performance must improve considerably compared to the Local Bypass test.
Then this test is broadened by using other conntrack marks that we have customized for the firewall.
Scenario
Step 1: Run command file copy http://10.215.168.1/~robot/test-performance.rules running:// force at DUT0 and expect this output:
Show output
% Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 129 100 129 0 0 3290 0 --:--:-- --:--:-- --:--:-- 3307
Step 2: Run command file show running://test-performance.rules at DUT0 and expect this output:
Show output
alert tcp any any -> any 5001 (msg: "Skipping test network performance traffic"; bypass; flow: established, to_server; sid: 40;)
Step 3: Set the following configuration in DUT0 :
set interfaces ethernet eth0 address 10.215.168.64/24 set interfaces ethernet eth0 traffic nat source rule 1 address masquerade set interfaces ethernet eth1 vif 101 address 40.0.0.1/8 set interfaces ethernet eth1 vif 101 traffic policy in FW_PLAN set interfaces ethernet eth1 vif 201 address 20.0.0.1/8 set interfaces ethernet eth1 vif 201 traffic policy in FW_PLAN set protocols static route 0.0.0.0/0 next-hop 10.215.168.1 set service dns static host-name WAN inet 10.215.168.1 set service firewall FW logging level config set service firewall FW logging outputs fast set service firewall FW mode inline queue FW_Q set service firewall FW ruleset file 'running://test-performance.rules' set service firewall FW stream bypass mark 129834765 set service firewall FW stream bypass mask 129834765 set service firewall FW stream bypass set-connmark set service firewall FW validator-timeout 20 set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0' set traffic policy FW_PLAN rule 2 action enqueue FW_Q set traffic policy FW_PLAN rule 2 selector FW_SEL_ENQUEUE set traffic queue FW_Q elements 1 set traffic selector FW_SEL_ENQUEUE rule 1 not connmark 129834765
Step 4: Ping IP address 20.0.0.2 from DUT1:
admin@DUT1$ ping 20.0.0.2 count 1 size 56 timeout 1Show output
PING 20.0.0.2 (20.0.0.2) 56(84) bytes of data. 64 bytes from 20.0.0.2: icmp_seq=1 ttl=63 time=0.744 ms --- 20.0.0.2 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.744/0.744/0.744/0.000 ms
Step 5: Ping IP address 40.0.0.2 from DUT2:
admin@DUT2$ ping 40.0.0.2 count 1 size 56 timeout 1Show output
PING 40.0.0.2 (40.0.0.2) 56(84) bytes of data. 64 bytes from 40.0.0.2: icmp_seq=1 ttl=63 time=0.546 ms --- 40.0.0.2 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.546/0.546/0.546/0.000 ms
Step 6: Initiate a bandwidth test from DUT2 to DUT1
admin@DUT1$ monitor test performance server port 5001 admin@DUT2$ monitor test performance client 40.0.0.2 duration 10 port 5001 parallel 1Expect this output in
DUT2:Connecting to host 40.0.0.2, port 5001 [ 5] local 20.0.0.2 port 46658 connected to 40.0.0.2 port 5001 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 313 MBytes 2.63 Gbits/sec 81 1.33 MBytes [ 5] 1.00-2.00 sec 288 MBytes 2.41 Gbits/sec 0 1.48 MBytes [ 5] 2.00-3.00 sec 294 MBytes 2.46 Gbits/sec 0 1.61 MBytes [ 5] 3.00-4.00 sec 279 MBytes 2.34 Gbits/sec 2 1.25 MBytes [ 5] 4.00-5.00 sec 262 MBytes 2.20 Gbits/sec 0 1.39 MBytes [ 5] 5.00-6.00 sec 310 MBytes 2.60 Gbits/sec 0 1.54 MBytes [ 5] 6.00-7.00 sec 336 MBytes 2.82 Gbits/sec 0 1.69 MBytes [ 5] 7.00-8.00 sec 310 MBytes 2.60 Gbits/sec 46 1.27 MBytes [ 5] 8.00-9.00 sec 336 MBytes 2.82 Gbits/sec 0 1.45 MBytes [ 5] 9.00-10.00 sec 329 MBytes 2.76 Gbits/sec 0 1.60 MBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-10.00 sec 2.99 GBytes 2.56 Gbits/sec 129 sender [ 5] 0.00-10.00 sec 2.98 GBytes 2.56 Gbits/sec receiver iperf Done.
Step 7: Run command service firewall FW show logging fast | tail at DUT0 and check if output matches the following regular expressions:
(?m)^.+(Skipping test network performance traffic).+$Show output
03/23/2026-11:21:03.752336 [**] [1:40:0] Skipping test network performance traffic [**] [Classification: (null)] [Priority: 3] {TCP} 20.0.0.2:46642 -> 40.0.0.2:5001 03/23/2026-11:21:03.753374 [**] [1:40:0] Skipping test network performance traffic [**] [Classification: (null)] [Priority: 3] {TCP} 20.0.0.2:46658 -> 40.0.0.2:5001
Step 8: Run command system conntrack show at DUT0 and check if output matches the following regular expressions:
(?m)^tcp\s+.*src=20.0.0.2 dst=40.0.0.2.+dport=5001.*mark=129834765.*$Show output
tcp 6 9 CLOSE src=20.0.0.2 dst=40.0.0.2 sport=46658 dport=5001 packets=2213163 bytes=3319726009 src=40.0.0.2 dst=20.0.0.2 sport=5001 dport=46658 packets=243682 bytes=12660384 [ASSURED] (Sc: not-bypass) mark=129834765 use=1 icmp 1 19 src=40.0.0.2 dst=20.0.0.2 type=8 code=0 id=310 packets=1 bytes=84 src=20.0.0.2 dst=40.0.0.2 type=0 code=0 id=310 packets=1 bytes=84 (Sc: not-bypass) mark=0 use=1 icmp 1 19 src=20.0.0.2 dst=40.0.0.2 type=8 code=0 id=56 packets=1 bytes=84 src=40.0.0.2 dst=20.0.0.2 type=0 code=0 id=56 packets=1 bytes=84 (Sc: not-bypass) mark=0 use=1 tcp 6 19 TIME_WAIT src=20.0.0.2 dst=40.0.0.2 sport=46642 dport=5001 packets=16 bytes=1300 src=40.0.0.2 dst=20.0.0.2 sport=5001 dport=46642 packets=13 bytes=1019 [ASSURED] (Sc: not-bypass) mark=129834765 use=1 conntrack v1.4.7 (conntrack-tools): 4 flow entries have been shown.
Note
The following steps are just a reiteration of the previous test, but with the difference that the conntrack mark used is an extra connmark.
Step 9: Modify the following configuration lines in DUT0 :
set service firewall FW stream bypass extra-mark 2 mask 3294967295 set service firewall FW stream bypass extra-mark 2 set-extra-connmark set service firewall FW stream bypass extra-mark 2 value 3294967295 set traffic policy FW_PLAN rule 2 selector FW_SEL_EXTRA_MARK set traffic selector FW_SEL_EXTRA_MARK rule 1 not extra-connmark 2 value 3294967295
Step 10: Initiate a bandwidth test from DUT2 to DUT1
admin@DUT1$ monitor test performance server port 5001 admin@DUT2$ monitor test performance client 40.0.0.2 duration 10 port 5001 parallel 1Expect this output in
DUT2:Connecting to host 40.0.0.2, port 5001 [ 5] local 20.0.0.2 port 48820 connected to 40.0.0.2 port 5001 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 288 MBytes 2.41 Gbits/sec 51 1.88 MBytes [ 5] 1.00-2.00 sec 328 MBytes 2.75 Gbits/sec 0 2.04 MBytes [ 5] 2.00-3.00 sec 308 MBytes 2.58 Gbits/sec 22 1.56 MBytes [ 5] 3.00-4.00 sec 362 MBytes 3.04 Gbits/sec 0 1.72 MBytes [ 5] 4.00-5.00 sec 352 MBytes 2.95 Gbits/sec 0 1.87 MBytes [ 5] 5.00-6.00 sec 340 MBytes 2.86 Gbits/sec 0 2.00 MBytes [ 5] 6.00-7.00 sec 361 MBytes 3.03 Gbits/sec 0 2.12 MBytes [ 5] 7.00-8.00 sec 349 MBytes 2.93 Gbits/sec 0 2.23 MBytes [ 5] 8.00-9.00 sec 345 MBytes 2.89 Gbits/sec 38 1.67 MBytes [ 5] 9.00-10.00 sec 244 MBytes 2.04 Gbits/sec 0 1.84 MBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-10.00 sec 3.20 GBytes 2.75 Gbits/sec 111 sender [ 5] 0.00-10.00 sec 3.20 GBytes 2.75 Gbits/sec receiver iperf Done.
Step 11: Run command service firewall FW show logging fast | tail at DUT0 and check if output matches the following regular expressions:
(?m)^.+(Skipping test network performance traffic).+$Show output
03/23/2026-11:21:03.752336 [**] [1:40:0] Skipping test network performance traffic [**] [Classification: (null)] [Priority: 3] {TCP} 20.0.0.2:46642 -> 40.0.0.2:5001 03/23/2026-11:21:03.753374 [**] [1:40:0] Skipping test network performance traffic [**] [Classification: (null)] [Priority: 3] {TCP} 20.0.0.2:46658 -> 40.0.0.2:5001 03/23/2026-11:21:19.554232 [**] [1:40:0] Skipping test network performance traffic [**] [Classification: (null)] [Priority: 3] {TCP} 20.0.0.2:48812 -> 40.0.0.2:5001 03/23/2026-11:21:19.555333 [**] [1:40:0] Skipping test network performance traffic [**] [Classification: (null)] [Priority: 3] {TCP} 20.0.0.2:48820 -> 40.0.0.2:5001
Step 12: Run command system conntrack show at DUT0 and check if output matches the following regular expressions:
(?m)^tcp\s+.*src=20.0.0.2 dst=40.0.0.2.+dport=5001.*emark2=3294967295.*$Show output
tcp 6 19 TIME_WAIT src=20.0.0.2 dst=40.0.0.2 sport=48812 dport=5001 packets=16 bytes=1295 src=40.0.0.2 dst=20.0.0.2 sport=5001 dport=48812 packets=13 bytes=1020 [ASSURED] (Sc: not-bypass) mark=129834765 emark2=3294967295 use=1 tcp 6 9 CLOSE src=20.0.0.2 dst=40.0.0.2 sport=48820 dport=5001 packets=2372526 bytes=3558768517 src=40.0.0.2 dst=20.0.0.2 sport=5001 dport=48820 packets=276644 bytes=14379696 [ASSURED] (Sc: not-bypass) mark=129834765 emark2=3294967295 use=1 conntrack v1.4.7 (conntrack-tools): 2 flow entries have been shown.
Test Bypass-Drop Using Conntrack Marks
Description
Builds a scenario with three DUTs in which a performance test is conducted between DUT1 and DUT2, and DUT0 is the router running the firewall. This test is aimed at configuring “Capture bypass drop” to avoid dropped packets from entering the firewall.
Scenario
Step 1: Run command file copy http://10.215.168.1/~robot/drop-performance.rules running:// force at DUT0 and expect this output:
Show output
% Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 200 100 200 0 0 3492 0 --:--:-- --:--:-- --:--:-- 3508
Step 2: Run command file show running://drop-performance.rules at DUT0 and expect this output:
Show output
drop tcp any any -> any 5000 (msg: "Dropping TCP performance test traffic"; sid: 1; flow: established, to_server;) drop udp any any -> any 5001 (msg: "Dropping UDP performance test traffic"; sid: 2;)
Step 3: Set the following configuration in DUT0 :
set interfaces ethernet eth0 address 10.215.168.64/24 set interfaces ethernet eth0 traffic nat source rule 1 address masquerade set interfaces ethernet eth1 vif 101 address 40.0.0.1/8 set interfaces ethernet eth1 vif 101 traffic policy in FW_PLAN set interfaces ethernet eth1 vif 201 address 20.0.0.1/8 set interfaces ethernet eth1 vif 201 traffic policy in FW_PLAN set protocols static route 0.0.0.0/0 next-hop 10.215.168.1 set service dns static host-name WAN inet 10.215.168.1 set service firewall FW bypass action drop set connmark mark 147652983 set service firewall FW logging level config set service firewall FW logging outputs fast set service firewall FW mode inline queue FW_Q set service firewall FW ruleset file 'running://drop-performance.rules' set service firewall FW validator-timeout 20 set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0' set traffic policy FW_PLAN rule 1 action drop set traffic policy FW_PLAN rule 1 selector FW_SEL_DROP set traffic policy FW_PLAN rule 2 action enqueue FW_Q set traffic queue FW_Q elements 1 set traffic selector FW_SEL_DROP rule 1 connmark 147652983
Step 4: Ping IP address 20.0.0.2 from DUT1:
admin@DUT1$ ping 20.0.0.2 count 1 size 56 timeout 1Show output
PING 20.0.0.2 (20.0.0.2) 56(84) bytes of data. 64 bytes from 20.0.0.2: icmp_seq=1 ttl=63 time=0.555 ms --- 20.0.0.2 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.555/0.555/0.555/0.000 ms
Step 5: Ping IP address 40.0.0.2 from DUT2:
admin@DUT2$ ping 40.0.0.2 count 1 size 56 timeout 1Show output
PING 40.0.0.2 (40.0.0.2) 56(84) bytes of data. 64 bytes from 40.0.0.2: icmp_seq=1 ttl=63 time=0.533 ms --- 40.0.0.2 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.533/0.533/0.533/0.000 ms
Step 6: Initiate a bandwidth test from DUT2 to DUT1
admin@DUT1$ monitor test performance server port 5000 admin@DUT2$ monitor test performance client 40.0.0.2 duration 10 port 5000 parallel 1Expect this output in
DUT2:^C- - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr iperf3: interrupt - the client has terminated admin@osdx$
Step 7: Run command service firewall FW show logging fast | tail at DUT0 and check if output matches the following regular expressions:
(?m)^.+(Dropping TCP performance test traffic).+$Show output
03/23/2026-11:21:58.486102 [Drop] [**] [1:1:0] Dropping TCP performance test traffic [**] [Classification: (null)] [Priority: 3] {TCP} 20.0.0.2:42124 -> 40.0.0.2:5000
Step 8: Run command system conntrack show at DUT0 and check if output matches the following regular expressions:
(?m)^tcp\s+.*src=20.0.0.2 dst=40.0.0.2.+dport=5000.*mark=147652983.*$Show output
icmp 1 26 src=40.0.0.2 dst=20.0.0.2 type=8 code=0 id=313 packets=1 bytes=84 src=20.0.0.2 dst=40.0.0.2 type=0 code=0 id=313 packets=1 bytes=84 (Sc: not-bypass) mark=0 use=1 tcp 6 19 TIME_WAIT src=20.0.0.2 dst=40.0.0.2 sport=42124 dport=5000 packets=8 bytes=646 src=40.0.0.2 dst=20.0.0.2 sport=5000 dport=42124 packets=4 bytes=217 [ASSURED] (Sc: not-bypass) mark=147652983 use=1 icmp 1 26 src=20.0.0.2 dst=40.0.0.2 type=8 code=0 id=59 packets=1 bytes=84 src=40.0.0.2 dst=20.0.0.2 type=0 code=0 id=59 packets=1 bytes=84 (Sc: not-bypass) mark=0 use=1 conntrack v1.4.7 (conntrack-tools): 3 flow entries have been shown.
Step 9: Run command traffic policy FW_PLAN show at DUT0 and check if output matches the following regular expressions:
(?m)^1\s+FW_SEL_DROP\s+[1-9].*$Show output
Policy FW_PLAN -- ifc eth1.101 -- hook in prio very-high ------------------------------------------------------------------ rule selector pkts match pkts eval bytes match bytes eval ------------------------------------------------------------------ 1 FW_SEL_DROP 4 7 210 438 2 - 3 3 228 228 ------------------------------------------------------------------ Total 7 7 438 438 Policy FW_PLAN -- ifc eth1.201 -- hook in prio very-high ------------------------------------------------------------------ rule selector pkts match pkts eval bytes match bytes eval ------------------------------------------------------------------ 1 FW_SEL_DROP 5 10 445 814 2 - 5 5 369 369 ------------------------------------------------------------------ Total 10 10 814 814
Note
Testing with another conntrack mark.
Step 10: Modify the following configuration lines in DUT0 :
delete service firewall FW bypass action drop set connmark mark set service firewall FW bypass action drop set connmark extra-mark 2 value 3967295294 set traffic policy FW_PLAN rule 1 selector FW_SEL_DROP_EM set traffic selector FW_SEL_DROP_EM rule 1 extra-connmark 2 value 3967295294
Step 11: Initiate a bandwidth test from DUT2 to DUT1
admin@DUT1$ monitor test performance server port 5000 admin@DUT2$ monitor test performance client 40.0.0.2 duration 10 port 5000 parallel 1Expect this output in
DUT2:^C- - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr iperf3: interrupt - the client has terminated admin@osdx$
Step 12: Run command service firewall FW show logging fast | tail at DUT0 and check if output matches the following regular expressions:
(?m)^.+(Dropping TCP performance test traffic).+$Show output
03/23/2026-11:21:58.486102 [Drop] [**] [1:1:0] Dropping TCP performance test traffic [**] [Classification: (null)] [Priority: 3] {TCP} 20.0.0.2:42124 -> 40.0.0.2:5000 03/23/2026-11:22:04.809700 [Drop] [**] [1:1:0] Dropping TCP performance test traffic [**] [Classification: (null)] [Priority: 3] {TCP} 20.0.0.2:42124 -> 40.0.0.2:5000 03/23/2026-11:22:06.274485 [Drop] [**] [1:1:0] Dropping TCP performance test traffic [**] [Classification: (null)] [Priority: 3] {TCP} 20.0.0.2:32828 -> 40.0.0.2:5000
Step 13: Run command system conntrack show at DUT0 and check if output matches the following regular expressions:
(?m)^tcp\s+.*src=20.0.0.2 dst=40.0.0.2.+dport=5000.*emark2=3967295294.*$Show output
tcp 6 29 LAST_ACK src=20.0.0.2 dst=40.0.0.2 sport=32828 dport=5000 packets=7 bytes=557 src=40.0.0.2 dst=20.0.0.2 sport=5000 dport=32828 packets=4 bytes=217 [ASSURED] (Sc: not-bypass) mark=0 emark2=3967295294 use=1 conntrack v1.4.7 (conntrack-tools): 1 flow entries have been shown.
Step 14: Run command traffic policy FW_PLAN show at DUT0 and check if output matches the following regular expressions:
(?m)^1\s+FW_SEL_DROP_EM\s+[1-9].*$Show output
Policy FW_PLAN -- ifc eth1.101 -- hook in prio very-high --------------------------------------------------------------------- rule selector pkts match pkts eval bytes match bytes eval --------------------------------------------------------------------- 1 FW_SEL_DROP_EM 4 7 210 376 2 - 3 3 166 166 --------------------------------------------------------------------- Total 7 7 376 376 Policy FW_PLAN -- ifc eth1.201 -- hook in prio very-high --------------------------------------------------------------------- rule selector pkts match pkts eval bytes match bytes eval --------------------------------------------------------------------- 1 FW_SEL_DROP_EM 5 10 445 775 2 - 5 5 330 330 --------------------------------------------------------------------- Total 10 10 775 775
Test Capture And Offload
Description
Builds a scenario with three DUTs in which a performance test is conducted between DUT1 and DUT2, and DUT0 is the router running the firewall. This test sets the conntrack mark directly, thus skipping all the steps required to set it later. In addition, OSDx is instructed to accelerate the flow using internal accelerators.
Performance must improve considerably compared to the previous test, to reach its top value.
Scenario
Step 1: Run command file copy http://10.215.168.1/~robot/test-performance.rules running:// force at DUT0 and expect this output:
Show output
% Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 129 100 129 0 0 21255 0 --:--:-- --:--:-- --:--:-- 21500
Step 2: Run command file show running://test-performance.rules at DUT0 and expect this output:
Show output
alert tcp any any -> any 5001 (msg: "Skipping test network performance traffic"; bypass; flow: established, to_server; sid: 40;)
Step 3: Set the following configuration in DUT0 :
set interfaces ethernet eth0 address 10.215.168.64/24 set interfaces ethernet eth0 traffic nat source rule 1 address masquerade set interfaces ethernet eth1 vif 101 address 40.0.0.1/8 set interfaces ethernet eth1 vif 101 traffic policy in FW_PLAN set interfaces ethernet eth1 vif 201 address 20.0.0.1/8 set interfaces ethernet eth1 vif 201 traffic policy in FW_PLAN set protocols static route 0.0.0.0/0 next-hop 10.215.168.1 set service dns static host-name WAN inet 10.215.168.1 set service firewall FW logging level config set service firewall FW logging outputs fast set service firewall FW mode inline queue FW_Q set service firewall FW ruleset file 'running://test-performance.rules' set service firewall FW stream bypass action accept set conntrack offload-flag set service firewall FW stream bypass mark 129834765 set service firewall FW stream bypass mask 129834765 set service firewall FW stream bypass set-connmark set service firewall FW validator-timeout 20 set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0' set traffic policy FW_PLAN rule 1 action enqueue FW_Q set traffic policy FW_PLAN rule 2 action enqueue FW_Q set traffic policy FW_PLAN rule 2 selector FW_SEL_ENQUEUE set traffic queue FW_Q elements 1 set traffic selector FW_SEL_ENQUEUE rule 1 not connmark 129834765
Step 4: Ping IP address 20.0.0.2 from DUT1:
admin@DUT1$ ping 20.0.0.2 count 1 size 56 timeout 1Show output
PING 20.0.0.2 (20.0.0.2) 56(84) bytes of data. 64 bytes from 20.0.0.2: icmp_seq=1 ttl=63 time=0.614 ms --- 20.0.0.2 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.614/0.614/0.614/0.000 ms
Step 5: Ping IP address 40.0.0.2 from DUT2:
admin@DUT2$ ping 40.0.0.2 count 1 size 56 timeout 1Show output
PING 40.0.0.2 (40.0.0.2) 56(84) bytes of data. 64 bytes from 40.0.0.2: icmp_seq=1 ttl=63 time=0.609 ms --- 40.0.0.2 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.609/0.609/0.609/0.000 ms
Step 6: Initiate a background bandwidth test from DUT2 to DUT1. The control is returned back allowing to perform another tasks while test is running
admin@DUT1$ monitor test performance server port 5001 admin@DUT2$ monitor test performance client 40.0.0.2 duration 10 port 5001 parallel 1
Step 7: Run command service firewall FW show logging fast | tail at DUT0 and check if output matches the following regular expressions:
(?m)^.+(Skipping test network performance traffic).+$Show output
03/23/2026-11:22:29.101076 [**] [1:40:0] Skipping test network performance traffic [**] [Classification: (null)] [Priority: 3] {TCP} 20.0.0.2:54130 -> 40.0.0.2:5001 03/23/2026-11:22:29.102270 [**] [1:40:0] Skipping test network performance traffic [**] [Classification: (null)] [Priority: 3] {TCP} 20.0.0.2:54144 -> 40.0.0.2:5001
Step 8: Run command system conntrack show at DUT0 and check if output matches the following regular expressions:
(?m)^tcp\s+.*src=20.0.0.2 dst=40.0.0.2.+dport=5001.+OFFLOAD.+mark=129834765.*$Show output
tcp 6 src=20.0.0.2 dst=40.0.0.2 sport=54130 dport=5001 packets=8 bytes=589 src=40.0.0.2 dst=20.0.0.2 sport=5001 dport=54130 packets=7 bytes=376 [ASSURED] [OFFLOAD, packets=2 bytes=104 packets=4 bytes=211] mark=129834765 use=3 tcp 6 src=20.0.0.2 dst=40.0.0.2 sport=54144 dport=5001 packets=58965 bytes=88442001 src=40.0.0.2 dst=20.0.0.2 sport=5001 dport=54144 packets=5736 bytes=299372 [ASSURED] [OFFLOAD, packets=58952 bytes=88426800 packets=5734 bytes=299260] mark=129834765 use=2 icmp 1 29 src=40.0.0.2 dst=20.0.0.2 type=8 code=0 id=316 packets=1 bytes=84 src=20.0.0.2 dst=40.0.0.2 type=0 code=0 id=316 packets=1 bytes=84 (Sc: not-bypass) mark=0 use=1 icmp 1 29 src=20.0.0.2 dst=40.0.0.2 type=8 code=0 id=62 packets=1 bytes=84 src=40.0.0.2 dst=20.0.0.2 type=0 code=0 id=62 packets=1 bytes=84 (Sc: not-bypass) mark=0 use=1 conntrack v1.4.7 (conntrack-tools): 4 flow entries have been shown.
Step 9: Stop the current bandwidth test between DUT2 and DUT1
Step 10: Run command file copy http://10.215.168.1/~robot/test-performance-udp.rules running:// force at DUT0 and expect this output:
Show output
% Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 133 100 133 0 0 7036 0 --:--:-- --:--:-- --:--:-- 7388
Step 11: Run command file show running://test-performance-udp.rules at DUT0 and expect this output:
Show output
alert udp any any -> any 5001 (msg: "Skipping test network performance UDP traffic"; bypass; flow: established, to_server; sid: 41;)
Step 12: Modify the following configuration lines in DUT0 :
set service firewall FW ruleset file 'running://test-performance-udp.rules'
Step 13: Initiate a background bandwidth test from DUT2 to DUT1. The control is returned back allowing to perform another tasks while test is running
admin@DUT1$ monitor test performance server port 5001 admin@DUT2$ monitor test performance client 40.0.0.2 duration 10 udp port 5001 parallel 1
Step 14: Run command service firewall FW show logging fast | tail at DUT0 and check if output matches the following regular expressions:
(?m)^.+(Skipping test network performance UDP traffic).+$Show output
03/23/2026-11:22:29.101076 [**] [1:40:0] Skipping test network performance traffic [**] [Classification: (null)] [Priority: 3] {TCP} 20.0.0.2:54130 -> 40.0.0.2:5001 03/23/2026-11:22:29.102270 [**] [1:40:0] Skipping test network performance traffic [**] [Classification: (null)] [Priority: 3] {TCP} 20.0.0.2:54144 -> 40.0.0.2:5001 03/23/2026-11:22:30.996515 [**] [1:40:0] Skipping test network performance traffic [**] [Classification: (null)] [Priority: 3] {TCP} 20.0.0.2:54156 -> 40.0.0.2:5001 03/23/2026-11:22:30.997952 [**] [1:41:0] Skipping test network performance UDP traffic [**] [Classification: (null)] [Priority: 3] {UDP} 20.0.0.2:40863 -> 40.0.0.2:5001 03/23/2026-11:22:31.008717 [**] [1:41:0] Skipping test network performance UDP traffic [**] [Classification: (null)] [Priority: 3] {UDP} 20.0.0.2:40863 -> 40.0.0.2:5001
Step 15: Run command system conntrack show at DUT0 and check if output matches the following regular expressions:
(?m)^udp\s+.*src=20.0.0.2 dst=40.0.0.2.+dport=5001.+OFFLOAD.+mark=129834765.*$Show output
tcp 6 src=20.0.0.2 dst=40.0.0.2 sport=54156 dport=5001 packets=8 bytes=607 src=40.0.0.2 dst=20.0.0.2 sport=5001 dport=54156 packets=7 bytes=376 [ASSURED] [OFFLOAD, packets=2 bytes=104 packets=4 bytes=211] mark=129834765 use=3 udp 17 src=20.0.0.2 dst=40.0.0.2 sport=40863 dport=5001 packets=10 bytes=13316 src=40.0.0.2 dst=20.0.0.2 sport=5001 dport=40863 packets=1 bytes=32 [OFFLOAD, packets=6 bytes=8856 packets=0 bytes=0] mark=129834765 use=2 conntrack v1.4.7 (conntrack-tools): 2 flow entries have been shown.
Step 16: Stop the current bandwidth test between DUT2 and DUT1
Test Traffic Early Dropping
Description
Builds a scenario with three DUTs and a simple ruleset to drop TCP traffic between DUT1 and DUT2. Such traffic must pass through port 5000 for the rule to match. Later, XDP is queried to check if packets are being dropped at the specified interface.
The contents of the rule file are:
drop tcp any any -> any 5000 (msg: "Dropping TCP performance test traffic"; sid: 1; flow: established, to_server;)
This rule allows the connection to be established and traffic to be dropped later.
Scenario
Step 1: Run command file copy http://10.215.168.1/~robot/drop-performance.rules running://drop-performance.rules force at DUT0 and expect this output:
Show output
% Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 200 100 200 0 0 35517 0 --:--:-- --:--:-- --:--:-- 40000
Step 2: Run command file show running://drop-performance.rules at DUT0 and expect this output:
Show output
drop tcp any any -> any 5000 (msg: "Dropping TCP performance test traffic"; sid: 1; flow: established, to_server;) drop udp any any -> any 5001 (msg: "Dropping UDP performance test traffic"; sid: 2;)
Step 3: Set the following configuration in DUT0 :
set interfaces ethernet eth0 address 10.215.168.64/24 set interfaces ethernet eth0 traffic nat source rule 1 address masquerade set interfaces ethernet eth1 vif 101 address 40.0.0.1/8 set interfaces ethernet eth1 vif 101 traffic policy in FW_PLAN set interfaces ethernet eth1 vif 201 address 20.0.0.1/8 set interfaces ethernet eth1 vif 201 traffic policy in FW_PLAN set protocols static route 0.0.0.0/0 next-hop 10.215.168.1 set service dns static host-name WAN inet 10.215.168.1 set service firewall FW logging level config set service firewall FW logging outputs fast set service firewall FW mode inline queue FW_Q set service firewall FW ruleset file 'running://drop-performance.rules' set service firewall FW stream bypass action drop set xdp-early-drop eth1 set service firewall FW validator-timeout 20 set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0' set traffic policy FW_PLAN rule 1 action enqueue FW_Q set traffic queue FW_Q elements 1
Step 4: Ping IP address 20.0.0.2 from DUT1:
admin@DUT1$ ping 20.0.0.2 count 1 size 56 timeout 1Show output
PING 20.0.0.2 (20.0.0.2) 56(84) bytes of data. 64 bytes from 20.0.0.2: icmp_seq=1 ttl=63 time=5.72 ms --- 20.0.0.2 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 5.716/5.716/5.716/0.000 ms
Step 5: Ping IP address 40.0.0.2 from DUT2:
admin@DUT2$ ping 40.0.0.2 count 1 size 56 timeout 1Show output
PING 40.0.0.2 (40.0.0.2) 56(84) bytes of data. 64 bytes from 40.0.0.2: icmp_seq=1 ttl=63 time=0.716 ms --- 40.0.0.2 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.716/0.716/0.716/0.000 ms
Step 6: Initiate a bandwidth test from DUT2 to DUT1
admin@DUT1$ monitor test performance server port 5000 admin@DUT2$ monitor test performance client 40.0.0.2 duration 10 port 5000 parallel 1Expect this output in
DUT2:^C- - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr iperf3: interrupt - the client has terminated admin@osdx$
Step 7: Run command service firewall FW show logging fast | tail at DUT0 and check if output matches the following regular expressions:
(?m)^.+(Dropping TCP performance test traffic).+$Show output
03/23/2026-11:22:52.704610 [Drop] [**] [1:1:0] Dropping TCP performance test traffic [**] [Classification: (null)] [Priority: 3] {TCP} 20.0.0.2:34048 -> 40.0.0.2:5000
Step 8: Run command service firewall FW show early-drop-stats eth1 at DUT0 and check if output matches the following regular expressions:
yes\s+201\s+\d+\s+[1-9]\d*\s+[1-9]\d*Show output
------------------------------------------------------------------------ src dst src port dst port tcp vlan_0 vlan_1 pkts bytes ------------------------------------------------------------------------ 40.0.0.2 20.0.0.2 5000 34048 yes 201 0 0 0 20.0.0.2 40.0.0.2 34048 5000 yes 201 0 6 544
Step 9: Run command interfaces ethernet eth1 monitor xdp-stats times 1 at DUT0 and expect this output:
Show output
Pin path: /sys/fs/bpf/eth1 Period of 0.250137s ending at 1774264976.309866 XDP_DROP 7 pkts ( 0 pps) 0 KiB ( 0 Mbits/s) XDP_PASS 11434600 pkts ( 0 pps) 15187658 KiB ( 0 Mbits/s) XDP_TX 0 pkts ( 0 pps) 0 KiB ( 0 Mbits/s) XDP_REDIRECT 0 pkts ( 0 pps) 0 KiB ( 0 Mbits/s)
Step 10: Initiate a bandwidth test from DUT2 to DUT1
admin@DUT1$ monitor test performance server port 5001 admin@DUT2$ monitor test performance client 40.0.0.2 duration 30 udp port 5001 parallel 1Expect this output in
DUT2:^C- - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Jitter Lost/Total Datagrams iperf3: interrupt - the client has terminated admin@osdx$
Step 11: Run command service firewall FW show logging fast | tail at DUT0 and check if output matches the following regular expressions:
(?m)^.+(Dropping UDP performance test traffic).+$Show output
03/23/2026-11:22:52.704610 [Drop] [**] [1:1:0] Dropping TCP performance test traffic [**] [Classification: (null)] [Priority: 3] {TCP} 20.0.0.2:34048 -> 40.0.0.2:5000 03/23/2026-11:22:56.471185 [Drop] [**] [1:2:0] Dropping UDP performance test traffic [**] [Classification: (null)] [Priority: 3] {UDP} 20.0.0.2:37232 -> 40.0.0.2:5001
Step 12: Run command service firewall FW show early-drop-stats eth1 at DUT0 and check if output matches the following regular expressions:
yes\s+201\s+\d+\s+[1-9]\d*\s+[1-9]\d*Show output
------------------------------------------------------------------------ src dst src port dst port tcp vlan_0 vlan_1 pkts bytes ------------------------------------------------------------------------ 40.0.0.2 20.0.0.2 5000 34048 yes 201 0 0 0 20.0.0.2 40.0.0.2 34048 5000 yes 201 0 10 776 40.0.0.2 20.0.0.2 5001 37232 no 201 0 0 0 20.0.0.2 40.0.0.2 37232 5001 no 201 0 0 0
Step 13: Run command interfaces ethernet eth1 monitor xdp-stats times 1 at DUT0 and expect this output:
Show output
Pin path: /sys/fs/bpf/eth1 Period of 0.250146s ending at 1774264980.166988 XDP_DROP 10 pkts ( 0 pps) 0 KiB ( 0 Mbits/s) XDP_PASS 11434640 pkts ( 0 pps) 15187661 KiB ( 0 Mbits/s) XDP_TX 0 pkts ( 0 pps) 0 KiB ( 0 Mbits/s) XDP_REDIRECT 0 pkts ( 0 pps) 0 KiB ( 0 Mbits/s)