thanks for the reply. after much thinkering i found out the iso i downloaded was corupted checked the md5. sry for wasting ya time

@YoMarK: If you're having timing problems when running pfSense as a VM, make sure that /boot/loader.conf contains the following lines: kern.hz="100" hint.apic.0.disabled=1 We are running a few pfSense(simple routers) Vm's on Vmware ESX here, and ntpdate offsets are minimum. @rsw686: One of the other issues I see is time keeping. A vmware machine has an emulated hardware clock which is not accurate. My linux vm varies by a few minutes. On Linux you can install Vmware Tools in the Vm. The tools then do direct time synchronization with the hosts hardware clock. This is very accurate. Unfortuanatly The Vmware tools for FreeBSD are not as good as the Linux ones. (Howver the solution above seems to be working fine) The VMware tools for linux work fine with 32bit guests. The problem is when using a 64bit guest. They fail to keep it accurate. Even with the kernel args "clock=pit nosmp noapic nolapic" I still had this issue. The only work around I found was to enable ntpd and disable the backup time clock in the ntpd config and its been working great.

only way your gettin 15 here is uncapping and or buying a few t1s :P i know personally i could max a t3 but hell..dont think that ATT has large trunks in this area…ill probably be the biggest cost effective ISP..no one here wants to pay 40+ for a 6mbit line :P

link you 2end nic to the vmnet2 network Could you please tell me how to do this? i tried couple of settings from vmware virtual network settings but i could not get it to work. how to do this. please elaborate. Thanks for your reply.

i did some more testing and somehow i believe that VmWare Bridging and WLAN dont go well together ^^" when i'm at home in and bridge the virtual pfsense WAN to hostmachine WLAN the pfsense recieve an IP from my wlan but cant communicate with anything on WAN. i cant even ping the hostmachine. i searched some forums and read some threads that VmWare Bridging is newly working on linux but i didnt find any information about windows so i assumed it is working, but apparently it is not :D

@ChillyWilly: Well the e1000 interfaces give me about 1.2 mbyte, so thats right in the middle. The PIII 866 is gonna be replaced bij a P4 2.8ghz machine so throughput won't be a problem then. Thats good to hear.  Please bench the 2.8ghz box when you get it in production.  I am curious how fast it will go.

@namezero: Will report back in two days. Good luck and be sure to edit the .vmx file and change the nic type out to e1000

What is wrong with Diagnostics -> Edit file?

Modify the scripts to copy the files into place at the end of the  process..  That is how we do it.

give it a try thanks