Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 10 Jan 2011 11:18:21 +0100
From:      Thomas Steen Rasmussen <thomas@gibfest.dk>
To:        Francisco Reyes <lists@stringsutils.com>
Cc:        freebsd-net@freebsd.org
Subject:   Re: Lagg questions
Message-ID:  <4D2ADCED.8060809@gibfest.dk>
In-Reply-To: <cone.1294602157.25706.3413.1000@shelca>
References:  <cone.1294602157.25706.3413.1000@shelca>

next in thread | previous in thread | raw e-mail | index | archive | help

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
 
On 09-01-2011 20:42, Francisco Reyes wrote:
> Found a couple of good lagg tutorials
> http://www.cyberciti.biz/faq/freebsd-network-link-aggregation-trunking/
> http://wisekuma.net/linux-bsd/freebsd-lagg/
>
> But there are a few things that I can't find so far...
>
> Does one need a third card to reach the machine where one runs lagg?
> Say I have em0 and em1, do I assign actual IPs to the cards before
> adding them to lagg or they can't have IPs of their own?
>
> Other than lacp protocol do the other options work without having to
> change anything at the switch?
>
> My situation is as follows:
> Have two connections, 1 T1 and a cable connection.
> Need to, temporarily, allow outbound traffic between both.
>
Hello,

I'm afraid you've misunderstood how lagg works.

lagg is for bundling _layer 2_ links. This basically means you can use
two or more physical cables to the same switch, to get better speed
and/or redundancy.

Using lagg to bundle two uplinks to two different providers will not work
as you intend. You need to look into using pf or something similar to
balance layer 3 traffic across two uplinks. I have had this running at
home for years with pf, and it works great.

Best regards

Thomas Steen Rasmussen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
 
iEYEARECAAYFAk0q3OwACgkQGjEBQafC9MB+4ACggVWVlUCFt25rJTUwBJewA/BA
dswAnjVM0Bo84DBAWJila0+NlivtxOxo
=B0j2
-----END PGP SIGNATURE-----




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4D2ADCED.8060809>