You don't have to have a switch, but will generally want one unless you don't need super-fast (gigabit) throughput between the hosts and must filter traffic between them for some reason. It's generally more sensible to get a switch, but depends on the circumstances.

Found the issue, our local users and servers are on the same LAN, but we had activated the Advanced option "Disable NAT Reflection" . When we took that option off everything started working properly. Thanks for the help. cjb

Hi, This problem are solve. The problem are on my client computer. Because when I use different computer to ping www.google.com with pfsense. My latency are back to 40ms. Thanks to all.

Looks like something corrupted the log file. It wouldn't really be a bug in the system log, though. I've seen messages interleaved on the console sort of like that, on multi-core/multi-CPU systems, but usually the logs are OK. I wouldn't worry about it unless it happens repeatedly, and if so, I'd check out all the hardware to make sure you don't have something flaky in that department.

cool. thanks for the advice. might switch back to sata for now and look at ssd as the price comes down.

There's only one rule there, created while setting up carp according to the book. Anyway, it's fixed, so no need to punish the brains any further… Thanks for helping!

How many local users? How many remote users? What VPN bandwidths (and packets per second) are you expecting to push at peak? How many VOIP phones are you planning on using? What else are you planning on running (rather than just apparently doing a copy and paste on somebody's question please list the packages or explain what you want to do)?

I thought your question was how to handle the DSL authentication automatically by pfSense but guess you just want to get to the auth page … What happens when you try to surf to the 173.23.0.3 page, browser time out? Can you post a screenshots of pfSense's Status->Interfaces and Diagnostic->Routes pages when connected with DHCP.

uTorrent has become really chatty due to its µTP algorithm. It floods routers with tiny UDP packets instead of most torrent clients which let TCP handle everything (which usually use the full 1500 bytes). I don't know if that's relevant, but you could try a client which doesn't support µTP and see what happens.

my temps look fine too, and inside is pretty clean, i only built the thing less than 6 months ago.

for those who you try to use easyphp as your web server for a repositry you need to do the following hardcode $freebsd_machine as described above edit your httdp.conf for two things:  listen on your interface (not just localhost) and change your default directory allowoverride to all (from none) add a .htaccess file to /packages/config directory that contains 'AddType text/plain php inc xml' to stop easyphp from trying to render the files rather than just transfering them.

When you make a bridge, it is not fully destroyed until you reboot, even if you disable it in the GUI.

Normal, pFsense hasn't a FTP server included. The question has been asked many times, and answered many times because why not. If you guys do a 1+1 (SSH+FTP)  - see the messages above then you have the solution : SFTP !! Works great with FileZilla or SmartFTP or …! These support de SFTP protocol. Just remember to use port 22 (SSH) - the user name will be 'root' (not 'admin') ans select the LAN IP of your pfSense box. Use also the SFTP protocol and you'll see !

i found the problem. my browser is always open and constantly refreshing bandwidthd and imspector. the downtime were when the wireless burped and timed out the page till i manual refreshed it. mystery solved