Date: Sun, 13 Sep 2009 09:22:31 -0700 From: Louis Kowolowski <louisk@cryptomonkeys.org> To: Marat N.Afanasyev <amarat@ksu.ru> Cc: FreeBSD <freebsd-stable@freebsd.org> Subject: Re: Question regarding vlans and lagg Message-ID: <9DAD6CD5-0BD7-4B06-8FA7-D0159419FEAE@cryptomonkeys.org> In-Reply-To: <4AAC3343.5030806@ksu.ru> References: <4AAC140F.2070203@stillbilde.net> <4AAC3343.5030806@ksu.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sep 12, 2009, at 4:48 PM, Marat N.Afanasyev wrote: > * PGP - S/MIME Signed by an unverified key: September 12, 2009 > 4:48:19 PM > > Svein Skogen (listmail account) wrote: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> Can the vlan "vlandev" be a lagg port of multiple physical interfaces >> (for redundancy)? >> //Svein > > i think that you should try the following: > > 1. join two ports on switch to trunk, say vport1 > 2. assign allowed vlans to this vport1 > 3. create lagg0 on freebsd > 4. create vlan interfaces on freebsd using vlandev lagg0 > > and i suppose it just should work ;) > You're looking for something along these lines: cloned_interfaces="lagg0 vlan0 vlan1" ifconfig_em0="up" ifconfig_em1="up" ifconfig_lagg0="laggproto failover laggport em0 laggport em1 up" ifconfig_vlan0="vlan 2 vlandev lagg0 up" ifconfig_vlan1="vlan 3 vlandev lagg0 up" ifconfig_vlan0_alias0="inet 192.168.1.41/24" ifconfig_vlan1_alias1="inet 172.16.0.20/24" This will give you failover for your lagg(8) interface, I believe you can also use something like etherchannel. -- Louis Kowolowski louisk@cryptomonkeys.org Cryptomonkeys: http://www.cryptomonkeys.org/~louisk Making life more interesting for people since 1977
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?9DAD6CD5-0BD7-4B06-8FA7-D0159419FEAE>