^Exactly. No need for three routers unless you have some other physical restriction we don't know about. Steve

@lbm_: @G.D.: Do you see the correct [EAP] authentication method advertised with the SSID, when you scan the WiFi band? How can I check this? As I remember it, I cannot see these details from the WLAN clients? Any kind of half-good WiFi scanner should be able to display that. I use the free WiFi Analyzer by Kevin Yuan, for example. I am glad you got the issue solved.

@pbxman123: How is pfSense with USB to serial adapter support, specifically with the FTDI chipset, can you or anyone comment?  Again the feedback is much appreciated.  Thanks. They work OK for me whenever I need them, but that's not very often.  Check out the FreeBSD supported hardware list (http://www.freebsd.org/releases/10.0R/hardware.html) and the uftdi(4) driver in particular (http://www.freebsd.org/cgi/man.cgi?query=uftdi&sektion=4&manpath=FreeBSD+8.3-RELEASE)

It's good ? I will tire .

Awesome!  Thanks guys. Rick

Thanks! I hope others have experience regarding this.

Yep, I agree something looks very wrong here. What sort of DDoS attack do you think is happening here? Most of the traffic is coming from your server, if anything ddos related is happening it's your server doing the attacking. Why so many ports open? Steve

I believe so, it's done via boot0cfg From boot0cfg(8): -t ticks             Set the timeout value to ticks.  (There are approximately 18.2             ticks per second.)

Did you read the system logs? I noticed something similar the other day when I shut down a vpn connection, and on checking the system logs noticed that pfSense restarted a bunch of services, triggered by the vpn state change. I haven't noticed that before, normally it's seamless.

@mkent: The pfsense reverted back to a DHCP IP address last night about 3am of it's own accord. The behaviour you describe is seriously unusual. :o  In your place my assumption would be that hardware is failing or that pfSense was corrupted during the original installation. If I was in your position and had a firewall behaving that way I would check the drive for problems, format the drive and reload it from scratch using install media that I'd verified the checksum on beforehand. If the problem persists after a full reinstall, I'd suspect either a driver incompatibility or a hardware issue which I would then start looking for in the runtime and boot logs for inconsistencies or errors. Here are the possible hardware causes that come to mind in troubleshooting order based on my personal experiences:     a. Cabling and/or switch (use a different port and cable)     b. LAN NIC (To verify, try swapping the LAN and WAN assignments using the console menu item #1 and see if the WAN then exhibits the same issue.)     c. Hard disk (check the logs for errors, use Diagnostics: SMART Status: Perform Self-tests, badblocks*)     d. RAM (replacing is the often the surest way to confirm)     e. BIOS bug/corruption (reinstall/upgrade bios)     f. Motherboard badblocks can erase all your data depending on options but is great at finding drive media problems     pkg_add -r e2fsprogs     http://www.freebsd.org/cgi/man.cgi?query=badblocks&sektion=8&apropos=0&manpath=SuSE+Linux%2fi386+7.3

I have the same issue. Checked the status of the gateway, and that is marked as active. NAT is set to automatic mode to carry the connection from LAN to WAN, but still there is no internet connection to my virtualbox hosts.

There is a Cron package addon you can install to allow cron style scripts. Go to "System->Packages->Available Packages" and look for Cron.

Finally back with one week of testing. I replaced my wireless router with a gigabit switch and then connected the router back into the network as a wireless access point farther downstream. Seems to have worked well. The router must have gotten all weird with heavy load. Thank you all for suggestions and help. It was the difference between failure and getting this thing fixed.

yay i'm on the list… and there is no update for my board yet... at least you cant get to via the internet

For others' information: this issue auto-solved in 2.2 Alpha, which suggests it might be a driver issue specific to 2.1.x.

that's why we are here :-) pfSense has a very active community, and lot's of them are network guru's.

Hello mindfulCoyote, Thanks for answer me, you are right :). I managed configure this option and tonight i'll test ipsec failover with virtual ip. ;D

@MindfulCoyote: Not to be pithy, but I think a diagram would be a great place to start. It would add clarity to your description as well as invite commentary. Aside from the additional detail it gives us, just creating the diagram can solidify your own conceptualization. Doesn't have to be fancy, but it should include your major goals like the server "DMZ" and split routing with as much detail as you are interested in adding. You could include this info in the diagram, but lacking the diagram, some questions that I have based on your description are: I'm not entirely clear on the topology. Are you saying it's something like: (LAN1 & LAN2) –> Switch(es) --> pfSense --> Cisco --> (ISP1 & ISP 2) What is the bandwidth of the various links (internet & internal). (pfSense will become a chokepoint in your design, not sure if a Netgate 7541 is up to it? I think the Netgate 7541 includes one year of support... maybe that's a resource for you?) What is the Cisco model number and why do you want to remove it? (Cisco's are generally fairly reliable and generally quite good at doing what they were designed to do.) Your flow diagram is correct. One ISP is currently 50Mbps and the other is 30Mbps. I will draw out a clearer diagram as soon as I can. As far as the hardware goes I was led to believe that it is more than enough for our needs so I hope that this is true. I will check with my Netgate contract… I know there is support but hadn't considered that they may actually help with the firewall setup beyond the basics.