/usr/local/www/themes/pfsense_ng/ @millimetrix: Hi Supermule Do you know where the CSS file/content is stored ?  I  want to change the "menu width" to something larger. I tried to make some live modifications with    firebug / chromium inspector    with no luck. The left-align variable doesn't solve this, Maybe adding a 'margin' left…. I'm so bad at CSS and I don't know which parameter changes that menu box's width. Comparing  the_wall  and  code-red  themes (they both looks very similar) didn't helped me either.

There was no time to spend on developing a "secure" solution. There is no way to make that work without major coding or backporting the 2.2 version, it was the most prudent course of action. On 2.2 you click one IP and it only resolves that one IP to its corresponding hostname, it just happens to replace it everywhere it's found on the page. It doesn't do a mass lookup, it's still single, but it's handled via AJAX/JS. If someone wants to code a JS/AJAX version that does a domTT or similar style "pop up" with more detail (that isn't an alert or a separate window), feel free to submit a pull request.

So….  I wonder if wiping the drive would help (-;

Will move it.  Thanks.

I just had something happen after an upgrade to 2.1.5 and subsequent configuration of a traffic shaping that resulted in a bad set of rules.  This made all my WAN ports wide open as if there was no firewall running.  No NAT or anything from LAN. What is the result of pfctl -vf /tmp/rules.debug Does it error out or complete normally? If you enter the following: pfctl -vf /tmp/rules.debug …rules output... echo $? you should see a zero.

There is xdebug, but few if any of us actually use it.

@rballester: Question: What i can do?? I suggest reading more carefully  :P (As pointed out, the copy/paste shows "alpha lima charlie zero"                                     and you've typed "alpha charlie lima zero")

Well the fault documented in this thread has been fixed so it's not that. The Alix can struggle with memory during upgrades. Are you running packages? Lots of interfaces? What CF size? Did it just fail to upgrade or crash out somehow? Anything in the logs, particularly the NanoBSD upgrade log in Diagnostics: NanoBSD:? Steve

The same effect is happening on a 2.2 development system also. I get the effect with 2.1.5 and 2.2 and Firefox browser (so it isn't just a specific browser thing). Can't immediately see an obvious change that caused this.

Thanks

That's not something you run at the command line. You have to add the line: ahci_load="YES" to the file  /boot/loader.conf.local You can do the using the webgui in Diagnosics: Edit File: or from the command line using the built in ee editor (or vi if you're a masochist!). Steve

I have seen routes for DynDNS go down that way.  I have also seen OpenNIC DNS do the same.  Also, its not unusual that ISPs try to block any DNS other than their own.  At any rate - See.  Not necessarily Pfsense (-; Glad its sorted out.

ath9k is a Linux driver and pfSense is not Linux. The uath(4) driver is already in the kernel but doesn't support that chipset. Steve

Nope.  I don't mean anything.  Stick with it.  To each his own.

@dlogan: I have pfSense embedded on a 4 GB flash card, it's actually a PFW201 from Tranquilnet.  I upgraded from 1.2.3 to 2.0.5 yesterday.  Snort installed.  Then I go to Services -> Snort and when I click to add an interface I get the following page: Fatal error: Call to undefined function snort_generate_id() in /usr/local/www/snort/snort_interfaces_edit.php on line 68 Ugh!  Another Nano install… :'( OK, I'm not completely hostile to Nano installs, but it seems there are frequently a number of problems with packages on these systems.  This error means that either you do not have a snort.inc file on the partition, or it is an exceedingly old one.  Since you didn't post with all the other errors I would expect if the file was completetly missing, I'm thinking your partition has one that is very, very old. Try removing the Snort package, rebooting, then installing it again.  If that doesn't work, you will need to put your system partition in read/write mode, and then go find the file /usr/local/pkg/snort/snort.inc and delete it.  Then try the install again. Bill

Thank you. Wi-Fi network seems to be working and WPA2 password authentication working. See how it goes with some other mobiles when visitors test it during the week.

It shouldn't be an issue. It's fixed now and I upgraded my box using the auto button no problem. The real lesson here might be to hold back a day or so and let someone else take the hit! Of course if your box is at hand, as mine was, then taking that hit so that someone else doesn't have to fly across the country to fix theirs is a good thing.  :) Steve