Using subnets with pfsense
I am running pfsense 1.2.2 and here is what i like to configure on my lan
The lan ip address is 192.168.0.0 subnet mask 255.255.255.192 which means i have 4 subnets
1. 192.168.0.0 /26
2. 192.168.0.64 /26
3. 192.168.0.128 /26
4. 192.168.0.192 /26
my pfsense box has an ip address 192.168.0.177 /26
Now, how can i use pfsense to make sure that pc's in the first subnet be able to access the pc's on other subnets and vice versa.
I've two interfaces one is WAN and other for LAN. all the pc's under pfsense has getaway as pfsense's lan address. what should i do
any one can help???
danswartz last edited by
Not understanding what you are trying to accomplish here? If you have one physical LAN, what is gained by having 4 subnets?
Ben.K last edited by
You'll need an interface in each subnet pfSense. Once you have this just configure the firewall rules to allow the traffic to pass from one subnet to another. If you don't have the actual physical interfaces, you could set up VLANs.
There really isn't much (anything?) to be gained by making this four small subnets.
i am subnetting my network to reduce the broadcasts
i've got more than 100 pc's on my lan and some use internet and some does not, so i will keep those pc's which use internet in one subnet and those who don't use internet will be kept in other subnet
in this way i can control the traffic on my lan
this is what i want to do..
HP managed switches can block multicast traffic just FYI.
If you plan to do it the easy way…..BUT. I would use VLANS to reduce traffic like that, if I did'nt have a switch that could....
blak111 last edited by
The subnetting alone won't reduce the amount of broadcasts on that network. It will just change the destination addresses. It will still be delivered to all of the nodes unless you actually divide the network using VLANs or separate hardware.
i don't have managed switch
i have only one 3com's managed switch and other switches are not managed, can i create the vlan in this scenario, i mean how can i use one manged switch to control the traffic
If the switch has VLAN option, it is no problem.
thanks very much
i'll give it a try
Smokeshow last edited by
This seems to be one of the major features missing in pfsense; the ability to assign more than one IP address to an interface. Yes, I know you can do so by modifying the config file manually, but I seem to have issues with this, especially when doing so on one of my WAN interfaces. Most of the linux firewall distros have the ability to do this easily and effectively, why can't pfsense?
ITCoresys last edited by
Even if you never use more than one pFsense, you can still add CARP virtual IP's to it to get "secondary" addresses on your WAN.
That way you can map inbound and outbound NAT to the CARP address as well as port forward statements, etc.
This is how I utilize more than a single IP in a block assigned by my ISP.
Not sure if this is the right way, but it allows me to have users port translate to address .2 and my mail server nat translate to .3 which is a CARP virtual IP.
Pls. explain more of that…..
ITCoresys last edited by
Say for example, my ISP assigns me an external address of 126.96.36.199/29 (255.255.255.248).
They describe it to you as 5 usable. Its really 6 but your ISP takes one for their router to be your default gateway leaving you 5 for your router(s).
So, your ISP uses 25 and you get 26-30 usable.
Put 188.8.131.52/29 on your WAN
Add 184.108.40.206/29 through 220.127.116.11/29 as Virtual IP's "CARP" types.
Optionally label each address with something that tells you what you intended it for like…
.26 = WAN Interface = Default outbound NAT translation for LAN network (Disable auto
.27 = EMAIL Server = Outbound translation of 192.168.x.x (Mail Server IP) to .27 (Carp virtual) and inbound port translations for TCP 25 (SMTP), TCP 110 (POP3), TCP 80,443 (Webmail)
.28 = Web server= Inbound port translations for TCP 80,443
Disable automatic outbound rule generation and use manual outbound rule generation for NAT to use the CARP virtual IP's out outbound for particular inside hosts.
This way, reverse DNS for .26 could be users.mydomain.com and the reverse DNS for .27 could be mymailserver.mydomain.com and the forward DNS for .27 could match mymailserver.mydomain.com. This way forward and reverse matches so you dont get penalized by some spam solutions for your outbound mail.
All this magical goodness because you can set more IP's on virtual IP CARP interfaces.
If you decide later to add a second pfSense for redundancy, you could set .30 on your second pfSense, set up replication from your current one and they will share those secondary addresses.
This makes it WAY better than Linux being able to have secondary addresses on its firewalls with ifconfig eth0:0 eth0:1, etc...
ktims last edited by
Yeah, I think a virtual IP on your LAN interface for each subnet would do the job here. You might need to tweak the rules a bit, but I think it should work fine.
Like everyone else though I question why you're doing it this way. Without VLANs or separate physical segments it doesn't buy you anything. Either upgrade your switches (or rearrange them so you have a VLAN-capable 'core' and unmanaged edge) or flatten it out since all it does is complicate your setup needlessly.