After posting the last reply, I saw what was wrong, LAN is now on 192.168.10.1 and it all works. So much for late nights! Thanks, ~Lawrence

Either go to:  https://<pfsense-ip>/status.php#sysctl%20hw.physmem or install the phpsysinfo package if you're not on embedded installs.</pfsense-ip>

@MTHead: Please please PLEASE tell me you mean "switch", not "hub"! …or just a 24/48-port bridge.  ::)

thanks for the info. It's very helpful

i've the same problem. 1 rc4 pool.ntp.org time zone: -5 Doum

Generally the WAN port will have a real ip and so any packets with private ip addresses will be unwanted (forged/part of attack etc) so by default all rfc1918 packets should be blocked.

I totally second what Scott wrote. Having posted a similar statement in the past myself gave a reply in which someone suggested to pick another theme when using IE. In  System: General Setup  use the theme: pfSense  if you have to work with IE.

Do this from a shell fetch -o /usr/bin/telnet http://www.pfsense.com/~sullrich/extra/telnet chmod a+rx /usr/bin/telnet

Sorry guys. My mistake. In our subnet the lowest IP (and also the highest) number cannot be assigned to the router gateway. I have changed the gw IP's from xx.xx.80.192 to xx.xx.80.193 and everything goes OK now.

Have a look at the states table and see if they are all originating from one LAN IP. I had an issue with some sort of DoS program on a machine that one morning started sending out thousands of requests to weather.com. Tied up the entire state table. I pulled that machine and all was back to normal.

We are considering creating a similar Sydney, Australia - based position if there are any Aussies looking. Cheers Andy C1, Sydney

Thanks for your quick reply I have now figured it out after some trial and error I am a pfsense noob but will learn quickly

Old configs are stored in  /cf/conf/backup Check if a previous version has been written there. The time stamp on the file might give you another hint.

awesome…..I'll check that too. I actually used another method to confirm the ports opened correctly.... Netcat on both rigs. (awesome program) The ports are forwarding just fine. Thanks !

I followed the advise and turn load balance feature off. I deleted the pools, firewall rules, and disable OPT1. User reports positive result … and has been stable for 5 hours now without experiencing random disconnect. That makes me wonder, whether or not I made configuration error for load balancing. :- But if there were configuration error, I'd assume the load balancing won't work. In my case it worked beautifully, doing fail-over without missing a beat! I turned off modem1, it automatically goes to modem2. I turned off modem2, it automatically goes to modem1.

Not "htop" explicitly, but there have been many threads about installing non-pfSense packages. Here's a few posts to help: http://forum.pfsense.org/index.php/topic,6386.msg36771.html#msg36771 http://forum.pfsense.org/index.php/topic,7636.msg43728.html#msg43728 http://forum.pfsense.org/index.php/topic,2904.0.html http://forum.pfsense.org/index.php/topic,2828.0.html

Don't worry! Unless you want to dive under the hood no OS knowledge is needed. All configuration stuff is done in the webGUI and shouldn't even be done in the file system. If you have a spare machine to test pfSense on you can d/l a live CD. Boot it, configure the interface(s) and access it from a host on the same subnet. Unless you actually install pfSense on that machine (doable with the same Live CD) no changes to a previously installed OS will be made!