A 1:1 NAT doesn't expose the complete hosz to the internet. You still need firewallrules to allow traffic. But I wouldn't use 1:1 NAT for only a few ports either and it's more flexible if you do it with portforwards as you can forward some ports to server a and some other ports to server b then. Another advantage is that portforwards will work with natreflection whereas 1:1 nat won't.

Thanks razor, once again!

What you are suggesting seems like a decent solution, but makes things pretty difficult (read: beyond my abilities) for other parts of my network.  Is there no way the modem can distribute public IPs via DHCP (static mappings of course)? According to Comcast there isn't, but why not? I think that would be the ideal solution.

My gut feeling thinks that the modem wants some sort of communication to establish whether the connection will be DHCP or else a bridged static IP.  The pfSense log is seeing the "link up" message on the WAN port when it comes up, but it is not taking any action as it is not a DHCP interface (on the pf side).  Perhaps there needs to be some sort of communication from pf when that link does come up?

Regards,
Aaron

@superwormy:

Incoming T1 connection, a few machines need to have public static IP addresses, the rest will be NATed and just need access to the Internet. I'd like to have the machines that are exposed to the Internet in something like a DMZ… does pfSense have DMZ support, or is there a better way to do this, or...?

I have 3 network cards in the pfSense box... if I use one for WAN, one for LAN, and one for the DMZ machines, will this work to isolate the LAN machines from the machines that should be in the DMZ?

take a look to the docu from monowall written by cmb, it runs as it should.
http://doc.m0n0.ch/handbook-single/#id2604946

@Tai:

Im not sure what disabling NAT Reflection really entails if it is a horrible security risk or just makes port forwarding/nat more work. ??
Cheers

It's not a security risk, it just puts more load on the pfSense box. The domain name you use to access your virtual sites internally looks up to a public IP. Thus the request goes out to the pfSense box. Enabling NAT reflection allows the pfSense box to redirect the request back into the internal network to the correct host.

If you had split DNS when inside your network the domain name would look up to the internal IP of the server. This would avoid the unnecessary loop to the pfSense box as the request would go directly to the server. When outside your network the domain name would look up to your public IP.

There are ways to do such configs not from the pfsense gui!

Search google if you want to do such a config but it just provides basic security and not a real protection.

Go to the console or ssh in (if you have ssh enabled at system>advanced) In the menu you'll find an item "pftop" that will do exactly what you are looking for. Press "h" for advanced options while running pftop.

THKQ very much.
I`ll wait it…

Try setting your harddisk in PIO4 mode if you still recive this message check your RAM.

There might be an edge case where might need to change the allocated memory to kernel vs. user base. What version of pfSense is this?

You need at least 2 interfaces (WAN and LAN) but you can have as many interfaces as your hardware supports basically with multiple LANs or WANs.

You only have to follow this simple guide: Rules are applied on incoming traffic only so if you want to do outbound balancing to multiple WANs the traffic is coming in on the LAN and leaving on the WANs/OPTs. Your rules have to go to the LAN tab therefor. And also have a look at the tutorials and docs. They should get you started quickly.

Assuming you have the full install then "pkg_add -r zoneinfo" (from the command line) should do it.

Great to hear that. Good progress has been made on the traffic shaper. Now can we put together a bounty to extend captve port to be multi-wan and multiple interface?

128 MB of RAM is the minimum supported.  If you ever plan on adding any packages you'll want to add more RAM.

I'd go with rsync over SSH.  Rsync will allow you to keep the webserver updated with changes on the fileserver and as you should be using SSH to admin it anyway you're not opening up any new holes.

Oke , sensei Ullrich

Thanks a lot

Doesn't matter if it's in the GUI for me, personally.  If the support was there, I was just going to modify /etc/inc/interfaces.inc to add the lines.  No big deal.

After posting the last reply, I saw what was wrong, LAN is now on 192.168.10.1 and it all works. So much for late nights! Thanks, ~Lawrence