Hey all,
happy new year to you all!
Some weeks ago i had a strange problem with a customer where he told me that Juniper firewall doesn't see a unix cluster failover.
I ofc was like, this can't be true, i have thousands of installations and noone ever complained!
The customer and me did some debuging (debug arp all, debug arp task) to see if this unix cluster sends out Gratuitous arps.
We saw that this was the case but that juniper firewall cluster didn't refresh the arp entry for this ip. (one ip and no virtual mac, so he needed to update this).
After some more debugs and working with Advanced JTAC we saw that the problem was related to the command "set arp nat-dst", this command make sure that the juniper firewall does proxy arp for policy based dst-nat. (see previous post).
if this command is in the config the juniper firewall will only refresh entry if he receives a G-arp response. (not to a g-arp request).
He must do it for both! if you remove command, he response to both.
This is a bug (and very hard one to find).
GreetZ,
Frac
Showing posts with label ARP. Show all posts
Showing posts with label ARP. Show all posts
Tuesday, January 6, 2009
Wednesday, April 23, 2008
Proxy arp
Hi all,
Proxy arp is something that not all people understand well. Some devices are able to do it, other not, and other do it automatic (sometimes), etc....
Here i will give a brief overview of how juniper firewalls handle proxy arp:
As most of you know there are 5 solutions to do NATTING in juniper firewalls:
MIP: one to one (bi-directional)
DIP: many to one (uni-directional)
VIP: one to many (uni-directional)
Destination NAT (policy): one to one, one to many (uni-directional)
Source NAT (policy): many to one, one to one (uni-directional)
So this is a overview of the natting, know when will the firewall to proxy arp for these NAT addresses?
Yes:
-MIP
-VIP
No:
-Dest nat
So you see that when using Destination nat you will have problem. Solution to solve this problem, ... place a static arp entry on higher level router, or when not in same network has the interface ... place a route to cluster ip of the juniper firewall.
Sometimes this isn't a solution, because the upstream router isn't managed by yourself. This means you need to be able to do proxy arp on firewall for these NAT addresses.
Well there is a hidden command "set arp nat-dst", which will do proxy arp for NAT addresses in a certain situation!!
When will he do it or not:
• The Destination NAT policy must be configured using the same source and
destination Layer 3 security zone. However, traffic that matches the policy
can then be sent to any Layer 3 security zone.
• The device does not respond to an ARP request if the Destination NAT IP is
in the same incoming subnet as a secondary IP address.
• In an HA environment, the device only supports the Destination NAT ARP
capability if using NSRP Active/Passive on interfaces that reside in VSD ID
0.
• In ScreenOS 5.0r7 and below, the device does not respond to an ARP request
for a Destination NAT IP that is in the same subnet as the incoming
interface for a Destination NAT policy.
Hope this helps you all.
Proxy arp is something that not all people understand well. Some devices are able to do it, other not, and other do it automatic (sometimes), etc....
Here i will give a brief overview of how juniper firewalls handle proxy arp:
As most of you know there are 5 solutions to do NATTING in juniper firewalls:
MIP: one to one (bi-directional)
DIP: many to one (uni-directional)
VIP: one to many (uni-directional)
Destination NAT (policy): one to one, one to many (uni-directional)
Source NAT (policy): many to one, one to one (uni-directional)
So this is a overview of the natting, know when will the firewall to proxy arp for these NAT addresses?
Yes:
-MIP
-VIP
No:
-Dest nat
So you see that when using Destination nat you will have problem. Solution to solve this problem, ... place a static arp entry on higher level router, or when not in same network has the interface ... place a route to cluster ip of the juniper firewall.
Sometimes this isn't a solution, because the upstream router isn't managed by yourself. This means you need to be able to do proxy arp on firewall for these NAT addresses.
Well there is a hidden command "set arp nat-dst", which will do proxy arp for NAT addresses in a certain situation!!
When will he do it or not:
• The Destination NAT policy must be configured using the same source and
destination Layer 3 security zone. However, traffic that matches the policy
can then be sent to any Layer 3 security zone.
• The device does not respond to an ARP request if the Destination NAT IP is
in the same incoming subnet as a secondary IP address.
• In an HA environment, the device only supports the Destination NAT ARP
capability if using NSRP Active/Passive on interfaces that reside in VSD ID
0.
• In ScreenOS 5.0r7 and below, the device does not respond to an ARP request
for a Destination NAT IP that is in the same subnet as the incoming
interface for a Destination NAT policy.
Hope this helps you all.
Labels:
ARP,
Dest-nat,
Juniper Networks,
NAT
Subscribe to:
Posts (Atom)
