Pre setup information
turtlenz last edited by
I am tempted to switch from smoothwall over to PFSense but i have a couple of questions that are needed before the switch
Q: i have 3 internal networks running and would like to bind them together: (Server Cab: 192.168.3.XX, Office Network: 192.168.2.XX, Wireless Network: 192.168.4.XX) these all connect to my main incoming server
so basically i would like to be able to access the server network from the office network.
Q: setup port forwards on pfsense to specific internal ip addresses: on my router i would bridge the router directly to the main firewall server then in the firewall server i would allow certain ports on certain internal ip addresses to access the net (incoming / outgoing ) for say teamspeak, db's and what not.
Q: traffic shape user accounts when accessing the portal: am i able to limit bandwidth based on ip addresses as we have 100+ users at any given time.
any answers to these would be very helpful.
rudelerius last edited by
I'm no expert, but I think everything you wish to do with pfSense should be possible. You probably need to provide more information about how you wish to implement these things. For example, do you have multiple NICs to segment the network, or do you wish to use vlans.
There is a lot of information here. Have you read the FAQ or the Tutorials? There is good info there.
turtlenz last edited by
ahh sorry for that
the firewall server has 4 NIC's at 10/100/1000
NIC1 = router for internet
NIC2 = Office Network
NIC3 = Server Cab Network
NIC4 = Wireless AP Network
i havnt read the faq / tutorials as of yet, i am going to install it on a spare server that we have
Yes you can do all of that.
Q1. If you have firewall rules in place pfSense will route traffic between the subnets. You can access a server at, say, 192.168.3.10 from a machine at 192.168.2.20 by simply entering it's IP. No need to bridge the subnets which would effectively make one big subnet. If you want to access servers by name you can add DNS overide entries to allow that. One area that can cause problems here is if you want to browse network shares. Generally the client OS will only look for servers inside it's own subnet. If you are running Windows clients and you have a Windows server you can specify the address of that as the WINS server in the DHCP information which will allow clients to know where to look.
Q2. Yep, port forwards are easy enough and well documented.
Q3. Yep, traffic shaping on a per IP basis can be done.
A better configuration would be to bridge your router so that your public IP is on the pfSense WAN interface. That will, as you say, make port forwarding easier.