Date: Sun, 5 Feb 2017 05:40:42 +0700 From: Eugene Grosbein <eugen@grosbein.net> To: Sean Bruno <sbruno@freebsd.org> Cc: freebsd-net@FreeBSD.org Subject: Re: NFSROOT and lagg(4) Message-ID: <20170204224042.GA82183@rdtc.ru> In-Reply-To: <3b771270-245a-cf8a-9cbe-f55df7680812@freebsd.org> References: <3b771270-245a-cf8a-9cbe-f55df7680812@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Feb 04, 2017 at 01:44:21PM -0700, Sean Bruno wrote: > "what I want" is to pxe/netboot and then switch over to using a lagg(4) > interface that includes the interface used in the pxe/netboot boot up. [skip] > lagg0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500 > > options=5259b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,VLAN_HWCSUM,TSO4,LRO,WOL_MAGIC,VLAN_HWFILTER,VLAN_HWTSO> > ether 00:30:18:c5:0a:a9 > inet 192.168.100.53 netmask 0xffffff00 broadcast 192.168.100.255 > nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL> > media: Ethernet autoselect > status: active > groups: lagg > laggproto lacp lagghash l2,l3,l4 OTOH, how do you expect make other side of link pass IP packets to your side before LACP protocol configures a port? Do you have pxe/netboot client capable of LACP? I guess, you'll have to stick with protocol-less "failover" LAGG mode using just physical link states. Eugene Grosbein
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20170204224042.GA82183>