From: Colin Alston <colin.alston@thusa.co.za>
To: shorewall-devel@lists.sourceforge.net
Cc: netdev@vger.kernel.org
Subject: Re: [Shorewall-devel] Fwd: iproute weight balancing problem with youtube
Date: Tue, 09 Dec 2008 20:30:40 +0200 [thread overview]
Message-ID: <493EB950.8020203@thusa.co.za> (raw)
In-Reply-To: <200812091803.35682.frahm@sybuca.de>
On 2008/12/09 07:03 PM Markus Frahm wrote:
> Dear Stephen Hemminger,
> we have found a problem with ip route and multiple internet connections using
> the ip route 'weight' option to balance the traffic of a NAT firewall between
> several lines. Internet sites like 'youtube' show videos only with 50%
> probability because youtube and similar sites demand several connections (for
> the web site and the flash stream) to come from the same source IP. Is there a
> simple solution for this problem for example to increase the time in the
> balancing algorithm or a cache for source IPs?
> Regards
>
Should not be a problem. YouTube uses a single stream for buffering and
there should not be any conflict between a change in source address with
the request for the flash applet and the stream. HTTP does not work that
way... There are some protocols that do, in which case there is contrac
to solve that problem, if there were a bug it would be in contrac so you
should raise the issue on the Netfilter lists.
I have personally used Shorewall in such a configuration (we are
designing a product at the moment for that exact purpose) and have not
seen any issues. Are you sure this is not a packet loss issue on one of
the upstreams?
prev parent reply other threads:[~2008-12-09 19:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-09 17:03 Fwd: iproute weight balancing problem with youtube Markus Frahm
2008-12-09 18:30 ` Colin Alston [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=493EB950.8020203@thusa.co.za \
--to=colin.alston@thusa.co.za \
--cc=netdev@vger.kernel.org \
--cc=shorewall-devel@lists.sourceforge.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;
as well as URLs for NNTP newsgroup(s).