From owner-freebsd-wireless@FreeBSD.ORG Mon Jan 9 19:43:40 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 49FC7106566C for ; Mon, 9 Jan 2012 19:43:40 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-vx0-f182.google.com (mail-vx0-f182.google.com [209.85.220.182]) by mx1.freebsd.org (Postfix) with ESMTP id 038698FC0C for ; Mon, 9 Jan 2012 19:43:39 +0000 (UTC) Received: by vcbfk1 with SMTP id fk1so4626998vcb.13 for ; Mon, 09 Jan 2012 11:43:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=YXMBUPg1VdHipZmOjC3pEwV0NIOa02ddn/9oaitqiGE=; b=iFMY5+Fv692ft7uVAwKuZnCGJEkU1oSiSd44mYQVmNdbGrkhOnhj81FbLRQVabEiI+ gFPJw9UuejqyI5Ilf0DLZHCqqwc45412TxfLUgPVNdHCii/u7ojJ+JIFZnJf0SNrk+k5 ker62CtDdWMwN8JgnT2aTpeB7wWBErKbfXDYA= MIME-Version: 1.0 Received: by 10.220.156.134 with SMTP id x6mr10032596vcw.17.1326138219407; Mon, 09 Jan 2012 11:43:39 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.52.36.5 with HTTP; Mon, 9 Jan 2012 11:43:39 -0800 (PST) In-Reply-To: References: Date: Mon, 9 Jan 2012 11:43:39 -0800 X-Google-Sender-Auth: 8GH4TAGh3ggN1ZPviyovpJ0_ILQ Message-ID: From: Adrian Chadd To: Monthadar Al Jaberi Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org Subject: Re: kick mesh node X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Jan 2012 19:43:40 -0000 Hi, That sounds fine. On 9 January 2012 09:09, Monthadar Al Jaberi wrote: > Hi, > > I dont know if this is the correct way to do it. > > if you run "ifconfig wlan0 mac:kick address" you will get Invalid > argument error because there is no code for MBSS. > > This is patch makes it possible to kick a mesh node, useful when for > example you have some entries left "dead" in your table awaiting node > reclaim timeout. > > Because there is no auth/assoc code for mesh I guess this is enough > (maybe we can try to send CLOSE LINK to the entry we kick so that it > updates its entries?): That also sounds like a good idea for a future project. I wonder if these ioctls should be broken out per-VAP.. Adrian