Try "pfctl -d" from the shell. This will disable the packetfilter. Then create the needed rule to access the webgui at WAN. Save, apply and reboot. You should now be able to do everything using the webgui at WAN. If your WAN has private IP-space make sure to uncheck the "block private IPs"-option at interfaces>wan too.

Polling prevents the system from getting blocked by interrupts. As long as you are not hitting such situations frequently I would not use polling.

@gendrix: @hoba: Try to disable UDMA. See http://devwiki.pfsense.org/BootOptions for how to do that and how to make it default. thancs tho HOBA, i have tried what you've wrote, and its work i have new problem now, i cant open the web configurator. I cant ping the lan interface, always show messeges : rl0 watchdog  timeout rl1 watchdog  timeout rl2 watchdog  timeout all my ehernet interfaces doesnt work. i shows not a normal detection on my ethernet switch. i try to move the ethernet card to other pc, it works ok. i don't whats the problem. i think my cpu is in trouble. any idea ??? ??? ??? You may want to check the hardware compatability list to make sure your NICs are there - if not it is hit or miss… gm...

The workaround above works with any version. However for embeddeds I recommend a reflash.

With 1.2: If I enable Upnp on both LAN and OPT1, on OPT1 the pfsense router is seen with the LAN address , but Utorrent can not open port with UpNp, maybe because I block the OPT1 -> LAN in the firewall rules. So I added a rule OPT1 -> Lan Address but still no port opening. If I enable OPT1 only,  pfsense is seen with the OPT1 address and Utorrent can open port with Upnp

I've also seen problems where particular brands of cards don't work in a particular brand of adapter, but other brands do.  So far I've not had any problems with the Crucial (Micron) brand of cards in any adapter.

Reinstall with the 1.2-RELEASE cd and then pick the SMP kernel.  Does this change the situation?

@vsnine: Additionally, http://192.168.1.1/status_nut.php is not actually dynamic. vi reveals that the page is just a dump of what it shows from some other page. Glad it is working now. The status_nut.php page utilizes NUT's upsc. The page parses the data returned from the command.

No i have not always had high collisions, only when using the hub.

1st: the name of the interface is not x10 its xl0 or rl0 (notice the difference betwen 1 and the letter "l") 2nd: too use auto detect u must first unplug the cable from bouth of youre interfaces and connect them when the dialog apears try this and post back reply

Nothing wrong with SMP on single-core machines :)

@corrumpu: More searching and I guess this appears to be a bios issue. I'm off to update from 0.98 to 0.99.. hopefully that does it. ::chris Thank you for the help…my two Alix 2C2 are now running, the problem was the same! bios update! Link to update the  bios: http://www.pcengines.ch/alix2.htm The process is simple with physdiskwrite.exe install  freedos_alixupdate_0.99.img ( inside freedos3.zip )  in a CF card, copy also the files in alixb099.zip to the CF card ( normal copy/paste under windows ) , boot the alix with this cf card ,  run sb.com and it´s donne ! Remenber...admin console parameters for hiperterminal: Freedos/ ALix  : 9600 8N1  no flow control Pfsense : 38400 8N1 no flow control the rest is going down the road... Best Regards Paulo Gomes

Thank you for the informations Hoba.

thanks RC

Have you installed squid and enabled transparent proxying?

i left my box runnig like this over night and in the morning some tunnels were up but veeeery slow after i power cycled the box everything came back up and works so far…

I've solved the problem, here is the solution : activate RAID in BIOS (F2 for my MB) create array for raid-1 with motherboard utility (ctrl+z on qwerty and ctrl+w on azerty) return in BIOS and desactivate RAID (=> "non raid") launch pfSense installation pfSense see 3 HDD : 2 in SATA and the RAID ! select the raid and all is ok ! I don't understand where raid is managed (OS or motherboard ?). I've try to create some file and unplug on disk : raid is ok (file is on both disks) no explication, just a solution… if someone can explain ?  ???

First step, upgrade to 1.2 release. Second, when it crashes, what error is produced?  It is likely that your hardware is faulty.