I came back to this a few hours later and the browser was still showing the disk heads moving. I did a browser reload and it finally went away. 1. it seems u need to reload the page 2. it also seems to take a long time might be better to have a % indicator as well

@jimp: If it's using UDP, you may want to go to Firewall > Advanced and set the firewall optimization to "conservative" which should keep states longer. A very belated thank you, it worked like a charm. For those (like me) who have to hunt around in the menus, the exact path is : System > Advanced. Select the "Firewall/NAT" tab and modify "Firewall Optimization Options".

Just tested yesterdays svn build of 2.0RC1 to see if PPPoE is finally working and it is still not…. :S 1. Interfaces -> assign -> PPP's -> edit interface which is from 1.2.3 NO INTERFACES ARE SELECTABLE - until I re-select PPPoE AGAIN in the drop down list. Why does WAN and LAN appear there? thats not a physical interface. :S But even then, PPPoE is not working: System log reports this when trying to connect: May 5 22:02:20 - php: : Could not find gateway for interface(wan).

Go to System: Routing: Gateways and add an entry for the IP address of the remote router that your are connected to via OPT3. Do not check the default gateway box. Save. Now go to System: Routing: Static Routes and add a route. Destination network is 192.168.4.0/24 (or whatever mask the fileserver uses) and the gateway is that you just created. Save. If you did it right then pfsense now knows that any packet destined for the 192.168.4.0/24 subnet needs to be routed through the 10.0.0.x router at the other end of your wireless link. Note that the router on the other end of the wireless link must also similarly have a route back to the networks connected to pfsense, using 10.0.0.253 as the gateway, unless you're using advanced outbound NAT to NAT everything out of OPT3, in which case the fileserver just thinks it's talking to 10.0.0.253, which the remote router already know how to find. If the remote network (192.168.4.0/24)'s router (10.0.0.x) is using pfsense as it's default gateway then you can disregard the last paragraph, as it will route all non-local traffic to pfsense anyway.

Stange….I deleted all files and directories in /tmp/ and reinstalled squid and no more problems in system log. I will come back if the problem returns and post the hopefully necessary files. Nevertheless - thanks

possibly I didn't wait enough. see other post for more info.

Not sure why at the moment, except for a general lack of time.

Oh I'm running 2.0-RC1 (i386) built on Mon Apr 25 20:52:49 EDT 2011 Thanks

I didn't fix it. Ermal did… Update to the lastest snapshot and give it try

Reinstall the package in about 5 minutes, the syntax error should be fixed.

Time zone setting are only fully applied after a reboot. Select the Denver time zone, reboot the router, and everything should be good again.

@cmb: Your config is correct. Probably one of 2 through 5 here, though check them all (short of 1 and 6 which aren't the case). http://doc.pfsense.org/index.php/Port_Forward_Troubleshooting Thank you, cmb. I finally got it work! The problem I had was "3. Client machine is not using pfSense as its default gateway." I changed the gateway on the server (which has sshd which I want access to) to my testing pfSense box and it works right away.

@AllenN: Unit boots and allows initial setup via console cable.  WebGUI is then active. Once this is complete, I can no longer access anything on the console cable/port.  The unit outputs info to screen via console until boot is complete then no more information is output and no access is available.  In 1.2.3 the console cable was the way you reset passwords, etc in case of lockout. I have the same problem. I searched around in the forum and tried to change the speed (of PuTTY) from 9600 to 115200 according to another  thread, changed from no flow control to XON/XOFF to DSR/DTR to RTS/CTS - nothing works. I also tried some of the latest pfSense Snapshots. But it's always the same behaviour. Any ideas what I could do? Thanks and kind regards

@MageMinds: Okay, reviving an old thread, but here is THE solution for torrents. You need to create a virtual ip address for your network interface where you use your torrent software. Then is your torrent software you go in advanced configuration and you find every "ip binding" settings and you put your new virtual ip address in and restart your software. In uTorrent there are two settings to change, I can't remember which one though. Then you shape this IP address completely without ports or anything. uTorrent will not use your listening port to connect to other peers, so those outgoing connections aren't shaped. Using my method everything uTorrent does is being shapped, even tracker scraping… I found this post because I was looking to learn how to make l7 working, I want to shape ftp and it needs a l7 to be shaped correctly because of passive servers. I want to shape my hosts connecting to remote passive ftp servers. MageMinds I understand how to use Multi-home for uTorrent but in my case, I'm looking at software where I have no control over like some online video streaming software that uses P2P technologies.

Well, I finally found what the problem was! I use LDAP authentication, and I had my DC configured by FQDN. For some reason the name could not be resolved (while, in fact, it resolves just fine via the console), and the lag with the lookups to the non-resolvable address eventually made the machine unmanageable via web. I sinply configured the DC by IP by editing the config file and rebooting. The interface is now snappy as they come!

That did it. Thanks!