This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

DM368IPNC-MT5 (release 5.0) can not respond to arp reguest

Hi,

I works with DM368IPNC-MT5, Software Release 5.0.0.

We made pilot batch of 300 IPNC.

I observed the flow of ARP requests targeting cameras to each other when cameras start up.

Thus, for 1-2 seconds on each of cameras incoming flow of about 300 hundred ARP requests only from cameras.

After that, about 15% of cameras were not available. These cameras are no longer responding to ping and ARP requests.

To avoid incorrect operation of other network equipment, cameras reconnect directly to PC without powering off supply.

But after that they did not respond to ping and ARP requests.

Next, we do test to determine the reaction of camera in the incoming stream of ARP requests.

One camera was used, as well as the program "Poison ARP", which generates ARP requests (up to 1000 arp requests per second).

The camera was connected directly to PC.

There was no answer from camera to ARP request. Is was impossible to get video stream from camera.

Camera is recovered after rebooting.

Results can be reproduced.

Under the same conditions, with the software release of 3, the camera responds to ARP requests.

Questions:

Is it possible to change network settings for release 5 to save camera ability to answer on ARP requests as for 3.0 release?

What files must be changed or replaced?

Thank you!

  • Hello,

    Can you please share the logs, arm load details when the camera is not responding?

    When you run "ps" command are the processes running is v3.x is same as that v5.x?

    It looks like some package is not running in the filesystem which might be causing this

    Meantime, can you also check using v5.1 as it will help to support/naroow down the issue well

    Also, please check with APpro supoprt list with all these details

    Regards,

    Raghu

  • Hello,

    We have solved this problem.
    Thank you.