<?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 Re: NAT on loopback interface in Switches, Hubs, and Modems</title>
    <link>https://community.hpe.com/t5/switches-hubs-and-modems/nat-on-loopback-interface/m-p/4194430#M14167</link>
    <description>Not exactly this policy because all the real/production interfaces already have applied policies and I don't exactly have time to build a new circuit for the simulation. &lt;BR /&gt;Firmaware - the lastest - 8.03&lt;BR /&gt;&lt;BR /&gt;have you spotted any mistake in that config? I guess the part of config with the loop interface could be easily replicated so you may see it for youself.&lt;BR /&gt;&lt;BR /&gt;As a part of an extra check I entered this config into cisco 3660 with some adjustments, of course. As I expected cisco can regulate access to the loop interface</description>
    <pubDate>Mon, 12 May 2008 16:57:29 GMT</pubDate>
    <dc:creator>_blkdog</dc:creator>
    <dc:date>2008-05-12T16:57:29Z</dc:date>
    <item>
      <title>NAT on loopback interface</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/nat-on-loopback-interface/m-p/4194426#M14163</link>
      <description>It concerns 7102 router.&lt;BR /&gt;I'd like to NAT several networks attached to different interfaces. Being lazy enough not to configure access-policy on each interface I created loop int for NATting&lt;BR /&gt;&lt;BR /&gt;interface loop 1&lt;BR /&gt;  ip address  192.168.0.104  255.255.255.255&lt;BR /&gt;  no shutdown&lt;BR /&gt;  access-policy NAT&lt;BR /&gt;&lt;BR /&gt;ip policy-class NAT&lt;BR /&gt;  nat destination list NAT_ACCESS address 192.168.2.70&lt;BR /&gt;&lt;BR /&gt;ip access-list extended NAT_ACCESS&lt;BR /&gt;  permit gre 192.168.0.0 0.0.1.255  host 192.168.0.104    &lt;BR /&gt;  permit tcp 192.168.0.0 0.0.1.255  host 192.168.0.104 eq 1723  &lt;BR /&gt;&lt;BR /&gt;So it means that I want to NAT all the PPTP traffic to the 192.168.2.70/30 server.&lt;BR /&gt;&lt;BR /&gt;Although it works with separate interfaces it does not with the loopback.&lt;BR /&gt;Moreover, even applying explicit discard-all access-policy on the loopback does not affect the traffic over that interface whatsoever. &lt;BR /&gt;Is this a bug or a feature? I spent 2 hours investigating this issue with no apparent result. Please, share you opinion on this.</description>
      <pubDate>Thu, 08 May 2008 16:24:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/nat-on-loopback-interface/m-p/4194426#M14163</guid>
      <dc:creator>_blkdog</dc:creator>
      <dc:date>2008-05-08T16:24:13Z</dc:date>
    </item>
    <item>
      <title>Re: NAT on loopback interface</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/nat-on-loopback-interface/m-p/4194427#M14164</link>
      <description>Hi&lt;BR /&gt;&lt;BR /&gt;I think you should check this :&lt;BR /&gt;&lt;A href="http://www.cisco.com/en/US/tech/tk648/tk361/technologies_tech_note09186a0080094430.shtml" target="_blank"&gt;http://www.cisco.com/en/US/tech/tk648/tk361/technologies_tech_note09186a0080094430.shtml&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Good Luck !!!</description>
      <pubDate>Fri, 09 May 2008 13:50:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/nat-on-loopback-interface/m-p/4194427#M14164</guid>
      <dc:creator>Mohieddin Kharnoub</dc:creator>
      <dc:date>2008-05-09T13:50:21Z</dc:date>
    </item>
    <item>
      <title>Re: NAT on loopback interface</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/nat-on-loopback-interface/m-p/4194428#M14165</link>
      <description>Nice link, thanks a lot. This is almost exact setup that I want to configure myself and I bet on Cisco it would work like a charm.&lt;BR /&gt;But like I said before on 7102 even simple access-policy applied to the loopback does not work. For example: &lt;BR /&gt;&lt;BR /&gt;interface loop 1&lt;BR /&gt;ip address 192.168.0.104 255.255.255.255&lt;BR /&gt;no shutdown&lt;BR /&gt;access-policy TEST&lt;BR /&gt;&lt;BR /&gt;ip policy-class TEST&lt;BR /&gt;allow list ONLYONEHOST&lt;BR /&gt;&lt;BR /&gt;ip access-list standard ONLYONEHOST&lt;BR /&gt;permit host 192.168.0.77&lt;BR /&gt;&lt;BR /&gt;Despite access-policy TEST I am able to access loop1 interface from any address, not only from host 192.168.0.77.&lt;BR /&gt;&lt;BR /&gt;I suspect that the fast-switching is implicitly enabled on loop1 and going to check it after the weekend. If it is not the case I am again clueless about what is wrong with my setup.&lt;BR /&gt;</description>
      <pubDate>Sat, 10 May 2008 03:46:15 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/nat-on-loopback-interface/m-p/4194428#M14165</guid>
      <dc:creator>_blkdog</dc:creator>
      <dc:date>2008-05-10T03:46:15Z</dc:date>
    </item>
    <item>
      <title>Re: NAT on loopback interface</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/nat-on-loopback-interface/m-p/4194429#M14166</link>
      <description>Have you tried this Policy on a Physical Interface ?&lt;BR /&gt;&lt;BR /&gt;Whats your Firmware version ?&lt;BR /&gt;&lt;BR /&gt;Good Luck !!!</description>
      <pubDate>Mon, 12 May 2008 06:53:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/nat-on-loopback-interface/m-p/4194429#M14166</guid>
      <dc:creator>Mohieddin Kharnoub</dc:creator>
      <dc:date>2008-05-12T06:53:09Z</dc:date>
    </item>
    <item>
      <title>Re: NAT on loopback interface</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/nat-on-loopback-interface/m-p/4194430#M14167</link>
      <description>Not exactly this policy because all the real/production interfaces already have applied policies and I don't exactly have time to build a new circuit for the simulation. &lt;BR /&gt;Firmaware - the lastest - 8.03&lt;BR /&gt;&lt;BR /&gt;have you spotted any mistake in that config? I guess the part of config with the loop interface could be easily replicated so you may see it for youself.&lt;BR /&gt;&lt;BR /&gt;As a part of an extra check I entered this config into cisco 3660 with some adjustments, of course. As I expected cisco can regulate access to the loop interface</description>
      <pubDate>Mon, 12 May 2008 16:57:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/nat-on-loopback-interface/m-p/4194430#M14167</guid>
      <dc:creator>_blkdog</dc:creator>
      <dc:date>2008-05-12T16:57:29Z</dc:date>
    </item>
    <item>
      <title>Re: NAT on loopback interface</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/nat-on-loopback-interface/m-p/4194431#M14168</link>
      <description>I'd open a case with HP to see if this is expected behaviour or something that can be fixed in a software updaet.</description>
      <pubDate>Tue, 13 May 2008 11:11:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/nat-on-loopback-interface/m-p/4194431#M14168</guid>
      <dc:creator>Matt Hobbs</dc:creator>
      <dc:date>2008-05-13T11:11:33Z</dc:date>
    </item>
    <item>
      <title>Re: NAT on loopback interface</title>
      <link>https://community.hpe.com/t5/switches-hubs-and-modems/nat-on-loopback-interface/m-p/4194432#M14169</link>
      <description>how am I supposed to do so?</description>
      <pubDate>Tue, 13 May 2008 11:50:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/switches-hubs-and-modems/nat-on-loopback-interface/m-p/4194432#M14169</guid>
      <dc:creator>_blkdog</dc:creator>
      <dc:date>2008-05-13T11:50:25Z</dc:date>
    </item>
  </channel>
</rss>

