<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Port forwarding and firewall rules in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/port-forwarding-and-firewall-rules/m-p/2128673#M395302</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;IMG src="http://supportforums.cisco.com/sites/default/files/legacy/2/7/7/114772-screen2.PNG" class="jive-image" /&gt;&lt;IMG src="http://supportforums.cisco.com/sites/default/files/legacy/1/7/7/114771-screen1.PNG" class="jive-image" /&gt;&lt;IMG src="http://supportforums.cisco.com/sites/default/files/legacy/3/7/7/114773-screen3.PNG" class="jive-image" /&gt;&lt;IMG src="http://supportforums.cisco.com/sites/default/files/legacy/4/7/7/114774-screen4.PNG" class="jive-image" /&gt;&lt;/P&gt;&lt;P&gt;Here you go.&lt;/P&gt;&lt;P&gt;Thanks again!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 22 Nov 2012 15:33:48 GMT</pubDate>
    <dc:creator>Anthony Wood</dc:creator>
    <dc:date>2012-11-22T15:33:48Z</dc:date>
    <item>
      <title>Port forwarding and firewall rules</title>
      <link>https://community.cisco.com/t5/network-security/port-forwarding-and-firewall-rules/m-p/2128669#M395298</link>
      <description>&lt;P&gt;I have a RV042 in one office and we are moving to a VOIP telephone system.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;They requested a bunch of ports open, and I wanted to make sure that only thier IP addresses get into the local net.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I setup port forwarding to forward ports internally to their phone server, and then I setup firewall access rules only allowing their IP addresses into that phone server.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now it seems as if all of the ports I forwarded are wide open!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What did I do wrong?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any help is greatly appreciated!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Ant&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 00:26:28 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/port-forwarding-and-firewall-rules/m-p/2128669#M395298</guid>
      <dc:creator>Anthony Wood</dc:creator>
      <dc:date>2019-03-12T00:26:28Z</dc:date>
    </item>
    <item>
      <title>Port forwarding and firewall rules</title>
      <link>https://community.cisco.com/t5/network-security/port-forwarding-and-firewall-rules/m-p/2128670#M395299</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Now it seems as if all of the ports I forwarded are wide open! &lt;/P&gt;&lt;P&gt;What do you mean, do you mean anyone can access it??&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can you share the configuration you used on that router&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 22 Nov 2012 00:53:47 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/port-forwarding-and-firewall-rules/m-p/2128670#M395299</guid>
      <dc:creator>Julio Carvajal</dc:creator>
      <dc:date>2012-11-22T00:53:47Z</dc:date>
    </item>
    <item>
      <title>Port forwarding and firewall rules</title>
      <link>https://community.cisco.com/t5/network-security/port-forwarding-and-firewall-rules/m-p/2128671#M395300</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I am unsure as to how to do that?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Do I need to telnet/ssh into the router?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Anthony&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 22 Nov 2012 01:39:28 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/port-forwarding-and-firewall-rules/m-p/2128671#M395300</guid>
      <dc:creator>Anthony Wood</dc:creator>
      <dc:date>2012-11-22T01:39:28Z</dc:date>
    </item>
    <item>
      <title>Port forwarding and firewall rules</title>
      <link>https://community.cisco.com/t5/network-security/port-forwarding-and-firewall-rules/m-p/2128672#M395301</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Anthony, &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You can do print/screen if you like ( easier,faster)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 22 Nov 2012 04:30:35 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/port-forwarding-and-firewall-rules/m-p/2128672#M395301</guid>
      <dc:creator>Julio Carvajal</dc:creator>
      <dc:date>2012-11-22T04:30:35Z</dc:date>
    </item>
    <item>
      <title>Port forwarding and firewall rules</title>
      <link>https://community.cisco.com/t5/network-security/port-forwarding-and-firewall-rules/m-p/2128673#M395302</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;IMG src="http://supportforums.cisco.com/sites/default/files/legacy/2/7/7/114772-screen2.PNG" class="jive-image" /&gt;&lt;IMG src="http://supportforums.cisco.com/sites/default/files/legacy/1/7/7/114771-screen1.PNG" class="jive-image" /&gt;&lt;IMG src="http://supportforums.cisco.com/sites/default/files/legacy/3/7/7/114773-screen3.PNG" class="jive-image" /&gt;&lt;IMG src="http://supportforums.cisco.com/sites/default/files/legacy/4/7/7/114774-screen4.PNG" class="jive-image" /&gt;&lt;/P&gt;&lt;P&gt;Here you go.&lt;/P&gt;&lt;P&gt;Thanks again!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 22 Nov 2012 15:33:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/port-forwarding-and-firewall-rules/m-p/2128673#M395302</guid>
      <dc:creator>Anthony Wood</dc:creator>
      <dc:date>2012-11-22T15:33:48Z</dc:date>
    </item>
    <item>
      <title>Port forwarding and firewall rules</title>
      <link>https://community.cisco.com/t5/network-security/port-forwarding-and-firewall-rules/m-p/2128674#M395303</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello Anthony Wood,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It is difficult to check the configuration with the screenshots but I will try to help you,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What you need to do with the ACL on the WAN interface is to allow traffic to the WAN interface ip address on the right ports ( SIP.HTTPS,FTP,etc) and then just configure a deny IP any any so you can allow the traffic required and then deny the rest of them,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also how did you test the router is open to the outside world?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 22 Nov 2012 17:00:52 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/port-forwarding-and-firewall-rules/m-p/2128674#M395303</guid>
      <dc:creator>Julio Carvajal</dc:creator>
      <dc:date>2012-11-22T17:00:52Z</dc:date>
    </item>
    <item>
      <title>Re: Port forwarding and firewall rules</title>
      <link>https://community.cisco.com/t5/network-security/port-forwarding-and-firewall-rules/m-p/2128675#M395305</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I used a port scanner and it came back that ftp, telnet and http were open.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am not sure what you mean by this.&lt;/P&gt;&lt;PRE __jive_macro_name="quote" class="jive_text_macro jive_macro_quote"&gt; "What you need to do with the ACL on the WAN interface is to allow&amp;nbsp; traffic to the WAN interface ip address on the right ports (&amp;nbsp; SIP.HTTPS,FTP,etc) "&lt;/PRE&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Are you saying to create a rule for every outside VOIP address to access WAN IP address, for every protocol needed?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also if you need clarification on somehting let me know.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Anthony&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 23 Nov 2012 01:29:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/port-forwarding-and-firewall-rules/m-p/2128675#M395305</guid>
      <dc:creator>Anthony Wood</dc:creator>
      <dc:date>2012-11-23T01:29:45Z</dc:date>
    </item>
    <item>
      <title>Re: Port forwarding and firewall rules</title>
      <link>https://community.cisco.com/t5/network-security/port-forwarding-and-firewall-rules/m-p/2128676#M395306</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P style="background-color: #ffffff; border-collapse: collapse; font-size: 12px; list-style: none; font-family: Arial, verdana, sans-serif;"&gt;Are you saying to create a rule for every outside VOIP address to access WAN IP address, for every protocol needed?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Exactly. that would be the most secure desing, now it will be the less scalable and easy to configure. So as this is a voice desing and there are going to be random ip addresses connecting permit just the right ports on the outside from any to the right TCP/UDP ports and then just a deny IP any/any on that outside interface.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Remember to rate all of the helpful posts&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;*** How to rate a post, mark the stars on the bottom of each reply, 5 being a thanks for the good answer 1 being a bad answer********&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 23 Nov 2012 05:27:50 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/port-forwarding-and-firewall-rules/m-p/2128676#M395306</guid>
      <dc:creator>Julio Carvajal</dc:creator>
      <dc:date>2012-11-23T05:27:50Z</dc:date>
    </item>
    <item>
      <title>Re: Port forwarding and firewall rules</title>
      <link>https://community.cisco.com/t5/network-security/port-forwarding-and-firewall-rules/m-p/2128677#M395307</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;What is "desing"?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Do the port forward rules apply to traffic before the firewall rules?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 23 Nov 2012 15:44:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/port-forwarding-and-firewall-rules/m-p/2128677#M395307</guid>
      <dc:creator>Anthony Wood</dc:creator>
      <dc:date>2012-11-23T15:44:30Z</dc:date>
    </item>
    <item>
      <title>Re: Port forwarding and firewall rules</title>
      <link>https://community.cisco.com/t5/network-security/port-forwarding-and-firewall-rules/m-p/2128678#M395308</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I mean design&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;No, NAT goes afterwards.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 23 Nov 2012 17:36:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/port-forwarding-and-firewall-rules/m-p/2128678#M395308</guid>
      <dc:creator>Julio Carvajal</dc:creator>
      <dc:date>2012-11-23T17:36:26Z</dc:date>
    </item>
  </channel>
</rss>

