From owner-freebsd-wireless@FreeBSD.ORG Sun Dec 8 05:33:21 2013 Return-Path: Delivered-To: freebsd-wireless@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 4EEFCA06 for ; Sun, 8 Dec 2013 05:33:21 +0000 (UTC) Received: from mail-qe0-x234.google.com (mail-qe0-x234.google.com [IPv6:2607:f8b0:400d:c02::234]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 07C4D134C for ; Sun, 8 Dec 2013 05:33:20 +0000 (UTC) Received: by mail-qe0-f52.google.com with SMTP id ne12so1805053qeb.39 for ; Sat, 07 Dec 2013 21:33:20 -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=PYi7rCurUx+Fe20af5fvcVww3aRxShzsQhevj1W1Y10=; b=c9n5xoJZqByV4PGZN/wF3AlUHFmv9OejwRH7KmU4FNFU31+AbppAUj32XRsZKeNod2 8AUT6SFDMw6cVBK+q5zTLWV5ET6bbqm3dHye5DjCz6Jy3B9JFyVSZsPpnGvJikDNebyE ODR5A7UlmoI/2VKeexnSN3nwFLVfiCZ2x7NaovGCwdtmqJ7gE5R/lBnlWjv8ePLnLnh3 1Qwu1iXZEZzcNDi5bOmqItlz5dHSSQggzmQTMnyXS7UanuT41WBjPQ+RTKne/4ANfUci csQ1sgf9PPS8UF0Oxwxr9PCORZVm4SmgGyFva1xg6Apr0sGUBnyrgZaI/rGQ3zfSPHuS 9Bug== MIME-Version: 1.0 X-Received: by 10.224.24.131 with SMTP id v3mr22379349qab.48.1386480800119; Sat, 07 Dec 2013 21:33:20 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.224.53.200 with HTTP; Sat, 7 Dec 2013 21:33:20 -0800 (PST) In-Reply-To: References: Date: Sat, 7 Dec 2013 21:33:20 -0800 X-Google-Sender-Auth: WowaRoBGjqXNRVX3fqH_20jQeko 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.17 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: Sun, 08 Dec 2013 05:33:21 -0000 Hi Monthadar and others, I'm starting to tackle this again. -a On 29 July 2013 06:11, Adrian Chadd wrote: > So what's the specific difference between normal station and meshSTA? > > > > -adrian > > On 29 July 2013 03:24, Monthadar Al Jaberi wrote: >> On Mon, Jul 29, 2013 at 5:32 AM, Adrian Chadd wrote: >>> 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 >> >> Yupp, the 80211 queue per meshSTA neighbour part is important if we >> want to queue in net80211, and that what Linux have. >> >>> * 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 >> >> Correct. >> >>> * 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? >> >> Sounds music to my ears =) >> >> Let's go for it! >> >>> >>> >>> >>> -adrian >> >> >> >> -- >> Monthadar Al Jaberi