Does a firewall rule block (and log) your ping attempt? See firewall log in web GUI: Status -> System logs, click on Firewall tab. On my pfSense box I get responses when I ping the IP address of the LAN interface and the IP address of the WAN interface.

You can install the backup package to make a backup of /var/db/rrd/ and then restore it on the 2.0 box. If I remember right, it should upgrade the rrd files if it finds them in the old format.

If that works you'll probably want to then change your firewall rule as you'll then have it setup to allow access from DMZ to LAN, probably not something you want. For example I have attched my rules on my wifi interface. I want to allow wireless clients access to internet. To do that I allow access the local dns forwarder. I also allow access to the pfSense gui for my convenience. My last rule allows access to anywhere except the IP alias LOCAL which is 192.168... Pretty much everything I have taked about earlier in this thread is more eloquently explained here. Steve [image: pffw1.jpg] [image: pffw1.jpg_thumb]

Brazilian, my apologies for mistaking you for Italian.  :-[ Have a look [url=http://forum.pfsense.org/index.php/board,12.0.html]here. Steve

@torontob: 1- If I am not wrong there is an snmp package on pfsense but I have never worked with snmp. I am exploring Cacti now. So, would cacti try to connect to snmpd or does snmpd connect to cacti and give it the information? (I want to know for security reason so I know which ports need to be opened or not) SNMP is built-in, Services > SNMP. Just enable it and the modules listed on the screen. Cacti would connect to the pfSense box via snmp and gather the info. A standard unix host template in Cacti should get the right info, if I remember right. You'd just need to allow udp/161 from the box running Cacti to the router. @torontob: 2- Would using syslog to send logs over the internet and the snmp logs use a lot of my bandwidth or otherwise stress the router if I am planning to log everything? It wouldn't use a ton of bandwidth in most cases really, but I wouldn't do either of those in the clear across a WAN link. If you must do that to a remote box, setup a VPN for it.

You might try a 2.0 snapshot. If the CD has issues, try the memstick image and boot from USB.

For folks hitting this old thread from Google, read this sticky post instead: http://forum.pfsense.org/index.php/topic,28264.0.html

I updated the page to reflect the current size limit. It's not possible or practical to use anything less than 512MB, and even then that's a stretch. Given how cheap CF media is, even for 4GB cards, there's no reason to cling to (probably old) small CF cards. Newegg has 4GB cards for $12-20. Well worth the price.

I was thinking that the command line did not auto detect the nic as up in command line setup portion. but once in GUI mode I was able to assign ip with out issue.

We successfully 'mode switched' a Novatel 3g modem in another thread by simply 'ejecting' the virtual cd-rom. Unfortunately the cdcontrol command is not included in pfSense by default to you need to copy it across from a FreeBSD install. This probably won't work for a lot of modems but it's worth a try as it's easy. Steve

That is by design. When you do an upgrade, the slice not currently in use is upgraded, and then you switch to it. If the upgrade fails, you go back to the first slice.

i solved it now. i installed the newest bios, and did an reinstall of pfsense. and now it works. :) i had to do an reinstall, otherwise pfsense wouldnt start…