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.

The 6501 is very picky about which USB sticks it will boot from. Out of the half dozen or more I tried, only one would boot. If you copy/paste the line from the BIOS detection that shows the drive, it would help to determine if it's a problem with the stick or not.

You can configure this path on squid package but usually it will be on /var(/squid) To get a better performance, enable soft updates on this new partition.

If that's on CD, that's normal, and not fatal. It's trying to read or probe the CD in some way that isn't possible while booting from CD.

On 2.0 that option can change the WAN IP as well. You really shouldn't be starting out with 1.2.3 at this stage, 2.0 (and 2.0.1) have been out for many months.

Thank you!

Thanks a bunch jimp ;). Cheers

Just import the files they give you into the Cert Manager. IIRC, If you made the CSR in the GUI, the CSR should still show up, you can press "e" to edit the CSR and input the result from your originating CA.

Solved by adding the kern.cam.boot_delay=10000 tricks…....... It would be nice if this is by default on, it doesn't really cause much extra time from booting but a few hours for ignorance like me to trouble-shoot ::)

It would interesting to know what they expect the network to look like. Presumably they have done this many times before and have found this be the best setup. I'd be interested in the opinion of someone with more experience on this. Steve

It's because the default rule on the pfSense LAN interface that allows access to the web GUI only allows access from the LAN subnet. If you are coming from a remote subnet routed via a VPN that will be blocked. You need to add a rule on LAN to allow access from your remote subnet. You should be able to so your routed access attempts being blocked in the firewall logs. Steve