jimp, you are genius ;) I tried to download /usr/local/www/javascript/index/sajax.js and I got the file. Than I executed a shell command "rm /usr/local/www/javascript/index/sajax.js ", cleared browser cache and voila, it is working now :) Thank you all! [image: Untitled-2.jpg] [image: Untitled-2.jpg_thumb]

Upon closer inspection and some more googling, I found that it does in fact correspond with the times the internet goes out, but only when it shows: Oct 13 10:15:30 check_reload_status: reloading filter Oct 13 10:15:19 apinger: alarm canceled: 75.151.13.201(75.151.13.201) *** down *** Oct 13 10:15:16 apinger: ALARM: 75.151.13.201(75.151.13.201) *** down *** as opposed to: Oct 13 09:06:11 check_reload_status: reloading filter Oct 13 09:06:01 apinger: alarm canceled: 75.x.x.201(75.x.x.201) *** delay *** Oct 13 09:06:01 apinger: alarm canceled: 75.x.x.206(75.x.x.206) *** delay *** It makes sense now, and now I feel dumb for not seeing it before. I also now realize that apinger (http://freshmeat.net/projects/apinger/) is just the thing that tells me it was down. How do I figure out what is causing it to go down though? The IPs its showing are the external IPs from my ISP..

Perhaps its time to upgrade to pfSense 2.0 - see http://forum.pfsense.org/index.php/topic,24337.0.html

I did get it working :D One big problem though. Upstream was reduced to 4Mbit with Zyxel from 10 Mbit with Thomson.

When you need to update many interface settings or virtual ips, the best and fast way is to manualy edit XML. To apply changes, restore backup with this XML or copy it to pfsense and reboot.

Thats the way pfSense works. Change the configuration through the web GUI. Don't mess with the application configuration files.

after i installed 2.0 Final i was going to WAN interface and choose L2TP and nothing happens.  it doesnt dial  > i watched the logs.

I had the same problem today after a manual update to JIMPs i386-20110929-1702.tgz I used Putty to get access into the console and ee to apply the fix above. Thanks to those who took the time to debug this and save me lots of time.

Reboot the pfsense box, I had this same issue. If you change the timezone I think you are supposed to reboot to make everything jive.

I SOLVE IT !!!! It was my mistake. The upgrade was not the problem. I used remote access with auth and the company asked me not to use auth but only certificate. So by mistake instead of choose remote access (without auth) I choosed peer to peer !!!! Changing it back to remote access the client export utility works fine again. But I wonder why openvpn server worked with peer to peer….  ??? Finally everything is OK now ! :)

Figured out what was wrong. Active Directory was setup only for Native 2000, and was not allowing me to select the option of "Control access through Remote Access Policy" Once I upgraded the domain to a 2003 domain, the option became available and I was able to use the IAS policies to control access. Cheers.

I finally knew the problem. I tried changing my domain name in System>General Setup. But when I checked with my PC and the scanner machine, the domain name was the previous domain. I did an ipconfig/flushdns, restarted the NIC of my PC but still the same. So I checked with the DHCP server, under Domain name, I specified my previous domain name. Even if I change the domain name, I always get my previous domain. I empty the box under Domain name, did a flushdns and restarted the scanner and everything is now ok. I still don't get it how that option affected my LAN. Anyway, thanks to all especially WALLYBOB for helping me with this.

May i make assumption. DHCP was serving .1 address as gateway and pfsense were .2?

Yeah, that's what I'm afraid. I might just use squid or varnish instead.  (I'm looking for a very lightweight HTTP CONNECT capable proxy server and tinyproxy sounded perfect but I don't want to break pfSense and tinyproxy has a ton of dependencies…)

Here are the commits and bug fixes: http://redmine.pfsense.org/projects/pfsense/roadmap This should help you find what you are looking for.

@Nachtfalke: whitlist allows the traffic always even if there is another rule with higher priority which blocks traffic. Whitlist: allows always allow: allows only if there is no other rule which blocks. Hope this makes it a little bit clearer !? wow! perfect man! Thank you so much!

Excellent, thanks guys.. its all working nicely.  Just wish i could get my public IP block forwarded so easily!! lol

I think not working on Chrome should be cause enough to call it a bug; Let alone the big base of clients that IE has. Anyhow, not trying to make this a philosophical issue but I think it can qualify as a bug if it ONLY works in Firefox. I can't test it on Firefox as I don't have it. I can also live with the bug as it's doesn't effect the functions but it's an aesthetic issue.