Date: Sat, 16 Jan 2010 05:31:44 -0800 (PST) From: Barney Cordoba <barney_cordoba@yahoo.com> To: freebsd-net@freebsd.org, Callum Gibson <callumgibson@optusnet.com.au> Subject: Re: lagg doesn't fail back to master Message-ID: <875287.68136.qm@web63906.mail.re1.yahoo.com> In-Reply-To: <20100114223241.GA67640@omma.gibson.athome>
next in thread | previous in thread | raw e-mail | index | archive | help
=0A=0A--- On Thu, 1/14/10, Callum Gibson <callumgibson@optusnet.com.au> wro= te:=0A=0A> From: Callum Gibson <callumgibson@optusnet.com.au>=0A> Subject: = Re: lagg doesn't fail back to master=0A> To: freebsd-net@freebsd.org=0A> Da= te: Thursday, January 14, 2010, 5:33 PM=0A> On 12Jan10 14:25, Callum Gibson= =0A> wrote:=0A> }I have the following in my rc.conf:=0A> }=0A> }wlans_bwi0= =3D"wlan0"=0A> }ifconfig_bwi0=3D"ether XXX"=0A> }ifconfig_wlan0=3D"WPA mode= 11g"=0A> }cloned_interfaces=3D"lagg0"=0A> }ifconfig_lagg0=3D"SYNCDHCP lagg= proto failover laggport bge0=0A> laggport wlan0"=0A> }=0A> }This seems to w= ork fine at boot. However, once I plug=0A> wired back in,=0A> }lagg doesn't= switch back to the master. Here is what=0A> ifconfig is showing:=0A> =0A> = Thanks for the replies. For the list, the solution was to=0A> add the follo= wing=0A> to rc.conf:=0A> =0A> ifconfig_bge0=3D"up"=0A> =0A> =A0 =A0 C=0A=0A= LAGG should up (init) the port on add, so if it doesn't then=0Ayour solutio= n is really a work-around to a bug in LAGG.=0A=0ABarney=0A=0A=0A
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?875287.68136.qm>