Linux Routing and SSL

I have a Fedora Linux box which I am using for a captive portal.  Basically this is the setup,  I have 3 vlans whose gateways are assigned to eth0.91, eth0.93 and eth0.90.  The traffic is checked by iptables and if the MAC address of client is in iptables then the traffic if forwarded out.

All Windows OS machines can access all sites with no problems.

The problem:

Linux machines will have inconsistent problems with https sites. Some https sites won't load at all, others just authentication problems.  I used Wireshark at the point of authentication and the client machine will try to transmit the same packet 5-6 times, with no reply from the https site.  After these 5-6 tries, the https site will send a RST, ACK packet back to the Linux system. Then the page will time out.  But I can reload the https site again with no problems, but still cannot authenticate. HTTP, ping, tracert all work, all the time.  

What is the difference here between the Linux OS and Windows OS that would treat https packets differently?
Mick FinleyNetwork EngineerAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

try this:
iptables -t filter -A FORWARD -p tcp -m tcp --tcp-flags SYN,RST SYN -m tcpmss --mss 900:1536 -j TCPMSS --clamp-mss-to-pmtu

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Mick FinleyNetwork EngineerAuthor Commented:
Ok...You pointed me in the right direction.

Here is the fix:

change the MTU on the Linux client machine to anything below 1492 and it all functions as expected.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Linux Networking

From novice to tech pro — start learning today.