I see you have 2 different interfaces on the same network subnet it appears:
119894 Feb 19, 2018 19:46:28.590 [0x7f42be64e800] DEBUG - * 5 br0 (192.168.1.12) (loopback: 0)
119895 Feb 19, 2018 19:46:28.590 [0x7f42be64e800] DEBUG - * 6 br1 (192.168.1.11) (loopback: 0)
Also seeing network errors in your logs:
120157 Feb 19, 2018 19:46:32.061 [0x7f42afd11700] WARN - HTTP error requesting GET http://192.168.1.1:8200/rootDesc.xml (0, No error) (Failed connect to 192.168.1.1:8200; No route to host)
120162 Feb 19, 2018 19:46:32.063 [0x7f42b1bff700] WARN - HTTP error requesting GET http://192.168.1.121:80/dms/device.xml (0, No error) (Failed connect to 192.168.1.121:80; No route to host)
120177 Feb 19, 2018 19:46:33.165 [0x7f42ae511700] WARN - HTTP error requesting GET http://192.168.1.113:8060/ (0, No error) (Failed connect to 192.168.1.113:8060; No route to host)
I know very little about QNAP but I would suggest unplugging one of the two local interfaces and see if you are able to connect to the HDHR with just one local interface. I believe that QNAP is providing you with more than 1 interface so you can aggregate the link to effectively double your upload/download to the network. Typically in all instances I have seen where link aggregation is used the network device the links connect to must also support the link aggregation. Interesting article found: http://www.itpro.co.uk/nas/29490/two-ports-no-waiting-the-pros-and-cons-of-link-aggregation.
