@Ns7: the driver does not find AR 8151. Please post the pfSense build ID (from the Version field of the home page of your pfSense box) and the output of the pfSense shell commands:``` dmesg ; pciconf -l

Thanks for your answers It's clear for me now)

One way (wich may/may not be acceptable) is to build a virtualization host with support for your nics and then put the Pfsense box as a VM on that server.

The problem is you can't have an alias name that's the same as an interface name. You had both an interface "DMZ" and an alias "DMZ" and can't have both. Input validation prevents that from happening on 2.x versions, but there was no such restriction on old versions.

Yes, it can run live just like the CD. It is the CD. Just in a memstick format.

@ssm14293: I have downloaded pfsense Which pfSense build? (The name of the file you downloaded will provide that). @ssm14293: installed it and and set up my WAN interface, but it never asked me for LAN interface. Perhaps you have only one interface recognised by pfSense. (A pfSense 2.1 build will support more interfaces than a 2.0.x build.) @ssm14293: The WAN interface is not getting any ip from DHCP. What is the WAN interface connected to? Perhaps pfSense needs to talk PPPoE to that device! Perhaps the physical connection is broken. Perhaps … Please post the output of pfSense shell commands``` /etc/rc.banner ifconfig Since you don't seem to have network access to the box you probably can't capture the output in a browser window or terminal window. If you can't, please post photos of the monitor showing the appropriate command and system response, one command per photo. JPEG files can be attached to a post by clicking on the Additional Options below the editing window for the post.

You really couldn't find any 2GB or 4GB cards? They are easily available here in the UK. By not using one of the images you are not getting any of the benefits of nanobsd. Steve

You don't want the ISO (LiveCD) You want one of the embedded installs - an .img Specifically, for a 4G card: pfSense-2.0.2-RELEASE-4g-amd64-nanobsd.img.gz <edit>or pfSense-2.0.2-RELEASE-4g-amd64-nanobsd_vga.img.gz if you prefer a screen to a serial port for 30 seconds worth of setup. http://www.pfsense.org/index.php?option=com_content&task=view&id=43&Itemid=44</edit>

Did you burn the file pfSense-LiveCD-2.0.2-RELEASE-amd64.iso.gz to the CD (wrong) or did you gunzip that file first then burn it as a disk image (not a file) to the CD?

Well its unfortunate that I did not get any suggestions on this thread. I am posting this for closure of this threads purposes. What I ended up doing is used another mini pc which was intel Atom based, pfsense 2.0.2 installation was fine as intended, setting up vlans was a bit of challenge(because of my lack of networking knowledge). At the end with a friends suggestion, I was able to create vlans and use them with singl NIC settings. I used netgear GS108e switch.

Thanks for you help pfSense 2.1 solved the problems :)

I have VLAN isolated VAP's working in Atheros DD-WRT. Never could get them working in Broadcom DD-WRT. I strongly recommend just buying an AP made for this. Right now, I'm recommending the EnGenius EAP-600.

@stephenw10: Edit: Some Googling has shown that the Cyrix M2 333 actually ran at 250MHz! 333 was just a rating relative to a P100. Yeah, I had the earlier P150+ that was rated to run at 120MHz.  It was so unstable at that speed, however, that we ended up clocking them down to 90MHz.  I ended up with 2 of them, back then.  They were pretty worthless for much of anything desktop related, but once they were clocked down they were perfectly stable.  They became a pair of DNS servers for our super-small colo we built back then.

finally got server to show green on zabbix agent & snmp on status. Below are my configs pfsense zabbix_agentd.conf –-------------------------- LogFile=/tmp/zabbix_agentd.log Server=192.168.56.101 Hostname=router zabbix server Server=localhost,zabbix Hostname=Zabbix Server StartAgents=5 DebugLevel=3 PidFile=/var/run/zabbix-agent/zabbix_agentd.pid LogFile=/var/log/zabbix-agent/zabbix_agentd.log Timeout=3 note: -i'm connecting trough IP, hence Hostname are based on host setting at zabbix interface -i add entry on /etc/hosts for zabbix hostname of zabbix server -templates used on pfsense host Template_SNMPv2_Device & Template_pfSense

em1 is your LAN interface, yes? It has an IP of 10.1.10.1/24 which is inside the RFC1918 private IPv4 address space. Hence if you have 'block private networks' checked pfSense will block packets initiating connections coming from the LAN subnet. You are not opening anything to attack by unchecking these on your LAN interface. By unchecking these on WAN you are no longer specifically blocking these things on that interface. However you are still not opening up the WAN interface to packets from the WAN side because everything is blocked by default anyway. You would have to put in specific allow rules on WAN to open it. In your case the WAN interface is in a private network so you probably should have it unchecked. Steve

Thanks its up now. Sorry for the late response have to sleep after 18 hours of work… :)