Kirk-even after setup the enviournment variable, net.nfs -tests getting broken

[smartganu]

-even after setup the environment variable test getting broken.
LTP net.nfs IPv6 test failures are due to internal network namespace design.
The test creates an isolated NFS server/client environment and does not use external NFS servers.
In our setup, NFS services are running on a separate host, causing mount attempts to fail.
Manual validation confirms NFSv3/v4 over IPv6 is working correctly.
we set as below,
export RHOST=192.xxx.xx.xx
export LHOST=192.xxx.xx.xx
export IPV4_LHOST="192.xxx.xx.xx"
export IPV4_RHOST="192.xxx.xx.xx"
export IPV6_LHOST="fd00:1:1:1::xx"
export IPV6_RHOST="fd00:1:1:1::xx"
export LHOST_IFACES="enp7s0"
export RHOST_IFACES="enp7s0"

./kirk --run-suite net.nfs --run-pattern nfs01_v40_ip6t -v
Suite: net.nfs
──────────────
──────────────────────────
      nfs01_v40_ip6t
──────────────────────────
Executing: nfs01.sh -6 -v 4.0 -t tcp

nfs01 1 TINFO: Running: nfs01.sh -6 -v 4.0 -t tcp

nfs01 1 TINFO: initialize 'lhost' 'ltp_ns_veth2' interface
nfs01 1 TINFO: add local addr 10.0.0.2/24
nfs01 1 TINFO: add local addr fd00:1:1:1::2/64
nfs01 1 TINFO: initialize 'rhost' 'ltp_ns_veth1' interface
nfs01 1 TINFO: add remote addr 10.0.0.1/24
nfs01 1 TINFO: add remote addr fd00:1:1:1::1/64
nfs01 1 TINFO: Network config (local -- remote):
nfs01 1 TINFO: ltp_ns_veth2 -- ltp_ns_veth1
nfs01 1 TINFO: 10.0.0.2/24 -- 10.0.0.1/24
nfs01 1 TINFO: fd00:1:1:1::2/64 -- fd00:1:1:1::1/64
nfs01 1 TINFO: Using /tmp/LTP_nfs01.36BsjU5t8i as tmpdir (xfs filesystem)
tst_device.c:98: TINFO: Found free device 2 '/dev/loop2'
tst_supported_fs_types.c:157: TINFO: Skipping ext2 as requested by the test
tst_supported_fs_types.c:157: TINFO: Skipping ext3 as requested by the test
tst_supported_fs_types.c:98: TINFO: Kernel supports ext4
tst_supported_fs_types.c:63: TINFO: mkfs.ext4 does exist
tst_supported_fs_types.c:98: TINFO: Kernel supports xfs
tst_supported_fs_types.c:63: TINFO: mkfs.xfs does exist
tst_supported_fs_types.c:129: TINFO: Filesystem btrfs is not supported
tst_supported_fs_types.c:106: TINFO: Skipping bcachefs because of FUSE blacklist
tst_supported_fs_types.c:157: TINFO: Skipping vfat as requested by the test
tst_supported_fs_types.c:157: TINFO: Skipping exfat as requested by the test
tst_supported_fs_types.c:157: TINFO: Skipping ntfs as requested by the test
tst_supported_fs_types.c:157: TINFO: Skipping tmpfs as requested by the test
nfs01 1 TINFO: === Testing on ext4 ===
nfs01 1 TINFO: Formatting ext4 with opts='/dev/loop2'
nfs01 1 TINFO: Mounting device: mount -t ext4 /dev/loop2 /tmp/LTP_nfs01.36BsjU5t8i/mntpoint
nfs01 1 TINFO: ceiling LTP_TIMEOUT_MUL to 11
nfs01 1 TINFO: timeout per run is 0h 55m 0s
nfs01 1 TINFO: checking rpc.mountd/rpc.statd on rhost
nfs01 1 TINFO: mount.nfs: (linux nfs-utils 2.5.4)
nfs01 1 TINFO: setup NFSv4.0, socket type tcp6
nfs01 1 TINFO: Mounting /tmp/LTP_nfs01.36BsjU5t8i/4.0/0
nfs01 1 TINFO: Mounting NFS: mount -v -t nfs -o proto=tcp6,vers=4.0 [fd00:1:1:1::2]:/tmp/LTP_nfs01.36BsjU5t8i/mntpoint/4.0/tcp6 /tmp/LTP_nfs01.36BsjU5t8i/4.0/0
mount.nfs: mount(2): Connection timed out
mount.nfs: Connection timed out
mount.nfs: timeout set for Wed Mar 18 02:38:05 2026
mount.nfs: trying text-based options 'proto=tcp6,vers=4.0,addr=fd00:1:1:1::2,clientaddr=fd00:1:1:1::1'
nfs01 1 TBROK: mount command failed
nfs01 1 TINFO: Cleaning up testcase
nfs01 1 TINFO: SELinux enabled in enforcing mode, this may affect test results
nfs01 1 TINFO: it can be disabled with TST_DISABLE_SELINUX=1 (requires super/root)
nfs01 1 TINFO: install seinfo to find used SELinux profiles
nfs01 1 TINFO: loaded SELinux profiles: none

Summary:
passed   0
failed   0
broken   1
skipped  0
warnings 0

Duration: 3m 5s
Execution time: 3m 5s
────────────────────────
      TEST SUMMARY
────────────────────────
Suite:   net.nfs
Runtime: 3m 5s
Runs:    1
Results:
    Passed:   0
    Failed:   0
    Broken:   1
    Skipped:  0
    Warnings: 0

Broken:
    • nfs01_v40_ip6t
=====================

=====================
Suite: net.nfs
──────────────
nfs01_v30_ip4u: skip  (2.998s)
nfs01_v42_ip4t: pass  (12.636s)
nfs01_v30_ip6u: skip  (2.957s)
nfs01_v30_ip6t: broken  (2m 14s)
nfs01_v40_ip6t: broken  (3m 5s)
nfs01_v41_ip6t: broken  (3m 4s)
nfs01_v42_ip6t: broken  (3m 4s)

[acerv]

Hi, there's a set of environment variables which are supported by network tests. These variables are not mapped into kirk and we should probably do that. Unfortunately, we take for granted that most of the env variables are documented as well as all the others and I missed this. Thanks for the feedback, I'm going to take a look at it.

@pevik can you please help with this? It seems to be a major issue. I'm not an expert on network tests and I need to know if the following env vars are enough to setup a network test in the correct way.

export RHOST=192.xxx.xx.xx
export LHOST=192.xxx.xx.xx
export IPV4_LHOST="192.xxx.xx.xx"
export IPV4_RHOST="192.xxx.xx.xx"
export IPV6_LHOST="fd00:1:1:1::xx"
export IPV6_RHOST="fd00:1:1:1::xx"
export LHOST_IFACES="enp7s0"
export RHOST_IFACES="enp7s0"

[acerv]

Since some of these tests are deprecated and some others are using old API, it's hard for me to extract all the data by hand. So I asked an LLM to extract all possible environment variables which can be set in order to execute network tests. Please @pevik let us know if the list is correct.

Network Test Environment Variables

Variables that can be set externally to configure LTP network tests.

Host / Connection

Variable	Default	Description
RHOST	(unset)	Remote host name or IP; if unset, network namespace is used
RUSER	(unset)	Remote user for SSH/FTP/telnet
PASSWD	(empty)	Remote user password
LTP_RSH	ssh -nq	Remote shell command
TST_USE_NETNS	yes	Use network namespace instead of real remote host
TST_NET_RHOST_RUN_DEBUG	(unset)	Enable debug output for tst_rhost_run

IPv4

Variable	Default	Description
IPV4_LHOST	10.0.0.2/24	Local host IPv4 address
IPV4_RHOST	10.0.0.1/24	Remote host IPv4 address

IPv6

Variable	Default	Description
IPV6_LHOST	fd00:1:1:1::2/64	Local host IPv6 address
IPV6_RHOST	fd00:1:1:1::1/64	Remote host IPv6 address

IP Version

Variable	Default	Description
TST_IPVER	4	IP version to use (4 or 6)

Interfaces

Variable	Default	Description
LHOST_IFACES	eth0	Local network interface name(s)
RHOST_IFACES	eth0	Remote network interface name(s)

Stress Test Parameters

Variable	Default	Description
NS_DURATION	10	Test duration in seconds
NS_TIMES	10	Number of repetitions
CONNECTION_TOTAL	10	Total number of connections
IP_TOTAL	100	Number of IP addresses to add
IP_TOTAL_FOR_TCPIP	100	IP addresses for TCP/IP multi-alias tests
ROUTE_TOTAL	100	Number of routes to add
ROUTE_CHANGE_IP	100	Number of IP route changes
ROUTE_CHANGE_NETLINK	10000	Number of netlink route changes
MTU_CHANGE_TIMES	100	Number of MTU change operations
IF_UPDOWN_TIMES	100	Number of interface up/down operations
PING_MAX	500	Max ICMP echo requests

ICMP / Multicast

Variable	Default	Description
NS_ICMPV4_SENDER_DATA_MAXSIZE	1472	Max ICMPv4 payload size
NS_ICMPV6_SENDER_DATA_MAXSIZE	1452	Max ICMPv6 payload size
MCASTNUM_NORMAL	20	Number of multicast groups (normal stress)
MCASTNUM_HEAVY	4000	Number of multicast groups (heavy stress)

Netload

Variable	Default	Description
TST_NETLOAD_CLN_NUMBER	2	Number of netload clients
TST_NETLOAD_CLN_REQUESTS	10000	Requests per client
TST_NETLOAD_MAX_SRV_REPLIES	500000	Max server replies
TST_NETLOAD_RUN_COUNT	5	Number of netload runs
TST_NETLOAD_BINDTODEVICE	1	Bind socket to device (0/1)
LTP_NET_FEATURES_IGNORE_PERFORMANCE_FAILURE	(unset)	Ignore performance failures in netload tests

File Transfer / Services

Variable	Default	Description
DOWNLOAD_BIGFILESIZE	2147483647	Large file size for download tests (bytes)
DOWNLOAD_REGFILESIZE	1048576	Regular file size for download tests (bytes)
UPLOAD_BIGFILESIZE	2147483647	Large file size for upload tests (bytes)
UPLOAD_REGFILESIZE	1024	Regular file size for upload tests (bytes)
HTTP_DOWNLOAD_DIR	/var/www/html	HTTP server document root
FTP_DOWNLOAD_DIR	/var/ftp	FTP server download directory
FTP_UPLOAD_DIR	/var/ftp/pub	FTP server upload directory
FTP_UPLOAD_URLDIR	pub	FTP upload URL path

IPsec / Virtual Interfaces

Variable	Default	Description
IPSEC_MODE	(variable)	IPsec mode (tunnel or transport)
IPSEC_PROTO	(variable)	IPsec protocol (ah or esp_aead)
VIRT_PERF_THRESHOLD	(variable)	Performance threshold for virtual interface tests

[smartganu]

i tried with merged commint#95 but getting error "tst_net_iface_prefix: command not found"
./kirk --run-suite net.nfs --run-pattern nfs01_v30_ip6t --verbose
Host information
Hostname: XXXX
Python: 3.9.25 (main, Jan 14 2026, 00:00:00)

    Directory:  /tmp/kirk.root/tmp7u2anei6

Connecting to SUT: default

Suite: net.nfs
──────────────
──────────────────────────
nfs01_v30_ip6t
──────────────────────────
Executing: nfs01.sh -6 -v 3 -t tcp

nfs01 1 TINFO: Running: nfs01.sh -6 -v 3 -t tcp
nfs01 1 TINFO: Tested kernel: xxxxxx
bash: line 1: tst_net_iface_prefix: command not found

Summary:
passed 0
failed 1
broken 0
skipped 0
warnings 0

Duration: 1.005s

Execution time: 1.091s

Disconnecting from SUT: default

[acerv]

bash: line 1: tst_net_iface_prefix: command not found

Verify your installation folder, because kirk works on the upstream now. I stopped the test because I didn't configure the NFS tests, but the executable is correctly seen:

$ sudo ./kirk --run-suite net.nfs --run-pattern nfs01_v30_ip6t --verbose

Host information
	Hostname:   localhost.localdomain
	Python:     3.13.12 (main, Feb 09 2026, 22:37:44) [GCC]
	Directory:  /tmp/kirk.root/tmpcj8jc_hw

Connecting to SUT: default

Suite: net.nfs
──────────────
──────────────────────────
      nfs01_v30_ip6t
──────────────────────────
Executing: nfs01.sh -6 -v 3 -t tcp

nfs01 1 TINFO: Running: nfs01.sh -6 -v 3 -t tcp
nfs01 1 TINFO: Tested kernel: Linux localhost.localdomain 6.12.0-160000.26-default #1 SMP PREEMPT_DYNAMIC Thu Feb  5 00:00:11 UTC 2026 (f762390) x86_64 x86_64 x86_64 GNU/Linux
nfs01 1 TINFO: initialize 'lhost' 'ltp_ns_veth2' interface
nfs01 1 TINFO: add local addr 10.0.0.2/24
nfs01 1 TINFO: add local addr fd00:1:1:1::2/64
nfs01 1 TINFO: initialize 'rhost' 'ltp_ns_veth1' interface
nfs01 1 TINFO: add remote addr 10.0.0.1/24
nfs01 1 TINFO: add remote addr fd00:1:1:1::1/64
nfs01 1 TINFO: Network config (local -- remote):
nfs01 1 TINFO: ltp_ns_veth2 -- ltp_ns_veth1
nfs01 1 TINFO: 10.0.0.2/24 -- 10.0.0.1/24
nfs01 1 TINFO: fd00:1:1:1::2/64 -- fd00:1:1:1::1/64
nfs01 1 TINFO: Using /tmp/LTP_nfs01.enG9ShX8oM as tmpdir (tmpfs filesystem)
tst_device.c:98: TINFO: Found free device 0 '/dev/loop0'
tst_supported_fs_types.c:157: TINFO: Skipping ext2 as requested by the test
tst_supported_fs_types.c:157: TINFO: Skipping ext3 as requested by the test
tst_supported_fs_types.c:98: TINFO: Kernel supports ext4
tst_supported_fs_types.c:63: TINFO: mkfs.ext4 does exist
tst_supported_fs_types.c:98: TINFO: Kernel supports xfs
tst_supported_fs_types.c:63: TINFO: mkfs.xfs does exist
tst_supported_fs_types.c:98: TINFO: Kernel supports btrfs
tst_supported_fs_types.c:63: TINFO: mkfs.btrfs does exist
tst_supported_fs_types.c:106: TINFO: Skipping bcachefs because of FUSE blacklist
tst_supported_fs_types.c:157: TINFO: Skipping vfat as requested by the test
tst_supported_fs_types.c:157: TINFO: Skipping exfat as requested by the test
tst_supported_fs_types.c:157: TINFO: Skipping ntfs as requested by the test
tst_supported_fs_types.c:157: TINFO: Skipping tmpfs as requested by the test
nfs01 1 TINFO: === Testing on ext4 ===
nfs01 1 TINFO: Formatting ext4 with opts='/dev/loop0'
nfs01 1 TINFO: Mounting device: mount -t ext4 /dev/loop0 /tmp/LTP_nfs01.enG9ShX8oM/mntpoint 
nfs01 1 TINFO: ceiling LTP_TIMEOUT_MUL to 11
nfs01 1 TINFO: timeout per run is 0h 55m 0s
nfs01 1 TCONF: rpc.mountd not running
nfs01 1 TINFO: Cleaning up testcase
^C
Summary:
passed   0
failed   0
broken   0
skipped  1
warnings 0

Duration: 2.734s


Execution time: 2.749s

Disconnecting from SUT: default

Target information
──────────────────
Kernel:   Linux 6.12.0-160000.26-default #1 SMP PREEMPT_DYNAMIC Thu Feb  5 00:00:11 UTC 2026 (f762390)
Cmdline:  BOOT_IMAGE=/boot/vmlinuz-6.12.0-160000.26-default
          root=UUID=7df22dee-1273-4a53-8f83-95ba6c000e39
          resume=UUID=2c0196fa-686c-455d-98d5-641c5ecbf57f
          mitigations=auto
          quiet
          security=selinux
          selinux=1
Machine:  x86_64
Arch:     x86_64
RAM:      61346668 kB
Swap:     2081088 kB
Distro:   opensuse-leap 16.0

────────────────────────
      TEST SUMMARY
────────────────────────
Suite:   net.nfs
Runtime: 2.734s
Runs:    1

Results:
    Passed:   0
    Failed:   0
    Broken:   0
    Skipped:  1
    Warnings: 0

Session stopped

[pevik]

@pevik can you please help with this? It seems to be a major issue. I'm not an expert on network tests and I need to know if the following env vars are enough to setup a network test in the correct way.

export RHOST=192.xxx.xx.xx
export LHOST=192.xxx.xx.xx
export IPV4_LHOST="192.xxx.xx.xx"
export IPV4_RHOST="192.xxx.xx.xx"
export IPV6_LHOST="fd00:1:1:1::xx"
export IPV6_RHOST="fd00:1:1:1::xx"
export LHOST_IFACES="enp7s0"
export RHOST_IFACES="enp7s0"

Well, using 2 host side configuration requires at least IPV{4,6}_{L,R}HOST variables requires also to specify prefix.

export IPV4_LHOST="192.xxx.xx.xx/yy"
export IPV4_RHOST="192.xxx.xx.xx/yy"
export IPV6_LHOST="fd00:1:1:1::xx/zz"
export IPV6_RHOST="fd00:1:1:1::xx/zz"

And I see our doc in https://github.com/linux-test-project/ltp/tree/master/testcases/network#two-host-configuration needs to be updated.

bash: line 1: tst_net_iface_prefix: command not found

Verify your installation folder, because kirk works on the upstream now.
Of course this means that LTP is installed incorrectly. That's documented:
https://github.com/linux-test-project/ltp/tree/master/testcases/network#ltp-setup

Install LTP testsuite (see INSTALL). In case of two hosts configuration, LTP needs to be installed the same exact location and LTPROOT and PATH environment variables set on both client and server machines. This is required because some tests expect to find server files in certain locations.

I stopped the test because I didn't configure the NFS tests, but the executable is correctly seen:

$ sudo ./kirk --run-suite net.nfs --run-pattern nfs01_v30_ip6t --verbose

Well, single host netns based configuration works out of the box. But 2 host requires a proper setup. ATM @metan-ucw and @schlad are discussing whether change the setup to be 3 host side.