From owner-freebsd-wireless@FreeBSD.ORG Mon Jul 29 13:11:17 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 ESMTP id 3406564F for ; Mon, 29 Jul 2013 13:11:17 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-we0-x22e.google.com (mail-we0-x22e.google.com [IPv6:2a00:1450:400c:c03::22e]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id BC3EB256F for ; Mon, 29 Jul 2013 13:11:16 +0000 (UTC) Received: by mail-we0-f174.google.com with SMTP id q54so3873363wes.5 for ; Mon, 29 Jul 2013 06:11:15 -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=Yn8JyojCDo3y9tsMUbAM9XZk4srIP+ztYUe3ZlBSpMs=; b=L1yWgbT4FIprUSHJKMdo62dptuYCqkX1BKRs1XPLwzVyNDv48ctLLT1Jc6ZkwNirzo 9NU3bdf+KRoV2uKd0Da3VgbRSCUCx6mEU3N/AETagWkZ6fXLYCfxXnbcAqRT0n3IKo4s +uQESB5aK3iA1rXFJGGbaBCHslmJcRZDGkZSYK8rOiUjSNWx4LnNwncF62zOIPHHXZ5C ABJD4xYZwsUuOQ2uARW76GHP5LanCi6hOG8Rk0V2g7bN4BYyoPoqJ/Wdt0xr8Gt1pzyG 6wQ3Hj3BItc+K1DQuJMpVlf/ilwX9ACCjEtlLjFJRsZ9nThIX376wtU22o08JbWbNZMv O75w== MIME-Version: 1.0 X-Received: by 10.180.39.212 with SMTP id r20mr7194233wik.30.1375103474996; Mon, 29 Jul 2013 06:11:14 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.217.94.132 with HTTP; Mon, 29 Jul 2013 06:11:14 -0700 (PDT) In-Reply-To: References: Date: Mon, 29 Jul 2013 06:11:14 -0700 X-Google-Sender-Auth: s4i2fd6R1Y1tMsSy2g4IxCuhtTk 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 13:11:17 -0000 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