Synology cannot connect to AD410

[warning]

Dear Forum members,

I have a weird issue that I've been struggling with...I would really appreciate your thoughts.

It's obvious, the network config is not the strength of this AD410 (not having proper UI to set manually, etc.), but it is still manageable from router side. What I cannot manage is the following issue.

Now I have an AD410, which cannot be pinged ONLY from my Synology:
ash-4.4# ping 192.168.1.105
PING 192.168.1.105 (192.168.1.105) 56(84) bytes of data.
From 192.168.1.108 icmp_seq=1 Destination Host Unreachable
From 192.168.1.108 icmp_seq=2 Destination Host Unreachable
From 192.168.1.108 icmp_seq=3 Destination Host Unreachable
From 192.168.1.108 icmp_seq=4 Destination Host Unreachable
^C
--- 192.168.1.105 ping statistics ---
6 packets transmitted, 0 received, +4 errors, 100% packet loss, time 1004ms

I can ping from everywhere else (even from a VM running in Synology):
peter@ubuntu:~$ ping doorbell
PING doorbell.lan (192.168.1.105) 56(84) bytes of data.
64 bytes from Doorbell.lan (192.168.1.105): icmp_seq=1 ttl=64 time=221 ms
64 bytes from Doorbell.lan (192.168.1.105): icmp_seq=2 ttl=64 time=2.07 ms
64 bytes from Doorbell.lan (192.168.1.105): icmp_seq=3 ttl=64 time=2.43 ms
^C
--- doorbell.lan ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2002ms

But, Synology can ping everything else, except this AD410.

What am I doing wrong?
I've reset many-many times, changed, IP many-many times, another WiFi SSID, etc., but the same result...
I've found a similar issue, logged here: https://community.synology.com/enu/forum/3/post/148039


Thank you,

Peter

[warning]

After a few hours in front of Wireshark...

Once I've changed this, it started to work:

"NetAddrIPv4" : {
"eth0" : {
"DefaultGateway" : "192.168.1.1",
"DnsServers" : [ "8.8.8.8", "8.8.8.8" ],
"IPAddress" : "192.168.1.108",
"NetMask" : "255.255.0.0"
},

This is the config command:
curl --digest --user admin:password -X GET 'http://192.168.1.105/cgi-bin/configMana ... .168.1.109'

I have no clue what this trash is all about, even after many hard resets.


So basically, there was a "predefined"/"preset" IP, the same IP, that I use for my Synology.

[Revo2Maxx]

I would have to look in my AD410, Right now my place is a mess and I don't know where the backup of the file is. However I don't remember 192.168.1.105 ever being in the IP address of the Device.

Normally IP addresses in Amcrest and other devices from Dahua are in 192.168.1.108, 192.168.1.123 or 192.168.0.108 and I don't normally use them IP ranges in my Normal Local area because of issues where the Device might default to a known used IP and don't want IP Conflicts. I will admit that I have some VPN that are setup with 192.168 IP's but they are for different reasoning.

So looking really fast I did find it for my AD410 and eth0 is a Ethernet port setup that isn't even used seeing it is a Wifi camera so not sure why your having a conflict with the cameras default info.

"NetAddrIPv4" : {
"eth0" : {
"DefaultGateway" : "192.168.1.1",
"DnsServers" : [ "8.8.8.8", "8.8.8.8" ],
"IPAddress" : "192.168.1.108",
"NetMask" : "255.255.0.0"
},
"eth2" : {
"DefaultGateway" : "10.0.0.1",
"DnsServers" : [ "10.0.0.1", "0.0.0.0" ],
"IPAddress" : "10.0.0.235",
"NetMask" : "255.255.255.0"

The Ad410 and other Wifi only devices use eth2 where 0 is normally setup for Ethernet cables.

[warning]

Dear team,

As I wrote, it was set:

"NetAddrIPv4" : {
"eth0" : {
"DefaultGateway" : "192.168.1.1",
"DnsServers" : [ "8.8.8.8", "8.8.8.8" ],
"IPAddress" : "192.168.1.108",
"NetMask" : "255.255.0.0"
},
"eth2" : {
"DefaultGateway" : "192.168.1.2",
"DnsServers" : [ "192.168.1.2", "0.0.0.0" ],
"IPAddress" : "192.168.1.105",
"NetMask" : "255.255.255.0"
}
},

I had to change the eth0's address, in spite of the fact that, I did not use and I did not set anywhere. So, it was the default.
Eth2, which came from my router (DHCP)
Unfortunately, my Synology also has the 192.168.1.108. I do not even understand, why this AD410 has another IP address to be set, no one requested. Completely out of control (and logic) the network settings.