From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Path MTU discovery broken / advmss
Date: Fri, 28 Aug 2015 19:42:11 +0100 [thread overview]
Message-ID: <1440787331.18358.90.camel@ipfire.org> (raw)
In-Reply-To: <CACSqvJ=LW5QrEYmaY8gdwCtBFweAoYQQYjm4qbUszhxE5TO=Xg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1718 bytes --]
Hi,
let's discuss this on the forums then since Arne already answered
there:
http://forum.ipfire.org/viewtopic.php?f=27&t=14783
-Michael
On Fri, 2015-08-28 at 16:23 +0000, John P Poet wrote:
> Hi,
>
> I hope it is okay if I ask a configuration question here.
>
> A couple of weeks ago, my internet dropped and I noticed that my DSL
> modem was rebooting. When it came back up I had a new public IP and
> I could no longer load most web pages. Other than google, the ones
> which would load were very slow. I was finally able to get a page to
> load which suggested this behaviour could be caused by a MTU problem.
> I tried lowering the MTU on one of my machines from 1500 to 1492
> and the problem was solved.
>
> I then went to all of my various computers and changed the MTU to
> 1492, except my iPad. Apple being Apple, does not allow users the
> ability to change things like MTU. This means that I can still not
> get to most web pages, etc, on my iPad.
>
> Further searching brought up pages like:
> https://blog.cloudflare.com/path-mtu-discovery-in-practice/
> http://rtoodtoo.net/path-mtu-ip-fragmentation-and-mss/
>
> Given the info on those pages, I have tried to set advmss on my
> router to 1452, 1200, 1024, etc. But no matter what I do, I end up
> killing the routing completely. I have tried doing things like:
>
> # echo 1 > /proc/sys/net/ipv4/tcp_mtu_probing
> # echo 1024 > /proc/sys/net/ipv4/tcp_base_mss
> or
> # ip route change 0.0.0.0/0 dev red0 advmss 1024
> Obviously, those are not the correct way to get ipfire to set mss to
> a lower value. I am hoping someone can tell me the correct way to
> work around a broken "path MTU discovery" issue.
>
> Thanks,
>
> John
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
parent reply other threads:[~2015-08-28 18:42 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CACSqvJ=LW5QrEYmaY8gdwCtBFweAoYQQYjm4qbUszhxE5TO=Xg@mail.gmail.com>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1440787331.18358.90.camel@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox