Security

Elevate Community & Juniper Customers: Here at Juniper, we recognize upgrading your SRX can be a challenging and delicate process. For this reason, we developed the SRX Upgrade Guide documentation to assist you. This guide has you covered from what ...

Hi Steve, Thank you for the clarification, but in my case there were no zone-based policies. Both policies were global, but with addition of "from-zone" and "to-zone" knob. It appears that this configuration is perfectly fine and working. The issue ...

For your global policies to work there has to be zero potential matches in standard zone to zone policies. If any existing standard zone to zone policy is possible they take priority. So you need to remove all the standard zone to zone matches to avoid ...

Hi folks, While testing firewall policies in isolated environment, I faced with a very strange behavior of the firewall. So, when a traditional security policy is created, from-zone and to-zone is specified. When it is checked with "show security ...

Well, as long as the Branch A admin already has policy and routes in place to push the branch B traffic to HQ you should be able to configure branch B and HQ to support it. If they don't have that in place, then there isn't really much that you can do. ...

This message was posted by a user wishing to remain anonymous If I understood correctly, in order for BranchA and BranchB to have communication, it is enough to reroute the traffic between BranchB and HQ, because I have access to them. I don't have ...

You should be able to just put routes on the routers to allow Branch A to use the HQ tunnel to send it's traffic for branch B to HQ which will then use the tunnel to branch A. That does assume that the other administrator will put a route for the Branch ...