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.

@cmb: Was about to reply that's what your BIOS is reporting, something not right there. Might want to check for a BIOS update as that seems like some kind of bug with it. Glad you found a workaround at least. It was fine until I reinstalled everything…..but I had been tinkering with BIOS settings trying to get the watchdog timeouts to stop. This is the first BIOS for this board and I'm hoping SuperMicro comes up with a fix for my watchdog timeouts.  Sure seems to be a hardware issue (details in the hardware forum thread).

No, nothing logged prior to the crash. I suspect this is either a Snort memory leak or badly configured Snort. I don't know Snort that well so I could have done something stupid.

The ISP fixed it, but in the mean time I managed to mitigate the problem by executing the following script every few minutes via a cron job: #!/bin/sh ALLDEST="8.8.8.8 208.67.222.222" COUNT=1 while [ $COUNT -le 2 ] do for DEST in $ALLDEST do ping -c1 $DEST >/dev/null 2>/dev/null if [ $? -eq 0 ] then exit 0 fi done if [ $COUNT -le 1 ] then /usr/local/sbin/pfSctl -c 'interface reload wan' >/dev/null 2>&1 exit 1 fi COUNT=`expr $COUNT + 1` done The script is a hybrid based on this script and the command in the last post here since the ifconfig doesn't work for pppoe. Big thanks to those guys. All credits go to them.

@mike254: That's where it switches over to serial console up until the boot process is complete. It's probably stopping at an interface assignment prompt which is only visible on the serial console. Connect a null modem cable to the serial port and console into it and you should be able to assign the NICs and continue. Get in touch with us via support if you need further help with that. Thanks cmb Does this mean the hardware is not faulty? Are there any commands i need to enter on my terminal to access the Serial console?

@CyberTiVo: There are many reasons to have a quick simple way to have spare pfSense backups since I have had quite a few USB sticks loose their cookies. Yes, there are many reason to have a backup. There are zero reasons to make backups by using completely broken methods like trying to dd a live system. Absolutely horrible idea leading to inconsistent state and broken filesystem.

what is Apinger using as the destination ip (my gateway ip doesnt reliable respond to pings) maybe it prioritises other internet traffic over the pings also i wouldnt trust that graph (apinger)find a different tool whats your cable modem show http://192.168.100.1

I'd be happy of he would just answer the simple questions he's being asked, such as What is it that you're really trying to do?