The firewall will interpret your NAT rules to determine how it should act with proxy-arpFor "hide" nat (sourcenat) it will proxy arp for the ip used as source nat, which is usually just the interface ip, which it will restrict to /32It will also look at the original destination setting (to intercept incoming session), which is typically also a /32, but if you set a larger subnet in the original destination, it will proxy arp for all of them
What are you seeing? Proxy arp is sent out of any (or all of misconfigured) when NAT is configured, if the interface is in layer3 mode (or has a layer3 vlan interface configured over a layer2 physical interface)
We are peering on a clients firewall at an exchange called NAP Africa here in South Africa. We have to source NAT out the sun-interface of our AE to be able to peer. They are telling us that we are proxy-arping on the /22.
Changed the NAT from interface address to translated address and still the same issue.
The firewall will interpret your NAT rules to determine how it should act with proxy-arp For "hide" nat (sourcenat) it will proxy arp for the ip used as source nat, which is usually just the interface ip, which it will restrict to /32 It will also look at the original destination setting (to intercept incoming session), which is typically also a /32, but if you set a larger subnet in the original destination, it will proxy arp for all of them
What are you seeing? Proxy arp is sent out of any (or all of misconfigured) when NAT is configured, if the interface is in layer3 mode (or has a layer3 vlan interface configured over a layer2 physical interface)