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 46153 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.757 ms --- 20.0.0.2 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.757/0.757/0.757/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.560 ms --- 40.0.0.2 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.560/0.560/0.560/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 47366 connected to 40.0.0.2 port 5001 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 143 MBytes 1.20 Gbits/sec 45 1.78 MBytes [ 5] 1.00-2.00 sec 140 MBytes 1.17 Gbits/sec 0 1.94 MBytes [ 5] 2.00-3.00 sec 148 MBytes 1.24 Gbits/sec 0 2.07 MBytes [ 5] 3.00-4.00 sec 144 MBytes 1.21 Gbits/sec 0 2.17 MBytes [ 5] 4.00-5.00 sec 83.8 MBytes 703 Mbits/sec 0 2.24 MBytes [ 5] 5.00-6.00 sec 52.5 MBytes 440 Mbits/sec 0 2.30 MBytes [ 5] 6.00-7.00 sec 51.2 MBytes 430 Mbits/sec 0 2.34 MBytes [ 5] 7.00-8.00 sec 55.0 MBytes 461 Mbits/sec 0 2.36 MBytes [ 5] 8.00-9.00 sec 53.8 MBytes 451 Mbits/sec 0 2.37 MBytes [ 5] 9.00-10.00 sec 52.5 MBytes 440 Mbits/sec 0 2.37 MBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-10.00 sec 923 MBytes 774 Mbits/sec 45 sender [ 5] 0.00-10.02 sec 923 MBytes 772 Mbits/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
05/04/2026-22:07:47.533444 [**] [1:40:0] Skipping test network performance traffic [**] [Classification: (null)] [Priority: 3] {TCP} 20.0.0.2:47352 -> 40.0.0.2:5001 05/04/2026-22:07:47.534386 [**] [1:40:0] Skipping test network performance traffic [**] [Classification: (null)] [Priority: 3] {TCP} 20.0.0.2:47366 -> 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 28073 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.553 ms --- 20.0.0.2 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.553/0.553/0.553/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.746 ms --- 40.0.0.2 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.746/0.746/0.746/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 56178 connected to 40.0.0.2 port 5001 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 369 MBytes 3.10 Gbits/sec 27 1.84 MBytes [ 5] 1.00-2.00 sec 385 MBytes 3.23 Gbits/sec 0 2.01 MBytes [ 5] 2.00-3.00 sec 359 MBytes 3.01 Gbits/sec 240 1.57 MBytes [ 5] 3.00-4.00 sec 361 MBytes 3.03 Gbits/sec 0 1.73 MBytes [ 5] 4.00-5.00 sec 341 MBytes 2.86 Gbits/sec 0 1.87 MBytes [ 5] 5.00-6.00 sec 359 MBytes 3.01 Gbits/sec 0 2.00 MBytes [ 5] 6.00-7.00 sec 348 MBytes 2.92 Gbits/sec 0 2.13 MBytes [ 5] 7.00-8.00 sec 365 MBytes 3.06 Gbits/sec 2 1.57 MBytes [ 5] 8.00-9.00 sec 346 MBytes 2.90 Gbits/sec 0 1.75 MBytes [ 5] 9.00-10.00 sec 369 MBytes 3.09 Gbits/sec 0 1.88 MBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-10.00 sec 3.52 GBytes 3.02 Gbits/sec 269 sender [ 5] 0.00-10.00 sec 3.52 GBytes 3.02 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
05/04/2026-22:08:18.398722 [**] [1:40:0] Skipping test network performance traffic [**] [Classification: (null)] [Priority: 3] {TCP} 20.0.0.2:56168 -> 40.0.0.2:5001 05/04/2026-22:08:18.399589 [**] [1:40:0] Skipping test network performance traffic [**] [Classification: (null)] [Priority: 3] {TCP} 20.0.0.2:56178 -> 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
May 04 22:08:11.000186 osdx systemd-timedated[89209]: Changed local time to Mon 2026-05-04 22:08:11 UTC May 04 22:08:11.000579 osdx systemd[1]: Started systemd-timedated.service - Time & Date Service. May 04 22:08:11.001531 osdx OSDxCLI[88731]: User 'admin' executed a new command: 'set date 2026-05-04 22:08:11'. May 04 22:08:11.002240 osdx systemd-journald[1908]: Time jumped backwards, rotating. May 04 22:08:11.282110 osdx systemd-journald[1908]: Runtime Journal (/run/log/journal/9e2a66651dea45ed982d8152051049c2) is 2.4M, max 13.8M, 11.3M free. May 04 22:08:11.282686 osdx systemd-journald[1908]: Received client request to rotate journal, rotating. May 04 22:08:11.282728 osdx systemd-journald[1908]: Vacuuming done, freed 0B of archived journals from /run/log/journal/9e2a66651dea45ed982d8152051049c2. May 04 22:08:11.291283 osdx OSDxCLI[88731]: User 'admin' executed a new command: 'system journal clear'. May 04 22:08:11.508862 osdx OSDxCLI[88731]: User 'admin' executed a new command: 'system coredump delete all'. May 04 22:08:11.716677 osdx OSDxCLI[88731]: User 'admin' entered the configuration menu. May 04 22:08:11.836131 osdx OSDxCLI[88731]: User 'admin' added a new cfg line: 'set interfaces ethernet eth0 address 10.215.168.64/24'. May 04 22:08:11.887342 osdx OSDxCLI[88731]: User 'admin' added a new cfg line: 'set interfaces ethernet eth0 traffic nat source rule 1 address masquerade'. May 04 22:08:11.980794 osdx OSDxCLI[88731]: User 'admin' added a new cfg line: 'set protocols static route 0.0.0.0/0 next-hop 10.215.168.1'. May 04 22:08:12.032732 osdx OSDxCLI[88731]: User 'admin' added a new cfg line: 'set service dns static host-name WAN inet 10.215.168.1'. May 04 22:08:12.127555 osdx OSDxCLI[88731]: User 'admin' added a new cfg line: 'set interfaces ethernet eth1 vif 101 address 40.0.0.1/8'. May 04 22:08:12.176594 osdx OSDxCLI[88731]: User 'admin' added a new cfg line: 'set interfaces ethernet eth1 vif 201 address 20.0.0.1/8'. May 04 22:08:12.281823 osdx OSDxCLI[88731]: User 'admin' added a new cfg line: 'show working'. May 04 22:08:12.340219 osdx ubnt-cfgd[89242]: inactive May 04 22:08:12.364188 osdx INFO[89248]: FRR daemons did not change May 04 22:08:12.390246 osdx kernel: 8021q: adding VLAN 0 to HW filter on device eth1 May 04 22:08:12.410495 osdx WARNING[89288]: No supported link modes on interface eth1 May 04 22:08:12.411800 osdx modulelauncher[89288]: osdx.utils.xos cmd error: /sbin/ethtool -A eth1 autoneg on May 04 22:08:12.411814 osdx modulelauncher[89288]: Command '/sbin/ethtool -A eth1 autoneg on' returned non-zero exit status 76. May 04 22:08:12.413044 osdx modulelauncher[89288]: osdx.utils.xos cmd error: /sbin/ethtool -s eth1 autoneg on advertise Pause off Asym_Pause off -- May 04 22:08:12.413050 osdx modulelauncher[89288]: Command '/sbin/ethtool -s eth1 autoneg on advertise Pause off Asym_Pause off --' returned non-zero exit status 75. May 04 22:08:12.446250 osdx kernel: 8021q: adding VLAN 0 to HW filter on device eth0 May 04 22:08:12.487310 osdx WARNING[89368]: No supported link modes on interface eth0 May 04 22:08:12.488654 osdx modulelauncher[89368]: osdx.utils.xos cmd error: /sbin/ethtool -A eth0 autoneg on May 04 22:08:12.488666 osdx modulelauncher[89368]: Command '/sbin/ethtool -A eth0 autoneg on' returned non-zero exit status 76. May 04 22:08:12.489786 osdx modulelauncher[89368]: osdx.utils.xos cmd error: /sbin/ethtool -s eth0 autoneg on advertise Pause off Asym_Pause off -- May 04 22:08:12.489793 osdx modulelauncher[89368]: Command '/sbin/ethtool -s eth0 autoneg on advertise Pause off Asym_Pause off --' returned non-zero exit status 75. May 04 22:08:12.499257 osdx (udev-worker)[89384]: Network interface NamePolicy= disabled on kernel command line. May 04 22:08:12.652218 osdx cfgd[1648]: [88731]Completed change to active configuration May 04 22:08:12.663007 osdx OSDxCLI[88731]: User 'admin' committed the configuration. May 04 22:08:12.683441 osdx OSDxCLI[88731]: User 'admin' left the configuration menu. May 04 22:08:14.627279 osdx OSDxCLI[88731]: User 'admin' executed a new command: 'ping 10.215.168.1 count 1 size 56 timeout 1'. May 04 22:08:14.700891 osdx OSDxCLI[88731]: User 'admin' executed a new command: 'ping 40.0.0.2 count 1 size 56 timeout 1'. May 04 22:08:14.808648 osdx OSDxCLI[88731]: User 'admin' executed a new command: 'ping 20.0.0.2 count 1 size 56 timeout 1'. May 04 22:08:15.310041 osdx file_operation[89564]: using src url: http://10.215.168.1/~robot/test-performance.rules dst url: running:// May 04 22:08:15.332899 osdx OSDxCLI[88731]: User 'admin' executed a new command: 'file copy http://10.215.168.1/~robot/test-performance.rules running:// force'. May 04 22:08:15.458414 osdx OSDxCLI[88731]: User 'admin' executed a new command: 'file show running://test-performance.rules'. May 04 22:08:15.602352 osdx OSDxCLI[88731]: User 'admin' entered the configuration menu. May 04 22:08:15.659943 osdx OSDxCLI[88731]: User 'admin' added a new cfg line: 'set service firewall FW ruleset file running://test-performance.rules'. May 04 22:08:15.755758 osdx OSDxCLI[88731]: User 'admin' added a new cfg line: 'set service firewall FW mode inline queue FW_Q'. May 04 22:08:15.807152 osdx OSDxCLI[88731]: User 'admin' added a new cfg line: 'set service firewall FW logging outputs fast'. May 04 22:08:15.898573 osdx OSDxCLI[88731]: User 'admin' added a new cfg line: 'set service firewall FW logging level config'. May 04 22:08:15.950422 osdx OSDxCLI[88731]: User 'admin' added a new cfg line: 'set service firewall FW validator-timeout 20'. May 04 22:08:16.043341 osdx OSDxCLI[88731]: User 'admin' added a new cfg line: 'set traffic queue FW_Q elements 1'. May 04 22:08:16.130367 osdx OSDxCLI[88731]: User 'admin' added a new cfg line: 'set interfaces ethernet eth1 vif 101 traffic policy in FW_PLAN'. May 04 22:08:16.185149 osdx OSDxCLI[88731]: User 'admin' added a new cfg line: 'set interfaces ethernet eth1 vif 201 traffic policy in FW_PLAN'. May 04 22:08:16.273559 osdx OSDxCLI[88731]: User 'admin' added a new cfg line: 'set service firewall FW stream bypass mark 129834765'. May 04 22:08:16.323958 osdx OSDxCLI[88731]: User 'admin' added a new cfg line: 'set service firewall FW stream bypass mask 129834765'. May 04 22:08:16.414725 osdx OSDxCLI[88731]: User 'admin' added a new cfg line: 'set traffic label BYPASS'. May 04 22:08:16.470645 osdx OSDxCLI[88731]: User 'admin' added a new cfg line: 'set traffic policy FW-SKIP rule 1 log prefix SKIP'. May 04 22:08:16.562077 osdx OSDxCLI[88731]: User 'admin' added a new cfg line: 'set traffic policy FW-SKIP rule 1 selector MARKED-PACKETS'. May 04 22:08:16.615875 osdx OSDxCLI[88731]: User 'admin' added a new cfg line: 'set traffic policy FW-SKIP rule 1 set label BYPASS'. May 04 22:08:16.709604 osdx OSDxCLI[88731]: User 'admin' added a new cfg line: 'set traffic selector MARKED-PACKETS rule 1 mark 129834765'. May 04 22:08:16.766223 osdx OSDxCLI[88731]: User 'admin' added a new cfg line: 'set traffic selector FW_SEL_ENQUEUE rule 1 not label BYPASS'. May 04 22:08:16.854765 osdx OSDxCLI[88731]: User 'admin' added a new cfg line: 'set traffic policy FW_PLAN rule 1 selector FW_SEL_ENQUEUE'. May 04 22:08:16.908732 osdx OSDxCLI[88731]: User 'admin' added a new cfg line: 'set interfaces ethernet eth1 vif 101 traffic policy out FW-SKIP'. May 04 22:08:16.999394 osdx OSDxCLI[88731]: User 'admin' added a new cfg line: 'set interfaces ethernet eth1 vif 201 traffic policy out FW-SKIP'. May 04 22:08:17.051748 osdx OSDxCLI[88731]: User 'admin' added a new cfg line: 'set traffic policy FW_PLAN rule 1 action enqueue FW_Q'. May 04 22:08:17.169264 osdx OSDxCLI[88731]: User 'admin' added a new cfg line: 'show working'. May 04 22:08:17.251005 osdx ubnt-cfgd[89612]: inactive May 04 22:08:17.324565 osdx INFO[89657]: FRR daemons did not change May 04 22:08:17.562758 osdx systemd[1]: Reloading. May 04 22:08:17.650254 osdx systemd-sysv-generator[89713]: stat() failed on /etc/init.d/README, ignoring: No such file or directory May 04 22:08:17.778840 osdx systemd[1]: Starting suricata@FW.service - Suricata client "FW" service... May 04 22:08:17.807490 osdx systemd[1]: Started suricata@FW.service - Suricata client "FW" service. May 04 22:08:17.991120 osdx INFO[89694]: Rules successfully loaded May 04 22:08:17.991810 osdx cfgd[1648]: [88731]Completed change to active configuration May 04 22:08:17.993922 osdx OSDxCLI[88731]: User 'admin' committed the configuration. May 04 22:08:18.007976 osdx OSDxCLI[88731]: User 'admin' left the configuration menu. May 04 22:08:18.402879 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=44208 DF PROTO=TCP SPT=56168 DPT=5001 WINDOW=502 RES=0x00 ACK PSH URGP=0 MARK=0x7bd1f0d May 04 22:08:18.402952 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=7449 DF PROTO=TCP SPT=56178 DPT=5001 WINDOW=502 RES=0x00 ACK PSH URGP=0 MARK=0x7bd1f0d May 04 22:08:28.547007 osdx OSDxCLI[88731]: 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 39586 connected to 40.0.0.2 port 5001 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 357 MBytes 2.99 Gbits/sec 58 1.89 MBytes [ 5] 1.00-2.00 sec 361 MBytes 3.03 Gbits/sec 0 2.05 MBytes [ 5] 2.00-3.00 sec 385 MBytes 3.23 Gbits/sec 0 2.17 MBytes [ 5] 3.00-4.00 sec 378 MBytes 3.17 Gbits/sec 11 1.64 MBytes [ 5] 4.00-5.00 sec 395 MBytes 3.31 Gbits/sec 0 1.81 MBytes [ 5] 5.00-6.00 sec 381 MBytes 3.20 Gbits/sec 0 1.96 MBytes [ 5] 6.00-7.00 sec 385 MBytes 3.23 Gbits/sec 0 2.10 MBytes [ 5] 7.00-8.00 sec 371 MBytes 3.11 Gbits/sec 9 1.60 MBytes [ 5] 8.00-9.00 sec 405 MBytes 3.40 Gbits/sec 0 1.78 MBytes [ 5] 9.00-10.00 sec 384 MBytes 3.22 Gbits/sec 0 1.93 MBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-10.00 sec 3.71 GBytes 3.19 Gbits/sec 78 sender [ 5] 0.00-10.00 sec 3.71 GBytes 3.19 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
05/04/2026-22:08:18.398722 [**] [1:40:0] Skipping test network performance traffic [**] [Classification: (null)] [Priority: 3] {TCP} 20.0.0.2:56168 -> 40.0.0.2:5001 05/04/2026-22:08:18.399589 [**] [1:40:0] Skipping test network performance traffic [**] [Classification: (null)] [Priority: 3] {TCP} 20.0.0.2:56178 -> 40.0.0.2:5001 05/04/2026-22:08:33.188828 [**] [1:40:0] Skipping test network performance traffic [**] [Classification: (null)] [Priority: 3] {TCP} 20.0.0.2:39574 -> 40.0.0.2:5001 05/04/2026-22:08:33.189759 [**] [1:40:0] Skipping test network performance traffic [**] [Classification: (null)] [Priority: 3] {TCP} 20.0.0.2:39586 -> 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
May 04 22:08:11.000186 osdx systemd-timedated[89209]: Changed local time to Mon 2026-05-04 22:08:11 UTC May 04 22:08:11.000579 osdx systemd[1]: Started systemd-timedated.service - Time & Date Service. May 04 22:08:11.001531 osdx OSDxCLI[88731]: User 'admin' executed a new command: 'set date 2026-05-04 22:08:11'. May 04 22:08:11.002240 osdx systemd-journald[1908]: Time jumped backwards, rotating. May 04 22:08:11.282110 osdx systemd-journald[1908]: Runtime Journal (/run/log/journal/9e2a66651dea45ed982d8152051049c2) is 2.4M, max 13.8M, 11.3M free. May 04 22:08:11.282686 osdx systemd-journald[1908]: Received client request to rotate journal, rotating. May 04 22:08:11.282728 osdx systemd-journald[1908]: Vacuuming done, freed 0B of archived journals from /run/log/journal/9e2a66651dea45ed982d8152051049c2. May 04 22:08:11.291283 osdx OSDxCLI[88731]: User 'admin' executed a new command: 'system journal clear'. May 04 22:08:11.508862 osdx OSDxCLI[88731]: User 'admin' executed a new command: 'system coredump delete all'. May 04 22:08:11.716677 osdx OSDxCLI[88731]: User 'admin' entered the configuration menu. May 04 22:08:11.836131 osdx OSDxCLI[88731]: User 'admin' added a new cfg line: 'set interfaces ethernet eth0 address 10.215.168.64/24'. May 04 22:08:11.887342 osdx OSDxCLI[88731]: User 'admin' added a new cfg line: 'set interfaces ethernet eth0 traffic nat source rule 1 address masquerade'. May 04 22:08:11.980794 osdx OSDxCLI[88731]: User 'admin' added a new cfg line: 'set protocols static route 0.0.0.0/0 next-hop 10.215.168.1'. May 04 22:08:12.032732 osdx OSDxCLI[88731]: User 'admin' added a new cfg line: 'set service dns static host-name WAN inet 10.215.168.1'. May 04 22:08:12.127555 osdx OSDxCLI[88731]: User 'admin' added a new cfg line: 'set interfaces ethernet eth1 vif 101 address 40.0.0.1/8'. May 04 22:08:12.176594 osdx OSDxCLI[88731]: User 'admin' added a new cfg line: 'set interfaces ethernet eth1 vif 201 address 20.0.0.1/8'. May 04 22:08:12.281823 osdx OSDxCLI[88731]: User 'admin' added a new cfg line: 'show working'. May 04 22:08:12.340219 osdx ubnt-cfgd[89242]: inactive May 04 22:08:12.364188 osdx INFO[89248]: FRR daemons did not change May 04 22:08:12.390246 osdx kernel: 8021q: adding VLAN 0 to HW filter on device eth1 May 04 22:08:12.410495 osdx WARNING[89288]: No supported link modes on interface eth1 May 04 22:08:12.411800 osdx modulelauncher[89288]: osdx.utils.xos cmd error: /sbin/ethtool -A eth1 autoneg on May 04 22:08:12.411814 osdx modulelauncher[89288]: Command '/sbin/ethtool -A eth1 autoneg on' returned non-zero exit status 76. May 04 22:08:12.413044 osdx modulelauncher[89288]: osdx.utils.xos cmd error: /sbin/ethtool -s eth1 autoneg on advertise Pause off Asym_Pause off -- May 04 22:08:12.413050 osdx modulelauncher[89288]: Command '/sbin/ethtool -s eth1 autoneg on advertise Pause off Asym_Pause off --' returned non-zero exit status 75. May 04 22:08:12.446250 osdx kernel: 8021q: adding VLAN 0 to HW filter on device eth0 May 04 22:08:12.487310 osdx WARNING[89368]: No supported link modes on interface eth0 May 04 22:08:12.488654 osdx modulelauncher[89368]: osdx.utils.xos cmd error: /sbin/ethtool -A eth0 autoneg on May 04 22:08:12.488666 osdx modulelauncher[89368]: Command '/sbin/ethtool -A eth0 autoneg on' returned non-zero exit status 76. May 04 22:08:12.489786 osdx modulelauncher[89368]: osdx.utils.xos cmd error: /sbin/ethtool -s eth0 autoneg on advertise Pause off Asym_Pause off -- May 04 22:08:12.489793 osdx modulelauncher[89368]: Command '/sbin/ethtool -s eth0 autoneg on advertise Pause off Asym_Pause off --' returned non-zero exit status 75. May 04 22:08:12.499257 osdx (udev-worker)[89384]: Network interface NamePolicy= disabled on kernel command line. May 04 22:08:12.652218 osdx cfgd[1648]: [88731]Completed change to active configuration May 04 22:08:12.663007 osdx OSDxCLI[88731]: User 'admin' committed the configuration. May 04 22:08:12.683441 osdx OSDxCLI[88731]: User 'admin' left the configuration menu. May 04 22:08:14.627279 osdx OSDxCLI[88731]: User 'admin' executed a new command: 'ping 10.215.168.1 count 1 size 56 timeout 1'. May 04 22:08:14.700891 osdx OSDxCLI[88731]: User 'admin' executed a new command: 'ping 40.0.0.2 count 1 size 56 timeout 1'. May 04 22:08:14.808648 osdx OSDxCLI[88731]: User 'admin' executed a new command: 'ping 20.0.0.2 count 1 size 56 timeout 1'. May 04 22:08:15.310041 osdx file_operation[89564]: using src url: http://10.215.168.1/~robot/test-performance.rules dst url: running:// May 04 22:08:15.332899 osdx OSDxCLI[88731]: User 'admin' executed a new command: 'file copy http://10.215.168.1/~robot/test-performance.rules running:// force'. May 04 22:08:15.458414 osdx OSDxCLI[88731]: User 'admin' executed a new command: 'file show running://test-performance.rules'. May 04 22:08:15.602352 osdx OSDxCLI[88731]: User 'admin' entered the configuration menu. May 04 22:08:15.659943 osdx OSDxCLI[88731]: User 'admin' added a new cfg line: 'set service firewall FW ruleset file running://test-performance.rules'. May 04 22:08:15.755758 osdx OSDxCLI[88731]: User 'admin' added a new cfg line: 'set service firewall FW mode inline queue FW_Q'. May 04 22:08:15.807152 osdx OSDxCLI[88731]: User 'admin' added a new cfg line: 'set service firewall FW logging outputs fast'. May 04 22:08:15.898573 osdx OSDxCLI[88731]: User 'admin' added a new cfg line: 'set service firewall FW logging level config'. May 04 22:08:15.950422 osdx OSDxCLI[88731]: User 'admin' added a new cfg line: 'set service firewall FW validator-timeout 20'. May 04 22:08:16.043341 osdx OSDxCLI[88731]: User 'admin' added a new cfg line: 'set traffic queue FW_Q elements 1'. May 04 22:08:16.130367 osdx OSDxCLI[88731]: User 'admin' added a new cfg line: 'set interfaces ethernet eth1 vif 101 traffic policy in FW_PLAN'. May 04 22:08:16.185149 osdx OSDxCLI[88731]: User 'admin' added a new cfg line: 'set interfaces ethernet eth1 vif 201 traffic policy in FW_PLAN'. May 04 22:08:16.273559 osdx OSDxCLI[88731]: User 'admin' added a new cfg line: 'set service firewall FW stream bypass mark 129834765'. May 04 22:08:16.323958 osdx OSDxCLI[88731]: User 'admin' added a new cfg line: 'set service firewall FW stream bypass mask 129834765'. May 04 22:08:16.414725 osdx OSDxCLI[88731]: User 'admin' added a new cfg line: 'set traffic label BYPASS'. May 04 22:08:16.470645 osdx OSDxCLI[88731]: User 'admin' added a new cfg line: 'set traffic policy FW-SKIP rule 1 log prefix SKIP'. May 04 22:08:16.562077 osdx OSDxCLI[88731]: User 'admin' added a new cfg line: 'set traffic policy FW-SKIP rule 1 selector MARKED-PACKETS'. May 04 22:08:16.615875 osdx OSDxCLI[88731]: User 'admin' added a new cfg line: 'set traffic policy FW-SKIP rule 1 set label BYPASS'. May 04 22:08:16.709604 osdx OSDxCLI[88731]: User 'admin' added a new cfg line: 'set traffic selector MARKED-PACKETS rule 1 mark 129834765'. May 04 22:08:16.766223 osdx OSDxCLI[88731]: User 'admin' added a new cfg line: 'set traffic selector FW_SEL_ENQUEUE rule 1 not label BYPASS'. May 04 22:08:16.854765 osdx OSDxCLI[88731]: User 'admin' added a new cfg line: 'set traffic policy FW_PLAN rule 1 selector FW_SEL_ENQUEUE'. May 04 22:08:16.908732 osdx OSDxCLI[88731]: User 'admin' added a new cfg line: 'set interfaces ethernet eth1 vif 101 traffic policy out FW-SKIP'. May 04 22:08:16.999394 osdx OSDxCLI[88731]: User 'admin' added a new cfg line: 'set interfaces ethernet eth1 vif 201 traffic policy out FW-SKIP'. May 04 22:08:17.051748 osdx OSDxCLI[88731]: User 'admin' added a new cfg line: 'set traffic policy FW_PLAN rule 1 action enqueue FW_Q'. May 04 22:08:17.169264 osdx OSDxCLI[88731]: User 'admin' added a new cfg line: 'show working'. May 04 22:08:17.251005 osdx ubnt-cfgd[89612]: inactive May 04 22:08:17.324565 osdx INFO[89657]: FRR daemons did not change May 04 22:08:17.562758 osdx systemd[1]: Reloading. May 04 22:08:17.650254 osdx systemd-sysv-generator[89713]: stat() failed on /etc/init.d/README, ignoring: No such file or directory May 04 22:08:17.778840 osdx systemd[1]: Starting suricata@FW.service - Suricata client "FW" service... May 04 22:08:17.807490 osdx systemd[1]: Started suricata@FW.service - Suricata client "FW" service. May 04 22:08:17.991120 osdx INFO[89694]: Rules successfully loaded May 04 22:08:17.991810 osdx cfgd[1648]: [88731]Completed change to active configuration May 04 22:08:17.993922 osdx OSDxCLI[88731]: User 'admin' committed the configuration. May 04 22:08:18.007976 osdx OSDxCLI[88731]: User 'admin' left the configuration menu. May 04 22:08:18.402879 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=44208 DF PROTO=TCP SPT=56168 DPT=5001 WINDOW=502 RES=0x00 ACK PSH URGP=0 MARK=0x7bd1f0d May 04 22:08:18.402952 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=7449 DF PROTO=TCP SPT=56178 DPT=5001 WINDOW=502 RES=0x00 ACK PSH URGP=0 MARK=0x7bd1f0d May 04 22:08:28.547007 osdx OSDxCLI[88731]: User 'admin' executed a new command: 'service firewall FW show logging fast | tail'. May 04 22:08:28.657596 osdx OSDxCLI[88731]: User 'admin' executed a new command: 'system journal show | cat'. May 04 22:08:28.894488 osdx OSDxCLI[88731]: User 'admin' entered the configuration menu. May 04 22:08:28.957098 osdx OSDxCLI[88731]: User 'admin' added a new cfg line: 'set service firewall FW ruleset file running://test-performance.rules'. May 04 22:08:29.055871 osdx OSDxCLI[88731]: User 'admin' added a new cfg line: 'set service firewall FW mode inline queue FW_Q'. May 04 22:08:29.113676 osdx OSDxCLI[88731]: User 'admin' added a new cfg line: 'set service firewall FW logging outputs fast'. May 04 22:08:29.196303 osdx OSDxCLI[88731]: User 'admin' added a new cfg line: 'set service firewall FW logging level config'. May 04 22:08:29.255339 osdx OSDxCLI[88731]: User 'admin' added a new cfg line: 'set service firewall FW validator-timeout 20'. May 04 22:08:29.347565 osdx OSDxCLI[88731]: User 'admin' added a new cfg line: 'set traffic queue FW_Q elements 1'. May 04 22:08:29.433477 osdx OSDxCLI[88731]: User 'admin' added a new cfg line: 'set interfaces ethernet eth1 vif 101 traffic policy in FW_PLAN'. May 04 22:08:29.497232 osdx OSDxCLI[88731]: User 'admin' added a new cfg line: 'set interfaces ethernet eth1 vif 201 traffic policy in FW_PLAN'. May 04 22:08:29.587315 osdx OSDxCLI[88731]: User 'admin' added a new cfg line: 'set service firewall FW stream bypass mark 129834765'. May 04 22:08:29.639082 osdx OSDxCLI[88731]: User 'admin' added a new cfg line: 'set service firewall FW stream bypass mask 129834765'. May 04 22:08:29.733706 osdx OSDxCLI[88731]: User 'admin' added a new cfg line: 'set traffic label BYPASS'. May 04 22:08:29.788790 osdx OSDxCLI[88731]: User 'admin' added a new cfg line: 'set traffic policy FW-SKIP rule 1 log prefix SKIP'. May 04 22:08:29.883075 osdx OSDxCLI[88731]: User 'admin' added a new cfg line: 'set traffic policy FW-SKIP rule 1 selector MARKED-PACKETS'. May 04 22:08:29.939188 osdx OSDxCLI[88731]: User 'admin' added a new cfg line: 'set traffic policy FW-SKIP rule 1 set label BYPASS'. May 04 22:08:30.030583 osdx OSDxCLI[88731]: User 'admin' added a new cfg line: 'set traffic selector MARKED-PACKETS rule 1 mark 129834765'. May 04 22:08:30.092006 osdx OSDxCLI[88731]: User 'admin' added a new cfg line: 'set traffic selector FW_SEL_ENQUEUE rule 1 not label BYPASS'. May 04 22:08:30.193294 osdx OSDxCLI[88731]: User 'admin' added a new cfg line: 'set traffic policy FW_PLAN rule 1 selector FW_SEL_ENQUEUE'. May 04 22:08:30.255157 osdx OSDxCLI[88731]: User 'admin' added a new cfg line: 'set interfaces ethernet eth1 vif 101 traffic policy out FW-SKIP'. May 04 22:08:30.346601 osdx OSDxCLI[88731]: User 'admin' added a new cfg line: 'set interfaces ethernet eth1 vif 201 traffic policy out FW-SKIP'. May 04 22:08:30.399091 osdx OSDxCLI[88731]: User 'admin' added a new cfg line: 'set traffic policy FW_PLAN rule 1 action enqueue FW_Q'. May 04 22:08:30.491942 osdx OSDxCLI[88731]: User 'admin' added a new cfg line: 'set service firewall FW stream bypass extra-mark 1 value 3294967295'. May 04 22:08:30.544285 osdx OSDxCLI[88731]: User 'admin' added a new cfg line: 'set service firewall FW stream bypass extra-mark 1 mask 3294967295'. May 04 22:08:30.636985 osdx OSDxCLI[88731]: User 'admin' added a new cfg line: 'set traffic policy FW-SKIP rule 1 selector FW_SEL_EXTRA_MARK'. May 04 22:08:30.703339 osdx OSDxCLI[88731]: User 'admin' added a new cfg line: 'set traffic selector FW_SEL_EXTRA_MARK rule 1 extra-mark 1 value 3294967295'. May 04 22:08:30.820260 osdx OSDxCLI[88731]: User 'admin' added a new cfg line: 'show changes'. May 04 22:08:30.890868 osdx ubnt-cfgd[89836]: inactive May 04 22:08:30.940718 osdx INFO[89856]: FRR daemons did not change May 04 22:08:31.190739 osdx systemd[1]: Stopping suricata@FW.service - Suricata client "FW" service... May 04 22:08:32.768539 osdx systemd[1]: suricata@FW.service: Deactivated successfully. May 04 22:08:32.768653 osdx systemd[1]: Stopped suricata@FW.service - Suricata client "FW" service. May 04 22:08:32.768685 osdx systemd[1]: suricata@FW.service: Consumed 1.674s CPU time. May 04 22:08:32.786545 osdx systemd[1]: Starting suricata@FW.service - Suricata client "FW" service... May 04 22:08:32.802718 osdx systemd[1]: Started suricata@FW.service - Suricata client "FW" service. May 04 22:08:32.975700 osdx INFO[89883]: Rules successfully loaded May 04 22:08:32.976238 osdx cfgd[1648]: [88731]Completed change to active configuration May 04 22:08:32.979172 osdx OSDxCLI[88731]: User 'admin' committed the configuration. May 04 22:08:33.033012 osdx OSDxCLI[88731]: User 'admin' left the configuration menu. May 04 22:08:33.190285 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=31067 DF PROTO=TCP SPT=39574 DPT=5001 WINDOW=502 RES=0x00 ACK PSH URGP=0 MARK=0x7bd1f0d EMARK1=0xc46535ff May 04 22:08:33.190361 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=60939 DF PROTO=TCP SPT=39586 DPT=5001 WINDOW=502 RES=0x00 ACK PSH URGP=0 MARK=0x7bd1f0d EMARK1=0xc46535ff May 04 22:08:41.030865 osdx systemd[1]: systemd-timedated.service: Deactivated successfully. May 04 22:08:43.365223 osdx OSDxCLI[88731]: 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 30920 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 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.746 ms --- 20.0.0.2 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.746/0.746/0.746/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.540 ms --- 40.0.0.2 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.540/0.540/0.540/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 35522 connected to 40.0.0.2 port 5001 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 357 MBytes 2.99 Gbits/sec 38 1.80 MBytes [ 5] 1.00-2.00 sec 370 MBytes 3.10 Gbits/sec 0 1.95 MBytes [ 5] 2.00-3.00 sec 364 MBytes 3.05 Gbits/sec 0 2.07 MBytes [ 5] 3.00-4.00 sec 362 MBytes 3.04 Gbits/sec 90 1.56 MBytes [ 5] 4.00-5.00 sec 384 MBytes 3.22 Gbits/sec 0 1.73 MBytes [ 5] 5.00-6.00 sec 376 MBytes 3.16 Gbits/sec 0 1.89 MBytes [ 5] 6.00-7.00 sec 361 MBytes 3.03 Gbits/sec 0 2.02 MBytes [ 5] 7.00-8.00 sec 389 MBytes 3.26 Gbits/sec 0 2.16 MBytes [ 5] 8.00-9.00 sec 366 MBytes 3.07 Gbits/sec 36 1.65 MBytes [ 5] 9.00-10.00 sec 385 MBytes 3.23 Gbits/sec 0 1.81 MBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-10.00 sec 3.63 GBytes 3.12 Gbits/sec 164 sender [ 5] 0.00-10.00 sec 3.63 GBytes 3.11 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
05/04/2026-22:09:11.003533 [**] [1:40:0] Skipping test network performance traffic [**] [Classification: (null)] [Priority: 3] {TCP} 20.0.0.2:35512 -> 40.0.0.2:5001 05/04/2026-22:09:11.004428 [**] [1:40:0] Skipping test network performance traffic [**] [Classification: (null)] [Priority: 3] {TCP} 20.0.0.2:35522 -> 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
icmp 1 19 src=40.0.0.2 dst=20.0.0.2 type=8 code=0 id=519 packets=1 bytes=84 src=20.0.0.2 dst=40.0.0.2 type=0 code=0 id=519 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=83 packets=1 bytes=84 src=40.0.0.2 dst=20.0.0.2 type=0 code=0 id=83 packets=1 bytes=84 (Sc: not-bypass) mark=0 use=1 tcp 6 9 CLOSE src=20.0.0.2 dst=40.0.0.2 sport=35522 dport=5001 packets=2689783 bytes=4034660201 src=40.0.0.2 dst=20.0.0.2 sport=5001 dport=35522 packets=377281 bytes=19605876 [ASSURED] (Sc: not-bypass) mark=129834765 use=1 tcp 6 19 TIME_WAIT src=20.0.0.2 dst=40.0.0.2 sport=35512 dport=5001 packets=16 bytes=1300 src=40.0.0.2 dst=20.0.0.2 sport=5001 dport=35512 packets=13 bytes=1018 [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 55464 connected to 40.0.0.2 port 5001 [ ID] Interval Transfer Bitrate Retr Cwnd [ 5] 0.00-1.00 sec 398 MBytes 3.34 Gbits/sec 18 1.90 MBytes [ 5] 1.00-2.00 sec 408 MBytes 3.42 Gbits/sec 0 2.05 MBytes [ 5] 2.00-3.00 sec 388 MBytes 3.25 Gbits/sec 2 1.55 MBytes [ 5] 3.00-4.00 sec 402 MBytes 3.38 Gbits/sec 0 1.73 MBytes [ 5] 4.00-5.00 sec 392 MBytes 3.29 Gbits/sec 0 1.89 MBytes [ 5] 5.00-6.00 sec 395 MBytes 3.31 Gbits/sec 0 2.04 MBytes [ 5] 6.00-7.00 sec 402 MBytes 3.38 Gbits/sec 0 2.18 MBytes [ 5] 7.00-8.00 sec 412 MBytes 3.46 Gbits/sec 15 1.70 MBytes [ 5] 8.00-9.00 sec 379 MBytes 3.18 Gbits/sec 0 1.85 MBytes [ 5] 9.00-10.00 sec 412 MBytes 3.46 Gbits/sec 0 2.01 MBytes - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate Retr [ 5] 0.00-10.00 sec 3.90 GBytes 3.35 Gbits/sec 35 sender [ 5] 0.00-10.00 sec 3.90 GBytes 3.34 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
05/04/2026-22:09:11.003533 [**] [1:40:0] Skipping test network performance traffic [**] [Classification: (null)] [Priority: 3] {TCP} 20.0.0.2:35512 -> 40.0.0.2:5001 05/04/2026-22:09:11.004428 [**] [1:40:0] Skipping test network performance traffic [**] [Classification: (null)] [Priority: 3] {TCP} 20.0.0.2:35522 -> 40.0.0.2:5001 05/04/2026-22:09:25.773731 [**] [1:40:0] Skipping test network performance traffic [**] [Classification: (null)] [Priority: 3] {TCP} 20.0.0.2:55450 -> 40.0.0.2:5001 05/04/2026-22:09:25.774636 [**] [1:40:0] Skipping test network performance traffic [**] [Classification: (null)] [Priority: 3] {TCP} 20.0.0.2:55464 -> 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=55450 dport=5001 packets=16 bytes=1301 src=40.0.0.2 dst=20.0.0.2 sport=5001 dport=55450 packets=13 bytes=1017 [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=55464 dport=5001 packets=2888934 bytes=4333387493 src=40.0.0.2 dst=20.0.0.2 sport=5001 dport=55464 packets=372165 bytes=19346984 [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 72674 0 --:--:-- --:--:-- --:--:-- 97k
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.631 ms --- 20.0.0.2 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.631/0.631/0.631/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.631 ms --- 40.0.0.2 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.631/0.631/0.631/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
05/04/2026-22:10:01.877099 [Drop] [**] [1:1:0] Dropping TCP performance test traffic [**] [Classification: (null)] [Priority: 3] {TCP} 20.0.0.2:46060 -> 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=522 packets=1 bytes=84 src=20.0.0.2 dst=40.0.0.2 type=0 code=0 id=522 packets=1 bytes=84 (Sc: not-bypass) mark=0 use=1 icmp 1 26 src=20.0.0.2 dst=40.0.0.2 type=8 code=0 id=86 packets=1 bytes=84 src=40.0.0.2 dst=20.0.0.2 type=0 code=0 id=86 packets=1 bytes=84 (Sc: not-bypass) mark=0 use=1 tcp 6 29 LAST_ACK src=20.0.0.2 dst=40.0.0.2 sport=46060 dport=5000 packets=7 bytes=557 src=40.0.0.2 dst=20.0.0.2 sport=5000 dport=46060 packets=4 bytes=217 [ASSURED] (Sc: not-bypass) mark=147652983 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 4 9 356 725 2 - 5 5 369 369 ------------------------------------------------------------------ Total 9 9 725 725
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
05/04/2026-22:10:01.877099 [Drop] [**] [1:1:0] Dropping TCP performance test traffic [**] [Classification: (null)] [Priority: 3] {TCP} 20.0.0.2:46060 -> 40.0.0.2:5000 05/04/2026-22:10:08.003479 [Drop] [**] [1:1:0] Dropping TCP performance test traffic [**] [Classification: (null)] [Priority: 3] {TCP} 20.0.0.2:46060 -> 40.0.0.2:5000 05/04/2026-22:10:09.437905 [Drop] [**] [1:1:0] Dropping TCP performance test traffic [**] [Classification: (null)] [Priority: 3] {TCP} 20.0.0.2:46062 -> 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=46062 dport=5000 packets=7 bytes=557 src=40.0.0.2 dst=20.0.0.2 sport=5000 dport=46062 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 4 9 356 686 2 - 5 5 330 330 --------------------------------------------------------------------- Total 9 9 686 686
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 29225 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 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.844 ms --- 20.0.0.2 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.844/0.844/0.844/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.571 ms --- 40.0.0.2 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.571/0.571/0.571/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
05/04/2026-22:10:31.285193 [**] [1:40:0] Skipping test network performance traffic [**] [Classification: (null)] [Priority: 3] {TCP} 20.0.0.2:41626 -> 40.0.0.2:5001 05/04/2026-22:10:31.286087 [**] [1:40:0] Skipping test network performance traffic [**] [Classification: (null)] [Priority: 3] {TCP} 20.0.0.2:41636 -> 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
icmp 1 29 src=20.0.0.2 dst=40.0.0.2 type=8 code=0 id=89 packets=1 bytes=84 src=40.0.0.2 dst=20.0.0.2 type=0 code=0 id=89 packets=1 bytes=84 (Sc: not-bypass) mark=0 use=1 tcp 6 src=20.0.0.2 dst=40.0.0.2 sport=41626 dport=5001 packets=7 bytes=537 src=40.0.0.2 dst=20.0.0.2 sport=5001 dport=41626 packets=7 bytes=376 [ASSURED] [OFFLOAD, packets=1 bytes=52 packets=4 bytes=211] mark=129834765 use=3 icmp 1 29 src=40.0.0.2 dst=20.0.0.2 type=8 code=0 id=525 packets=1 bytes=84 src=20.0.0.2 dst=40.0.0.2 type=0 code=0 id=525 packets=1 bytes=84 (Sc: not-bypass) mark=0 use=1 tcp 6 src=20.0.0.2 dst=40.0.0.2 sport=41636 dport=5001 packets=85988 bytes=128976181 src=40.0.0.2 dst=20.0.0.2 sport=5001 dport=41636 packets=13726 bytes=715036 [ASSURED] [OFFLOAD, packets=85976 bytes=128962480 packets=13724 bytes=714924] mark=129834765 use=2 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 26248 0 --:--:-- --:--:-- --:--:-- 26600
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
05/04/2026-22:10:31.285193 [**] [1:40:0] Skipping test network performance traffic [**] [Classification: (null)] [Priority: 3] {TCP} 20.0.0.2:41626 -> 40.0.0.2:5001 05/04/2026-22:10:31.286087 [**] [1:40:0] Skipping test network performance traffic [**] [Classification: (null)] [Priority: 3] {TCP} 20.0.0.2:41636 -> 40.0.0.2:5001 05/04/2026-22:10:33.276409 [**] [1:40:0] Skipping test network performance traffic [**] [Classification: (null)] [Priority: 3] {TCP} 20.0.0.2:32928 -> 40.0.0.2:5001 05/04/2026-22:10:33.277839 [**] [1:41:0] Skipping test network performance UDP traffic [**] [Classification: (null)] [Priority: 3] {UDP} 20.0.0.2:59314 -> 40.0.0.2:5001 05/04/2026-22:10:33.288537 [**] [1:41:0] Skipping test network performance UDP traffic [**] [Classification: (null)] [Priority: 3] {UDP} 20.0.0.2:59314 -> 40.0.0.2:5001 05/04/2026-22:10:33.300525 [**] [1:41:0] Skipping test network performance UDP traffic [**] [Classification: (null)] [Priority: 3] {UDP} 20.0.0.2:59314 -> 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
udp 17 src=20.0.0.2 dst=40.0.0.2 sport=59314 dport=5001 packets=11 bytes=14792 src=40.0.0.2 dst=20.0.0.2 sport=5001 dport=59314 packets=1 bytes=32 [OFFLOAD, packets=7 bytes=10332 packets=0 bytes=0] mark=129834765 use=2 tcp 6 src=20.0.0.2 dst=40.0.0.2 sport=32928 dport=5001 packets=8 bytes=607 src=40.0.0.2 dst=20.0.0.2 sport=5001 dport=32928 packets=7 bytes=376 [ASSURED] [OFFLOAD, packets=2 bytes=104 packets=4 bytes=211] mark=129834765 use=3 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 42826 0 --:--:-- --:--:-- --:--:-- 50000
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=0.823 ms --- 20.0.0.2 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.823/0.823/0.823/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.901 ms --- 40.0.0.2 ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 0.901/0.901/0.901/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
05/04/2026-22:10:52.514678 [Drop] [**] [1:1:0] Dropping TCP performance test traffic [**] [Classification: (null)] [Priority: 3] {TCP} 20.0.0.2:57366 -> 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 57366 yes 201 0 0 0 20.0.0.2 40.0.0.2 57366 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.250167s ending at 1777932656.156683 XDP_DROP 7 pkts ( 0 pps) 0 KiB ( 0 Mbits/s) XDP_PASS 13 pkts ( 0 pps) 1 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
05/04/2026-22:10:52.514678 [Drop] [**] [1:1:0] Dropping TCP performance test traffic [**] [Classification: (null)] [Priority: 3] {TCP} 20.0.0.2:57366 -> 40.0.0.2:5000 05/04/2026-22:10:56.300762 [Drop] [**] [1:2:0] Dropping UDP performance test traffic [**] [Classification: (null)] [Priority: 3] {UDP} 20.0.0.2:47996 -> 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 57366 yes 201 0 0 0 40.0.0.2 20.0.0.2 5001 47996 no 201 0 0 0 20.0.0.2 40.0.0.2 47996 5001 no 201 0 0 0 20.0.0.2 40.0.0.2 57366 5000 yes 201 0 10 776
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.250126s ending at 1777932659.854541 XDP_DROP 10 pkts ( 0 pps) 0 KiB ( 0 Mbits/s) XDP_PASS 33 pkts ( 0 pps) 2 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)