You need to stop messing with config files via shell.

run(away)

I understood you. Thank you for taking the time to find a solution to this problem! I very much hope that in future versions will be implemented to support the transfer H323 protocol to the fullest!

Try this: http://wiki.pcbsd.org/index.php/Talk:Installation_Troubleshooting I had to set HD access mode to LBA on a box here but you're not using a HD. Will that box not boot from USB then? Steve

Seems like you hit some 'random weirdness' which is never a good thing. Garbled serial output is very often a serial cable or adapter problem which may not be obvious. Steve

Ill give that a shot, removing vlan 1 and making it just a pass though port. I thought the PVID on the switch defaulted to vlan 1.

I was able to get my networking working and the host can join the domain. I assume using the built in NAT from VMWare is enough and a firewall would not really benefit me any for this type of internal private network. Thanks for the help.

hmm…i have a serial to usb cisco cable here around...it might help.

My own stupid fault.  In the advanced pass through options I manually bound haproxy to port 80 to facilitate http > https redirection and specified the public ip of my production environment which is inaccessible from my test bench. I am not a smart man.

1.  Yes! WPAD Autoconfigure for Squid 2.  Squid will cache HTTP or HTTPS.  Your hit ratio depend entirely on the sites that you visit and the frequency at which you visit them.4-8% is around the same ratio I get. 3.  I have had limited success with dynamic content.  Nobody seems to have a config that works well.  All the various wikis etc say the same thing: play with it, see what happens, YMMV, but nothing concrete.  That combined with the poor hit ratio has me thinking about deploying Squid just as a base for SquidGuard filtering.

Unlikely, it's only older hardware that now requires this workaround. It's pretty easy to do though now you know about it.  :) Steve

Thanks heper for your quick response. the NAT issue was actually me being too tired to do installations. i only reseted the first router after configuring the NAT so NAT works great ( tested with different ports ). the second issue is even more obvious. as i have the default rule ( LAN net  to get out ) it was higher then the rule of the change WAN for my ip. this why you shouldnt deal with networking installation after 3:00AM

It looks like the driver is included: [2.2-RELEASE][root@pfsense.fire.box]/root: kldstat -v | grep sas 256 pci/mrsas It just needs to be given priority over the mfi(4) driver by setting that loader variable. See: https://www.freebsd.org/cgi/man.cgi?query=mrsas&apropos=0&sektion=0&manpath=FreeBSD+10.1-RELEASE Steve

this hardware is based on " 2.1.5-RELEASE (i386) " installed SQUID version is 2.7.9 pkg v.4.3.4 Squidguard version is 1.4_4 i've removed the packages as mentioned and update, after the update had to reinstall the packages. configuration was picked up automatically thank you

@stephenw10: Hmm, interesting. At least you've proved it's not a pfSense specific issue. I'm on Plusnet and seeing very few issues. However if you are you should get on to their support forum and ask because they have real people with real technical knowledge there who will help. One of their support guys went to amazing lengths to pin down a fault I found. Are you on fibre? I used a V120 with their adsl2 service for years. Steve Thanks Steve, moving discussion over to Plusnet Support Forum http://community.plus.net/forum/index.php/topic,137223.0.html

Or alternatively, I was thinking of posting a bounty for this… what do you all think would be a reasonable amount for adding something like this? I was thinking $500-1000 USD?

Whoa, Got this working. The interface used for WAN under hyperV (sconfig, not vswitch in VMMC) was set to DHCP. I set this interface to static: IP = ISP Gateway ip (don't think IP matters) Gateway = ISP gateway IP DNS = ISP DNS ip So in CMD prompt it appears as going to my ISP. LAN interface was already set to the same subnet range as PFsense LAN. So now everything it working fine for internet traffic etc. What do I do about the DNS resolver issue in bootup? Should I still go for a reinstall with regards to this?