[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 768
  • Last Modified:

Juniper Netscreen L2L VPN with Public IP Addresses

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.

TIA.
0
ccfcfc
Asked:
ccfcfc
  • 3
  • 2
  • 2
2 Solutions
 
Sanga CollinsSystems AdminCommented:
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.
0
 
ccfcfcAuthor Commented:
sangamc,

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.

Thanks.
0
 
Sanga CollinsSystems AdminCommented:
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.

http://kb.juniper.net/InfoCenter/index?page=content&id=KB4748
0
Prepare for your VMware VCP6-DCV exam.

Josh Coen and Jason Langer have prepared the latest edition of VCP study guide. Both authors have been working in the IT field for more than a decade, and both hold VMware certifications. This 163-page guide covers all 10 of the exam blueprint sections.

 
QlemoC++ DeveloperCommented:
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.
0
 
Sanga CollinsSystems AdminCommented:
I had some concerns about what the remote site admin was asking as well, but didn't want to step on any toes inadvertently.
0
 
ccfcfcAuthor Commented:
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.
0
 
QlemoC++ DeveloperCommented:
Well, public IPs are likely to collide with not yet used public IPs ;-) IPv4 doesn't allow for many "free" IP addresses any more.
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

  • 3
  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now