Solved : It was hard disk issue , bad sectors and couldn't read files correctly . since reset to factory defaults makes the new data applied to ram directly .. it's OK . but after reboot and load settings from Disk ..  Nothing is OK . I noticed it won't read queue statistics in webgui says I have to set traffic shaper while it's already set . and even after resetting to factory defaults , some rules doesn't work as expected after setting them up. also by many reboots I noticed there is a fast warning messages about mounting disk in pfsense boot screen . now everything works fine after replacing the disk . Thanks anyway  :) .

Does the new PFSense box have the same internal (LAN) IP as your broken PFSense box? Are you sure your gateway and DNS addresses on your client machine are correct? Can you resolve DNS does "nslookup google.com" give you back an IP-address?

Generally your problem with VoIP is latency and jitter, which is inherent in your connection, and the only thing multiple lines will get you is more bandwidth. You can carefully load balance VoIP (like send one portion of phones over one connection, another portion over another, not just load balancing connections as you'll break VoIP) and actually have enough devices that you're bandwidth-limited, then yes you can use multi-WAN for that.

@doktornotor: Perhaps time to stop exposing your firewall GUI to internet?  ::) ::) ::) Indeed. The logs in question are often from a monitoring system that just tries to connect to the TCP port. Or in the case of leaving it open to the Internet, who knows what kind of crap from random scanners. @fibrewire: I get this same message, anyone want to help me troubleshoot this? the firewall traffic stops but I can still operate from the console, however selecting option 5 (reboot) does not succeed. Highly unlikely this log has anything to do with that log. Start a new thread with specifics - can you hit the LAN IP at all, get to Internet from the console?

It was one lab pfsense, On boot some times it load the ip.txt files and some times no. I´m not using that lab anymore.

thx dr.  I thought I had somehow made a partition only 3.4MB in size when I installed pfsense and was filling it up! I understand now that the bottom part  /var/run (ufs in RAM)  is what is in RAM and not taking up space on my hard drive. Alls ok now no issues here anymore! ty

Ok. Thanks.

You could use several PFSense boxes. As for NAT, I read somewhere that you can setup several instances of NAT on PFSense, this way you can make better use of more cores.

I stand corrected.  How on Earth would anybody know to find or use that?  But then the same could be said for sfc.exe.  Thanks for the tip.  Straight into the bag of tricks it goes.

and/or perhaps open a new topic about it in the virtualization section of this forum :)

this looks like what im looking for… in this case there strangers... but i made a user just for that... guest user with simple password so its not really a problem...

@cmb: @Derelict: Unfortunately not. It's a fairly old machine. Might be getting a little tired. Possibly. Also not sure how well ale(4) NIC driver works or how good that hardware is in general. If it's quirky, maybe specifically to that combination of hardware, it could mess up the entire machine. The hardware specs are: Intel Atom N270 1.6GHz 1GB RAM Atheros Giga Ethernet Card (can't remember the chipset, but it does use the ale driver) WAN interface uses a generic USB/ethernet adapter (this works fine as the upstream connection isn't fast enough to notice) Not actually sure how to find out the wireless chipset on pfsense - lspci doesn't appear to be installed. Is there anything I can do to tweak the ale which might solve the problem?

You should have your managed switch's management interface on a separate VLAN. Then you wouldn't have had that issue in the first place.

Uhm… Use the Captive Portal.

Yeah it's never listed IPv6 IPs in the list there.

Ideally you should never have swap usage on a firewall, but if you're hanging out at 10% usage, you probably could unallocate some VM memory. Don't forget, a state consumes about 1KiB of memory and each connection has 2 states. Just make sure you have enough memory to handle your maximum number of states. 1KiB per state, 2 states per connection.

apinger is the component that current versions of pfSense use to monitor gateways - whether each gateway is up or down, also working out latency and packet loss. Unfortunately, apinger is a rather troublesome program, as searches of this forum and especially Redmine will attest. There have been various comments endorsing the desirability of replacing apinger, such as Chris Buechler's comment on Redmine #4081 suggesting pfSense 2.3 will use something different. What is clear is that apinger thinks your gateway is going down, and pfSense is responding accordingly. What is unclear is whether your gateway is actually going down, or whether apinger is falsely concluding the gateway is down when it is not. If you are experiencing problems with apinger, it can help to check 'State Killing on Gateway Failure' in System -> Advanced, Miscellaneous tab. This option is arguably named incorrectly - it should really be called 'No state killing on gateway failure'. When checked, it stops pfSense from resetting all states using a gateway when that gateway is reported to have gone down.