From: Marek Lindner <lindner_marek@yahoo.de>
To: The list for a Better Approach To Mobile Ad-hoc Networking
<b.a.t.m.a.n@lists.open-mesh.net>
Subject: Re: [B.A.T.M.A.N.] batman-adv and TCP problem
Date: Tue, 6 Oct 2009 20:55:13 +0800 [thread overview]
Message-ID: <200910062055.14214.lindner_marek@yahoo.de> (raw)
In-Reply-To: <d9bba8670910060333i45d91b8eyc5fb1f1b05b94194@mail.gmail.com>
Hi,
> you can find as attachment the dump on eth2 of GW (tcpdump -ni eth2 -s 0 -w
> gw.cap);
> the output of batctl td -p 4 eth1 is:
I could not find anything revealing in the logs you provided. Could you please
follow Sven's suggestion to log both ends as well ?
Just to not forget the obvious:
* What batman-adv version are you running ?
* GW1 routes the packets - does this work via NAT or do you manually add
routing entries to both ends ?
> A question: am I the first one with this problem?
AFAIK batman-adv has no problem transporting TCP traffic (unless you found an
undiscovered bug nobody has seen before). The most common source of trouble is
the configuration of the setup, in particular MTU settings or routing issues
(which is why most people simply bridge).
Regards,
Marek
next prev parent reply other threads:[~2009-10-06 12:55 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-05 9:21 [B.A.T.M.A.N.] batman-adv and TCP problem Andrea Ghittino
2009-10-05 10:49 ` Marek Lindner
2009-10-05 12:12 ` a
2009-10-05 14:01 ` Marek Lindner
2009-10-05 20:54 ` a
2009-10-05 21:24 ` Sven Eckelmann
2009-10-06 9:26 ` a
2009-10-06 9:43 ` Sven Eckelmann
2009-10-06 10:33 ` a
2009-10-06 10:54 ` Andrew Lunn
2009-10-06 11:11 ` a
2009-10-06 11:19 ` Andrew Lunn
2009-10-06 11:55 ` a
2009-10-06 12:55 ` Marek Lindner [this message]
2009-10-06 13:14 ` a
2009-10-06 16:31 ` a
2009-10-06 10:49 ` a
2009-10-06 9:49 ` Andrew Lunn
2009-10-06 10:27 ` a
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=200910062055.14214.lindner_marek@yahoo.de \
--to=lindner_marek@yahoo.de \
--cc=b.a.t.m.a.n@lists.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.