From owner-freebsd-net@freebsd.org Thu Nov 17 01:52:35 2016 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 52FD8C458E4 for ; Thu, 17 Nov 2016 01:52:35 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-vk0-x22d.google.com (mail-vk0-x22d.google.com [IPv6:2607:f8b0:400c:c05::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0B19C1933 for ; Thu, 17 Nov 2016 01:52:35 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: by mail-vk0-x22d.google.com with SMTP id w194so130414843vkw.2 for ; Wed, 16 Nov 2016 17:52:35 -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:from:date:message-id :subject:to:cc; bh=xDwE8P4+RyAbVCfhYm1UANhz4Cy2kGUtY1ALxdrxav0=; b=Ljr2sZDJSG3StRzVVNiwc2HxJnjIo3MmzWSZcUGzXip1kncVLlAknqoj/T8Ficd3Rw S3LTVHhx/LPCcnEj2dFivNL96ACSIPUZ4UYJ+WCUs36hjF+JHqfqD/Ye2Ws8rMDjlR7A IDxhRXRp3BoIoIU9S2J+NUl9uQ/Rpep1fQMalwQvGOvq2GQkW7YVZqCa762qF5dKzaDA uIzofXlUmaKytJNsmExTlcKOtl3O1BI0hKv0qiL3I9Rp44DuApBL/EfL1tm26Fzs0jPc YeKcPAIRFt/imzUoyO1MGspMKE1MvRfiWXX8jacG0y0gUHjQv6czb7ivusxfpQYybW0x 1WBA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=xDwE8P4+RyAbVCfhYm1UANhz4Cy2kGUtY1ALxdrxav0=; b=lpdJtw1fgvuOOPqisqExTCAUn8ZLRAFtk5Ud7RCZ0vPWwI/PHuCBKWpvLG7ShW2BLU YA/XY11KpQEJCeFES+gHsBotwcqEqpsNmB/INi5/YLR4w4tro6prG6xdzKf7bjHldozy qRjre8CyIUxyai7SwiuJYHnCJXyaWUrJ1kIUPf/EXfMJQ3vagVzh/+27SDCZxls759cR I7WQFnCkSzQrySLbicDPiDzBZ//SVgc7DjsBRCYb6JkoVnTQzrBDqNZf8Gs30WPJfdCa 3efS7fyP+O6Tghop1yGMb5HcEoY5G8kOy9aXIan1zvNHl7DhuBpoxrTkXLIc2z/D/gqi aJZg== X-Gm-Message-State: AKaTC01gYaRdUme8Sp8GbWgJ4KuGYlmRYKanN4F40B8jWF3ycsF21zFqP4gheLP/2q3R50zaHuU9BUkrZwk9rQ== X-Received: by 10.31.237.131 with SMTP id l125mr322572vkh.56.1479347554124; Wed, 16 Nov 2016 17:52:34 -0800 (PST) MIME-Version: 1.0 Sender: kob6558@gmail.com Received: by 10.103.119.79 with HTTP; Wed, 16 Nov 2016 17:52:33 -0800 (PST) In-Reply-To: <20161116113435.72014@relay.ibs.dn.ua> References: <20161018144313.45827@relay.ibs.dn.ua> <20161018141513.4936f1ea@shibato> <20161018201040.72694@relay.ibs.dn.ua> <20161116113435.72014@relay.ibs.dn.ua> From: Kevin Oberman Date: Wed, 16 Nov 2016 17:52:33 -0800 X-Google-Sender-Auth: He4NPvJwsJejTlMpAg2ITPRJPd4 Message-ID: Subject: Re: is lagg (re+wlan) working on 11.0-RELEASE? To: Zeus Panchenko Cc: "freebsd-net@freebsd.org" Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.23 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Nov 2016 01:52:35 -0000 On Wed, Nov 16, 2016 at 1:34 AM, Zeus Panchenko wrote: > thanks for quick reply > > J.R. Oldroyd wrote: > > There is a work-around. Configure the re interface with the MAC > > address of the wlan instead of the other way around. > > I done it and here is what happens: > > 1. I boot notebook with wire *not* plugged in, > wlan is up, associated and authed, network is OK > > 2. I plug wire and network becomes stale > > 3. I run `tcpdump -ni lagg0' to see what's going on and oh wonder, > network comes back lo life! > > > so ... either to not to use lagg or run tcpdump constantly ... it is > rather weird :( > > -- > Zeus V. Panchenko jid:zeus@im.ibs.dn.ua > IT Dpt., I.B.S. LLC GMT+2 (EET) > A bit odd, but not weird. Running tcpdump turns on promiscuous mode. Try "tcpdump -p" and I'm pretty sure it will not make any difference. The real question is where the fault lies. It looks like the problem may be in the re(4) driver. It looks to me like the "new" MAC address is not getting properly instantiated so that packets to that MAC address are being ignored. It is also possible that the packets are being sent to the correct IP address, but the wrong MAC. (Pretty unlikely, though.) What does ipconfig re0 show? Is the MAC correct? Capture traffic (tcpdump -pe dst host LAGG-IP-ADDRESS) and confirm that the MAC and IP addresses are correct. If they are, the issue is either hardware or the driver. Since re-writing the MAC is a fairly uncommon operation so it is possible that the firmware has an issue and it may be specific to a less common re variant. Of course, slight differences in hardware revisions can trigger driver issues that don't break things on most variants. And, lest I knew, RealTek did not provide documentation adequate to write a driver and this makes drivers more likely to have subtle bugs. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkoberman@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683