What we need is forcing interfaces to some default IP's so we can get acess to it via wireless, that's the main problem, or at least to force LAN, and skip other interfaces (DHCP) so the system would be acessible via LAN. Anyway… yup, it's not a worthy feature, maybe with some bonty? ;)

@hsiang: I had uninstall the squid package and install the new beta 2.6.5_1-p15 but the same error still happened. any way to stop and squid the service properly? system stopped Executing rc.d items     Stopping /usr/local/etc/rc.d/proxy_monitor.sh…... This question has been asked atleast 15 times now.  Update to the latest snapshot from: http://snapshots.pfsense.com/FreeBSD6/RELENG_1/

unfortunately the spare machine is going to be the NAS server. I could just use a switch etc. anyway which Mini-pci card is recommended? I need one which can do b/g and WPA2.

Finding 128MB cards is difficult. hardly anyone stocks them.

No, only ethernet type interfaces are supported.

The last time I installed a different operating system on a IP330 I had to manually assign the hardware addresses to each interface. It's been about year, but I also had to manually redirect all output to serial.

Please see http://www.mail-archive.com/support@pfsense.com/msg08382.html

Thanks for the posts.  DS3=45 mb we have two servicing the site.  Now it is a manual fail-over by switching cables.

The current squid version p8 supports rudimentary blacklisting and whitelisting.

My only problem I guess is, I dont have a netopia modem/router.  I have a speedstream 5360.  Is it possible with this modem?

i fonud it in the Diagnostics>Route Diagnostics: Routing tables Name resolution  Enable Enable this to attempt to resolve names when displaying the tables. Note: By enabling name resolution, the query should take a bit longer. You can stop it at any time by clicking the Stop button in your browser. IPv4 Destination Gateway Flags Refs Use Mtu Netif Expire default 218.10.111.185 UGS 0 2 1500 fxp0  127.0.0.1 127.0.0.1 UH 0 0 16384 lo0  192.168.0 link#2 UC 0 0 1500 fxp1  192.168.0.86 00:0d:87:bd:8e:f1 UHLW 1 193 1500 fxp1 1140 it shows the gateway was correct. i halt the pfsense yesterday. and after i press the bottom to open it this morning , it works.

nice tutorial

What does status>interfaces report? Can you ping your WAN gateway from diagnostics>ping? Do your Clients at LAN have the correct gatewaysetting? If you traceroute from a Client to an adress at WAN where does it stop? Is DNS working properly? Maybe you have just Nameresolution issues?

I am currently having this problem on a non embedded image of PFsense, this is the second time this has happened to me. It's not a big deal to reflash except that I loose my config everytime I do so… I'm not sure why it is happening, I think it does have something to do with a hard shutdown because this time it happened after the power went out.

Executive Summary * If you intend to hang it of a radio mast somewhere out there or for a bussines use the embedded install. If this is a box in the cupboard or celar, do a hd install to CF. and buy a 256MB or larger CF and not create a swap partition. Detail * Yes you can do a normal HD install onto a CF card which is in a IDE-CF converter. This means the filesystem is mounted RW normally. So if you reset the box it will perform a fsck on the volume. If you create no SWAP and you have 128+ MB ram this should work fine. I run my testbox this way and the Kingston ValueLine 512MB CF card has not failed yet. It's been a year. When the CF card will start failing I cannot say as most modern cards have a defect recovery mechanism that is so good that by the time we notice disk errors we can pretty much confirm it is shot. When you use a CF install the filesystem is normally mounted read-only and is mounted rw only for config actions or firmware upgrades. Yes you can replace binaries on a embedded system by mounting the CF rw by using /etc/rc.conf_mount_rw. All the variable data that is created in /var or /tmp is on a memory fs. The rest is all read-only. The rrd data is saved to a TGZ file on the config partition of the CF and restored on each reboot. That said, memory cards these days are pretty good, and so cheap that replacing them is easy. A recent test by the magazine c`t tried to break a USB memory stick but it still did not fail after 40 million write actions. If that is anything to go by it is unlikely to fail in our lifetime.

This problem was solved by enabling the only available power related option in the dell bios. Flash forward a couple of months… building another pfsense system on new dell hardware, same problem, but now the bios doesnt have ANY power related options to change and I dont see a workaround. Not sure what I'll do. If I figure it out I'll follow up.

I'm using a rt2500 pci without problems. Normal power supply.

Yeah must be a BSD issue.

I'm seeing the same thing with an external USB CD/DVD drive (Philips USB 2.0 SPD3100CC, 16X DVD +/- RW). FreeBSD 6.2-RC1 acts the same way, so it's not a pfsense issue. There is a FreeBSD PR related to this, kern/85257.  http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/85257 Hopefully it'll get fixed in FreeBSD eventually…

I found the problem or at least an easy work around. If I make fxp0 the WAN and fxp1 the LAN. The pfsense automatically assigns the default gateway to the WAN (fxp0). It strikes me that this isn't all that intuitive. I think one of these options (or something similar) should be done: Modify the setup pages so they recommend you use fxp0 for the WAN instead of fxp1. Modify the rc.interfaces_* scripts so that they set explicitly set the interface when running ifconfig for the default gateway to the interface of the WAN. Modify the UI and the rc.interfaces scripts to explicitly specify the interface for the default gateway.