right.

Bridged interfaces in pfSense support STP too and as you can configure pfSync independently from carp the first solution from that doc might be doable with pfSense though you still need a fake IP for the WANs. If you test this let us know how it works.

Thanks for the feedback. This board is great! I'd like to be able to administer the firewall remotely (including updates), so I guess a hard drive version is still the easiest way to go.

Whenever FreeBSD 6.2 is released.

Thanks for the quick response. I'll test it out either this week or next.

things have changsed mutch sins then the beta's where on freebsd 6.0 the rc's and 1.0 release and 1.0.1 are on  freebsd 6.1 the snapshots you can download now are freebsd 6.2 beta

even on this version with freebsd 6.2 it still always detects sis0 or sis1 interface alot even if it doesnt exist. and on this version i get some errors when i partition and install to hdd. just trying to give some info about this version. if u all wanna know the error msg i can post it here. thought it works just fine

the CRC error is ok. But i got this error on another installation too, but after that it worked fine. So any more ideas? :)

Thanks for that I was trying to avoid having to take the firewall apart to change this box to PF guess I will have to take it to bits then

and 3)  -> OK then. Is enough for my test. tnx a lot

pfctl: DIOCSETSTATUSIF indicates a interface is present in the XML configuration but for some reason PF is not seeing the interface.  You may want to reset to factory defaults.

Did you try a biosupdate?

@Imajica: @jeroen234: setting a proxy server you do in youre internet browser Ah.  Then pfSense won't do what I need it to do… Yes, it will. What he's saying is that you just need to set the proxy option in the browser, not at the router.

I'm beginning to think Squid had something to do with it.  Since uninstalling Squid, I haven't had any lockups.  I'll report back with log excerpts if this changes.

oops! thanks for pointing that out… guess, hv to give up on this machine.  :-[

In the webgui at system>advanced.

thnx for ur help.

Freebsd doesn't like your cdrom dive/controller. Some of the messages can be ignored if it works (at one of my systems I get the read_big_illegal_requests too but it works), however your system is not able to boot up completely. Try setting your bios to pio mode for the cdrom drive (disable UDMA modes). Also see http://wiki.pfsense.com/wikka.php?wakka=BootOptions how to disable dma for atapi drives. If nothing helps try with another cdrom-drive. Oh, and next time don't shoot your image with such a high resolution  ;)