Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 13 Sep 2009 21:55:37 +0400
From:      "Marat N.Afanasyev" <amarat@ksu.ru>
To:        Louis Kowolowski <louisk@cryptomonkeys.org>
Cc:        FreeBSD <freebsd-stable@freebsd.org>
Subject:   Re: Question regarding vlans and lagg
Message-ID:  <4AAD3219.9040806@ksu.ru>
In-Reply-To: <9DAD6CD5-0BD7-4B06-8FA7-D0159419FEAE@cryptomonkeys.org>
References:  <4AAC140F.2070203@stillbilde.net> <4AAC3343.5030806@ksu.ru> <9DAD6CD5-0BD7-4B06-8FA7-D0159419FEAE@cryptomonkeys.org>

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

[-- Attachment #1 --]
Louis Kowolowski wrote:
> 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.

lagg can be configured as etherchannel, afaik

and yes, everything i'd proposed could be done from rc.conf

and remember that cloned_interfaces could not be restarted via
/etc/rc.d/neif restart ifN

-- 
SY, Marat

[-- Attachment #2 --]
0	*H
010	+0	*H
00=zl2zc<`)0
	*H
0b10	UZA1%0#U
Thawte Consulting (Pty) Ltd.1,0*U#Thawte Personal Freemail Issuing CA0
090401191518Z
100401191518Z0?10UThawte Freemail Member10	*H
	
amarat@ksu.ru0"0
	*H
0
1
S8@7>pUb
B@	
uQ05T͞%8ɴ6=]$DZ{{}X۵eSSwS֠8/87.`ZY)zyp`
@M *[SW[l
W,Oɏ9f»@&$Yad5{=D(<f:?6_rW(ؚ+8 mUO\{*0(0U0
amarat@ksu.ru0U00
	*H
nHrN<!ۢ/N}Ə<4@z;]GBJ2uژ	:s\cb?2V	f,;	NDمĖ5WXݝ?"q%Y
.i1FFy띑l00=zl2zc<`)0
	*H
0b10	UZA1%0#U
Thawte Consulting (Pty) Ltd.1,0*U#Thawte Personal Freemail Issuing CA0
090401191518Z
100401191518Z0?10UThawte Freemail Member10	*H
	
amarat@ksu.ru0"0
	*H
0
1
S8@7>pUb
B@	
uQ05T͞%8ɴ6=]$DZ{{}X۵eSSwS֠8/87.`ZY)zyp`
@M *[SW[l
W,Oɏ9f»@&$Yad5{=D(<f:?6_rW(ؚ+8 mUO\{*0(0U0
amarat@ksu.ru0U00
	*H
nHrN<!ۢ/N}Ə<4@z;]GBJ2uژ	:s\cb?2V	f,;	NDمĖ5WXݝ?"q%Y
.i1FFy띑l0?0
0
	*H
010	UZA10UWestern Cape10U	Cape Town10U
Thawte Consulting1(0&UCertification Services Division1$0"UThawte Personal Freemail CA1+0)	*H
	personal-freemail@thawte.com0
030717000000Z
130716235959Z0b10	UZA1%0#U
Thawte Consulting (Pty) Ltd.1,0*U#Thawte Personal Freemail Issuing CA00
	*H
0Ħ<UsUNʙZhup[v:aQP
0cZ,p+Z?qV˯<6$*+w=+>@dקe*TH<a@dr`00U00CU<0:08642http://crl.thawte.com/ThawtePersonalFreemailCA.crl0U0)U"0 010UPrivateLabel2-1380
	*H
HP.
fgCL!6-6/P p<ab:~t%Pb'qW%ݩ9 Oe_N4[5MwV!x!5$F]_eO1d0`0v0b10	UZA1%0#U
Thawte Consulting (Pty) Ltd.1,0*U#Thawte Personal Freemail Issuing CAzl2zc<`)0	+0	*H
	1	*H
0	*H
	1
090913175537Z0#	*H
	1luҳg#G֧t.0R	*H
	1E0C0
*H
0*H
0
*H
@0+0
*H
(0	+71x0v0b10	UZA1%0#U
Thawte Consulting (Pty) Ltd.1,0*U#Thawte Personal Freemail Issuing CAzl2zc<`)0*H
	1xv0b10	UZA1%0#U
Thawte Consulting (Pty) Ltd.1,0*U#Thawte Personal Freemail Issuing CAzl2zc<`)0
	*H
[dЭl$v`ZO$jF<#5Q'jJ˔	&M9E{&f{{[*QVmHzux pubjX	[FD[n`r>WĭD^{'4|+>yOyiz&>:i4Ҏt7{lGk] 3!#uV3\sM84T\0jedT,\Bu 	Cyd# Q

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