From owner-freebsd-wireless@FreeBSD.ORG Mon Jul 29 03:32:31 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id C86B1163 for ; Mon, 29 Jul 2013 03:32:31 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wg0-x233.google.com (mail-wg0-x233.google.com [IPv6:2a00:1450:400c:c00::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 5D4B028A7 for ; Mon, 29 Jul 2013 03:32:31 +0000 (UTC) Received: by mail-wg0-f51.google.com with SMTP id a12so640128wgh.6 for ; Sun, 28 Jul 2013 20:32:29 -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=4geWeUT1L55OQXyc+X4+pOyPRlmOHU+/TFlctDpvQ/g=; b=sAXdU2sMDaPlO/fr/PRbqk3tDlJl/9PMV1Qxma5EM+PQNhMizVMuZ/nVnZ6a/Gozx6 TZ6vEezPSjQETerLEdIH+Ok6KiKmQSPPhZF/ei4j40pW5uip4myBfPb7OwpvAqf/MP5x peQS+qyLTcYcqBVLgItvfRFdo1+iGeVzU5RFlgb0MwrVOQqkCe/7B5r0GzyeqQ6gTHkK Zi2uShesc6GxzV+0820rInNT5eHxRVazbLVlP5kij0sN8ueqKDpx+RmaIj4FLFvnr68W Sn30Y+Z9OquF5/uwaP4dIqhKnKWY0MvEQKfQf6MoKfMDr6GuAULEPaSvHvfvbCeh4Qv7 OluQ== MIME-Version: 1.0 X-Received: by 10.180.14.105 with SMTP id o9mr5725298wic.30.1375068749520; Sun, 28 Jul 2013 20:32:29 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.217.94.132 with HTTP; Sun, 28 Jul 2013 20:32:29 -0700 (PDT) In-Reply-To: References: Date: Sun, 28 Jul 2013 20:32:29 -0700 X-Google-Sender-Auth: FTKqaBINR2Yk11Nn9CaZ1T0k_3Y Message-ID: Subject: Re: [802.11s] mesh_forward() and (re)-encapsulating frames From: Adrian Chadd To: Monthadar Al Jaberi Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 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, 29 Jul 2013 03:32:31 -0000 Hi, * I think we can get away with one queue per mesh STA neighbor for now. Which is effectively what we have in ath(4) and we will have in net80211 soon * THanks for the clarification for mesh sequence number. So we: + Increment it if we're generating a frame into the mesh network; + Keep it the same if we're forwarding a frame to a mesh peer / mesh gate * If we store the mesh control header in the mbuf, and de-encapsulate the frame, then re-inject into the VAP path with the correct destination node, we could then teach the VAP path to check for that tag and if it's there, populate the mesh header from _that_. If it's not there, we create a new mesh tag and continue the encapsulation phase. How's that sound? -adrian