Depends on the switch. On pfSense it is in Interfaces > Assignments, LAGGs

So there's no way to know but to try it. As has been said many times, it might or might not work. Want to process dot1q? Use a dot1q switch.

Uhm… https://support.microsoft.com/en-us/help/17472/windows-internet-explorer-11-fix-site-display-problems-compatibility-v

Yes the SSL/Proxy should be completely separate from the pfSense webgui. I would expect you could use letsencrypt for both or either. But they would need to be on different ports. Steve

I started with a fresh install, as suggested by tripplex, restoring the settings and that seems to resolve the issue. I'm still monitoring if it remains online. Once it happens again, I'll wireshark & check the states Steve. Keep you guys updated!

Which OS is your Plex Server running on? Can you use "nslookup" or "dig" for www.google.com from plex console, if so what's the result? Probably not related to your problem but you know that 20.1.1.0/24 is not a designated RFC1918 private address space. It belongs to CSC, Computer Sciences Corporation (CSC and HPE Enterprise Services are now DXC Technology). So whatever services they are hosting from those IPs they won't be accessible to you.

I have toyed a bit with this , and here is a working solution wo. to much "no..no" ********* Works wo sudo hack on linux ************** Only first time (ever) - to make ssh work wo. asking for passwd ssh-keygen ssh-copy-id user@pfsense-fw If sudo is installed on pfsense ---------------------------------- remote:~$ mkfifo /tmp/pcap remote:~$ sudo tcpdump -iigb1 -U -s0 -w - 'not port 22' > /tmp/pcap If sudo is not installed on pfsense ------------------------------------ ssh to pfsense as root/admin , enter 8 for shell remote:~# mkfifo /tmp/pcap remote:~# tcpdump -iigb1 -U -s0 -w - 'not port 22' > /tmp/pcap and send the data by a separate connection: local:~$ mkfifo /tmp/pcap local:~$ ssh user@pfsense-fw "cat /tmp/pcap" > /tmp/pcap and finally start Wireshark local:~$ sudo wireshark -k -i /tmp/pcap ********************* end *************** I do have this one liner working As local root (due to wireshark needs root) local:# ssh user@pfsense-fw sudo tcpdump -iigb1 -U -s0 -w - 'not port 22' | wireshark -k -i - But it requires sudo to be installed on pfsense https://www.cyberciti.biz/faq/how-to-add-delete-grant-sudo-privileges-to-users-on-freebsd-unix-server/ install pkg install security/sudo And some "nasty" visudo things, that would get a "security officer/revision" to get "Red Ears" …. I could prob lock it down to just work with tcpdump , but for now it's allowing my local user to sudo anything wo even asking for a pwd. Provided he's a member of the admin group. Have fun "Sharking" Ps: Most of this nasty stuff would prob not be needed of we could get a way to ssh into pfsense as root , wo. hitting the "menu". Or if we could ssh into pfsense w. a user that was allowed to run tcpdump on an interface. /Bingo

Heper, Thanks for that…..one I had not considered and will probably perform exactly what I need.... In fact as I was typing, on that same system, I just marked the Gateway Offline and put the Gateway Default back to the Primary Link (which has been marked as down) The results were Forwarded Ports to the Secondary WAN link  - responsive Inbound OpenVPN connections working Outbound OpenVPN Connections working Everything else working as it should in a failover situation. Heper, Thanks that appears to do exactly what I need….. Regards Bob

I believe you. Currently working with FreePBX forum to resolve this.

Ha, no need to feel bad, I'm glad you got up and running.  :) Steve

Thank you for replay. I will check and inform.

Completely up to your switches. pfSense LACP will not care.

@valnurat: ….. But is it not possible to use 8.8.8.8 instead of my ISP? Yep. If you prefer that Google knows all about your DNS requests (so they know what your are doing every time) instead of your ISP, then it is ok to switch to them. Normally, you shouldn't do this all together, and just use the Resolver -as it is activated by default.

I'm not sure what you mean here. Sounds like you are asking for something for the captive portal? It already has a popout logout button feature. Steve

No. You need to understand VLANs. Edge devices get untagged, access ports in almost all cases. Connections to VLAN-aware devices like other switches, pfSense with tagged ports, Access Points, etc get tagged, "trunk" ports. Chapter 2: https://books.google.com/books?id=dkDsJmnsejEC&pg=PA51&source=gbs_toc_r&cad=4

here [image: vpnserversettings.png] [image: vpnserversettings.png_thumb]