From owner-freebsd-net@FreeBSD.ORG Fri Oct 19 06:53:22 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 F30B1F3F for ; Fri, 19 Oct 2012 06:53:21 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-pa0-f54.google.com (mail-pa0-f54.google.com [209.85.220.54]) by mx1.freebsd.org (Postfix) with ESMTP id C0EF48FC0A for ; Fri, 19 Oct 2012 06:53:21 +0000 (UTC) Received: by mail-pa0-f54.google.com with SMTP id bi1so148914pad.13 for ; Thu, 18 Oct 2012 23:53:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=uEnKUqssRp4PjGfZ0pIJ93+U5sajYSJCSzW/wTkqC9s=; b=cfCFhw0lvTgvx8b4kcaH7qPugDGVsij8DninMpZVl4BCpu3rPMDgEDN7zpKEgYTiqC 7l/RIKGTAzVK/ByhmaIuPs6gJS+X7uLYj5o3oW/nNIqnfxyaOjgoRHBiIi5Q7RsEVrah Kn5sYcW3oDoRHptk7Iv8Tbwo/AWiSO2JhcZS6c6UM9+cjS5jcuSWOETHFB5INoN2if3Q iJFn7o8WXS7pHtZ1rEOSt/kv/NENZGrWznikhQgac99w88Xv6cvlZBXb/6nDly/0JUU4 wCMELqLUP1EorvGvbLvN1KiCUEC5n3yp798xGZ05gYT/B/+SDVNMz47RqckzIHFASSfh kCyA== MIME-Version: 1.0 Received: by 10.68.229.138 with SMTP id sq10mr2509879pbc.126.1350629601239; Thu, 18 Oct 2012 23:53:21 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.68.146.233 with HTTP; Thu, 18 Oct 2012 23:53:21 -0700 (PDT) In-Reply-To: <2529.1350620676@tristatelogic.com> References: <2529.1350620676@tristatelogic.com> Date: Thu, 18 Oct 2012 23:53:21 -0700 X-Google-Sender-Auth: tJqo2dGfIP6XUI-VIWyWmZotzH0 Message-ID: Subject: Re: Wireless Networking Bug(s) in 9.1-RC2 (?) From: Adrian Chadd To: "Ronald F. Guilmette" Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-net@freebsd.org, Kevin Oberman X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Oct 2012 06:53:22 -0000 The obscure answer has to do with what the L2 adjacency stuff is doing. Because it adds that default route out a specific interface, it will send ARP requests out that. Even if the other interface goes down, it'll still throw them out that interface. It's just a side effect of how the L2 adjacency stuff works. Adrian