<?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 Problem in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/port-forwarding-problem/m-p/1619073#M594292</link>
    <description>&lt;DIV&gt;Hi&lt;/DIV&gt;&lt;DIV&gt;&lt;BR /&gt;&lt;/DIV&gt;&lt;DIV&gt;This is my first time working with Cisco routers and I'm setting up a brand new 1812 with IOS 12.4.&lt;/DIV&gt;&lt;DIV&gt;&lt;BR /&gt;&lt;/DIV&gt;&lt;DIV&gt;I&amp;nbsp; used CCP to configure it including the ZFW with DMZ on 10.10.3.1. Traffic flows from&amp;nbsp; in to out but now I need to open some ports for inbound ssh traffic. I&amp;nbsp; want connections on port 29 to be directed to a specific&amp;nbsp; machine 10.10.0.199 on the inside. CCP didn't add any inbound rules so&amp;nbsp; I'm trying to figure this out by hand but it's not working. &lt;/DIV&gt;&lt;DIV&gt;&lt;BR /&gt;&lt;/DIV&gt;&lt;DIV&gt;I'm not sure where to start asking questions so let&amp;nbsp; me start with the following and hopefully someone can point me in the&amp;nbsp; right direction or at least get the discussion going.&lt;BR /&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;BR /&gt;&lt;/DIV&gt;&lt;DIV&gt;Now, it looks to me that I should be using port mapping so I've added the following (via CCP): &lt;/DIV&gt;&lt;DIV&gt;&lt;BR /&gt;&lt;/DIV&gt;&lt;DIV&gt;ip port-map user-ssh-29 port tcp 29 list 3 &lt;/DIV&gt;&lt;DIV&gt;access-list 3 permit 10.10.0.199&lt;/DIV&gt;&lt;DIV&gt;&lt;BR /&gt;&lt;/DIV&gt;&lt;DIV&gt;From discussions I've read on this forum and around the net I'm seem to be missing some NAT rule(s). Something like&lt;/DIV&gt;&lt;DIV&gt;ip nat inside source static tcp 10.10.0.199 29 interface FastEthernet0 29&lt;/DIV&gt;&lt;DIV&gt;&lt;BR /&gt;&lt;/DIV&gt;&lt;DIV&gt;The rules that were created are:&lt;/DIV&gt;&lt;DIV&gt;class-map type inspect match-any user-ssh-29&lt;/DIV&gt;&lt;DIV&gt; match protocol user-ssh-29&lt;/DIV&gt;&lt;DIV&gt; &lt;/DIV&gt;&lt;DIV&gt;class-map type inspect match-all ccp-cls--1&lt;/DIV&gt;&lt;DIV&gt; match class-map user-ssh-29&lt;/DIV&gt;&lt;DIV&gt; match access-group name incoming-abc&lt;/DIV&gt;&lt;DIV&gt;&lt;BR /&gt;&lt;/DIV&gt;&lt;DIV&gt;ip access-list extended incoming-abc&lt;/DIV&gt;&lt;DIV&gt; remark CCP_ACL Category=128&lt;/DIV&gt;&lt;DIV&gt; permit ip any host 10.10.0.199&lt;/DIV&gt;&lt;DIV&gt;&lt;BR /&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;BR /&gt;&lt;/DIV&gt;&lt;DIV&gt;The&amp;nbsp; net effect is that inbound connections are not getting through, they&amp;nbsp; don't fail with a connection refused, but they hang waiting ...&lt;/DIV&gt;&lt;DIV&gt;&lt;BR /&gt;&lt;/DIV&gt;&lt;DIV&gt;Using the CCP monitoring features it looks like the&amp;nbsp; router is taking these connection attempts to be outside-&amp;gt;self rather&amp;nbsp; than outside-&amp;gt;inside as the the packets show up in Firewall Status&amp;nbsp; out-&amp;gt;self dropped packets monitor&lt;/DIV&gt;&lt;DIV&gt;&lt;BR /&gt;&lt;/DIV&gt;&lt;DIV&gt;The 1812's outside interface in on a subnet 10.10.2.0 behind a DSL modem/router.&lt;/DIV&gt;&lt;DIV&gt;&lt;BR /&gt;&lt;/DIV&gt;&lt;DIV&gt;Thanks&lt;/DIV&gt;&lt;DIV&gt;&lt;BR /&gt;&lt;/DIV&gt;</description>
    <pubDate>Mon, 11 Mar 2019 19:34:59 GMT</pubDate>
    <dc:creator>reseauxjcnet</dc:creator>
    <dc:date>2019-03-11T19:34:59Z</dc:date>
    <item>
      <title>Port Forwarding Problem</title>
      <link>https://community.cisco.com/t5/network-security/port-forwarding-problem/m-p/1619073#M594292</link>
      <description>&lt;DIV&gt;Hi&lt;/DIV&gt;&lt;DIV&gt;&lt;BR /&gt;&lt;/DIV&gt;&lt;DIV&gt;This is my first time working with Cisco routers and I'm setting up a brand new 1812 with IOS 12.4.&lt;/DIV&gt;&lt;DIV&gt;&lt;BR /&gt;&lt;/DIV&gt;&lt;DIV&gt;I&amp;nbsp; used CCP to configure it including the ZFW with DMZ on 10.10.3.1. Traffic flows from&amp;nbsp; in to out but now I need to open some ports for inbound ssh traffic. I&amp;nbsp; want connections on port 29 to be directed to a specific&amp;nbsp; machine 10.10.0.199 on the inside. CCP didn't add any inbound rules so&amp;nbsp; I'm trying to figure this out by hand but it's not working. &lt;/DIV&gt;&lt;DIV&gt;&lt;BR /&gt;&lt;/DIV&gt;&lt;DIV&gt;I'm not sure where to start asking questions so let&amp;nbsp; me start with the following and hopefully someone can point me in the&amp;nbsp; right direction or at least get the discussion going.&lt;BR /&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;BR /&gt;&lt;/DIV&gt;&lt;DIV&gt;Now, it looks to me that I should be using port mapping so I've added the following (via CCP): &lt;/DIV&gt;&lt;DIV&gt;&lt;BR /&gt;&lt;/DIV&gt;&lt;DIV&gt;ip port-map user-ssh-29 port tcp 29 list 3 &lt;/DIV&gt;&lt;DIV&gt;access-list 3 permit 10.10.0.199&lt;/DIV&gt;&lt;DIV&gt;&lt;BR /&gt;&lt;/DIV&gt;&lt;DIV&gt;From discussions I've read on this forum and around the net I'm seem to be missing some NAT rule(s). Something like&lt;/DIV&gt;&lt;DIV&gt;ip nat inside source static tcp 10.10.0.199 29 interface FastEthernet0 29&lt;/DIV&gt;&lt;DIV&gt;&lt;BR /&gt;&lt;/DIV&gt;&lt;DIV&gt;The rules that were created are:&lt;/DIV&gt;&lt;DIV&gt;class-map type inspect match-any user-ssh-29&lt;/DIV&gt;&lt;DIV&gt; match protocol user-ssh-29&lt;/DIV&gt;&lt;DIV&gt; &lt;/DIV&gt;&lt;DIV&gt;class-map type inspect match-all ccp-cls--1&lt;/DIV&gt;&lt;DIV&gt; match class-map user-ssh-29&lt;/DIV&gt;&lt;DIV&gt; match access-group name incoming-abc&lt;/DIV&gt;&lt;DIV&gt;&lt;BR /&gt;&lt;/DIV&gt;&lt;DIV&gt;ip access-list extended incoming-abc&lt;/DIV&gt;&lt;DIV&gt; remark CCP_ACL Category=128&lt;/DIV&gt;&lt;DIV&gt; permit ip any host 10.10.0.199&lt;/DIV&gt;&lt;DIV&gt;&lt;BR /&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;BR /&gt;&lt;/DIV&gt;&lt;DIV&gt;The&amp;nbsp; net effect is that inbound connections are not getting through, they&amp;nbsp; don't fail with a connection refused, but they hang waiting ...&lt;/DIV&gt;&lt;DIV&gt;&lt;BR /&gt;&lt;/DIV&gt;&lt;DIV&gt;Using the CCP monitoring features it looks like the&amp;nbsp; router is taking these connection attempts to be outside-&amp;gt;self rather&amp;nbsp; than outside-&amp;gt;inside as the the packets show up in Firewall Status&amp;nbsp; out-&amp;gt;self dropped packets monitor&lt;/DIV&gt;&lt;DIV&gt;&lt;BR /&gt;&lt;/DIV&gt;&lt;DIV&gt;The 1812's outside interface in on a subnet 10.10.2.0 behind a DSL modem/router.&lt;/DIV&gt;&lt;DIV&gt;&lt;BR /&gt;&lt;/DIV&gt;&lt;DIV&gt;Thanks&lt;/DIV&gt;&lt;DIV&gt;&lt;BR /&gt;&lt;/DIV&gt;</description>
      <pubDate>Mon, 11 Mar 2019 19:34:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/port-forwarding-problem/m-p/1619073#M594292</guid>
      <dc:creator>reseauxjcnet</dc:creator>
      <dc:date>2019-03-11T19:34:59Z</dc:date>
    </item>
    <item>
      <title>Re: Port Forwarding Problem</title>
      <link>https://community.cisco.com/t5/network-security/port-forwarding-problem/m-p/1619074#M594293</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;For port forwarding you need the NAT rule you mentioned:&lt;/P&gt;&lt;P&gt;ip nat inside source static tcp 10.10.0.199 29 interface FastEthernet0 29&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The above command says that when the router receives an inbound TCP packet on port 29 on its FastEthernet interface, it will redirect it to 10.10.0.199 on the same port.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you have an ACL applied to this FastEthernet interface, the ACL should permit this traffic in.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Federico.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 14 Jan 2011 13:13:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/port-forwarding-problem/m-p/1619074#M594293</guid>
      <dc:creator>Federico Coto Fajardo</dc:creator>
      <dc:date>2011-01-14T13:13:42Z</dc:date>
    </item>
    <item>
      <title>Re: Port Forwarding Problem</title>
      <link>https://community.cisco.com/t5/network-security/port-forwarding-problem/m-p/1619075#M594294</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I've been away ... but still need help. I know that I'm missing something.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What exactly would ACL look like? I've tried a number of things that haven't worked.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In order to understand this stuff I've stripped it down to the below, having removed the fw parts. Outgoing is ok but the incoming map on port 29 doesn't work. The debug trace produces stuff like this:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; NAT*: o: tcp (10.10.0.100, 37237) -&amp;gt; (10.10.0.8, 29) [0]&lt;/P&gt;&lt;P&gt; NAT*: s=10.10.0.100, d=10.10.0.8-&amp;gt;10.10.5.20 [0]&lt;/P&gt;&lt;P&gt; NAT*: i: tcp (10.10.5.20, 29) -&amp;gt; (10.10.0.100, 37237) [14190]&lt;/P&gt;&lt;P&gt; NAT*: s=10.10.5.20-&amp;gt;10.10.0.8, d=10.10.0.100 [14190]&lt;/P&gt;&lt;DIV&gt; &lt;/DIV&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;version 12.4&lt;/P&gt;&lt;P&gt;no service pad&lt;/P&gt;&lt;P&gt;service tcp-keepalives-in&lt;/P&gt;&lt;P&gt;service tcp-keepalives-out&lt;/P&gt;&lt;P&gt;service timestamps debug datetime msec localtime show-timezone&lt;/P&gt;&lt;P&gt;service timestamps log datetime msec localtime show-timezone&lt;/P&gt;&lt;P&gt;service password-encryption&lt;/P&gt;&lt;P&gt;service sequence-numbers&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;hostname gw1&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;boot-start-marker&lt;/P&gt;&lt;P&gt;boot-end-marker&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;dot11 syslog&lt;/P&gt;&lt;P&gt;no ip source-route&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;ip cef&lt;/P&gt;&lt;P&gt;no ip bootp server&lt;/P&gt;&lt;P&gt;ip domain name xx.com&lt;/P&gt;&lt;P&gt;ip name-server 10.10.0.5&lt;/P&gt;&lt;P&gt;no ipv6 cef&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;ip tcp synwait-time 10&lt;/P&gt;&lt;P&gt;ip ssh time-out 60&lt;/P&gt;&lt;P&gt;ip ssh authentication-retries 2&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;interface FastEthernet0&lt;/P&gt;&lt;P&gt; ip address 10.10.0.8 255.255.255.0&lt;/P&gt;&lt;P&gt; no ip redirects&lt;/P&gt;&lt;P&gt; no ip unreachables&lt;/P&gt;&lt;P&gt; no ip proxy-arp&lt;/P&gt;&lt;P&gt; ip flow ingress&lt;/P&gt;&lt;P&gt; ip nat outside&lt;/P&gt;&lt;P&gt; ip virtual-reassembly&lt;/P&gt;&lt;P&gt; duplex auto&lt;/P&gt;&lt;P&gt; speed auto&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;interface Vlan1&lt;/P&gt;&lt;P&gt; description $ETH-SW-LAUNCH$$INTF-INFO-FE 2$$ES_LAN$$FW_INSIDE$&lt;/P&gt;&lt;P&gt; ip address 10.10.5.1 255.255.255.0&lt;/P&gt;&lt;P&gt; no ip redirects&lt;/P&gt;&lt;P&gt; no ip unreachables&lt;/P&gt;&lt;P&gt; no ip proxy-arp&lt;/P&gt;&lt;P&gt; ip flow ingress&lt;/P&gt;&lt;P&gt; ip nat inside&lt;/P&gt;&lt;P&gt; ip virtual-reassembly&lt;/P&gt;&lt;P&gt; ip tcp adjust-mss 1452&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;interface Async1&lt;/P&gt;&lt;P&gt; no ip address&lt;/P&gt;&lt;P&gt; no ip redirects&lt;/P&gt;&lt;P&gt; no ip unreachables&lt;/P&gt;&lt;P&gt; no ip proxy-arp&lt;/P&gt;&lt;P&gt; encapsulation slip&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;ip forward-protocol nd&lt;/P&gt;&lt;P&gt;ip route 0.0.0.0 0.0.0.0 10.10.0.5 permanent&lt;/P&gt;&lt;P&gt;ip http server&lt;/P&gt;&lt;P&gt;ip http access-class 23&lt;/P&gt;&lt;P&gt;ip http authentication local&lt;/P&gt;&lt;P&gt;ip http secure-server&lt;/P&gt;&lt;P&gt;ip http timeout-policy idle 60 life 86400 requests 10000&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;ip nat inside source static tcp 10.10.5.20 29 interface FastEthernet0 29&lt;/P&gt;&lt;P&gt;ip nat inside source list 1 interface FastEthernet0 overload&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;logging trap debugging&lt;/P&gt;&lt;P&gt;access-list 1 remark CCP_ACL Category=2&lt;/P&gt;&lt;P&gt;access-list 1 permit 10.10.5.20 0.0.0.255&lt;/P&gt;&lt;P&gt;no cdp run&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;control-plane&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;end&lt;/P&gt;&lt;DIV&gt; &lt;/DIV&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 26 Jan 2011 21:17:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/port-forwarding-problem/m-p/1619075#M594294</guid>
      <dc:creator>reseauxjcnet</dc:creator>
      <dc:date>2011-01-26T21:17:55Z</dc:date>
    </item>
  </channel>
</rss>

