<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[DDNS and DVR-Access from WAN]]></title><description><![CDATA[<p dir="auto">Currently there is a DVR on the network with a local address of 192.168.1.160. Users need to be able to access this device from the WAN. DDNS is configured on the DVR. Example address is sitedvr.dwddns.net</p>
<p dir="auto">The port that is configured on the DVR is 8245.</p>
<p dir="auto">We recently installed a netgate 3100. When I am on the LAN and enter 192.168.1.160:8245 into the browser I am able to bring up the DVR login screen. When I try from a WAN connection to get to sitedvr.dwddns.net nothing is resolved. When I type sitedvr.dwddns.net into a browser on the LAN it brings me to the pfsense login screen.</p>
<p dir="auto">The mobile app that users have to access the DVR is configured with the sitedvr.dwddns.net address and port 8245. Users were able to access the live camera feeds in the app the previous router, but I do not have access to see what settings were configured on that device.</p>
<p dir="auto">Any advice on how to configure pfsense to allow users to access the DVR from outside the network? Thanks for any help.</p>
]]></description><link>https://forum.netgate.com/topic/141773/ddns-and-dvr-access-from-wan</link><generator>RSS for Node</generator><lastBuildDate>Sat, 07 Mar 2026 09:28:26 GMT</lastBuildDate><atom:link href="https://forum.netgate.com/topic/141773.rss" rel="self" type="application/rss+xml"/><pubDate>Wed, 20 Mar 2019 18:11:51 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to DDNS and DVR-Access from WAN on Thu, 18 Apr 2019 15:39:26 GMT]]></title><description><![CDATA[<p dir="auto">So you have what problem exactly your ddns not resolve publicly? Or you do not have port forwarding setup?</p>
<p dir="auto">You should prob start your own thread with your details if you want any help... And again its bad idea to open your DVR to the public internet.</p>
]]></description><link>https://forum.netgate.com/post/838091</link><guid isPermaLink="true">https://forum.netgate.com/post/838091</guid><dc:creator><![CDATA[johnpoz]]></dc:creator><pubDate>Thu, 18 Apr 2019 15:39:26 GMT</pubDate></item><item><title><![CDATA[Reply to DDNS and DVR-Access from WAN on Thu, 18 Apr 2019 15:29:37 GMT]]></title><description><![CDATA[<p dir="auto">Did you solve the problem? I still have this problem</p>
]]></description><link>https://forum.netgate.com/post/838089</link><guid isPermaLink="true">https://forum.netgate.com/post/838089</guid><dc:creator><![CDATA[Pretoriano Gdl]]></dc:creator><pubDate>Thu, 18 Apr 2019 15:29:37 GMT</pubDate></item><item><title><![CDATA[Reply to DDNS and DVR-Access from WAN on Thu, 18 Apr 2019 15:34:46 GMT]]></title><description><![CDATA[<p dir="auto">Read the links provided by Grimson - doesn't sound like you setup any port forwarding which is going to be required to access from the outside.</p>
<p dir="auto">But also - I would really suggest you not do that.. Be much better to vpn into your network when your remote to access such resources.</p>
]]></description><link>https://forum.netgate.com/post/831886</link><guid isPermaLink="true">https://forum.netgate.com/post/831886</guid><dc:creator><![CDATA[johnpoz]]></dc:creator><pubDate>Thu, 18 Apr 2019 15:34:46 GMT</pubDate></item><item><title><![CDATA[Reply to DDNS and DVR-Access from WAN on Wed, 20 Mar 2019 18:13:47 GMT]]></title><description><![CDATA[<p dir="auto">RTFM:<br />
https://docs.netgate.com/pfsense/en/latest/nat/forwarding-ports-with-pfsense.html<br />
https://docs.netgate.com/pfsense/en/latest/nat/port-forward-troubleshooting.html</p>
<p dir="auto">but you would be better of to use a VPN to access internal resources.</p>
]]></description><link>https://forum.netgate.com/post/831883</link><guid isPermaLink="true">https://forum.netgate.com/post/831883</guid><dc:creator><![CDATA[Grimson]]></dc:creator><pubDate>Wed, 20 Mar 2019 18:13:47 GMT</pubDate></item></channel></rss>