From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: IPFire 3.x development
Date: Tue, 06 Feb 2018 16:40:26 +0000 [thread overview]
Message-ID: <1517935226.21272.95.camel@ipfire.org> (raw)
In-Reply-To: <CAOE8VWoK_0qM+h2RkbxTF-RwqGQc3LDJQWoAjR75EpueMxpRZQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1161 bytes --]
Hello,
I am afraid we won't be able to provide what you are looking for. IPFire 3
supports multiple WAN zones but there won't be load-balancing for them. This is
designed to do failover which IPFire 2 can do as well for dialup connections
over DSL to LTE for example.
If you need load-balancing, please contact your ISP and get them to bundle
multiple connections you buy off of them together. It makes a lot more sense to
do this on layer 2 and let special hardware handle the managing the link because
it will know more about the underlying technology. The firewall can only
randomly throw packets at routers and hope that one of them makes it through.
That isn't serious networking.
Of course the best solution would just be to get one proper connection if
capacity of one isn't enough for you.
Best,
-Michael
On Mon, 2018-02-05 at 15:06 +0100, Marco Querci wrote:
> Hi everyone,
>
> I'm testing IPFire and I like it very much, it's a great product.
> I read about IPFire 3.x and the multi-wan support. I'd like to know about the
> development status of IPFire 3.x.
>
> Anyone knows something about it?
>
> Many thanks.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
parent reply other threads:[~2018-02-06 16:40 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CAOE8VWoK_0qM+h2RkbxTF-RwqGQc3LDJQWoAjR75EpueMxpRZQ@mail.gmail.com>]
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=1517935226.21272.95.camel@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.org \
/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