How did I miss that page! Thanks Biggsy.  :)

http://doc.pfsense.org/index.php/PfSense_2_on_VMware_ESXi_5

Steve

Yeah, couldn't care less about that wireless card. I might replace it with something more useful down the road, but for now I'm using an external AP.

And you're right, that pciconf is from the working system. So, if there's no interest in fixing this hardware for 2.0 (or understanding why 2.1 works where 2.0 doesn't), then I think we can call this one solved. :)

@Jimp

I am very grateful … thanks.  ;D

Ana

yup, ad0, that worked.  Thanks.  Time to read up on BSD disk layouts, me thinks.

Hi Jason

Thanks for the prompt reply.

@steve_eo:

The only thing that was missing from what you told me . . .

Thanks for completing the story. I've never had to do this because my WAN interfaces have always used DHVP or PPPoE.

@wifiguy:

What type of throughput/routing should a box like this be able to handle?  Close to a full Gig shouldn't it?

Depends on the actual CPUs installed and what packages, traffic shaping, etc. you use.

The reason people with i3 and i5 CPUs can get close to wire-speed on Gbe is their extremely high clock speed.  For simple routing+firewall performance, a brand new box with an i3-2130 would crush the R900 box you probably spent $20K on, an i5 has even more capacity because of Turbo Boost and the fact that the workload is largely single-threaded.

EDIT:  What is your current hardware?  What, exactly, do you plan to use this pfSense box for other than firewall duties?

The TZ-180 uses a MIPS CPU and hence is not supported by pfSense.  :(
See: http://forum.m0n0.ch/index.php?topic=5016.0

Steve

was need to enable Hardware Virtualization in the ML350 BIOS.
thank your help.

I don't have any problems either. There might be something wrong with your config or you have some other packages that are messing with communications. Please let us know what extra packages you have installed and perhaps any special config you have going on.

You could also start with traceroutes and DNS lookup to make sure those are happily working.

ok got it to work.

The most important thing is to have the latest version on openvpn installed on the client.
As then follow the instruction as per robi so create 2 bat files one connectionname_up and the other connectionname_down.

Put these 2 files in the config directory of openvpn, where the certs and connectionnane.ovpn files are.

ust use connectionname_up.bat and connectionname_down.bat command scripts and they will run automatically at connect and disconnect.

Example connectionname_up.bat:
Code:

net use U: /DELETE /yes
net use U: \192.168.1.10\users

Example connectionname_down.bat:
Code:

net use U: /DELETE /yes

Et voila job done.

Thanks so much for your help robi and i hope  this can be of some help for someone else also

Raj  :-)

The different files expand to different image sizes for various sized flash media, 1 Gigabyte, 2Gigabytes etc.
There is very little advantage to using a larger image even if you have a large flash drive. Manufacturers often label a flash drive '2GB' when it's actually something slightly smaller leading to the image failing to write.
Using a 1GB image on it ensures it will fit.
It also writes a lot faster, an issue for me since my CF card reader is only USB 1!  ::).

I was trying to find a post showing what will likely happen when you boot the usb drive but failed.
Assuming that your system is able to boot from the USB drive without issue it will very liekly fail to a command prompt complaining it can't mount root. This is because, as I said, it expects to mount root from an IDE connected device. It should then give you a list of possible locations and you can type one in.
Like this:

Trying to mount root from ufs:/dev/ufs/pfsense0 ROOT MOUNT ERROR: If you have invalid mount options, reboot, and first try the following from the loader prompt:     set vfs.root.mountfrom.options=rw and then remove invalid mount options from /etc/fstab. Loader variables: vfs.root.mountfrom=ufs:/dev/ufs/pfsense0 vfs.root.mountfrom.options=ro,sync,noatime Manual root filesystem specification:   <fstype>:<device>Mount <device>using filesystem <fstype>eg. ufs:/dev/ad0                       eg. cd9660:/dev/acd0                       This is equivalent to: mount -t cd9660 /dev/ad0 /   ?                  List valid disk boot devices   <empty line="">Abort manual input mountroot></empty></fstype></device></device></fstype>

At that prompt you probably want to type: ufs:/dev/da0s1a
However I'm not 100% on that!  ::)

Once it has booted correctly you will have to edit the fstab so that it knows where to mount root from in the future.

Steve

@imeitoiu:

The virtual machine has 2 processors from vmware and it is configured correctly from this point of view.

The VM BIOS also has to tell FreeBSD how many CPUs are available. This can be done by MPTABLE or ACPI. (There might be a vmware configuration item for either or both of these.) If using ACPI then FreeBSD has to take notice of ACPI (there is a FreeBSD boot option to ignore ACPI).

http://doc.pfsense.org/index.php/Does_pfSense_support_SMP_%28multi-processor_and/or_core%29_systems%3F says the SMP kernel needs to be chosen at installation time. The SMP in the string returned by the uname -a commands suggests
you are running the SMP kernel but I am not certain.

???

Outgoing port was closed form client side.

@chpalmer:

I was just able to play with this… Seems the WAN will still get an address in the private network space even if the "block private networks" box is checked...

Block private networks is strictly for ingress traffic, DHCP requests are egress.

I wrote  a guide a while back, and it shows you the options to pick from a CD install to a HDD
http://www.overclockers.com/building-pfsense-firewall
have a look at that.  Are they the same steps you have done?

Thanks Steve!

Ok… sorry for this...  :'(
Thanks.
Andrea.