Want to win a PS4? Go Premium and enter to win our High-Tech Treats giveaway. Enter to Win


Juniper Netscreen L2L VPN with Public IP Addresses

Posted on 2013-05-20
Medium Priority
Last Modified: 2013-06-10
I have a requirement to implement multiple VPN L2L tunnels to a number of different peers.

Some of the resources behind my side of the VPN will need to be accessed by several of the remote sites.

To avoid same-private-subnet issues a number of the peers that I need to connect to insist on having pubic IP NATs applied to the hosts to be accessed on either side of the tunnel.

I can set this up with no issues on my Cisco ASA. I just setup the static NAT for each host that needs to be accessed over a tunnel and then apply whatever access rules are needed per tunnel in the interface and crypto ACLs.

This seems to be an issue, however, on the Juniper.

It seems that, on the Juniper, once a host has been NAT'd to a public IP and applied to a tunnel it cannot be applied to another tunnel. This means that those resources on my side of the VPN that need to be shared by multiple peers can only be accessed by one peer.

Is this correct ? Is there no way around this ?

If this is correct it would appear to be a fairly fundamental issue with regard to the functionality of this kit.

Question by:ccfcfc
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 2
  • 2
LVL 18

Expert Comment

by:Sanga Collins
ID: 39181538
With juniper devices you can use a Dynamic IP pool (DIP) to assign IPs to be NATd to private network servers and devices. This will get around the limitations of using a MIP.

Author Comment

ID: 39181557

Thanks for the quick response.

Can you point me at any info on this ? I am from the Cisco world and am new to Juniper so any relevant how-to or configuration example would be really useful.

LVL 18

Accepted Solution

Sanga Collins earned 1050 total points
ID: 39181574
here is the KB article for DIP pool on juniper devices with ScreenOS. If you have an srx serise device thats running Junos firmware, let me know and I will post the KB article for DIP configurations.

Q2 2017 - Latest Malware & Internet Attacks

WatchGuard’s Threat Lab is a group of dedicated threat researchers committed to helping you stay ahead of the bad guys by providing in-depth analysis of the top security threats to your network.  Check out our latest Quarterly Internet Security Report!

LVL 71

Assisted Solution

Qlemo earned 450 total points
ID: 39181624
Are you are using different public IPs for each server, or perform port forwarding on one or a few public IPs?

DIPs only work as source address, that is for outgoing traffic. This needs to be set up in the respective policy. You would have to combine that with a incoming policy applying destination NAT. This allows for a bidrectional communication, if necessary.

VIPs only work for incoming traffic, and are used commonly for port-mapping.

MIPs implement 1:1 NAT.

Having said that, what your peers demand is nonsense. It makes sense to map to another private network, but usually only one party has to do that. It also makes sense to use a "transfer network" type of translation on both sides - this can be done on your side with either MIPs or DIPs and appropriately set up policies, as described above.
LVL 18

Expert Comment

by:Sanga Collins
ID: 39181672
I had some concerns about what the remote site admin was asking as well, but didn't want to step on any toes inadvertently.

Author Comment

ID: 39181735
I agree on the issue of the requirement for Public IP address utilisation. However, when you are dealing with huge global organisations and that is their policy it can be difficult to get them to change it.
LVL 71

Expert Comment

ID: 39181758
Well, public IPs are likely to collide with not yet used public IPs ;-) IPv4 doesn't allow for many "free" IP addresses any more.

Featured Post

[Webinar] Lessons on Recovering from Petya

Skyport is working hard to help customers recover from recent attacks, like the Petya worm. This work has brought to light some important lessons. New malware attacks like this can take down your entire environment. Learn from others mistakes on how to prevent Petya like worms.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This article will inform Clients about common and important expectations from the freelancers (Experts) who are looking at your Gig.
This article explains the fundamentals of industrial networking which ultimately is the backbone network which is providing communications for process devices like robots and other not so interesting stuff.
Here's a very brief overview of the methods PRTG Network Monitor (https://www.paessler.com/prtg) offers for monitoring bandwidth, to help you decide which methods you´d like to investigate in more detail.  The methods are covered in more detail in o…
Monitoring a network: why having a policy is the best policy? Michael Kulchisky, MCSE, MCSA, MCP, VTSP, VSP, CCSP outlines the enormous benefits of having a policy-based approach when monitoring medium and large networks. Software utilized in this v…
Suggested Courses

610 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question