I figured this out myself. I had a hunch that reapplying the 1.2.3 full update would fix any missing files and this seems to be the case. /usr/local/etc is full of files now and no errors on starting services and the reboot worked without a hitch.

Nvm figured it out. Added a port forward to redirect port 81 on wan to port 80 on lan

Great! Thanks  :D

the only official reseller that i know of is http://www.applianceshop.eu/index.php/firewalls/opnsense.html others can sell it but can not charge you for the software. pre-configured anything are easier for anything as you have support from the person who sold it to you, they have to (US at least) provide some type of after sale support, not sure of the min duration though. Are you the in house tech? For support if you dont buy from them, theres the book and the forum and the main website for recommended min hardware as well as the official support from BSD Perimeter https://portal.pfsense.org/index.php/support-subscription, there is also support from other companies/individuals as well, so its up to you as to the route you choose to go.

Can you show a screenshot of your pool and the firewall rules on your LAN?

Wow, this is depressing - a fresh install (the 4th so far this week) has fixed it. Setup is exactly as described previously. I'm starting to think I had some strange hardware problem somewhere. Still, I'll put this little bit into a tutorial as planned. At least it someone else had the same problem, they'll know that it should work. Thank you everyone for your help. -Jason

They are not reversed. It's just a question of the point of view. From the pfsense seen your downloads are traffic going out on the LAN interface, and your uploads are traffic comming in. Nothing to fix here.

Thanks for the info.  I will play around with the configuration and post some results.  Perhaps others will find this useful…

Just enable DHCP on the LAN2 interface and then create firewall rules on each interface that blocks traffic destined to the other segment.

I think I get where your going with this but I think the answer is no! Bonding only works if the device doing the 'packet splitting' is splitting them in such an 'ordered' fashion that the device doing the joining (switch/router) knows and expects how to re-join them. If the packets are coming from completely different souses they will arrive in a shot-gun fashion. bonding requires order and harmony and the internet is anything but. Cheers

Ok, Resolved. It was the windows Firewall on the aimed server. It should have been deactivated, but apparently was not (wonder why?).

Yes filtering is completely disabled. The problem was solved, there was an issue with my vlan setup on my switches.

I have had this same problem on multiple new installs with different CF cards and on multiple hardware platforms (net5501 and PC hardware) Houston, we have a real problem here!  A problem I can live with but none the less a problem that should be addressed. Roy…

@subfire91: hi guys i have 3 interfaces on my pfsense 1 for wan 1 for lan and one empty. i need to connect my linksys to the empty pfsense port and i need recommendations on the connectivity and settings. First of all i will connect the linksys WAN port on the empty pfsense port using a cross cable right? Furthermore will static routes be needed in order for my lan to communicate with the wireless lan? Finally what settings should i configure on the linksys ? i will have to enter dns settings manually right ? thnx for the time Find a router that can set its wan as lan (to have an extra port) or just tape over the wan port (reminds me not to use the port), give it an ip in same subnet & don't forget to give it an address of your gateway for the DNS, and turn off the DHCP server.

No. By default the webgui is not open on the WAN. There are no open ports on a default install. If you are failing the shields up test you configured something wrong. Or it's not coming from your firewall. what he said ^ Satellite…  dont they put you on a proxy?  The results may be showing you something related to the noc...