From owner-freebsd-net@FreeBSD.ORG Mon Apr 2 09:25:09 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 711F7106566B for ; Mon, 2 Apr 2012 09:25:09 +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 CCBBC8FC0C for ; Mon, 2 Apr 2012 09:25:07 +0000 (UTC) Received: by lagv3 with SMTP id v3so4240758lag.13 for ; Mon, 02 Apr 2012 02:25:06 -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=8tGVQIJr8JstQUUliK3xnLtqaTC2FM5cAdAtP0ye1G8=; b=NpzZ411gZ1Gs1OrTRq7S+nS/P1qiFB8wPlG9wRxyPYlFnDjSyhXo9l44/7jI91izoF HBN5Ibapx67ATic5gOKueZRdfYyldWVum6Hl7UPxrnphpJw8FOF40ezCz20Wua4oI0P5 JxilIoUp7f7HX5GFG5bqsFLugGJgmLQxf5yUg= 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=8tGVQIJr8JstQUUliK3xnLtqaTC2FM5cAdAtP0ye1G8=; b=O9lou6tdAwXmxujg7ajJ3C20Hl/VRTedRCwRpZ29emtYXvd2GqZYH9T1MGvwRnfZxP WCvkNPJlTXtc3QMd7XD2c+7kvLdRP80eZbGCHziHuHYU9HY8laH8gqeiIuAHvzLnC9R5 qCcA5xvgTu57fGO2DqnkXSb4I2+CipHXLYNs1peNJF0jxbeWGON5HFGxf35KKwT2Z/oX I99/dAL14L5LUELh1VSVkSnsMAb40oM+2whUv3kiyvVprAtFaf86v3ezWPAjfCBfP9qp HcSdKtoDRfakH13jXDxZm8E6/tYuGqhvlLNCvS8sKZqJzyQVZHPDsb1vd7+gMnwb+LzW vnAg== MIME-Version: 1.0 Received: by 10.152.131.3 with SMTP id oi3mr8975569lab.35.1333358706755; Mon, 02 Apr 2012 02:25:06 -0700 (PDT) Sender: rsb@berentweb.com Received: by 10.112.77.15 with HTTP; Mon, 2 Apr 2012 02:25:06 -0700 (PDT) X-Originating-IP: [85.110.29.196] In-Reply-To: <20120329072054.GA45082@server.vk2pj.dyndns.org> References: <20120329072054.GA45082@server.vk2pj.dyndns.org> Date: Mon, 2 Apr 2012 12:25:06 +0300 X-Google-Sender-Auth: gKesosWWU1bah-TLXdzQBcG_Y9U Message-ID: From: Beeblebrox To: freebsd-net@freebsd.org X-Gm-Message-State: ALoCoQmg2zenAceu9swA1SPHFvf5R9vU14ZjU5WcMpaAsKlZRt3+TfgTcpRfbJF5boKdbqcIFISS Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: lagg problems on diskless client 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:25:09 -0000 Hi, Peter. I had looked into failover with wireless and tried it before posting, but got nowhere. I delayed posting an answer because I needed to do more fiddleing; and I made some headwy, but still problems: 1. With below setup in diskless client's rc.conf, the client is able to boot and gets to login screen: ifconfig_re1="up ether 00:30:67:91:6c:c2" cloned_interfaces="lagg0" ifconfig_lagg0="up laggproto failover laggport re1 192.168.2.2 netmask 255.255.255.0" 2. ifconfig at that point shows all good: same mac addr and lagg0 active. re0: flags=8843 metric 0 mtu 1500 options=8209b ether 00:30:67:91:6c:c2 inet 192.168.2.2 netmask 0xffffff00 broadcast 192.168.2.255 media: Ethernet autoselect (100baseTX ) status: active re1: flags=8843 metric 0 mtu 1500 options=8209b ether 00:30:67:91:6c:c2 media: Ethernet autoselect (1000baseT ) status: active lagg0: flags=8843 metric 0 mtu 1500 options=8209b ether 00:30:67:91:6c:c2 media: Ethernet autoselect status: active laggproto failover laggport: re1 flags=5 Now if I go and unplug NIC10/100 on diskless client and "list folder", the client will freeze - so failover does not switch. After some time passes, client informs that NFS server 192.168.2.1 is not responding. PS- I mistakenly double-posted: http://docs.freebsd.org/cgi/getmsg.cgi?fetch=39210+0+current/freebsd-net *************************************************************** On Thu, Mar 29, 2012 at 10:20 AM, Peter Jeremy wrote: > On 2012-Mar-28 13:16:06 +0300, "Raif S. Berent" wrote: > >I have some problems implementing lagg(4) on dual NIC's on the diskless > >client side. It may be because my switch is a cheap, un-managed Gbit > switch > >or hopefully some other reason. I would like to either get lagg working > >properly or find an alternative method of solving the problem. > > Whilst I haven't specifically done this, I have done diskless booting > on a wired NIC and then switched to a wired/wifi lagg. Have a look at > http://www.bugs.au.freebsd.org/dokuwiki/doku.php/laggdiskless > > >I concede that under this structure lagg's loadbalance or LACP are > probably > >not going to work. > > FEC & LACP require support at both ends and so won't work. loadbalance > & roundrobin should work but aren't really appropriate unless your > interfaces are identical. > > >In general, as soon as lagg is brought up, NIC pool no longer responds to > >pings and gives an "I'm busy now" message. > > Yes. Once you create the lagg, the interfaces comprising it will no > longer work standalone and you can't atomically migrate the IP address > from re0 to lagg0 - hence the script linked from the above page. > > -- > Peter Jeremy >