mvIPConfigure: On some Linux systems, misconfigured GEV devices are not being discovered successfully

mvBlueCOUGAR-X, mvBlueCOUGAR-XD

Fixed since driver version 2.25.0

In mvIPConfigure, misconfigured cameras are only displayed when they are connected at the default gateway. You can indentify this interface like the following way:

Open a console window and type in route -n. You will see the following routing table:

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         192.168.65.15   0.0.0.0         UG    0      0        0 eth0
169.254.0.0     0.0.0.0         255.255.0.0     U     0      0        0 eth1
169.254.0.0     0.0.0.0         255.255.0.0     U     1000   0        0 eth2
192.168.65.0    0.0.0.0         255.255.255.0   U     0      0        0 eth0
192.168.201.0   0.0.0.0         255.255.255.0   U     0      0        0 eth2

The Flags column will indicate the default gateway using the G flag. If several interfaces are marked with the G flag, the one with the smallest metric will be used as the default gateway. If the metric is the same as well, then the first listed interface will be used as the default gateway. You have to connect the misconfigured camera at this interface so that it will be discovered by mvIPConfigure.

It is also possible to manipulate the routing table. E.g.:

sudo route del default eth0
sudo route add default gw 192.168.201.1

Then the routing table will look like follows:

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         192.168.201.1   0.0.0.0         UG    0      0        0 eth2
169.254.0.0     0.0.0.0         255.255.0.0     U     0      0        0 eth1
169.254.0.0     0.0.0.0         255.255.0.0     U     1000   0        0 eth2
192.168.65.0    0.0.0.0         255.255.255.0   U     0      0        0 eth0
192.168.201.0   0.0.0.0         255.255.255.0   U     0      0        0 eth2

Now, the camera at eth2 will be discovered and you can re-configure it. Finally you have to fix or re-start the routing table.

Back