@NKRA: @marcelloc: go to firewall -> virtual ips. then add 'ip alias' Hi, Would it be possible to setup the following 10.1.1.1/24  (LAN) 192.168.1.1/24 (LAN) Both IP block run on on LAN port (no VLAN) with no routing between the two and also DHCP for both IP blocks.  BTW, only have one WAN port with one public IP. Regards While you can have both subnets on a single interface, you can not have a DHCP for both ranges. Only one rsnge per interface. How would the server know out of which pool it would have to assign if 2 were available?

Not yet, no. Not that I'm aware of (yet) It's on the list of things to enhance for 2.1.

You haven't nearly outgrown the project if you're replacing with a 5510, only time that's remotely feasible is if you're at the point where you need a 5580. There is nothing on pfSense that can affect VTP in any way.

The admin user in the GUI is also the root user in the shell (as well as the admin user there) To change the root password, you must change the admin password in the GUI, and root will follow. The password is synchronized to the OS from the config.xml version at bootup, so any changes you make in the shell alone will not survive a reboot.

Running the MySQL client isn't as dangerous as the server, so it's not too bad there. That said, you'd have to compile php52-mysql, which can be done using a pfSense builder setup (check the doc wiki), and then copy the files over to the firewall.

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.