@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… :)

@cmb:

You definitely can use Squid and Squidguard on embedded, many people do.

Thanks. I'll investigate but it looks like the blocklist itself must be loaded on the ramdisk (modifying the configuration files to access it from the CF wasn't successful according to some forum posts) and the default one are oversized for 512Mo RAM.

Almost impossible to do this. Certainly that would be impractical.
There is too greater difference between pfSense and FreeBSD to simply lay in on top.

Steve

are you going to be installing to hard drive?  If so then no you wouldn't use a nanbsd/embedded image

have you looked at
http://www.pfsense.org/index.php?option=com_content&task=view&id=43&Itemid=44

This goes over all the different versions

example
Embedded (NanoBSD)
The embedded version is specifically tailored for use with any hardware using Compact Flash rather than a hard drive.

Architectures
Starting with pfSense 2.0, there are versions for both i386 (32-bit) and amd64 (64-bit) architectures. This architecture is noted in each of the filenames for download. If you are unsure which version to use, then use i386. It is the most mature and well-tested architecture, and it will work on both 32-bit and 64-bit capable systems. The amd64 architecture (which does work even on Intel 64-bit CPUs) can address more memory and may have other performance advantages, but requires a compatible CPU.

Now with that 8GB ram you have - if you want to have full use of that 64bit should be used.  But 8GB seems a bit high for a pfsense box..  Are you planning on running stuff like squid and snort, ntop, etc.?

I've had a default installation of snort take out the entire network.  Even after uninstall the box is down.  Snort's FW block rules are time-based and persist even after uninstallation.  I'm not sure if this is a fact, but it was the root cause for my non-routing box.  I had to reinstall snort, remove all of the rules, purge the block list, and then uninstall for routing to work again.  I've learned the hard way that snort is not 100% out of the box "set and forget" friendly.  Add one rule at a time and review the logs.  Lots of people take out their network thinking snort is "set and forget".

Hi All,

Thanks all on your comments and efforts to help me, My specific issue was to create a router with pfSense and to set it up as a virtual machine inside a windows machine, windows machine is also virtual , A nested virtual machine. The system I have established is for testing an application.
Finally I decided to install pfsense on a stand alone machine of course virtual , So I set up my pfSense machine as a router between two virtual switches inside ESxi.

Now my next challenge is how to set up different NAT types…(asymmetric, Port-restricted)....
Any suggestions?

Thanks In Advanced.