The ConfigureIp tool (/usr/src/framos/camerasuite/Tools/) will list the cameras connected to the computer network, even if the IP addresses are not in the same subnet mask.

We have noticed that on Linux-based systems, particularly those that have been freshly flashed, Ethernet ports may not yet have an IPv4 address assigned. 

When the computer Ethernet port is set to DHCP, the computer is expecting to receive an IP address from a DHCP server and not to suggest an IP address to the camera.

It may result in the network port having no IPv4 address assigned to it, thus the camera(s) that eventually connect to that port are not listed in the ConfigureIp tool.

Type the following command in the terminal and check the output.

ip addr show

We run the tests with an AAEON embedded PC, which features an NVIDIA Jetson AGX Orin and 4x Ethernet PoE ports.

Only the eth2 has an IPv$ address assigned to it.

Notice that eth1 has an IPv6 address assigned, and eth3 has no IP address assigned.

Only the camera connected to the eth2 is listed in the ConfigureIp tool.

Now, we will assign an IPv4 address to eth1 and eth3, regardless of whether it matches the subnet of an eventual static IP address of the camera.

Example for setting the IP 192.168.0.100 to the eth1:

sudo ip addr add 192.168.0.100/24 dev eth1
sudo ip link set eth1 up

Three Ethernet ports have an IPv4 address assigned, and all the connected cameras are listed. In our case, one camera is not accessible because the network settings need to be adjusted, but the camera is listed in the application.

By default, Jetson is a DHCP client only: details on NVIDIA forum 

The camera connected to eth3 has the DHCP enabled. If we flush the IP settings of eth3 and assign a new IP address to it, the camera will be listed (discovered) but won't be accessible, because the Jetson is not a DHCP server (in opposition to Windows).

sudo ip addr flush dev eth3
sudo ip addr add 192.164.20.100/24 dev eth3
sudo ip link set eth3 up

Photo of the physical setup:

TSS