Thanks,  I will start to search for AP's that allow "Allow intra-BSS communication" to be disabled.

You should run the single processor kernel. Embedded disables some things (like DMA) which you do not normally want to disable on a full PC, but typically have to be disabled for things to work on embedded hardware.

There is no measurable performance difference between any of the kernels. They all have largely the same options.

Not likely that anything has changed since earlier this year, I wouldn't recommend trying.

You need to do a full install to the CF like you would a HD. The logs still aren't just going to pile up forever though, they're still rotated long before they get anywhere near 100 MB. If you want to do a full install to just keep more logs locally, that's not going to achieve what you desire.

No, the documentation is outdated. Use 1.2RC2.

@Master:

Any particular thread in mind? I already searched the forums, but I could not find anything relevant concerning a recent (FreeBSD 6.2 based) USB installation. I know, that booting something from USB has always been kind of problematic, and I never played around with it (mainly due to the lack of a large enough USB media), but I assume it should be possible somehow.

Many, but basically it comes down to the fact that consumer grade flash memory (which includes CF cards and USB disks) will "burn out" with a sustained write load.  The embedded install is designed with this in mind, but the full install isn't and writes merrily to the disk.

@Master:

Still a good question, because I have no clue, what a full installation needs "2 GB hard drive or larger" for. I am actually running a full installation on a machine with a 18 GB softraid-1, and this is what the discs are used for:

<–-SNIP--->
So even with some packages installed, we are far away from the specified minimum hardware requirement for harddrive size.

Is it possible, that embedded & full installation just have the same memory requirements nowadays?

The embedded install is a fixed size - no packages.  The full install is a variable size that depends on the packages you install and the size of the logs.  I suspect 2 GB was picked as a reasonable upper limit on what people would require.  My 4 GB microdrive (of which only 3.2 GB is usable) currently has about 0.5 GB used.  By this point a 1 GB unit would be looking a little too small for my liking.

There's a problem right now with an apparent bug in Lighttpd where it chews up a bunch of memory and dies during upgrades. If you run into this, the console upgrade will still work fine. I actually like console upgrade better because you can just paste the URL in and it downloads and upgrades automatically.

Well - you don't want to run two devices with the same IP/Netmask so what you need to do is bring up the system without connecting the lan side to the network where the 192.168.1.1 router is - then use the "Set LAN IP Address" selection ( selection 2 ) and set the IP address to something that is not assigned on the 192.168.1.0/24 network - set the netmask to 24 and save the settings - then you can connect the lan interface to the 192.168.1.0/24 network and access the pfSense server using http://{the IP address you assigned to the lan interface here} (without the {}) and you should get a login page.

Make sense???

gm…

did you change the webgui of pfSense to another port?

Impossible for us to help without posting system logs.

Not off hand at the moment but this may be possible soon. I'll repost here if I ever swap the box out.

ARP cache induced problems are very common when switching firewalls, power cycle the router upstream of your firewall if you have access to it, and also any DSL or cable modems, if applicable. You may be forced to call your ISP, or wait a few hours for the ARP cache to clear.

It's standard port 80 HTTP traffic.

It's not possible to use a proxy at this time, it's on our wishlist so hopefully it'll get implemented at some point.

Well, I got my IP back at least tonight. And the box is bootstrapping as I write - it's probably going to take a while. I don't think that poor old P-II 400 mhz cpu is really up to the task in a speedy manner, or so to speak.

I think perhaps the HD was in a bad shape, because I couldn't get the machine to start the bootstrapping .. I swapped out the HD with another one, and off it went. So, obviously I am on a 1.2 router right now. Let's hope the connection stays up. I probably won't fiddle around with the traffic shaper this time, since that was when my problems started the last time I was on a 1.2 system… Hopefully I can use Project Evil and get the WLAN card up and running as well, following the guide I posted a link to above.

Oh, and obviously I didn't consider the fact that the bootstrap process would also update the software of the router ... So sorry for my confusion about the BETA-1 developer image. ;)

Use the embedded image and write it to the cf.
You know how to do that from m0n0wall already.

If you are keen on the latest test build for 1.2 use this image:
http://snapshots.pfsense.com/FreeBSD6/RELENG_1_2/embedded/

Here

http://snapshots.pfsense.com/FreeBSD6/RELENG_1_2/