From: Axel Neumann <axel@open-mesh.net>
To: The list for a Better Approach To Mobile Ad-hoc Networking
<b.a.t.m.a.n@open-mesh.net>
Subject: Re: [B.A.T.M.A.N.] two-way-tunnel quirks
Date: Tue, 4 Dec 2007 13:37:17 +0100 [thread overview]
Message-ID: <200712041337.17976.axel@open-mesh.net> (raw)
In-Reply-To: <200712041101.06161.axel@open-mesh.net>
Hi,
>
> Still I could not yet reproduce the problem but I am quite sure
> that this has something to do with the msn&co.coms' reluctance to
> respond to icmp messages.
Well, after a while my office colleague did.
Actually, it took me a while to understand that my experiments on our office
server and his annoyance about an "unstable" imap account had something in
common :-(
The only solution we found to circumvent such small-mtu paths was:
- avoid related web services OR (not so good)
- Use openvpn over the path with the reduced mtu. Seems like openvpn fragments
and de-fragments the packets transparently between related end2end tun0
interfaces. This even worked on his windows machine.
Perhaps this might also become an outlook-item for the next batman tunnel
implementation :-)
ciao,
axel
>
> ciao,
> axel
>
> > cheers
> >
> > --Jan
>
> _______________________________________________
> B.A.T.M.A.N mailing list
> B.A.T.M.A.N@open-mesh.net
> https://list.open-mesh.net/mm/listinfo/b.a.t.m.a.n
prev parent reply other threads:[~2007-12-04 12:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-30 23:28 [B.A.T.M.A.N.] two-way-tunnel quirks Jan Hetges
2007-12-01 17:34 ` Marek Lindner
2007-12-01 20:41 ` Axel Neumann
2007-12-02 5:39 ` Jan Hetges
2007-12-06 3:18 ` Marek Lindner
2007-12-02 4:32 ` Jan Hetges
2007-12-02 18:54 ` Axel Neumann
2007-12-03 17:47 ` Predrag Balorda
2007-12-04 4:03 ` Jan Hetges
2007-12-04 9:05 ` Axel Neumann
2007-12-04 13:00 ` Jan Hetges
2007-12-04 15:05 ` Axel Neumann
2007-12-04 10:01 ` Axel Neumann
2007-12-04 12:37 ` Axel Neumann [this message]
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=200712041337.17976.axel@open-mesh.net \
--to=axel@open-mesh.net \
--cc=b.a.t.m.a.n@open-mesh.net \
/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