Force-Ipv4

SSH connection tests using force-ipv4 parameter to control IP protocol version. Tests validate proper behavior when forcing IPv4 protocol with matching and mismatched IP address formats.

SSH Force IPv4 with IPv4 Address Success

Description

SSH force-ipv4 with IPv4 address should work correctly due to address family match.

Scenario

Step 1: Set the following configuration in DUT0 :

set interfaces ethernet eth0 address 10.215.168.20/24
set service ssh
set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0'

Step 2: Set the following configuration in DUT1 :

set interfaces ethernet eth0 address 10.215.168.21/24
set service ssh
set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0'

Step 3: Ping IP address 10.215.168.20 from DUT1:

admin@DUT1$ ping 10.215.168.20 count 1 size 56 timeout 1
Show output
PING 10.215.168.20 (10.215.168.20) 56(84) bytes of data.
64 bytes from 10.215.168.20: icmp_seq=1 ttl=64 time=0.464 ms

--- 10.215.168.20 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.464/0.464/0.464/0.000 ms

Step 4: Init an SSH connection from DUT1 to IP address 10.215.168.20 with the user admin:

admin@DUT1$ ssh admin@10.215.168.20 option StrictHostKeyChecking=no option UserKnownHostsFile=/dev/null force-ipv4
Show output
Warning: Permanently added '10.215.168.20' (ECDSA) to the list of known hosts.
admin@10.215.168.20's password:
Welcome to Teldat OSDx v4.2.8.1

This system includes free software.
Contact Teldat for licenses information and source code.

Last login: Thu Dec 11 18:17:41 2025
admin@osdx$

SSH Force IPv4 with IPv6 Address Should Fail

Description

SSH force-ipv4 with IPv6 address should fail due to address family mismatch.

Scenario

Step 1: Set the following configuration in DUT0 :

set interfaces ethernet eth0 address '11::2/64'
set service ssh
set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0'

Step 2: Set the following configuration in DUT1 :

set interfaces ethernet eth0 address '11::3/64'
set system login user admin authentication encrypted-password '$6$GSjsCj8gHLv$/VcqU6FLi6CT2Oxn0MJQ2C2tqnRDrYKNF8HIYWJp68nvXvPdFccDsT04.WtigUONbKYrgKg8d6rEs8PjljMkH0'

Step 3: Ping IP address 11::2 from DUT1:

admin@DUT1$ ping 11::2 count 1 size 56 timeout 1
Show output
PING 11::2(11::2) 56 data bytes
64 bytes from 11::2: icmp_seq=1 ttl=64 time=440 ms

--- 11::2 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 440.485/440.485/440.485/0.000 ms

Step 4: Init an SSH connection from DUT1 to IP address 11::2 with the user admin which is going to fail:

admin@DUT1$ ssh admin@11::2 option StrictHostKeyChecking=no option UserKnownHostsFile=/dev/null force-ipv4
Show output
ssh: Could not resolve hostname 11::2: Address family for hostname not supported
  CLI Error: Invalid token [option]
  CLI Error: Command error
admin@osdx$