Starting /usr/local/etc/rc.d/vmware-guestd.sh…done. Starting /usr/local/etc/rc.d/vmware-kmod.sh...done. Seems like the execute bits are set to off in my install. Running returns permission denied. Need to chmod +x to get it running properly.

No problems here either. 2.2.1 (newinstall) x64, hyper-v guest LAN, WAN, GUESTLAN(VLAN), OpenVPN-server and IPSEC lines, Squid, Squidfilter, Sarg, Lightsquid Went smooth to up to 2.2.2 (gambled and did it remotely connected with VPN…)  :o Brgs,

@cmb: ah, I tend to assume Viscosity==Mac. That log describes the root issue, it's not able to assign an IP or route. It shouldn't end up with a 169.254.x.x IP though, that indicates you have DHCP enabled on Viscosity's interface. Nothing in that regard would change by upgrading, something else changed related to your Viscosity or Windows system if that worked previously. There should be a lengthier log from Viscosity somewhere (not familiar with the Windows client). Compare your Viscosity config with the working OpenVPN client config.  Check the interface and Viscosity config. If Viscosity's adapter was screwed up in Windows and that's the only root cause, uninstall and reinstall of Viscosity might fix tha.t strange behaivor. just did reinstall but the issue still exist. i've reinstalled the VMware tools on my VM i use to connect from. et voila everything starts working. thank you for your help

Found it =) Thanks

Have you tried by-passing PFSense to see if the problem continues?

Yes, I agree (2) is a risk but if you have a test box hardware related problems should be found during proper use case acceptance testing. I learned this the hard way upgrading from 2.2RC to 2.2 Release without adequate use case testing. In the event of an unpatchable hardware specific vulnerability, second hand kit capable of running pfSense is both cheap and abundant.

@phil.davis: The bandwidthd issue is bug https://redmine.pfsense.org/issues/3986 If anyone can work out what is causing that interaction with PHP-FPM and even better, how to fix it, you will be a hero! I would live without bandwidthd, and maybe your troubles will all og away. Yeah I saw that last night, lots of error messages in the syslog, I thought I had everything working but the DHCP service tanking, not sure what the heck is going on.  I could get on the web gui but restarting DHCP service didnt appear to be working, was just acting funky.  Kind of like BandwidthD but something is not happy with my configuration, so I might uninstall most of the packages and just get back to the basics and see what that does, when things have been stable for so long kind of a bummer to have things not like they were…. I will be poking around when I get home and see if its still working...

And yes 100% tested ok now  just switch off the BIOS com serial comport and it will boot

I tried it again and it worked. Not sure how long it took since I left the room. Its the 3rd time I posted about this and you are the first one mentioning this. I really appreciate it. Thanks.

@cmb: How is your bridge assigned, or is it assigned at all? The sysctls you're using are opposite the default, so you must assign the bridge. There were some bridge configs in 2.1x and prior versions that could work even though they were wrong in that regard. @opalit: Version 2.0.3 had one of the few IPsec VPN servers that not only did site to site VPN but also IPsec for road warriors and it supported Iphone/Ipad VPN as well as Shrewsoft. All that works in 2.2x versions too. See Pictures in other posting

Possibly this: https://doc.pfsense.org/index.php/UpgradeGuide#Old.2FBroken_GEOM_Mirrors Steve

You cannot flash this on any Linksys router. pfSense is i386/amd64 only, plus requires at minimum 1GB of flash memory for the smallest embedded install available.

Here's a way to install pfSense on the HP thin clients without having to remove the DOM from the client: https://forum.pfsense.org/index.php?topic=87606.msg481510#msg481510 You need a USB stick to boot from. Tested on tens of t5730s, I guess it should work the same with t5740 also.

Key management can be a hassle, yes.  Not too bad for those who actually try to verify the integrity of their downloaded firewall software prior to use.  Only a few people have to be doing it.  They can raise the flag if they see something amiss. You can stop trying to convince me of all the reasons this is not a good idea.  You are wrong.  It's the best, currently-available solution to the problem.  Yes, they should also DNSSEC. They should also PGP sign their announcements.  Even if posted to the forum or blog there should be at least a link to the PGP-signed version.

Fresh install 2.2 with PuTTY. Alix HW output reads with 9600 or 38400. pfSense 1st boot & base setup output works with 115200. Until you've set 38400 in webgui.

Whow… solved... it works after a reboot... ::) Sorry... Pascal.

I hate to dredge up this really old post, but I'm seeing this as well, and I can't seem to find that anyone figured out a solution. Oddly enough, it is only happening on one of our pfSense installs (we have 11 running 2.2.1).  Of course, it is the one at our main corporate office, which means I'd like to get meaningful non-doubled bandwidth usage numbers from SNMP. One thought I had - this is also the only box we have running ipv6 and ipv4.  All of the others are ipv4 only. Any thoughts?