Turn up another inside interface that doesn't use squid/squidguard and test again.

Posted a reaction about natting on ipsec in that other thread.. Its not the same as for regular interfaces.

Have you tried either of those devices? What was the result?

That list is by no means complete, it's only what people have confirmed as working.

Steve

It still might be a problem with your radios and the number of simultaneous associations they can handle.

Router or bridge mode shouldn't matter that much.

"I want to put their traffic in a higher queue to speed it up. "

Doesn't work that way - unless your pipe was full and that is the reason it slow.

I have direct tv, and have no issues at all.. And I sure don't have anything special setup.  Now queues that is for sure ;)

Hi jcl,
How many SSID you setup in your router? If you try to disable Captive Portal for a few sec, what happen?

I also see you can use System Tunables and add the sysctl.

On menu under System >Advanced >System Tunables
Pick 'add' and use hw.acpi.lid_switch_state as the tunable and desired Power State as 'value'

An update…not that any one has replied yet.

I did a test.  Installed a clean pfsense build on a new hard drive.  Only configured WAN and LAN.

Issue was the same.  This means that it has nothing to do with any of my configurations, out of the box there is something weird happening.

The only other thing...that I have not tried...is a completely different box...but I just cannot imagine that this is the problem.  This resources are nothing on this box.

Thoughts??

Sorry that I didn't mention mptcp from the beginning but I didn't want someone to think that I wanted to use this protocol particularly to achieve what I wanted even more when I'm not sure of what this protocol exactly is  :D

Thank you for the links, I think I'm going to put in place a load balancing configuration !

Just a stupid I can't really see why you can't have protocol or something capable of : "Hello Server  I'm Wan1 I want to download this file but you can send packets to this adresses Wan 1 and Wan 2. Then after behind the Wans you have a bond that can reorder the packets in order to obtain your complete file and deliver it to the local machine that was doing the request" ? I agree it seems a bit complicated like that but not impossible from my amateur point of view…

@Derelict:

What does this have to do with pfSense?

When I googled the message Im getting the ONLY link that came up was this forum.

"Your just wanting to edit the descriptive name…" Yes :)

https://redmine.pfsense.org/issues/7861

Which direction are you using the VPN?  If incoming, to access your network, you'll need a public IP address.

Well, have you fired up Wireshark on the Ubuntu box, to see if the pings are received?  Any replies?

Happy reading.

https://www.dslreports.com/forum/r29903721-AT-T-Residential-Gateway-Bypass-True-bridge-mode

Turns out the router in front of the PFSense box wasn't clearing down sessions.  This is why I couldn't see loads of sessions in PFSense.  The router had a non released version of firmware on it (Draytek) to try to stabilise the VDSL BT Infinity line, but seems this caused issues with sessions.  Putting the current firmware on it has sorted the problem.

Do you have the appropriate default firewall rule (allow LAN Net to Any?)

Very simple setup over here. No VLANS configured on the firewall and it looks like it is a default PFSense install with some changes to get Internet connectivity and VPN access. I always make a backup of the config before doing anything, learnt that lesson the hard way before :). Thank you for your advice :).

FOUND IT!

For future reference, u-verse 5268AC has a firewall at IP level under LAN IP Address Allocation. Disabled it and pf took over.


I didn't even notice we could attach images…. There you go :)

NAT is used, but I made sure anything going between the two would pass, or at least there is nothing blocking the way...

EDIT: It resolved itself. I do not know if the version of pfsense I was using was not recent enough or if I made a typo somewhere but after the last re-installation with a new cd of pfsense it worked.

XoquCtW.jpg
XoquCtW.jpg_thumb