Welcome, Guest. Please login or register.
Did you miss your activation email?
+  pfSense Forum
|-+  pfSense English Support» NAT» MPLS no nat
Username:
Password:
 
 

Pages: [1]   Go Down
  Print  
Author Topic: MPLS no nat  (Read 266 times)
0 Members and 1 Guest are viewing this topic.
Jonb
Sr. Member
****
Offline Offline

Posts: 300


View Profile
« on: June 24, 2010, 04:01:30 am »

I am going to have point to point lines installed that will have their own subnet and own port on the firewall. What my question is what is the most effective way to turn off Nating between each lan and have it on for the internet access.

My original thought would be under AON to create a rule going between subnets to have the not nat option selected.
« Last Edit: June 24, 2010, 04:26:57 am by Jonb » Logged
GruensFroeschli
Global Moderator
Hero Member
*****
Offline Offline

Posts: 4253


No i will not fix your computer!


View Profile WWW
« Reply #1 on: June 24, 2010, 05:24:12 am »

NAT between OPTs and LAN is off per default.

If you're using AoN.
Have a single rule for the WAN, with as source your NATed subnets.
Make sure you dont have any rules for LAN/OPTs.

No rule = no NAT.
 
Logged

We do what we must, because we can.
Jonb
Sr. Member
****
Offline Offline

Posts: 300


View Profile
« Reply #2 on: June 24, 2010, 05:50:09 am »

Ohh ok cool now you put it that way kinda obvious. Thanks
Logged
jimp
Administrator
Hero Member
*****
Offline Offline

Posts: 3790



View Profile
« Reply #3 on: June 24, 2010, 09:19:40 am »

Actually, if you put a gateway on the OPT interface settings, it may get NAT applied since it is then considered a WAN-type interface.

But it's easy to get around that by doing as GruensFroeschli said: enable Manual Outbound NAT (AON), and make sure you do not have a rule set there for the OPT interface.
Logged

Co-Author of pfSense: The Definitive Guide.

Need help fast? Try Commercial Support.

Also check the Doc Wiki for additional information.
Pages: [1]   Go Up
  Print  
 
Jump to:  

 

Page created in 0.145 seconds with 21 queries.