<?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 ASA NAT Proxy ARP (Cable ISP) in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa-nat-proxy-arp-cable-isp/m-p/1783678#M533015</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; Enabling DNS doctoring that will solve your issue.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sun, 21 Aug 2011 18:42:48 GMT</pubDate>
    <dc:creator>haivrajesh</dc:creator>
    <dc:date>2011-08-21T18:42:48Z</dc:date>
    <item>
      <title>ASA NAT Proxy ARP (Cable ISP)</title>
      <link>https://community.cisco.com/t5/network-security/asa-nat-proxy-arp-cable-isp/m-p/1783675#M533004</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have the following problem:&lt;/P&gt;&lt;P&gt;Our new provider (cable) has got an MAC address filter on it's devices.&lt;/P&gt;&lt;P&gt;Furthermore: Every single official IP needs &lt;SPAN __jive_emoticon_name="alert" __jive_macro_name="emoticon" class="jive_macro jive_emote" src="https://community.cisco.com/4.5.4/images/emoticons/alert.gif"&gt;&lt;/SPAN&gt; a different MAC to bypass this filter.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In my case:&lt;/P&gt;&lt;P&gt;I've got the official IPs (e.g.)&lt;/P&gt;&lt;P&gt;A = 109.2.1.3 / MAC 00d0.efef.1234 / Subnetmask 255.255.255.0&lt;/P&gt;&lt;P&gt;B = 109.2.1.4 / MAC aaaa.efef.1234 / Subnetmask 255.255.255.0&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So both IPs are in the same subnet. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A is bound to my outside ASA interface.&lt;/P&gt;&lt;P&gt;B should be used as NAT IP for my mailserver which is located in my dmz.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Problem:&lt;/P&gt;&lt;P&gt;Everytime I access IP B the ARP reply is send from MAC A (normal ASA proxy ARP behavior) and therefore all packets have the4 source MAC A.&lt;/P&gt;&lt;P&gt;But in my case the cable provider drops this packets since they are sourced with the wrong MAC (remember: MAC A not MAC B).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So I need a way to replay arp requests with MAC B if there are packets for IP B. Is there a way to configure this on an ASA?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm running the latest 4.2 release.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you very much for your help.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Markus&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 21:14:43 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-nat-proxy-arp-cable-isp/m-p/1783675#M533004</guid>
      <dc:creator>m.hoeschen</dc:creator>
      <dc:date>2019-03-11T21:14:43Z</dc:date>
    </item>
    <item>
      <title>ASA NAT Proxy ARP (Cable ISP)</title>
      <link>https://community.cisco.com/t5/network-security/asa-nat-proxy-arp-cable-isp/m-p/1783676#M533009</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Markus,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Proxy-arp is a default beahvior of the firewall and in your case it might be an issue, so you need to disbale proxy-arp on the outside interace of the ASA, you can do this by:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;sysopt noproxyarp outside&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;and this should resolve your issue.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Moreover, you can also disable the proxy arp for a particular regular static nat statement in Version 8.4.2, this feature was added only in this version. Have a look at this:&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-external-small" href="http://www.cisco.com/en/US/customer/docs/security/asa/asa84/release/notes/asarn84.html#wp535067"&gt;http://www.cisco.com/en/US/customer/docs/security/asa/asa84/release/notes/asarn84.html#wp535067&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'll follow up with more info.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Varun&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Do rate helpful posts.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 20 Aug 2011 15:42:11 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-nat-proxy-arp-cable-isp/m-p/1783676#M533009</guid>
      <dc:creator>varrao</dc:creator>
      <dc:date>2011-08-20T15:42:11Z</dc:date>
    </item>
    <item>
      <title>ASA NAT Proxy ARP (Cable ISP)</title>
      <link>https://community.cisco.com/t5/network-security/asa-nat-proxy-arp-cable-isp/m-p/1783677#M533012</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Markus ,&lt;/P&gt;&lt;P&gt;i don't think disabling Proxy Arp will solve your case , this is how the ASA behaves for any ARP request that it not for the ASA interface ip address, in your case the ISP is having a filter "for each IP address we have ONE MAC address".&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;they have to re check this , since that proxy-arp is needed by the ASA to Answer all the requests to the published Servers . if you disable Proxy-Arp then you will not get any response for the ARP request to that ip address . &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;cheers.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 21 Aug 2011 15:22:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-nat-proxy-arp-cable-isp/m-p/1783677#M533012</guid>
      <dc:creator>Mohammad Alhyari</dc:creator>
      <dc:date>2011-08-21T15:22:45Z</dc:date>
    </item>
    <item>
      <title>ASA NAT Proxy ARP (Cable ISP)</title>
      <link>https://community.cisco.com/t5/network-security/asa-nat-proxy-arp-cable-isp/m-p/1783678#M533015</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt; Enabling DNS doctoring that will solve your issue.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 21 Aug 2011 18:42:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-nat-proxy-arp-cable-isp/m-p/1783678#M533015</guid>
      <dc:creator>haivrajesh</dc:creator>
      <dc:date>2011-08-21T18:42:48Z</dc:date>
    </item>
    <item>
      <title>ASA NAT Proxy ARP (Cable ISP)</title>
      <link>https://community.cisco.com/t5/network-security/asa-nat-proxy-arp-cable-isp/m-p/1783679#M533016</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I don't think that DNS doctoring or disabling proxy-arp will solve my problem.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;From an other point of view my problem is that I need two different IP addresses (of the same subnet) on the same physical interface AND every IP needs it's own mac address....&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I've also tried to use the the static arp configuration options: but the nat process don't uses the information stored here...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So, I need to do NAT to different IPs with different MACs on the same physical interface... I don't think the ASA (or another firewall) could handle this...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;cheers.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 22 Aug 2011 07:05:47 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-nat-proxy-arp-cable-isp/m-p/1783679#M533016</guid>
      <dc:creator>m.hoeschen</dc:creator>
      <dc:date>2011-08-22T07:05:47Z</dc:date>
    </item>
    <item>
      <title>ASA NAT Proxy ARP (Cable ISP)</title>
      <link>https://community.cisco.com/t5/network-security/asa-nat-proxy-arp-cable-isp/m-p/1783680#M533017</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Markus, &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You are totally right. Disabling proxy ARP wont work. However I dont see anyway that we can configure so that can work. See, when somebody out there is looking for IP B (Which is the one that is not assigned to the interface) The device in front of the ASA needs to fill up the layer 2 header with the mac-address of the next hop, in this case the ASA. So basically, you will have IP A and B with the same mac-address. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So Far, I have not seen a way on the ASA nor a Cisco Router to advertise an IP with a different mac-address and still be able to proceess the packet correctly. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Maybe when they resolve this bug &lt;A href="http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&amp;amp;bugId=CSCsy85614"&gt;&lt;STRONG&gt;CSCsy85614&lt;/STRONG&gt;&lt;/A&gt; there will be a way to do it, but if they have not implemented that on the router, I dont think that would be something on the ASA. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Mike &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 23 Aug 2011 01:40:18 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-nat-proxy-arp-cable-isp/m-p/1783680#M533017</guid>
      <dc:creator>Maykol Rojas</dc:creator>
      <dc:date>2011-08-23T01:40:18Z</dc:date>
    </item>
  </channel>
</rss>

