@johnpoz: So what your saying is your messed the mask on the interface, or prob set a gateway on it? while doing it from cmd line ;) You might have wanted to mention that you were not using the default IP, etc. Good point, sorry, I didn't think that was relevant.  I guess too much information is better that not enough.  The subnet I was setting was a /8 BTW @stephenw10: If that is the case it would be great to know exactly what happened. There have been many instances recently of people misconfiguring internal interfaces but I've not been able to replicate it. Also I'm not sure quite how that would explain the promiscuous mode. Steve Yeah, it was definitely a strange problem.  Is there a log or something I could send to help you figure out what happened?

https://redmine.pfsense.org/issues/3501 https://redmine.pfsense.org/issues/3597 Probably others.

Maybe not now, but in the near future. The i5 has aes ni, the celeron does not. Pfsense does not currently support aes ni well, but it will in the very near future. The i5 will therefore likely use less power than the celeron with VPN

Firewall rules - you probably have "pass all" rules. Make those more restrictive, like: VLAN2: Pass source VLAN2net destination !VLAN3net VLAN3: Pass source VLAN3net destination !VLAN2net

Hello! Some ISP networks makes such trouble if you have the interfaces flow control on. So try to shut it off on WAN if. This could be done by adding a line like hw.vr0.fc_setting=0 to your /boot/loader.conf.local. "vr0" in this example is the name of the affected interface and depends on the hardware driver. In your case it may be something else. If /boot/loader.conf.local doesn't exist yet, create it at first. Maybe it's also possible to configure this in system > advanced > system tunables, but i've made research that not everything which works in loader.conf also works there.

@cmb: You can run many clients and/or servers, something referring to a single instance would be one particular client or one particular server. Thank you very much.

My pfSense box is having some HDD issues at this moment so I'll have to update this later on if it works out well. Thanks for the quick reply!

I am iranian too! I have customized pfsense completely. I am Self-employed. If You're Interested, We can make a contract.

Thanks

generally speaking for dmz with private ips: 1. create DMZ 2. create NAT Mapping (DMZ = home for hosts that are reachable from the outside, so you want your external ips translated into private ips - or map ports of your external ip to the private ips) 3. create inbound rules for dmz (here you use as destination the private ips of the dmz hosts) the default lan to anything rule allows you to access the dmz hosts if you like to access lan hosts from your dmz (which you dont do generally) you need to create dmz->lan rules too hope that helps to find more detailed infos

Did you install the vmware tools? Then you see the vmware ifs. Otherwise i had also IntelPro1000 in the list (hope i dont mix it up with fusion right now)

Considering Gmail ONLY lets you use the encrypted variants (465/587, 993, 995), cannot see what's strange about this.

The only way you might be able to get away with a slightly simpler configuration is if your new switches support "private VLANs", the actual name varies by brand/implementation. Basically you define one upstream port (the gateway, pfSense) and define the other ports as client ports, and then the client ports may only talk to the upstream port. It's similar to AP client isolation, but for wired clients. Using Separate VLANs is a more secure practice, but also significantly more to manage.

What's your network's default gateway? If it's 192.168.1.1, it would be because of a duplicate gateway. That will wreak havoc with a network.

On pfSense you must have the first interface, which is internally named "wan" and can be assigned to whatever network device you like and you can give it a "friendly name" - e.g. yours is called "DSL". Look in /cf/conf/config.xml for "DSL" and "wan" - I expect you will find those together in one of the interface sections. I guess you are saying that "DSL" and the selected device are not used any more, and you ant to get rid of them. You can shuffle device assignments around to get some other current WAN device on that first entry, rename the friendly name to whatever is good for you, then you would have to re-enter the settings and rules from whatever OPTn the WAN-style interface used to be and put thme on the "real wan" interface.