There should be 0 collisions on a switched, gig-e network.

Only reason to reboot should be pfSense version updates and hardware maintenance.

there are no fix-all solutions. you could check the E2guardian bounty. https://forum.pfsense.org/index.php?topic=87526.0

@LFCavalcanti: 3 - If you say security concerns for NAS in pfSense are BS, you clearly understand s** about security. You NEVER, EVER expose your files or any sensitive data for that matter, in the very OS that serves as Firewall between your network and the rest of the world. When your boss know what you do in bed, sensitive data last thing on your mind. Some people understand everything about security, some of those people understand it will be losing battle. If I'm getting paid for it then yes, for myself I could care less. It's always about getting things you don't need. It reminds me when I stop by a Mcdonalds few years back while on the road at night. I saw this very over weight woman, she couldn't even wait for her order to get done. She was eating it right at the counter, my other boss was like "OMG you don't need take other bite of that. Put it down!" Yes idea of firewall and NAS is not normal, but sometimes people do odd things. @jwt: Also:  "Woof!" Arf

@johnpoz: The current proxy the old helper/proxy could do NOTING with ftps..  The helper/proxy looks in the control channels and fixes the IP to be public, and opens ports if needed in the firewall for data channel.  When your control channel is encrypted… It is not possible for helper to see anything in the control channel to either change the IP to the public one vs private or know what ports to open via seeing the port command.. Why don't you just connect in passive mode.. You don't need anything special to connect in passive mode.. Since in passive mode the server tells you what port to connect too.. So unless you have restrictive outbound firewall rules that limit ports.. You can connect to any ftp ftps server using ssl/tls or not since there is no aspect of the data channel where the server is connecting to you..  Its all you connecting to the ftp server IP and ports. Thanks for the answer. Perhaps indeed a problem in the client. I'll check.

@tymanthius: EDIT: I added the Lan gateway as an upstream gateway to Opt1. Seemed to help for a min, then its gone. You know, I actually wanted the screenshots to check that you did NOT set that up. Completely broken idea. And yeah, sounds like dead HW to me.

If you are not routing traffic through pfsense, then there is really little reason for L3 mode on your cisco..

Thank you cmb! I will remember that, thats why it was not working :)

@tomli: Thank you for your suggestions. Would you mind teaching me how to set Active/Active or Active/passive in pfsense? No I can´t do so, sorry. I was using LAGs for a short time, but not together with pfSense, than I switched over to 10 GBit/s thats more efficient and more reliable and stable. In shorter words, there are two modes and one is using all lines of the aggregated line and the other modes is using only one line and if this line is full the next one will be begin to use. And they are also two different ways you can walk this road, one is automatic over the LACP with dynamic LAGs and the other is the manual way using static LAGs and you will be able to choose the method by your own to balance this out over more line at the same time. I was using even static LAGs, active/active and together with the "weighted round robin" method, to fill all lines constantly. So I was thinking if there is now something likes you were reporting likes port flapping or packet drops it would be perhaps the problem of the active/passive usage of the LAG.

https://forum.pfsense.org/index.php?topic=101186.0

Alright.  Looks like removing default gateway from the WAN interface, then, going command line and running: route add -net [network] [gateway] Fixes the issue.  Now able to access via devices on the sophos LAN, and it has internet connectivity. Tried advertising a default route from the WAN pfSense, instead of setting static via command line, but for whatever reason, it didn't want to work.  Even though the OSPF routing showed a 0.0.0.0/0 route learned, it wouldn't use it.

Thank you very much doktornotor  :) I'll try this today.

Wonderful thing, Google: https://www.youtube.com/watch?v=O9D2fM883Fc http://hubpages.com/technology/How-to-Set-Up-a-Captive-Portal-Using-pfSense http://pfsensebuddy.weebly.com/blog/setup-pfsense-captive-portal-in-easy-steps https://doc.pfsense.org/index.php/Using_Captive_Portal_with_FreeRADIUS

Makes sense, thanks!

https://github.com/pfsense/pfsense/search?utf8=%E2%9C%93&q=edns

Hi BlueKobold, Thanks for the reply.  I've thought of similar solutions where I put another router device between the modem and pfsense computer, however, I really don't want to introduce an additional component.  I would prefer to have everything work (as it should) with just the pfsense computer and HughesNet modem. Gordon