indeed.  You can't ping what?  from where?

@christianb: I managed to get the install on a 2.5" disk. First I put the disk into my old laptop, and swapped out the intel2200bg card for an atheros one, so there would be two interfaces. PF sense intsalled, went through everything and hit 99 option for hdd install and even allocated 1gb of swap. Then put the 2.5" disk into the soekris, and interestingly console worked enough to tell me that it could not find the original LAN interface, but let me assign a new one, from there it was GUI all the way. It definately runs quicker from a GUI point of view, even though no swap space used as yet, I shall do some testing at some point to see if on HDD it works better under load. I have seen soekris have launched a version with 256mb of embedded memory BTW. Has there been any thought to having a dual HDD and CF install? with read-only on CF, swap and storage on HDD. Basically it could be a CF install, then a script similar to the one to allocate free space on a CF card, but to HDD, and add packages in the process? Thanks again for all your help, and look forward to seeing the usb boot version That's on my list of things I'd like to work on at some point (I've got a couple Nexcom that are spinning platters that are entirely unused right now). –Bill

here is the Captive portal topic http://forum.pfsense.org/index.php?topic=490.msg3076#msg3076

You can do manual upgrades for non embedded versions. For embedded versions we provide mini update files. These however only upgrade the webgui.

Okay thanks, I'll check it out.

I have tried again just now. This time i tried it with a bios update. Its 1.05 now. And im still having trouble installing pfsense 1.0 beta to my HD. I checked the bios settings and i set IDE to manual, Mode to LBA, PIO to mode4 and disabled UMDA for the master device on IDE1 that has my toshiba 40gig HD connected to it. But i have installed pfsense ( through the Safe mode option ). After install I still have to boot pfsense in safe mode for it to run. If i let the boot loader run the default choice, pfsense will end with the messages that it cant mount the root partition. And wont start. Can keep it running in this safe mode? Are there only hardware related options 'off' or also network specific option 'off' ? Thnx for any help

Thanks for reminding me what hoba said earlier in this thread. No, I did not have a serial cable plugged up. I tried to figure out how to connect a PC monitor to the serial port  :-[ and then I remembered something I read about m0n0wall on a Soekris and a serial port, here: http://doc.m0n0.ch/quickstartsoekris/ under 3.2. Connecting to the Soekris serial console. The null modem cable that I used had only pins 2 and 3 crossed, for the rest it was different than the null modem cables described in http://www.nullmodem.com/NullModem.htm . However, with HyperTerminal under Windows XP and the following settings, 2400 bits per second, 8 data bits, parity none, stop bits 1 and flow control hardware, I got some garbled output in the HyperTerminal window. Then I changed to the speed to 19200 bps, still garbled output.  Finally I found here http://www.fozzee.net/wrap/ that the default speed in m0n0wall is 9600 bps.  When I entered that in HyperTerminal for the serial connection to the router, I finally got the non-garbled boot messages in the HyperTerminal window. pfSense rocks. Thanks for making it. I like the traffic shaper very much.

We shouldn't be vulnerable to this anyway as PF loads and will match first before ipfw.  PF will drop or otherwise scrub the ICMP before ipfw ever sees it. –Bill

@RDS_Correia: What do you want to predicate? I REALLY know that these PRE…XXX-images aren't official Updates, nevertheless I'm interested in testing particular improvements as soon, as I can get them. And there are other users too, using these Images. So I think, it's ok to inform in this forum about running into problems with these images. Don't you think so? I haven't posted to blame Scott, or any of the developers.

Alpha builds were labeled 0.xx Beta builds are 1.0betaX (for example for beta versions of 1.0) The files from the link I posted are more or less preview snapshots of the upcoming 1.0beta2. I can recommend using these as they solve some ftp issues and have several other bugfixes. Stability in my experience is no issue since around the 0.8x alphas and these were mostly freebsd related.

this thing blows my head off, it seams to me that the module or its configuration is not operational…. because it looks like the NAT part does the "bridging" instead....  I didnt use monowall, but do they have operational bridge function? caz i dont really want to dig in this for now... i just need to get my device to operate the way i need it ... and than do any improovements to the OS

I just wanted to say thanks for the info. I made the changes from auto to LBA and unchecked packet mode and the system works great. Thanks

@cmb: Yeah but unless you have a few thousand machines, there's no way you'll ever exceed 100 Mb in that scenario. or a few large cache files.  ;)

You have a 4801, why not put in a laptop hard drive and run a normal install from that?  I believe that should work. Much faster than any USB 1.1 device too.

Negatif. Going 'back' to M0n0wall 1.21 (new release) enables this option (with some config.xml pathing). But, anyway, in this case the ADSL device isn't a router, just a PPPOE bridge between phoneline and WAN network card, so I gave up the 'want to have' idear of having telnet/web access to this device. There isn't mutch to administer anyway. I have a final choice of putting this modem in Router mode (my ISP doesn't bother) and give pfSense a static/fixed 'internal' IP on his WAN interface (or even use client DHCP for that mather) - this will mean that all firewall rules concerning WAN & outside NAT have to be duplicated in the modem/router - this means access is possible, and very very needed. To make things short : don't need a gun if there are no rabbits to kill anyway  :D

The basic file structure is very FreeBSDish.  Expect to find files where they should normally live on a FreeBSD server.  For instances, almost all FreeBSD packages install their configuration files to /usr/local/etc so if you're curious about how squid is configured you can look at /usr/local/etc/squid.conf and in there you'll find the cache_dir directive specifying where the squid cache is kept.  You might reconsider using WinSCP (which is primarily used for transfering programs) and instead go with a full ssh client (like putty or SecureCRT) so that you can use very useful shell commands like find.