@Klaws: I prefer regular APs instead of built-in WiFi cards. No driver issues, no need to buy outdated hardware. And you gain the flexibility to put the pfSense box at a convinient location while the AP goes to the optimum position for RF coverage. I agree with those listed advantages for external APs but I have found the pfSense reporting and troubleshooting facilities far superior to those on any commodity AP that I have encountered.

You can just copy the last good config from /cf/conf/backups/ to /cf/conf/config.xml and reboot.

I tried the WiFi option in pfSense as well and I had to give up at the end (I posted about it in the wireless section). I came to the conclusion that the hardware that works well with FreeBSD 8.3 in AP mode is very limited and hard to find at best. I could spend hours trying to find the right ath based card on ebay or just spend $90 for a proper AP and be done with it.

Okay thanks so much. Luke K.

well guess i will have to use a normal pc for my setup. Thanks alot for the great helpful and informative andvise

Ah, sorry, I misunderstood your first post - I thought the issue was related to a "new version installed".

You can add external batteries to most UPS boxes with a bit of effort too. Pick one that is about double your power use so it is running in the most efficient range and get a reasonable runtime in the basic box. Add as much external battery as you like, recharge will take a long time but otherwise all will be just fine. I really like AGM (absorbed glass mat) batteries for inside use, no chance of acid fumes or spillage unless you horribly abuse them.

Hi Guys I've been experiencing something similar, though I'm not sure if it is the same.  My post is here: http://forum.pfsense.org/index.php/topic,59546.0.html Essentially what's happening is something is triggering my interfaces to kick out, and only a reboot of either the DSL modem or firewall bring them back.  I do see the WAN gateway alarm where is cannot reach it, but that could be the chicken or the egg - did it go down because the interface died or did it go down first and then the firewall could not recover.  I have DSL/pppoe. -Lou

Does the Services menu have a Bandwidthd entry? If so, then your system has had the actual Bandwidthd package installed at some point, but an upgrade (or something) has somehow lost it from the installed packages list. In that case, from System->Packages you can install Bandwidthd, then uninstall it again. That will get rid of the menu entry, and the program. Otherwise, post the output of pkg_info command. (You can then probably use pkg_delete to get rid of bandwidthd, but there might be other bits that could also be removed, and there might be other things installed or customised on your system?)

@stan-qaz: Man page: http://www.freebsd.org/cgi/man.cgi?query=kill&sektion=1 Start with just kill and your process (from your other post) id:  kill 5018 Add options if that doesn't work, -9 or -15 kill -9 5018  or kill -15 5018 It worked :) thank you very much sir.

Thanks for the reply jimp. I am running a firewall sizing work, new servers etc and for that reason I would like to know how many new connections are created in the firewall per second. So, I will consider the state table, insert option to calculate my new connections per second. Thank you,

We are still tracking down and updating things as we find them, announcements went out to the development and committers lists already.

This is awesome… thanks Phil!  (I'm the guy who initially pointed out the annoying no-ip behavior) but hey it's free, right?  Oh wait a second... pfSense is free too but there's no annoying behavior.  :) IIRC, the cron job in pfSense does these updates at 1:00am or so.  If that is indeed the case then it's very unlikely to adversely impact anyone. As for alternatives, I've found FreeDNS to be quite useful.  DNS-O-Matic does look interesting and since it's an OpenDNS service, I would expect that there's almost no chance of this sort of "monkey business" cropping up in the future. Thanks again, Phil

That should be fine for the OS, assuming your hardware is capable of using those effectively. We have people running with hundreds of VLAN interfaces or other virtual interfaces and it's OK that way, the only question there is your hardware.

Chrome is nice it just caches too aggressively. You didn't need to reinstall chrome, just empty the cache and/or force a reload of the page (hold shift + click refresh button)

nobody has an idea?

I forward (WAN side) port 80 to port server 1 port 80 (LAN side). Port 81 goes to server 2, port 80. Port 82 goes to server 3, port 80. Port 443 goes to server 4, port 443. I access all other boxes via an IPSec VPN.

Ashish, I fixed bandwidthd so it should run OK on nanobsd Alix systems. Did you install the latest version 2.0.1.4? and it takes a few minutes to make the first graphs. Edit: You were still on 2.0.1.3. I updated bandwidthd and set the parameters back to the defaults (it will update usage every 2.5 minutes) plus selected output_cdf and recover_cdf so it will reload everything when bandwidthd restarts. Note: At the moment on nanoBSD the bandwidthd cdf data files are not saved anywhere - they are lost on reboot. Tonight I will try and add the code to save the data periodically to the CF card.

Edit: Oh, I'm sorry, you mean Monitor IP. No, all different on all interfaces (2 WAN, 2 VPN). But both VPNs have the same gateway IP.