WD My Cloud Mirror - inaccessibility from under networks of the range 172.16.0.0/12
If your network uses the address space of 172.16.0.0/12, then you may encounter a situation, the NAS code will not be available, although everything seems to be OK.
The problem is really foolish - anyone who logs into the console of such a drive, and entering “ip a”, will immediately see what the matter is. But the fact is that WD (in my case it is: WD My Cloud Mirror) uses Docker for launching Web applications, the interface of which occupies the range 172.17.0.0/16.
I decided this simply - at the gateway, I disguised the traffic from the corresponding network. That's all.
The problem is really foolish - anyone who logs into the console of such a drive, and entering “ip a”, will immediately see what the matter is. But the fact is that WD (in my case it is: WD My Cloud Mirror) uses Docker for launching Web applications, the interface of which occupies the range 172.17.0.0/16.
I decided this simply - at the gateway, I disguised the traffic from the corresponding network. That's all.
')
Source: https://habr.com/ru/post/310420/
All Articles