hotneutron 0 Posted April 16, 2013 This is tested on Q-See's QC804, should work on Dahua NVRs as well. Assuming you are using windows client, you need two commands: route add 10.1.1.0 mask 255.255.255.0 192.168.0.2 echo 1 > /proc/sys/net/ipv4/ip_forward Let's assume NVR's IP address is 192.168.0.2 Step 1) add static route open "command prompt" with admin privilege (right click on command prompt, and select "run as administrator") type (replace 192.168.0.2 with NVR's actual IP): route add 10.1.1.0 mask 255.255.255.0 192.168.0.2 Step 2) add ip-forward on NVR Use a telnet client (for example putty), telnet to 192.168.0.2 Connected to dvr. Escape character is '^]'. (none) login: <-type "root" Password: <- type "vizxv" BusyBox v1.18.4 (2012-05-17 14:08:15 CST) built-in shell (ash) Platform: N6, Revision: 321 Enter 'help' for a list of built-in commands. ~ # enable IP forward, type "echo 1 > /proc/sys/net/ipv4/ip_forward" Then list the ip camera on the NVR: type "arp -a" ~ # arp -a ? (10.1.1.66) at 90:02:a9:12:16:c5 [ether] PERM on eth1 ? (10.1.1.65) at 90:02:a9:12:17:c0 [ether] PERM on eth1 Step 3) connect to the IP cameras on the PoE ports of NVR Goto web browser and type http://10.1.1.65:85/ or http://10.1.1.66:85, the 85 port of ip addresses returned by previous "arp -a" command. You can change the default passwords for better security. Share this post Link to post Share on other sites
Sifter 0 Posted April 16, 2013 Good info! I was just starting down this road 2 days ago, you've done my work for me! Share this post Link to post Share on other sites
shockwave199 0 Posted April 17, 2013 This is actually an excellent thing and something anyone would want- to be able to access the cameras web interface even if it's hooked up to a hardware NVR's POE. But, I wouldn't have a clue how to do what you said. I have heard recently that there is indeed a work around to do this, but I didn't ask for specifics yet, and I'd hope it's not this invloved. Share this post Link to post Share on other sites
dexterash 0 Posted April 17, 2013 This works until reboot... Share this post Link to post Share on other sites
porto 0 Posted April 18, 2013 hi all, Very good info but i dont have good results with NVR3204 I tried with NVR3204 and ipc2100 cameras connected and I can not connect to the cameras. What is the adjustment in the swicth settings of NVR? IP adress? Mask? Gateway? Http port of my NVR3204 is 80 What is the http port cameras? Thank you for your help Share this post Link to post Share on other sites
porto 0 Posted April 19, 2013 hi all, I need your help to setup NVR network and switch settings to make it work. Thank's for your help Best regards porto Share this post Link to post Share on other sites
silencery 0 Posted April 19, 2013 hotneutron, Thanks for posting this! GREAT tip. I'll have to try it out. This works until reboot... Yes, I had the same question. Is there a way to permanently commit the routing tables, i.e. maybe with a startup script? Share this post Link to post Share on other sites
MaxIcon 0 Posted April 19, 2013 If you add the -p switch to the Route Add line, it should be persistent through reboots. At least, this worked on WinXP, last few times I had to do this. Share this post Link to post Share on other sites
dexterash 0 Posted April 20, 2013 hotneutron, Thanks for posting this! GREAT tip. I'll have to try it out. This works until reboot... Yes, I had the same question. Is there a way to permanently commit the routing tables, i.e. maybe with a startup script? Nope, read-only filesystem... also no startup script, unless one reverese-enginere the full firmware (of a security system, btw ). Share this post Link to post Share on other sites
porto 0 Posted April 20, 2013 hi all, Please help me. I add static route in linux like this : route add -net 192.1.1.0 netmask 255.255.255.0 gw 192.168.1.27 192.168.1.27 is ip of NVR 192.1.1.0 range ip of switch settings in NVR (or may i use 10.1.1.0 ????) result of route commande we can see route is added: root@manu-HP-ProBook-4710s:~# routeTable de routage IP du noyau Destination Passerelle Genmask Indic Metric Ref Use Iface 192.1.1.0 192.168.1.27 255.255.255.0 UG 0 0 0 wlan0 I add ip-forward on NVR in telnet like this : echo 1 > /proc/sys/net/ipv4/ip_forward result of login and command: root@manu-HP-ProBook-4710s:~# telnet 192.168.1.27Trying 192.168.1.27... Connected to 192.168.1.27. Escape character is '^]'. (none) login: root Password: BusyBox v1.18.4 (2012-05-17 14:08:15 CST) built-in shell (ash) Platform: N6, Revision: 321 Enter 'help' for a list of built-in commands. ~ # echo 1 > /proc/sys/net/ipv4/ip_forward ~ # To verify if ip_forward is run i use cat command, output is 1 (active): ~ # cat /proc/sys/net/ipv4/ip_forward1 ~ # If the output is 1, it is enabled if 0, then it is disabled arp command: ~ # arp -a? (192.1.1.65) at 90:02:a9:0f:a5:21 [ether] PERM on eth1 ? (192.1.1.66) at 90:02:a9:0b:32:80 [ether] PERM on eth1 I dont know what's wrong may be range ip of switch settings (192.1.1.??) must be 10.1.1.0 ?? What do you think?? Please help me Best regards porto Share this post Link to post Share on other sites
hotneutron 0 Posted April 20, 2013 One thing is for sure that 192.1.1.x are valid IP addresses, unlike private IPv4 ranges 192.168.x.x or 10.x.x.x http://en.wikipedia.org/wiki/IP_address#IPv4_private_addresses IANA-reserved private IPv4 network ranges Start End No. of addresses 24-bit block (/8 prefix, 1 × A) 10.0.0.0 10.255.255.255 16777216 20-bit block (/12 prefix, 16 × B) 172.16.0.0 172.31.255.255 1048576 16-bit block (/16 prefix, 256 × C) 192.168.0.0 192.168.255.255 65536 Share this post Link to post Share on other sites
porto 0 Posted April 22, 2013 Thx now it works Best regards porto Share this post Link to post Share on other sites