<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: ASA and Proxy ARP</title>
	<atom:link href="http://aconaway.com/2009/09/11/asa-and-proxy-arp/feed/" rel="self" type="application/rss+xml" />
	<link>http://aconaway.com/2009/09/11/asa-and-proxy-arp/</link>
	<description>It&#039;s possible that someone somewhere needs to see this.</description>
	<lastBuildDate>Fri, 10 Feb 2012 13:52:17 -0700</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.4</generator>
	<item>
		<title>By: Joe Schulte</title>
		<link>http://aconaway.com/2009/09/11/asa-and-proxy-arp/comment-page-1/#comment-82296</link>
		<dc:creator>Joe Schulte</dc:creator>
		<pubDate>Tue, 10 Jan 2012 14:02:56 +0000</pubDate>
		<guid isPermaLink="false">http://aconaway.com/?p=362#comment-82296</guid>
		<description>Interestingly enough I just did an upgrade from 8.2 to 8.4 and got hosed by this, but in the opposite way. 

Because it&#039;s a small site, the two main purposes of ASA was internet firewall and routing between two VLANs. 

Keeping in mind that the only uplink through the ASA was at the core switch (no routing on it - don&#039;t ask me, just part of the nightmare I walked into), I somehow had stuff on Subnet A showing the ASA&#039;s MAC as the MAC for about half the equipment on that subnet. I was able to ping those addresses of course, because it was actually the ASA responding, but nothing else would communicate with those hosts correctly. 

Eventually the Google led me to a post on Proxy Arp and how to disable it. With no better ideas I just did it and hoped. 

Solved my problem though. 

I&#039;m guessing the default went from proxy ARP being off to on at the big 8.3 switch. Thanks, Cisco!</description>
		<content:encoded><![CDATA[<p>Interestingly enough I just did an upgrade from 8.2 to 8.4 and got hosed by this, but in the opposite way. </p>
<p>Because it&#8217;s a small site, the two main purposes of ASA was internet firewall and routing between two VLANs. </p>
<p>Keeping in mind that the only uplink through the ASA was at the core switch (no routing on it &#8211; don&#8217;t ask me, just part of the nightmare I walked into), I somehow had stuff on Subnet A showing the ASA&#8217;s MAC as the MAC for about half the equipment on that subnet. I was able to ping those addresses of course, because it was actually the ASA responding, but nothing else would communicate with those hosts correctly. </p>
<p>Eventually the Google led me to a post on Proxy Arp and how to disable it. With no better ideas I just did it and hoped. </p>
<p>Solved my problem though. </p>
<p>I&#8217;m guessing the default went from proxy ARP being off to on at the big 8.3 switch. Thanks, Cisco!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Justin Ellison</title>
		<link>http://aconaway.com/2009/09/11/asa-and-proxy-arp/comment-page-1/#comment-31175</link>
		<dc:creator>Justin Ellison</dc:creator>
		<pubDate>Wed, 15 Sep 2010 09:58:11 +0000</pubDate>
		<guid isPermaLink="false">http://aconaway.com/?p=362#comment-31175</guid>
		<description>@Pulsarav - I think Cisco bug CSCti38867 is what you&#039;re looking for.  I believe I just tripped over that myself.</description>
		<content:encoded><![CDATA[<p>@Pulsarav &#8211; I think Cisco bug CSCti38867 is what you&#8217;re looking for.  I believe I just tripped over that myself.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aaron Conaway</title>
		<link>http://aconaway.com/2009/09/11/asa-and-proxy-arp/comment-page-1/#comment-23283</link>
		<dc:creator>Aaron Conaway</dc:creator>
		<pubDate>Thu, 27 May 2010 01:52:52 +0000</pubDate>
		<guid isPermaLink="false">http://aconaway.com/?p=362#comment-23283</guid>
		<description>According to what you submitted and what I found, proxy ARP is indeed enabled by default (no sysopt proxyarp X), but it surely wasn&#039;t on our 5540.  I can&#039;t find any other documentation that says it should be that way, though.  I&#039;ve got no answer.  :(</description>
		<content:encoded><![CDATA[<p>According to what you submitted and what I found, proxy ARP is indeed enabled by default (no sysopt proxyarp X), but it surely wasn&#8217;t on our 5540.  I can&#8217;t find any other documentation that says it should be that way, though.  I&#8217;ve got no answer.  :(</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pulsarav</title>
		<link>http://aconaway.com/2009/09/11/asa-and-proxy-arp/comment-page-1/#comment-23282</link>
		<dc:creator>Pulsarav</dc:creator>
		<pubDate>Wed, 26 May 2010 22:43:51 +0000</pubDate>
		<guid isPermaLink="false">http://aconaway.com/?p=362#comment-23282</guid>
		<description>I ran across this post while researching the same issue as you describe, however in this case proxy arp is turned on.  The ASA is running the latest 8.3 code, so I suspect a bug.

On another note, the Cisco web site indicates that proxy arp is *on* by default on the ASA&#039;s.  Do you have a Cisco source that says it isn&#039;t?

~~~~~~~~
To disable proxy ARP for NAT global addresses or VPN client addresses on an interface, use the sysopt noproxyarp command in global configuration mode. To reenable proxy ARP, use the no form of this command. 

sysopt noproxyarp interface_name 

no sysopt noproxyarp interface_name 

Syntax Description
 interface_name 
 The interface name for which you want to disable proxy ARP. 
 
Defaults 
Proxy ARP is enabled by default. 
~~~~~~~~~~

Thanks,

Pulsarav</description>
		<content:encoded><![CDATA[<p>I ran across this post while researching the same issue as you describe, however in this case proxy arp is turned on.  The ASA is running the latest 8.3 code, so I suspect a bug.</p>
<p>On another note, the Cisco web site indicates that proxy arp is *on* by default on the ASA&#8217;s.  Do you have a Cisco source that says it isn&#8217;t?</p>
<p>~~~~~~~~<br />
To disable proxy ARP for NAT global addresses or VPN client addresses on an interface, use the sysopt noproxyarp command in global configuration mode. To reenable proxy ARP, use the no form of this command. </p>
<p>sysopt noproxyarp interface_name </p>
<p>no sysopt noproxyarp interface_name </p>
<p>Syntax Description<br />
 interface_name<br />
 The interface name for which you want to disable proxy ARP. </p>
<p>Defaults<br />
Proxy ARP is enabled by default.<br />
~~~~~~~~~~</p>
<p>Thanks,</p>
<p>Pulsarav</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aaron Conaway</title>
		<link>http://aconaway.com/2009/09/11/asa-and-proxy-arp/comment-page-1/#comment-20307</link>
		<dc:creator>Aaron Conaway</dc:creator>
		<pubDate>Fri, 18 Sep 2009 13:05:46 +0000</pubDate>
		<guid isPermaLink="false">http://aconaway.com/?p=362#comment-20307</guid>
		<description>Hi, NN11:

This particular instance was a 5540 running 8.2(1).  The NAT was a 1-to-1 host NAT, so all traffic to/from the billing server is NATted.

I&#039;d rather not share too much information on the topology, but it&#039;s quite simple.  The billing network is on an interface with security level of 0.  The production network is off an interface with security level of 50.  In this case, the productions servers were another layer-3 hop away, but the same would hold true if it were directly attached to the network with the production interface.  So, simplistically, you have

&lt;pre&gt;
      &lt;- Static NAT -&gt;
Billing -- 5540 -- Production&lt;/pre&gt;

I hope that clears it up for you.  If you have questions on using VLANs on the 7600, I can see what I can drag up for you.</description>
		<content:encoded><![CDATA[<p>Hi, NN11:</p>
<p>This particular instance was a 5540 running 8.2(1).  The NAT was a 1-to-1 host NAT, so all traffic to/from the billing server is NATted.</p>
<p>I&#8217;d rather not share too much information on the topology, but it&#8217;s quite simple.  The billing network is on an interface with security level of 0.  The production network is off an interface with security level of 50.  In this case, the productions servers were another layer-3 hop away, but the same would hold true if it were directly attached to the network with the production interface.  So, simplistically, you have</p>
<pre>
      < - Static NAT ->
Billing -- 5540 -- Production</pre>
<p>I hope that clears it up for you.  If you have questions on using VLANs on the 7600, I can see what I can drag up for you.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: netninja11</title>
		<link>http://aconaway.com/2009/09/11/asa-and-proxy-arp/comment-page-1/#comment-20295</link>
		<dc:creator>netninja11</dc:creator>
		<pubDate>Fri, 18 Sep 2009 03:03:01 +0000</pubDate>
		<guid isPermaLink="false">http://aconaway.com/?p=362#comment-20295</guid>
		<description>Hi,
Good to know about the ARP Reply issue with the ASA.  What ASA model and code is running on the appliance?

So what type of Static NAT policy did you have on the ASA?  Sounds like a Static NAT that covers an entire subnet (1-1, host-host).
I do not seem to get the network topology from your description above.  Can you email me one?  I would like to see the VLAN layout to understand the traffic flow from the production server to/fro accounting server (no ip addresses please...:-)).

Thanks,
netninja11</description>
		<content:encoded><![CDATA[<p>Hi,<br />
Good to know about the ARP Reply issue with the ASA.  What ASA model and code is running on the appliance?</p>
<p>So what type of Static NAT policy did you have on the ASA?  Sounds like a Static NAT that covers an entire subnet (1-1, host-host).<br />
I do not seem to get the network topology from your description above.  Can you email me one?  I would like to see the VLAN layout to understand the traffic flow from the production server to/fro accounting server (no ip addresses please&#8230;:-)).</p>
<p>Thanks,<br />
netninja11</p>
]]></content:encoded>
	</item>
</channel>
</rss>

