I'm not seeing that. When I click + on the Dashboard in IE on Windows 7 it doesn't do anything, that's a separate issue. Created a ticket linking here and including the + Dashboard issue. http://redmine.pfsense.org/issues/show/202

@khan: u select 1 with destination 1 with source. leave other as their default now at firewall/ rule in lan rule table delete default rule creat 1 rule as please don't delete the default rule. whenever i delet the default rule i lost access to my gui interface. you can keep your default rule, but take it to the end of the rule list. this will not interfere with your above rules. this is only my personal experience, i can't say anything as final as im also new to networking things.

@bbhoss: The web interface won't work in the latest snapshot of PfSense 2.0 Alpha-Alpha.  Whenever I go to 192.168.1.1, I get a bunch of odd characters, like this: [image: 0dhuy.png] If this is a known issue, how can I fix it?  Also, how to I upgrade to the latest snapshot over ssh/console? I can confirm this problem using 20091129 nanobsd.

@cmb: The config conversion for user manager isn't done yet so you will break your CP. Regardless of that, don't upgrade to 2.0 at this point, for any reason, in a production environment. ok, how long will it take to be done? im waiting for it :) and btw if i install 2.0 at this point and use its own cp will it work? will i be able to update my 2.0 to the next releases without re installing? thanks.

OK that is how I have set it up, allowing TCP traffic for ports such as 20000->65535 for my clients. Not very safe for a firewall :( So that should give you enough conviction that FTP over NAT support would be good to happen as well non non-NAT interfaces ;)

Ok, this problem is solveable too. When on console and you get bombed with squid-errors, you can open a shell via pressing 8 (maybe try several times till it works: Was so with my box.) then change to /usr/local/sbin and rename squid to squidx or whatever. After a reboot no more squid-errors, because its not there. I think its because of the reinstall of the packages: The binaries are not deleted, the config-files are still not available due to whatever, and you get bombed. Install all as wanted and you will be on again. Don't forget to rename or delete squid again afterwards.

You don't need to report errors with any package on pfSense 2.0 as long as it is in alpha. No package maintainer will seriously look at it.

Hello devs, confirmed fix with 2.0-AA-20091120-0004.tgz thank you very much for your effort. cheers,

Looks like it isn't loading the background image for the menu for some reason. You might try going to System > General Setup and reselect the theme as pfsense_ng.

I know it was working before, don't know if it was RC2 or older version of FreeBSD. Now its broken and I'll wait. Good things will need time! And pfSense is a very good thing! Congrats to all programmers out there

Easier and more elegant solution is linking: ln -s libx liby. Copying needs much more space! (Its like making aliases.)

if its a new install, then yes. If you upgrade, look at updates on snap-server

Follow the directions here: http://devwiki.pfsense.org/DevelopersBootStrapAndDevIso But instead of using build_iso.sh, use build_nano.sh

This problem has been fixed.

This is probably related to a kernel patch that was causing problems and has been fixed since, try a new snapshot.

Do you have a package in head? Some fail, most not.

You can open a bounty for this. Otherwise i am not sure all this list is in a priority.

I am currently testing with yesterdays snapshot and the problem seems to have been solved  :)