Failure in running smb2.multichannel tests

[spuiuk]

There appears to be problem with setting up iptable rules and the issue is meant to track the investigation into this.

[gd]

Could these issues be related to some more generic firewall issues we were encountering elsewhere?

[spuiuk]

The following tests fail along with the reasons for their failure.

smb2.multichannel.oplocks.test2 - multichannel.c: 734 - request for a batch oplock and get one. This causes failure.
smb2.multichannel.oplocks.test3_windows - same

smb2.multichannel.oplocks.test3_specification - Port blocked and oplock request is therefore not delivered. However the server doesn't appear to retry the oplock break and instead responds to the create call within a second.

smb2.multichannel.leases.test2 - multichannel.c:1653 Check the lease set when new file created. Expected RH but received RWH
smb2.multichannel.leases.test4 - We open multiple channels, block them and check to see if lease breaks will be retried after a timeout. This doesn't happen in this case. The server doesn't wait for the lease break to timeout and instead returns a successful create. Therefore no retries are done and the test fails. This is the same reason as for
smb2.multichannel.oplocks.test3_specification.

Tested with both iptables and fsctl.

[spuiuk]

Note that multichannel was enabled by default just recently on Samba.

commit 7f03d7c85e62bec3f97143980ec45db8bd0e5383
Author: Stefan Metzmacher metze@samba.org
Date: Wed Jul 14 00:14:24 2021 +0200

lib/param: enable "server multi channel support" by default on Linux and FreeBSD

Signed-off-by: Stefan Metzmacher <metze@samba.org>
Reviewed-by: Jeremy Allison <jra@samba.org>