From: Nicholas Mc Guire <der.herr@hofr.at>
To: Celelibi <celelibi@gmail.com>
Cc: Randi Botse <nightdecoder@gmail.com>,
linux-c-programming@vger.kernel.org
Subject: Re: Sending and receiving packets from multiple lines
Date: Sun, 24 Mar 2013 11:58:10 +0100 [thread overview]
Message-ID: <20130324105810.GA19857@opentech.at> (raw)
In-Reply-To: <CAJR2zJ9JTLp3w3amqhRpC7dVZDDszWF7pVTmu1AWaK4TmqzwxQ@mail.gmail.com>
On Sat, 23 Mar 2013, Celelibi wrote:
> Hello,
>
> TCP should reorder packet fragments.
> If you're using UDP or a custom protocol over IP, you have absolutemy
> no guarantee about the delivery of packets.
>
> 2013/3/23, Randi Botse <nightdecoder@gmail.com>:
> > Hi All,
> >
> > My network implements interface bonding, aggregate several lines into
> > one logical line to achieve higher connection throughput and
> > redundancy.
> > I'm writing a network application in Linux that basically send packets
> > to another host outside. I got problem with packet ordering on
> > destination host, for example. packet1 from line1 should arrived
> > earlier than packet3 from line3, etc. I want them to be delivered in
> > correct order. Is this possible? if yes, what is the better way for
> > doing this?.
> >
you can implement that your self of course but it probably would be better
to use channel bonding to do that and then send all the data over the bond
device and let the kernel take care of ordering issues - handling all the
corener cases of losing single lines, notably temporarily is a pain in the but.
Also with the use of bondign devices you get all the benifits of clean
firewall and traffic control handling at kernel level - I doubt it is resonable
to handle this over multiple distinct lines in a meaningful way (with finite
effort that is...)
thx
hofrat
prev parent reply other threads:[~2013-03-24 10:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-23 2:52 Sending and receiving packets from multiple lines Randi Botse
2013-03-23 16:42 ` Celelibi
2013-03-24 10:58 ` Nicholas Mc Guire [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=20130324105810.GA19857@opentech.at \
--to=der.herr@hofr.at \
--cc=celelibi@gmail.com \
--cc=linux-c-programming@vger.kernel.org \
--cc=nightdecoder@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;
as well as URLs for NNTP newsgroup(s).