From: Andrew Lunn <andrew@lunn.ch>
To: The list for a Better Approach To Mobile Ad-hoc Networking
<b.a.t.m.a.n@lists.open-mesh.org>
Cc: Hans-Werner Hilse <hwhilse@gmail.com>
Subject: Re: [B.A.T.M.A.N.] [RFC] alfred: implement TCP support for server-to-server communication
Date: Mon, 21 Mar 2016 14:25:10 +0100 [thread overview]
Message-ID: <20160321132510.GG28582@lunn.ch> (raw)
In-Reply-To: <4157766.3ikgnCPmEQ@prime>
> I was also thinking that we might want to use TCP in general when the packet
> size reaches a certain threshold (e.g. >3kB), and always use UDP for small
> packets. Then we would also not need the commandline option (unless you think
> we should leave a way to force a mode). Any thoughts on that?
Hi Simon
Either/or behaviour like this can cause hard to understand
issues. e.g. i opened a hole in the firewall to let Alfred traffic
though, but it suddenly stops when the network gets big, because it
swapped to TCP, and i don't have a hole of that. Similar for QoS
filters, i prioritise UDP Alfred packets, but when it swaps to TCP
they are not prioritised and get discarded during congestion...
Andrew
next prev parent reply other threads:[~2016-03-21 13:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-21 9:03 [B.A.T.M.A.N.] [RFC] alfred: implement TCP support for server-to-server Hans-Werner Hilse
2016-03-21 9:03 ` [B.A.T.M.A.N.] [RFC] alfred: implement TCP support for server-to-server communication Hans-Werner Hilse
2016-03-21 9:13 ` Sven Eckelmann
2016-03-21 9:38 ` Hans-Werner Hilse
2016-03-21 12:29 ` Simon Wunderlich
2016-03-21 13:25 ` Andrew Lunn [this message]
2016-03-27 18:26 ` [B.A.T.M.A.N.] [RFC v2] " Hans-Werner Hilse
2016-03-27 18:37 ` Hans-Werner Hilse
2016-04-22 18:37 ` jens
2016-04-24 22:02 ` Hans-Werner Hilse
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=20160321132510.GG28582@lunn.ch \
--to=andrew@lunn.ch \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=hwhilse@gmail.com \
/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