From owner-freebsd-net@FreeBSD.ORG Mon Apr 2 09:06:17 2012 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 964B81065672 for ; Mon, 2 Apr 2012 09:06:17 +0000 (UTC) (envelope-from rsb@berentweb.com) Received: from mail-lpp01m010-f54.google.com (mail-lpp01m010-f54.google.com [209.85.215.54]) by mx1.freebsd.org (Postfix) with ESMTP id E7CE08FC1A for ; Mon, 2 Apr 2012 09:06:16 +0000 (UTC) Received: by lagv3 with SMTP id v3so4215368lag.13 for ; Mon, 02 Apr 2012 02:06:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=berentweb.com; s=google; h=mime-version:sender:x-originating-ip:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; bh=Y1L4zkXHLCKQmTuG2c+ybFBTY+hwAC5MoKQrbo47DPc=; b=au5rRXM4T1jZzeZI7flseDz2C5rnDbgm75ygnofHuz10FVbu9m37ATpjlEO4IVakxv Mb1hic3GhpCG7eGTpX+Osdryif0L5deJNuJrYHJQcfzCSjBmEvDtCCR6KHjEE0335Ut9 hLl3sCzO8m1CfZRQtF4k9HPyOAd7oS8m6e+3U= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:sender:x-originating-ip:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type :x-gm-message-state; bh=Y1L4zkXHLCKQmTuG2c+ybFBTY+hwAC5MoKQrbo47DPc=; b=J6VZAcauvv//GNmKMi8uvzjSvpi92J2pGLIpOwzcPZLuhbXag3WHNudanxYCJYXCK9 csLb5LKovH/o+h8wIRo+Bi30t3e8JOWKXd841W4q9mESDXUd+PNRVEv4FH4ZMwOWjvU6 jMPfjRJw8w+QmG8O9pQ17wDCGJY/lwmx+L04D/qhZian1GautE5VaIsQnAlZWB57yZjP rrwSntaCMC4wfbGZpiksUWSbGuKRHLMyzwyu/1kEOa1ehX/54/G75UTDRTGho/AXC8fC EdRfIXLmRxbel5dCSHMP47tGPD7iKRQu/tt9GlfwVTdZLt9j8gCVIrfOOBwocrfNaUaI 8Ozw== MIME-Version: 1.0 Received: by 10.152.131.3 with SMTP id oi3mr8916433lab.35.1333357570412; Mon, 02 Apr 2012 02:06:10 -0700 (PDT) Sender: rsb@berentweb.com Received: by 10.112.77.15 with HTTP; Mon, 2 Apr 2012 02:06:10 -0700 (PDT) X-Originating-IP: [85.110.29.196] In-Reply-To: <20120330054318.GB4154@DataIX.net> References: <20120330054318.GB4154@DataIX.net> Date: Mon, 2 Apr 2012 12:06:10 +0300 X-Google-Sender-Auth: NX3LNwBH-IbfBd9x20M9K39mJZY Message-ID: From: Beeblebrox To: freebsd-net@freebsd.org X-Gm-Message-State: ALoCoQm9vRiUCJSNYnTw6pmVQEdjrirtBOz5HHD583ceS64qF+WEIW7dHL6t0XVYhjxjlJBXFVlR Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: (no subject) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Apr 2012 09:06:17 -0000 >> 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 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. > > > > > > 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... > > > > > 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 > 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 =; >