From: Jarek Poplawski <jarkao2@o2.pl>
To: lartc@vger.kernel.org
Subject: [LARTC] Re: Routing packets over multiple links (NICS) all on the
Date: Wed, 16 Aug 2006 09:36:12 +0000 [thread overview]
Message-ID: <ebuoth$aeu$1@sea.gmane.org> (raw)
On 14-08-2006 17:42, Jacques Rompen wrote:
...
> What we want to do is the following:
> I live in a student complex with 7 other people. Every room has its own
> internet connection from the same ISP.
> Ip, gateway, subnet are asigned through dhcp on mac-adres basis. Every
> internet connection is capped at 20mbit
> up/down.
> We want to get all computers on an internal network. So we need some
> sort of router that accepts all 8 internet
> connections and routes it out over a gbit nic -> switch -> internal network
> So we have a computer with 10 nics and "hopefully" enough internal bandwith.
Maybe you have some other reasons to make one gateway but to have
internal network you only need to set a second address from local
range (not colliding with that used by ISP) on each box.
But if you really need this together and with multipath, setting
CONFIG_IP_ROUTE_MULTIPATH = "y" and
CONFIG_IP_ROUTE_MULTIPATH_CACHED = "n" (!) should change
multipath randomly.
Jarek P.
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next reply other threads:[~2006-08-16 9:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-16 9:36 Jarek Poplawski [this message]
2006-08-16 12:50 ` [LARTC] Re: Routing packets over multiple links (NICS) all on the Jacques Rompen
2006-08-16 13:52 ` Jarek Poplawski
2006-08-16 14:18 ` Jacques Rompen
2006-08-17 6:54 ` Jarek Poplawski
2006-08-17 17:11 ` Luciano Ruete
2006-08-17 17:48 ` Jacques Rompen
2006-08-17 19:02 ` Luciano Ruete
2006-08-21 12:20 ` Jacques Rompen
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='ebuoth$aeu$1@sea.gmane.org' \
--to=jarkao2@o2.pl \
--cc=lartc@vger.kernel.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 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.