From owner-freebsd-current@FreeBSD.ORG Tue Dec 17 15:54:53 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 866BFF04 for ; Tue, 17 Dec 2013 15:54:53 +0000 (UTC) Received: from mail-qc0-x234.google.com (mail-qc0-x234.google.com [IPv6:2607:f8b0:400d:c01::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 45E021143 for ; Tue, 17 Dec 2013 15:54:53 +0000 (UTC) Received: by mail-qc0-f180.google.com with SMTP id w7so5097438qcr.11 for ; Tue, 17 Dec 2013 07:54:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=j4qMLa7hjY7SMlScWtYAwibIyOerE0ZNFkZ5RhFNb7k=; b=g3WOoYeimdw+k7l0rsJTOJT3gvWNcNgCWCJ4PWwt+WGIStyuhNZM8CaaI43j71naXj KTvXiigEXrSJ9EJsrA5DJunHislZMVggQ3T0TbWy/mcOytMHIX4SghxQJQHarNXN+GNj Ms8KlH5tgAdbAA2c5SJH+Yq08PMvXfXMxmFvNe9KWPXDGpYFCZKOEFVaRc3terp1chGy iXGhgt6vS1SBgRU+B2Y+otqEYFgRia0t1KhdQYVkkNAEx6FGsJgjsGW8g71lkEsNuxkK E7p9ZoNzTPWNlQ8eYXA56FxiunmhbCJoENaVgi/LxoZ4TjsgAMG+oTMWqgo2u4Qw2RZt /EIQ== MIME-Version: 1.0 X-Received: by 10.49.131.5 with SMTP id oi5mr44470473qeb.38.1387295692320; Tue, 17 Dec 2013 07:54:52 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.224.53.200 with HTTP; Tue, 17 Dec 2013 07:54:52 -0800 (PST) In-Reply-To: <80a9ff942e0bf413ceaf9aa469b50687@rdsor.ro> References: <80a9ff942e0bf413ceaf9aa469b50687@rdsor.ro> Date: Tue, 17 Dec 2013 07:54:52 -0800 X-Google-Sender-Auth: -rxaV8ItNz04MUlKysJgpTlFbvk Message-ID: Subject: Re: 10-RC2 current wireless link aggregation not working correctly From: Adrian Chadd To: dan_partelly Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Dec 2013 15:54:53 -0000 Hi, The MAC of the lagg needs to be the same as the wireless interface. I'm going to just state right now that using lagg as the failover method for doing wireless/wired integration isn't supported by me. If someone wants to make it supported then they need to claim it. :) -a On 17 December 2013 05:06, dan_partelly wrote: > > Hi all, > > I've set up wireless link aggregation on FreeBSD 10 RC1 and RC2 as > described in the FreeBSD handbook, on an oldish Compaq nc6320 laptop. > > What happens is: > > If I boot the system with the Ethernet cable attached, I correctly get > lagg0 active port on master- bg0- and the network is working correctly. > (I mainly test pinging my gateway). When I pull the cable out, lagg0 > device correctly switches to wlan0 as shown by ifconfig (wlan0 is created > from wpi0), but at the same time I get no more ping replies from my > gateway. I can leave the system in this state for several minutes as an > example > and no replies are coming through. A simple list of interfaces with > ifconfig with no parameters brigs the network back to life, and I start to > get back the due ping replyes, this time thrugh wireless link. > > > Please, if possible en-light me on tis problem. I sat at your disposition > with any info you may deem necessary to get this fixed (if it needs a fix). > > > Dan > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"