Currently, the SSH configuration uses the IPv4 address of a device. However, devices may also have an IPv6 address available, and some tests may configure the device to only have an IPv6 address on eth0.
How did you do it?
Modify the SSH config generation to support generating a separate entry with the IPv6 address instead of the IPv4 address. These entries will have a suffix of -v6.
A separate entry approach was chosen partly because OpenSSH's config doesn't support using multiple literal IP addresses.
How did you verify/test it?
Tested the OpenSSH config generation, and it looks file. Have not tested the SecureCRT config generation.
Any platform specific information?
Supported testbed topology if it's a new test case?
Description of PR
Summary: Fixes # (issue)
Type of change
Back port request
Approach
What is the motivation for this PR?
Currently, the SSH configuration uses the IPv4 address of a device. However, devices may also have an IPv6 address available, and some tests may configure the device to only have an IPv6 address on eth0.
How did you do it?
Modify the SSH config generation to support generating a separate entry with the IPv6 address instead of the IPv4 address. These entries will have a suffix of
-v6
.A separate entry approach was chosen partly because OpenSSH's config doesn't support using multiple literal IP addresses.
How did you verify/test it?
Tested the OpenSSH config generation, and it looks file. Have not tested the SecureCRT config generation.
Any platform specific information?
Supported testbed topology if it's a new test case?
Documentation