Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 2 Apr 2012 12:06:10 +0300
From:      Beeblebrox <zaphod@berentweb.com>
To:        freebsd-net@freebsd.org
Subject:   Re: (no subject)
Message-ID:  <CAPSTskt0Z1OwBmTcPNifzsmex-Wp0JPO=kgbDASbF4GQGVzTEQ@mail.gmail.com>
In-Reply-To: <20120330054318.GB4154@DataIX.net>
References:  <CAPSTskscqzf609Fr2g1xzdwCqXmw-vzMcC9w9%2Bv=c0Axp74pPQ@mail.gmail.com> <CAJ-VmonBaBVNphaRK4K6vVynJQ=A-=_QDcphw1eg1F_yzkYViQ@mail.gmail.com> <CAPSTskuLbtivg5qfB2d5J7Jn-UMu_7vC6rGbcbmg_OV6Jr8=0A@mail.gmail.com> <CAPSTskuu_YWf6UJ3EXYJs96HsRmiAFoAyJYMD=NGk4p5bqvkPg@mail.gmail.com> <20120330054318.GB4154@DataIX.net>

next in thread | previous in thread | raw e-mail | index | archive | help
>> Why on earth would you do that when configuring the LAgg does this for
you...!
ALSO! you do not need an address on either of the nics!. That should be
placed explicitly on the LAgg and add a alias for each sub address you
would like.<<

Incorrect! Try adding failover on 2 NIC's, leaving it up to lagg. You will
see that lagg device gets MACaddr of NIC2 - and this,for diskless clients
will not work because BOTH lagg and NIC2 need to be assigned MACaddr of
NIC1. Without NIC1 MACaddr, the client will loose the credentials on server
which it had established at boot-up.

Suggest you read man lagg, example #2 (failover interface between wired and
wireless)
++++++++++++++++


On Fri, Mar 30, 2012 at 8:43 AM, Jason Hellenthal <jhellenthal@dataix.net>wrote:

>
>
> On Thu, Mar 29, 2012 at 04:42:38AM +0300, Beeblebrox wrote:
> > Hi Adrian,
> >
> > Re your comments; you are 100% right, as I have not done steps 1 & 4 from
> > your list below.
> > I must also admit that my knowledge of networking, on a scale of 0-10, is
> > probably -1.
> >
> > <what does ifconfig look like?>
> > I assume you mean for Client? For example, re0 has static IP assigned by
> > DHCP and re1 (GBit NIC) has no IP untill I assign same MAC Address as
> re0,
> > create lagg and do an ifconfig lagg.
> >
>
> *****
> Why on earth would you do that when configuring the LAgg does this for
> you...!
> *****
>
> ALSO! you do not need an address on either of the nics!. That should be
> placed explicitly on the LAgg and add a alias for each sub address you
> would like...
>
> > <what's the routing table look like?>
> > Can't boot Client at the moment as I have an NFS mount problem. All
> > diskless clients boot from 192.168.2.1; DHCP, inetd, (and hopefully NFS)
> > run from jail and are bound to that IP. No firewall (yet) on that NIC.
> >
> > I'd like to try steps 1 & 4 as per your suggestion and see if that solves
> > it - so,
> > 1. What commands should I run for steps 1 & 4 ?
> > 2. lagg should be set up ass failover right? I assume loadbalance is
> > impossible when hubs are involved?
> > 3. Is it possible to assign lagg instruction through DHCP or some other
> > service on HOST, rather than settings in CLIENT rc.conf?
> >
> > Thanks so much for your help...
> >
> >
> >
> > > On Wed, Mar 28, 2012 at 9:37 PM, Adrian Chadd <adrian@freebsd.org>
> wrote:
> > >
> > >> Hi,
> > >>
> > >> what's the routing table and ifconfig output look like?
> > >>
> > >> It sounds like you're creating the interface and moving things over
> > >> without:
> > >>
> > >> * deleting the route/IP table entry;
> > >> * create the lagg;
> > >> * adding the interfaces to the lagg, including the one you booted off
> of;
> > >> * assigning the correct IP and readding the default route.
> > >>
> > >>
> > >> adrian
> > >>
> > >
> > >
> > _______________________________________________
> > freebsd-net@freebsd.org mailing list
> > http://lists.freebsd.org/mailman/listinfo/freebsd-net
> > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org"
>
> --
> ;s =;
>



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAPSTskt0Z1OwBmTcPNifzsmex-Wp0JPO=kgbDASbF4GQGVzTEQ>