From owner-freebsd-wireless@FreeBSD.ORG Sun Jul 7 08:21:02 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id C4044C50; Sun, 7 Jul 2013 08:21:02 +0000 (UTC) (envelope-from hiren.panchasara@gmail.com) Received: from mail-ee0-x22c.google.com (mail-ee0-x22c.google.com [IPv6:2a00:1450:4013:c00::22c]) by mx1.freebsd.org (Postfix) with ESMTP id 336571953; Sun, 7 Jul 2013 08:21:02 +0000 (UTC) Received: by mail-ee0-f44.google.com with SMTP id c13so2163420eek.17 for ; Sun, 07 Jul 2013 01:21:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=LUmO7P82aFDJudSgCw5fCQ/GRSJfI9IvlOjr9nEdAoo=; b=W+jzG2T7IW+FxuMDp/qBnEbewl3OdlF/FZhphBQaj1w9zIoCCsn4bZ09W2xQtv7pUY W66iqPs/hML77qP5wu35fxeH/46rF/qsPRlpOWyTiGfqL1OaO0DfSPhJB4FAY++8/K7/ oSZGWs5uSeCgNYnY2KvrqoscmJdT7gYeSDq0ze5VLVLpo5Dc7bJLGwHe7M6vynjc740+ dXKtyk8NCQaaCWjOvCAf/LeU76rKQ1LzEngxHIC8h6mzJAI1UVGRZEtXx08VChyD41ls WSkAE0/0ueuE9GJ/FyWWfsEgdj0SdkvGOg9kw7P6ZZevB0XYFKi0pGudAHSn2FAxeT2D +wVQ== MIME-Version: 1.0 X-Received: by 10.14.1.70 with SMTP id 46mr19704720eec.82.1373185260660; Sun, 07 Jul 2013 01:21:00 -0700 (PDT) Received: by 10.14.119.203 with HTTP; Sun, 7 Jul 2013 01:21:00 -0700 (PDT) In-Reply-To: <1373026721.13264.YahooMailNeo@web160106.mail.bf1.yahoo.com> References: <7671255B-5582-428A-8ADC-3DF7AA32C772@FreeBSD.org> <8819701.20130630194938@serebryakov.spb.ru> <192717829.20130703121844@serebryakov.spb.ru> <51D42F29.6010609@yahoo.com> <1372988069.39151.YahooMailNeo@web160101.mail.bf1.yahoo.com> <78276777-F786-47DF-A7A4-A574809E97CD@FreeBSD.org> <1372988865.53918.YahooMailNeo@web160101.mail.bf1.yahoo.com> <1373026721.13264.YahooMailNeo@web160106.mail.bf1.yahoo.com> Date: Sun, 7 Jul 2013 01:21:00 -0700 Message-ID: Subject: Re: CFT: wpa_supplicant/hostapd import patch From: hiren panchasara To: Rui Paulo Content-Type: text/plain; charset=UTF-8 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: Sun, 07 Jul 2013 08:21:02 -0000 After this change I've started getting following messages: flymockour-l7% grep rekeying /var/log/messages | less Jul 6 12:09:52 flymockour-l7 wpa_supplicant[1153]: wlan0: WPA: Group rekeying completed with 00:24:b2:50:7c:38 [GTK=TKIP] Jul 6 12:19:52 flymockour-l7 wpa_supplicant[1153]: wlan0: WPA: Group rekeying completed with 00:24:b2:50:7c:38 [GTK=TKIP] Jul 6 12:29:52 flymockour-l7 wpa_supplicant[1153]: wlan0: WPA: Group rekeying completed with 00:24:b2:50:7c:38 [GTK=TKIP] Jul 6 12:39:50 flymockour-l7 wpa_supplicant[1153]: wlan0: WPA: Group rekeying completed with 00:24:b2:50:7c:38 [GTK=TKIP] so, every 10 mins I am getting these messages. I am not sure if this (rekeying) is something wpa2 is enforcing. Is anyone else getting such messages? Does it make sense to move this message from MSG_INFO to MSG_DEBUG? cheers, Hiren flymockour-l7% svn diff Index: contrib/wpa/src/rsn_supp/wpa.c =================================================================== --- contrib/wpa/src/rsn_supp/wpa.c (revision 252757) +++ contrib/wpa/src/rsn_supp/wpa.c (working copy) @@ -1348,7 +1348,7 @@ goto failed; if (rekey) { - wpa_msg(sm->ctx->msg_ctx, MSG_INFO, "WPA: Group rekeying " + wpa_msg(sm->ctx->msg_ctx, MSG_DEBUG, "WPA: Group rekeying " "completed with " MACSTR " [GTK=%s]", MAC2STR(sm->bssid), wpa_cipher_txt(sm->group_cipher)); wpa_sm_cancel_auth_timeout(sm); From owner-freebsd-wireless@FreeBSD.ORG Sun Jul 7 19:25:47 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id A59D44BE for ; Sun, 7 Jul 2013 19:25:47 +0000 (UTC) (envelope-from rpaulo@freebsd.org) Received: from felyko.com (felyko.com [174.136.100.2]) by mx1.freebsd.org (Postfix) with ESMTP id 8C9451159 for ; Sun, 7 Jul 2013 19:25:47 +0000 (UTC) Received: from [IPv6:2601:9:4d00:119:b446:8df4:1336:11e1] (unknown [IPv6:2601:9:4d00:119:b446:8df4:1336:11e1]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by felyko.com (Postfix) with ESMTPSA id EE5223982B; Sun, 7 Jul 2013 12:25:45 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\)) Subject: Re: CFT: wpa_supplicant/hostapd import patch From: Rui Paulo In-Reply-To: Date: Sun, 7 Jul 2013 12:25:45 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: <8651A2AF-2AAE-4E3D-9BB7-8246D9C5AC47@freebsd.org> References: <7671255B-5582-428A-8ADC-3DF7AA32C772@FreeBSD.org> <8819701.20130630194938@serebryakov.spb.ru> <192717829.20130703121844@serebryakov.spb.ru> <51D42F29.6010609@yahoo.com> <1372988069.39151.YahooMailNeo@web160101.mail.bf1.yahoo.com> <78276777-F786-47DF-A7A4-A574809E97CD@FreeBSD.org> <1372988865.53918.YahooMailNeo@web160101.mail.bf1.yahoo.com> <1373026721.13264.YahooMailNeo@web160106.mail.bf1.yahoo.com> To: hiren panchasara X-Mailer: Apple Mail (2.1508) 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: Sun, 07 Jul 2013 19:25:47 -0000 On 7 Jul 2013, at 01:21, hiren panchasara = wrote: > After this change I've started getting following messages: >=20 > flymockour-l7% grep rekeying /var/log/messages | less > Jul 6 12:09:52 flymockour-l7 wpa_supplicant[1153]: wlan0: WPA: Group > rekeying completed with 00:24:b2:50:7c:38 [GTK=3DTKIP] > Jul 6 12:19:52 flymockour-l7 wpa_supplicant[1153]: wlan0: WPA: Group > rekeying completed with 00:24:b2:50:7c:38 [GTK=3DTKIP] > Jul 6 12:29:52 flymockour-l7 wpa_supplicant[1153]: wlan0: WPA: Group > rekeying completed with 00:24:b2:50:7c:38 [GTK=3DTKIP] > Jul 6 12:39:50 flymockour-l7 wpa_supplicant[1153]: wlan0: WPA: Group > rekeying completed with 00:24:b2:50:7c:38 [GTK=3DTKIP] >=20 >=20 > so, every 10 mins I am getting these messages. >=20 > I am not sure if this (rekeying) is something wpa2 is enforcing. Is > anyone else getting such messages? >=20 > Does it make sense to move this message from MSG_INFO to MSG_DEBUG? >=20 > cheers, > Hiren >=20 > flymockour-l7% svn diff > Index: contrib/wpa/src/rsn_supp/wpa.c > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > --- contrib/wpa/src/rsn_supp/wpa.c (revision 252757) > +++ contrib/wpa/src/rsn_supp/wpa.c (working copy) > @@ -1348,7 +1348,7 @@ > goto failed; >=20 > if (rekey) { > - wpa_msg(sm->ctx->msg_ctx, MSG_INFO, "WPA: Group = rekeying " > + wpa_msg(sm->ctx->msg_ctx, MSG_DEBUG, "WPA: Group = rekeying " > "completed with " MACSTR " [GTK=3D%s]", > MAC2STR(sm->bssid), = wpa_cipher_txt(sm->group_cipher)); > wpa_sm_cancel_auth_timeout(sm); Feel free to commit this. -- Rui Paulo From owner-freebsd-wireless@FreeBSD.ORG Sun Jul 7 19:34:03 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id EBE975EF; Sun, 7 Jul 2013 19:34:03 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-pb0-x234.google.com (mail-pb0-x234.google.com [IPv6:2607:f8b0:400e:c01::234]) by mx1.freebsd.org (Postfix) with ESMTP id C17CA1183; Sun, 7 Jul 2013 19:34:03 +0000 (UTC) Received: by mail-pb0-f52.google.com with SMTP id xa12so3565747pbc.25 for ; Sun, 07 Jul 2013 12:34:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:to:cc:reply-to:subject:in-reply-to:x-mailer :mime-version:content-type; bh=XuDR6Wdkl7bqqA51pfvWEqh2Cx0wnJkfx0d/7uDL780=; b=bl0EASpfhMJgGIponYUwZNSRZUHTW8yF8YE+t3YLF+ghT0WUquvj+2IBVuticDHfs1 A1fI/kbgkkQHJPjubS8PALa/kAhzTMKo6INPFc4ghpUCjkowezIcqxD0XYm1TF7zULcD fxO3vM1rH3RFAd0/5tg03UooVxos34aB6slejw9ZrsYZUlc79ArJF/SpFbQ8qQMlXaDn CRqBp1qIuUdhY49a+dHOsR7nwY+lmO1J/W+gJmxGGzvk8Xk2k+0ZyjftHBOaHh5Qp9Qw 7xCZ6YE0v+c5X5y8NFOEIw/LjEN+ac5Y3g8hEH0olN36WrR3AwItF2omNoemmInu3fIz 2eJw== X-Received: by 10.66.249.202 with SMTP id yw10mr19622791pac.145.1373225643473; Sun, 07 Jul 2013 12:34:03 -0700 (PDT) Received: from www.palm.com (50-197-170-142-static.hfc.comcastbusiness.net. [50.197.170.142]) by mx.google.com with ESMTPSA id qu10sm18380610pbb.12.2013.07.07.12.33.59 for (version=TLSv1 cipher=RC4-SHA bits=128/128); Sun, 07 Jul 2013 12:34:02 -0700 (PDT) Message-ID: <51d9c2aa.0a8b440a.34ef.0ce1@mx.google.com> Date: Sun, 7 Jul 2013 07:16:37 -0700 From: "Adrian Chadd" To: "Rui Paulo" , "hiren panchasara" Subject: Re: CFT: wpa_supplicant/hostapd import patch In-Reply-To: <8651A2AF-2AAE-4E3D-9BB7-8246D9C5AC47@freebsd.org> X-Mailer: Palm webOS v1.0.1 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Adrian Chadd 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, 07 Jul 2013 19:34:04 -0000 Yup, commit away! -adrian Sent from my Palm Pre on AT&T On Jul 7, 2013 12:25 PM, Rui Paulo <rpaulo@freebsd.org> wrote:=20 On 7 Jul 2013, at 01:21, hiren panchasara <hiren.panchasara@gmail.com>= ; wrote: > After this change I've started getting following messages: >=20 > flymockour-l7% grep rekeying /var/log/messages | less > Jul 6 12:09:52 flymockour-l7 wpa_supplicant[1153]: wlan0: WPA: Group > rekeying completed with 00:24:b2:50:7c:38 [GTK=3DTKIP] > Jul 6 12:19:52 flymockour-l7 wpa_supplicant[1153]: wlan0: WPA: Group > rekeying completed with 00:24:b2:50:7c:38 [GTK=3DTKIP] > Jul 6 12:29:52 flymockour-l7 wpa_supplicant[1153]: wlan0: WPA: Group > rekeying completed with 00:24:b2:50:7c:38 [GTK=3DTKIP] > Jul 6 12:39:50 flymockour-l7 wpa_supplicant[1153]: wlan0: WPA: Group > rekeying completed with 00:24:b2:50:7c:38 [GTK=3DTKIP] >=20 >=20 > so, every 10 mins I am getting these messages. >=20 > I am not sure if this (rekeying) is something wpa2 is enforcing. Is > anyone else getting such messages? >=20 > Does it make sense to move this message from MSG_INFO to MSG_DEBUG? >=20 > cheers, > Hiren >=20 > flymockour-l7% svn diff > Index: contrib/wpa/src/rsn_supp/wpa.c > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > --- contrib/wpa/src/rsn_supp/wpa.c (revision 252757) > +++ contrib/wpa/src/rsn_supp/wpa.c (working copy) > @@ -1348,7 +1348,7 @@ > goto failed; >=20 > if (rekey) { > - wpa_msg(sm->ctx->msg_ctx, MSG_INFO, "WPA: Group= rekeying " > + wpa_msg(sm->ctx->msg_ctx, MSG_DEBUG, "WPA: Group= rekeying " > "completed with " MACSTR " [GTK=3D%s]", > MAC2STR(sm->bssid), wpa_cipher_txt(sm->gr= oup_cipher)); > wpa_sm_cancel_auth_timeout(sm); Feel free to commit this. -- Rui Paulo _______________________________________________ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.org" From owner-freebsd-wireless@FreeBSD.ORG Sun Jul 7 19:42:09 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 72E3376D; Sun, 7 Jul 2013 19:42:09 +0000 (UTC) (envelope-from hiren.panchasara@gmail.com) Received: from mail-ea0-x234.google.com (mail-ea0-x234.google.com [IPv6:2a00:1450:4013:c01::234]) by mx1.freebsd.org (Postfix) with ESMTP id D985E11D6; Sun, 7 Jul 2013 19:42:08 +0000 (UTC) Received: by mail-ea0-f180.google.com with SMTP id k10so2543537eaj.11 for ; Sun, 07 Jul 2013 12:42:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=tmL2rHMCvsoAAC9FbfmdmqC3fWJXw4IUQvt5Jb+4j0I=; b=gXcn3o7vFSq+nMxV2f7Hdj0IP/QfUa+P2tuWx10VAwgo5T4pVHGle3CM4R9RDTaFUW PuyrhTQ07gmugHrr25vUNN+Bt6s62kY2xkkoCjsi/cVQQ4aAWYs1jObJDHA/cs+8KEtI dm6zk0lBYE/OTkBWLW6VkgJGkdGtUI2zzQcd7kPtq5V2nA79NDEwVh5OdUKbzpT4T9Fu 8TFbNbzxWE8V5W/7kNuO32eZ/Wbhikhd0s+Vvzqez+KIyXAPv14ov3kS1E0ZfCEQ9Aja p8tHSJxT4fvYaZLgNDIHEavGu/qaJMyI9vbcysozA7Of8q3Zo0Ty3nmiZnWSfiiYKXTL c5vA== MIME-Version: 1.0 X-Received: by 10.14.48.77 with SMTP id u53mr21148560eeb.154.1373226127879; Sun, 07 Jul 2013 12:42:07 -0700 (PDT) Received: by 10.14.119.203 with HTTP; Sun, 7 Jul 2013 12:42:07 -0700 (PDT) In-Reply-To: <51d9c2aa.0a8b440a.34ef.0ce1@mx.google.com> References: <8651A2AF-2AAE-4E3D-9BB7-8246D9C5AC47@freebsd.org> <51d9c2aa.0a8b440a.34ef.0ce1@mx.google.com> Date: Sun, 7 Jul 2013 12:42:07 -0700 Message-ID: Subject: Re: CFT: wpa_supplicant/hostapd import patch From: hiren panchasara To: Adrian Chadd Content-Type: text/plain; charset=UTF-8 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: Sun, 07 Jul 2013 19:42:09 -0000 On Sun, Jul 7, 2013 at 7:16 AM, Adrian Chadd wrote: > > Yup, commit away! > > > > -adrian > > > Feel free to commit this. > > -- > Rui Paulo Will commit it. Thanks, Hiren > > _______________________________________________ > freebsd-wireless@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.org" From owner-freebsd-wireless@FreeBSD.ORG Sun Jul 7 20:58:44 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 56394E1 for ; Sun, 7 Jul 2013 20:58:44 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-qc0-x235.google.com (mail-qc0-x235.google.com [IPv6:2607:f8b0:400d:c01::235]) by mx1.freebsd.org (Postfix) with ESMTP id 1D767166B for ; Sun, 7 Jul 2013 20:58:44 +0000 (UTC) Received: by mail-qc0-f181.google.com with SMTP id u12so1935013qcx.26 for ; Sun, 07 Jul 2013 13:58:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:x-google-sender-auth:message-id:subject :from:to:content-type; bh=LL8696QImmPG1CQzzxLBw9wI7J9cklODie7lVc7NFNs=; b=tazYH0yrMr8co3bNrvPbc2vUeAVlBRs5dsE7SNc1Bu+q7XyhjmjKgl6/BcbeDAwsB0 Fd97sKdUHPgKcMs0kfcGpIXEihpDn+PKXXaPI/GC0xLfwClZyc9MxLIzsrdqu9vPiC7m qEmsna75BbtCV2veJ1cODJrqssKmxhH7P57j2tYa9BkODV8lDOH097ouPfVyGf/aXGfR EQ+g/RLicCnYzJUF/lG/RDhUgzulJwm0VP5d/S2eTAMP7LD3NDoWsqmCWz3zrkHhoiDH a6lYTKFWzztEvMwXADVUMZYFY0y749/fqnzJbORcaGbK4ceT83e0sf9sSzx6eCW2gIhV Vb1g== MIME-Version: 1.0 X-Received: by 10.224.5.199 with SMTP id 7mr1275860qaw.87.1373230722697; Sun, 07 Jul 2013 13:58:42 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.195.72 with HTTP; Sun, 7 Jul 2013 13:58:42 -0700 (PDT) Date: Sun, 7 Jul 2013 13:58:42 -0700 X-Google-Sender-Auth: dMM6uHHgVP9c6SX0OhOx1AIwZTM Message-ID: Subject: [802.11s] mesh_forward() and (re)-encapsulating frames From: Adrian Chadd To: freebsd-wireless@freebsd.org, Monthadar Al Jaberi Content-Type: text/plain; charset=ISO-8859-1 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: Sun, 07 Jul 2013 20:58:44 -0000 Hi monthadar (and others), I'm tidying up the 802.11s TX path in preparation to support 802.11n, encryption, power-save handling, aggregation/fast-frames and other such loveliness. In order to do this, the 802.11s TX path needs to use the existing VAP methods to encapsulate and queue frames rather than directly queuing to the parent device (ie, the physical device itself.) Because it bypasses the normal encap path, it doesn't give the transmit path the opportunity to do all the above handling. I've fixed this for all but the mesh_forward() path. In this case it just fiddles with the mesh header, selects a new destination and sends it to the physical interface. This assumes the frame is already encapsulated from the receive path and it _completely_ uses the contents of the existing frame before doing this. It bypasses all processing. I've talked with monthadar about this in the past but we didn't come up with an easy, satisfactory change to make this feasible. I'm now at the point where I'd like to implement this. I'd like to take the existing frame, store the mesh header somewhere, de-encapsulate it, then re-encapsulate it with the correct mesh information. But I don't know how the mesh forwarding is supposed to work. So, Monthadar (and others), what's supposed to happen with a mesh frame being forwarded to another gateway? * What's supposed to happen to the mesh sequence number? * What's supposed to happen to the QoS header sequence number? (ie, the sequence number space between the two peers) * What's supposed to happen for encryption? is it end-to-end encryption, or hop-by-hop encryption? Can I just get away with extending ieee80211_encap() to take a meshcntl header and if I provide it, just use that instead of calculating the contents in ieee80211_encap()? I think that'll be good enough to get around the data path requirements and we can get back on track getting this stuff ready for 802.11n and encryption. Thanks! -adrian From owner-freebsd-wireless@FreeBSD.ORG Mon Jul 8 11:41:12 2013 Return-Path: Delivered-To: freebsd-wireless@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 16E1258C for ; Mon, 8 Jul 2013 11:41:12 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id EED6C15D6 for ; Mon, 8 Jul 2013 11:41:11 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id r68BeXgi053981 for ; Mon, 8 Jul 2013 11:41:11 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id r68B6i32046251 for freebsd-wireless@FreeBSD.org; Mon, 8 Jul 2013 11:06:44 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 8 Jul 2013 11:06:44 GMT Message-Id: <201307081106.r68B6i32046251@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-wireless@FreeBSD.org Subject: Current problem reports assigned to 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, 08 Jul 2013 11:41:12 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/179847 wireless [ath] [patch] Update regdomain in ath drivers includin o kern/179709 wireless [ath] Atheros 5212 does not work: stuck beacon; resett o kern/179547 wireless [ath] Add AR9485 custom board fixes (CUS198) o kern/179482 wireless [ath] [patch] Fix AR9462 external LNA configuration o kern/179269 wireless [ath] [AR9285] RX antenna diversity is not functioning o kern/179232 wireless [ath] panic in ath o kern/178986 wireless [ath] Change mac address of ath(4) is not reflected wh o kern/178492 wireless [ath] ath0 (AR9287) panic o kern/178491 wireless [ath] ath0 (AR9287) stuck beacon o kern/178477 wireless [ath] missed beacon / soft reset in STA mode results i o kern/178470 wireless [panic][ath] bss vap can and does change o kern/178411 wireless [ral] [panic] FreeBSD kernel crash in rt2860 o kern/178379 wireless [net80211] [ath] WPA rekey on the STA side fails when o kern/178378 wireless [net80211] crypto state isn't reset during a reassocia o kern/178263 wireless [ath] review the use of ic_freq / ic_ieee / ic_flags / o kern/177847 wireless [ath] With TPC enabled, TX power values aren't clamped o kern/177846 wireless [ath] [net80211] net80211 TX power limit isn't correct o conf/177688 wireless WiFi regodmains information is inconsistent between "e o kern/177530 wireless [ath] ath driver isn't 32 bit int clean o kern/177465 wireless [iwn] 20%-100% packet loss with iwn driver o kern/177451 wireless [ieee80211] page fault in ieee80211_tx_mgt_timeout o kern/176238 wireless [ath] [patch] Correct buffer size calculation and simp o kern/176201 wireless [net80211] [patch] 11n station includes unrelated ht p o kern/176104 wireless [iwn] iwn0: iwn_intr: fatal firmware error o kern/175722 wireless [ath]lot of bad seriesx hwrate in kernel messages o kern/175446 wireless [ath] high volumes of PHY errors lead to BB/MAC hangs o kern/175227 wireless [ath] beacon timers aren't necessarily reprogrammed af o kern/175183 wireless [iwn] iwn(4) becomes unresponsive during initial confi o kern/175053 wireless [iwn] iwn firmware error on 9-stable with Ultimate-N 6 o kern/174891 wireless [ieee80211] struct ieee80211_node is freed during acti o kern/174722 wireless [wlan] can't use channel 12 and 13 (14) with my wifi i o kern/174661 wireless [wlan] lost alias on wlan interface o kern/174283 wireless [net80211] panics in ieee80211_ff_age() and ieee80211_ o kern/174276 wireless [ath] if_ath memory modified after free o kern/174273 wireless [net80211] taking down a net80211 node with active fas o kern/173917 wireless [iwn] wpa-supplicant issues on iwn o kern/173898 wireless [iwn] [patch] iwn(4) DOES support 6235 chip. o kern/173883 wireless [ath] ath0: unable to attach - pci issue? o kern/173711 wireless [ath] powerd kills ath on the Asus EeePC 1005HA o kern/173342 wireless PS-Poll isn't working o kern/173336 wireless [ath] Atheros card improper device poweroff handling o o kern/172955 wireless [ath] 11n does not work in adhoc mode o kern/172706 wireless [wpi] wpi0 fails to load firmware when using country o kern/172672 wireless [ubt] Bluetooth device recognised but not working o kern/172661 wireless hostapd(8) securing wireless adapter in HostAP mode is o kern/172338 wireless [ath] [net80211] CCMP IV transmit counters are not cor o kern/171598 wireless [ath] TP-Link TL-WN951N W-LAN PCI Adapter 300 MBit stu o kern/171235 wireless [ath] ath loses connection, system freezes on netif re o kern/170889 wireless [ath] ath driver uses some uninitilized memory o kern/170620 wireless [ath] LOR and deadlock when multiple vaps are used o kern/170573 wireless [iwi] Intel 2200BG iwi NIC hangs with need multicast c o kern/170513 wireless [ath] ath logs: ath_tx_aggr_comp_aggr: AR5416 bug: o kern/170433 wireless [ath] TX hang after a stuck beacon message with active o kern/170397 wireless [ath] [patch] Uninitialized variables in ah_eeprom_928 o kern/170302 wireless [ath] 802.11n frames are not being transmitted with mu o kern/170281 wireless [ath] 802.11n locks up on aggregation setup (ampdutx) o kern/170098 wireless [ath] [net80211] VAPs (Virtual access points) with Ath o kern/170066 wireless [ral] ral(4) rt61pci Linksys freezes the machine as so o kern/169432 wireless [ath] BAR TX hang when aggregation session is reset du p kern/169362 wireless [ath] AR5416: radar pulse PHY errors sometimes include o kern/169336 wireless [ath] ANI isn't triggering in a busy/noisy environment o kern/169199 wireless [ath] Cannot set up static ip addresses for wireless w o kern/169084 wireless [ath] suspend/resume doesn't cause a rescan; the assoc o kern/168530 wireless [ath] Broken WEP probably o kern/168393 wireless AR9285: suspend/resume sometimes fails o kern/168170 wireless [net80211] ieee80211_send_bar() doesn't complete corre o kern/167870 wireless [ath] adhoc wifi client does not join an existing IBSS o kern/167834 wireless [ath] kickpcu; 'handled 0 packets' o kern/167828 wireless [iwn] iwn(4) doesn't recover automatically after firmw o kern/167798 wireless ifconfig(8): problem with "ifconfig list scan" command o kern/167491 wireless [ath] TID != hardware queue TID in ath_tx_aggr_comp_ag o kern/167113 wireless [ath] AR5210: "stuck" TX seems to be occuring, without o kern/167080 wireless [ath] channel switch on another VAP break channel setu o kern/166684 wireless [ath] [net80211] mgmtrate/mcastrate isn't updated base p kern/166642 wireless [ieee80211] [patch] in 802.11n mode for FreeBSD AP, ha o kern/166641 wireless [ieee80211] [patch] mbuf/cluster leak in AP mode in 80 p kern/166357 wireless [ath] 802.11n TX stall when the first frame in the BAW o kern/166286 wireless [net80211] [ath] initial switch to HT40 isn't causing p kern/166190 wireless [ath] TX hangs and frames stuck in TX queue o kern/166086 wireless [Patch][ath] Reflect state of rfkill switch in a sysct o kern/165969 wireless [ath] Slower performance in adhoc mode vs Client/AP mo o kern/165966 wireless [ath] ath0: device timeout on SMP machines due to race o kern/165895 wireless [ath] overly busy cabq can tie up all tx buffers o kern/165870 wireless [bwn] bwn driver does not attach on HP Pavilion dv9420 o kern/165866 wireless [ath] TX hangs, requiring a "scan" to properly reset t o kern/165849 wireless [ath] [hang] network ath driver freeze o kern/165595 wireless [ipw] ipw(4): Can't load firmare for ipw2200bg o kern/165543 wireless [ath] ath0 endless scanning of channels without connec o kern/165517 wireless [net80211] bgscan isn't triggered when invalid beacons o kern/165475 wireless [ath] operational mode change doesn't poke the underly o kern/165382 wireless [kernel] taskqueue_unblock doesn't unblock currently q o kern/165306 wireless [ath] race conditions between scanning and beacon time o kern/165220 wireless [ath] "ath_rx_tasklet: sc_inreset_cnt > 0; skipping" m o kern/165214 wireless [ieee80211] Kernel panic in ieee80211_output.c:2505 o kern/165212 wireless [ath] No WiFi on Acer Aspire One 751h (Atheros AR5BHB6 o kern/165149 wireless [ath] [net80211] Ping with data length more than iv_fr o kern/165146 wireless [net80211] Net802.11 Fragment number is assigned 1 (sh o kern/165060 wireless [ath] vap->iv_bss race conditions causing crashes insi o kern/165021 wireless [ath] ath device timeout during scan/attach, if wlan_c o kern/164721 wireless [ath] ath device timeouts o kern/164499 wireless [wi] [patch] if_wi needs fix for big endian architectu o kern/164382 wireless [ath] crash when down/deleting a vap - inside ieee8021 o kern/164365 wireless [iwi] iwi0: UP/DOWN in o bin/164102 wireless hostapd not configured for 802.11n o kern/163759 wireless [ath] ath(4) "stops working" in hostap mode o kern/163724 wireless [mwl] [patch] NULL check before dereference o kern/163719 wireless [ath] ath interface do not receive multicast o kern/163689 wireless [ath] TX timeouts when sending probe/mgmt frames durin o kern/163574 wireless [net80211] overly-frequent HT occupancy changes o kern/163573 wireless [ath] hostap mode TX buffer hang o kern/163559 wireless [ath] kernel panic AH_DEBUG o kern/163318 wireless [ath] ath(4) stops working p kern/163312 wireless [panic] [ath driver] kernel panic: page fault with ath o kern/163237 wireless [ath] AR5416 as HostAP. Delays among clients when a cl o kern/163082 wireless [ath] ar9285 diversity fixes o kern/162648 wireless [ath] AR9227 ADC DC calibration failure o kern/162647 wireless [ath] 11n TX aggregation session / TX hang o kern/161293 wireless [iwn] hang at startup when starting network o kern/161035 wireless [ieee80211] Incorrect number describing 11ng MCS rate o kern/160391 wireless [ieee80211] [patch] Panic in mesh mode o kern/160296 wireless [zyd] [panic] 802.11 usb device reboots system on 'ifc o misc/160176 wireless [mips] [panic] Kernel panic on AR7161 platform with AR o kern/157449 wireless [ath] MAC address conflict causes system to freeze o kern/157243 wireless [ath] investigate beacon TX (AP) / RX (STA) when under o kern/156904 wireless [ath] AR9285 antenna diversity algorithm is buggy and o kern/156884 wireless [ath] ath instablity o kern/156327 wireless [bwn] bwn driver causes 20%-50% packet loss o kern/156322 wireless [wpi] no ahdemo support for if_wpi o kern/156321 wireless [ath] ahdemo doesn't work with if_ath o kern/155498 wireless [ral] ral(4) needs to be resynced with OpenBSD's to ga o kern/155100 wireless [ath] ath driver on busy channel: "stuck beacon" p kern/154598 wireless [ath] Atheros 5424/2424 can't connect to WPA network o kern/154567 wireless [ath] ath(4) lot of bad series(0) o kern/154327 wireless [ath] AR5416 in station mode hangs when transmitting f o kern/154284 wireless [ath] Modern ath wifi cards (such as AR9285) have miss o kern/154153 wireless [ath] AR5213 + MIPS + WPA group key packet corruption o kern/153594 wireless [wlan] netif/devd race o kern/153448 wireless [ath] ath networking device loses association after a o kern/152750 wireless [ath] ath0 lot of bad series hwrate o kern/151198 wireless [ath] ath/5416 fails bgscan with "ath0: ath_chan_set: o kern/149786 wireless [bwn] bwn on Dell Inspiron 1150: connections stall o kern/149516 wireless [ath] ath(4) hostap with fake MAC/BSSID results in sta o kern/149373 wireless [realtek/atheros]: None of my network card working o kern/148322 wireless [ath] Triggering atheros wifi beacon misses in hostap o kern/148317 wireless [ath] FreeBSD 7.x hostap memory leak in net80211 or At o kern/148078 wireless [ath] wireless networking stops functioning o kern/146426 wireless [mwl] 802.11n rates not possible on mwl o kern/146425 wireless [mwl] mwl dropping all packets during and after high u o kern/145826 wireless [panic] [ath] Unable to configure adhoc mode on ath0/w o kern/144987 wireless [wpi] [panic] injecting packets with wlaninject using o kern/144755 wireless [wlan] netif/devd race o bin/144109 wireless hostapd(8) uses the MAC of the wireless interface, but o conf/143079 wireless hostapd(8) startup missing multi wlan functionality p kern/140567 wireless [ath] [patch] ath is not worked on my notebook PC o kern/140245 wireless [ath] [panic] Kernel panic during network activity on o kern/137592 wireless [ath] panic - 7-STABLE (Aug 7, 2009 UTC) crashes on ne o kern/136943 wireless [wpi] [lor] wpi0_com_lock / wpi0 o kern/136836 wireless [ath] atheros card stops functioning after about 12 ho o kern/132722 wireless [ath] Wifi ath0 associates fine with AP, but DHCP or I o bin/131549 wireless ifconfig(8) can't clear 'monitor' mode on the wireless o kern/126475 wireless [ath] [panic] ath pcmcia card inevitably panics under o kern/125721 wireless [ath] Terrible throughput/high ping latency with Ubiqu o kern/125617 wireless [ath] [panic] ath(4) related panic o kern/125501 wireless [ath] atheros cardbus driver hangs o kern/125332 wireless [ath] [panic] crash under any non-tiny networking unde o kern/124767 wireless [iwi] Wireless connection using iwi0 driver (Intel 220 o kern/124753 wireless [ieee80211] net80211 discards power-save queue packets o kern/121061 wireless [ath] [panic] panic while ejecting ath(4)-adapter duri o docs/120456 wireless ath(4) needs to specify requirement on wlan_scan_sta o kern/119513 wireless [ath] [irq] inserting dlink dwl-g630 wireless card res o kern/116747 wireless [ndis] FreeBSD 7.0-CURRENT crash with Dell TrueMobile f kern/105348 wireless [ath] ath device stopps TX 172 problems total. From owner-freebsd-wireless@FreeBSD.ORG Mon Jul 8 12:15:39 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 5835053C for ; Mon, 8 Jul 2013 12:15:39 +0000 (UTC) (envelope-from ghw@7axu.com) Received: from mail-we0-f174.google.com (mail-we0-f174.google.com [74.125.82.174]) by mx1.freebsd.org (Postfix) with ESMTP id E9F081CDE for ; Mon, 8 Jul 2013 12:15:38 +0000 (UTC) Received: by mail-we0-f174.google.com with SMTP id q58so3650512wes.33 for ; Mon, 08 Jul 2013 05:15:32 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:from:date:message-id:subject:to :content-type:x-gm-message-state; bh=a+zDffftJsqi7JI4ptez/Q8Aqv+RF23PKV1pEbNZlm4=; b=j6DzQxy5qz+AudAh+gc6CxPfbf354y+RuJcbKuZbS5Dm2v3oEVEhghVBowYMWX0H9R i81qJpK0p9sv3gwmy4l0gJxN5C4LgxZmoQCbtGoqsIcIYFECh8ujWgMtO1Img0uHnAzF XTSR8kU2nc4dgaeFEkM9J4cUJAHVWvw+sjH6xA0VsFZdwsG/qNuCLN6ptfTD8gn1DEB3 Jao02Gw1ET8at8Jcyi/joO2NRpk6HHJMtj45Gk0Tn3tq7OKQkAUOduGDWVSgKzzAFDHp 77ZMZlaL7JtDobDoox3/Es+lQlXm7CTFE1tcwtGEvi0sqxqmtCss2SqKXLe8E7686QoN qPaw== X-Received: by 10.180.99.67 with SMTP id eo3mr11332947wib.35.1373285346813; Mon, 08 Jul 2013 05:09:06 -0700 (PDT) MIME-Version: 1.0 Received: by 10.194.93.34 with HTTP; Mon, 8 Jul 2013 05:08:26 -0700 (PDT) X-Originating-IP: [124.90.189.225] From: XiaoQI Ge Date: Mon, 8 Jul 2013 20:08:26 +0800 Message-ID: Subject: I want to buy a wireless card To: freebsd-arm@freebsd.org, freebsd-wireless@freebsd.org X-Gm-Message-State: ALoCoQmc+m60yqc1LE9kCuea2/CWG0lNNo9n8QGnUp9FtOQpT2FH2RPWDNVkX4xX1wVPkFpCNR4q Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 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, 08 Jul 2013 12:15:39 -0000 I want to buy a wireless card, users CubieBoard (ARM) Internet connection I want to buy a wireless card, but if_rum seems only say that they support WN321G, do not know or not to support [WN321G +] The wireless network card, http://www.tp-link.com.cn/product_28.html === Or is there a cheaper USB wireless network adapter recommend it? Thank you === Regards. By: XiaoQI Ge; PGP:8B09D5F7 WWW: https://www.7axu.com/ Gtalk/E-Mail :ghw@7axu.com From owner-freebsd-wireless@FreeBSD.ORG Mon Jul 8 23:00:57 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id DACD9FE0; Mon, 8 Jul 2013 23:00:57 +0000 (UTC) (envelope-from monthadar@gmail.com) Received: from mail-wg0-x236.google.com (mail-wg0-x236.google.com [IPv6:2a00:1450:400c:c00::236]) by mx1.freebsd.org (Postfix) with ESMTP id 510501DE5; Mon, 8 Jul 2013 23:00:57 +0000 (UTC) Received: by mail-wg0-f54.google.com with SMTP id n11so4162446wgh.33 for ; Mon, 08 Jul 2013 16:00:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=FwrqXpAGZEeCTHUa3IiPR6OFlvGlU50Bahso2dL5BSU=; b=tts20Rmkc2Lyda8DBzPc8FiuXy0MxGvhpITDqarECeauIMnXO+bZVpQ4cJW6wKpCbN 91p5BKyxSHVydULgoOw4X0o5MssmJHnbyxUltc17TIAI8ZIMd63fgexrSg09LdtcANIz aD15JpSJbAAZGUhtm2kYEKlSN4fguCum21xwBJZEtn72HFl1+pkqI0C6sM4n3OqBee9Q F3OoyiUFT3ZnOgnRE8J2Er4m8vQphQqGSye8rH4Egb+aIdsJGc2wWZOBFk+JIcEH6zry Yxm6pu0qZzIC8qPAkOH1I3m1vcUlDwbk8bhs2OX4Fl58wGHbyupClLp5IwItDIVG25bw PTTA== MIME-Version: 1.0 X-Received: by 10.180.80.166 with SMTP id s6mr3610229wix.38.1373324456481; Mon, 08 Jul 2013 16:00:56 -0700 (PDT) Received: by 10.227.173.141 with HTTP; Mon, 8 Jul 2013 16:00:56 -0700 (PDT) In-Reply-To: References: Date: Tue, 9 Jul 2013 01:00:56 +0200 Message-ID: Subject: Re: [802.11s] mesh_forward() and (re)-encapsulating frames From: Monthadar Al Jaberi To: Adrian Chadd 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, 08 Jul 2013 23:00:57 -0000 Hi, On Sun, Jul 7, 2013 at 10:58 PM, Adrian Chadd wrote: > Hi monthadar (and others), > > I'm tidying up the 802.11s TX path in preparation to support 802.11n, > encryption, power-save handling, aggregation/fast-frames and other > such loveliness. > > In order to do this, the 802.11s TX path needs to use the existing VAP > methods to encapsulate and queue frames rather than directly queuing > to the parent device (ie, the physical device itself.) Because it > bypasses the normal encap path, it doesn't give the transmit path the > opportunity to do all the above handling. > > I've fixed this for all but the mesh_forward() path. In this case it > just fiddles with the mesh header, selects a new destination and sends > it to the physical interface. This assumes the frame is already > encapsulated from the receive path and it _completely_ uses the > contents of the existing frame before doing this. It bypasses all > processing. > > I've talked with monthadar about this in the past but we didn't come > up with an easy, satisfactory change to make this feasible. I'm now at > the point where I'd like to implement this. > > I'd like to take the existing frame, store the mesh header somewhere, > de-encapsulate it, then re-encapsulate it with the correct mesh > information. But I don't know how the mesh forwarding is supposed to > work. So, Monthadar (and others), what's supposed to happen with a > mesh frame being forwarded to another gateway? Basically what a meshSTA send to meshgate is an original frame, so no special case there, unless your thinking of a special case? But either way should be solved as what I have answered below. > > * What's supposed to happen to the mesh sequence number? Mesh sequence number should be decreased with 1. > * What's supposed to happen to the QoS header sequence number? (ie, > the sequence number space between the two peers) This is as if the frame is being sent originally from source mesh. As any other frame. > * What's supposed to happen for encryption? is it end-to-end > encryption, or hop-by-hop encryption? I havn't worked with encryption, others could have better knowldge. But to my knowldge it is hop-by-hop. > > Can I just get away with extending ieee80211_encap() to take a > meshcntl header and if I provide it, just use that instead of > calculating the contents in ieee80211_encap()? I think that'll be good > enough to get around the data path requirements and we can get back on > track getting this stuff ready for 802.11n and encryption. That is good enough, but how do you intend to save the mesh ctrl header to be associated with correct frame when it is in powersave? Mesh ctrl header is part the frame payload, so why not keep it there? That way you only decap the 802.11 header. The header could be either 3 or 4 address frames. But lets get something done first, and your solution is good enough for now :) > > Thanks! > > > -adrian -- Monthadar Al Jaberi From owner-freebsd-wireless@FreeBSD.ORG Mon Jul 8 23:33:05 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 6435E9DE for ; Mon, 8 Jul 2013 23:33:05 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-qe0-x233.google.com (mail-qe0-x233.google.com [IPv6:2607:f8b0:400d:c02::233]) by mx1.freebsd.org (Postfix) with ESMTP id 2AC021F40 for ; Mon, 8 Jul 2013 23:33:05 +0000 (UTC) Received: by mail-qe0-f51.google.com with SMTP id a11so2679875qen.38 for ; Mon, 08 Jul 2013 16:33:04 -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=5mtrlz0lIdtSWCYzzR41P3eJzYIH1MYEJU3ynP7kPTU=; b=iH2twD8rPUod5UP6IImWYGSZxa0Z+i/XEHz3aOMRuMt3QiDxsiPQF3dToC5kZwnk+Q oyBiLj5G6fNXmMp6LkU/CqWCvagJaBzxVkcBs2/ozu/Tv0M70qn5ocodRDqT5wOyGLyK gUBsy9J5H3Qcq1GxI/1fQCzHFSrEu4+RTjhxakytmnG2fsL0dQ/gEwdVxdvY0YhuvWWy vof7ZbbcSO4P2kukhFOY73VzhVQ7YN48LOvMkRYiNhvPqjGgm79BgRG+ypD10G19QE8q bI4tor1cgsYGzg8O+ywuC0kTbDmAuEVqIQoLQ6UH7nZVAL/ra9UDXFsmxMxQYmJaQhN8 CZpQ== MIME-Version: 1.0 X-Received: by 10.229.204.131 with SMTP id fm3mr4322013qcb.15.1373326384170; Mon, 08 Jul 2013 16:33:04 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.224.195.72 with HTTP; Mon, 8 Jul 2013 16:33:04 -0700 (PDT) In-Reply-To: References: Date: Mon, 8 Jul 2013 16:33:04 -0700 X-Google-Sender-Auth: Q0IoPTi8-Cyft-7p8dvbTwCtxng 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, 08 Jul 2013 23:33:05 -0000 On 8 July 2013 16:00, Monthadar Al Jaberi wrote: >> >> * What's supposed to happen to the mesh sequence number? > > Mesh sequence number should be decreased with 1. Decreased or increased by one? I can see the mesh TTL being decremented by one. >> * What's supposed to happen to the QoS header sequence number? (ie, >> the sequence number space between the two peers) > > This is as if the frame is being sent originally from source mesh. As > any other frame. The mesh header comes _after_ the QoS header, right? So there's both? >> * What's supposed to happen for encryption? is it end-to-end >> encryption, or hop-by-hop encryption? > > I havn't worked with encryption, others could have better knowldge. > But to my knowldge it is hop-by-hop. Right. That's a bit sucky from a security perspective, but sure. It makes it much easier to do hardware encryption and such. >> Can I just get away with extending ieee80211_encap() to take a >> meshcntl header and if I provide it, just use that instead of >> calculating the contents in ieee80211_encap()? I think that'll be good >> enough to get around the data path requirements and we can get back on >> track getting this stuff ready for 802.11n and encryption. > > That is good enough, but how do you intend to save the mesh ctrl > header to be associated with correct frame when it is in powersave? That's the real question, isn't it? Same with AMSDU/fast-frames support, etc. > Mesh ctrl header is part the frame payload, so why not keep it there? > That way you only decap the 802.11 header. The header could be either > 3 or 4 address frames. > > But lets get something done first, and your solution is good enough for now :) Well, the evil adrian here thinks we could just decap the 802.11 bit and store it as a frame that has mesh + 802.3. But then we'll have to special case things again, and I'm not really interested in having three cases in the code (802.3, 802.11, 802.11s.) It'll make things difficult to juggle. That's why I'm thinking we can just store the mesh information in an mbuf tag and reuse it when we need to. But what I really need to understand is all of the crazy logic and use-cases for the meshgate stuff. I don't have a clear picture of it in my head - admittedly I haven't sat down and _done_ the hard work to get a clear picture in my head. But I'll get there. Thus far: * When it's time to transmit it in ath(4) (ie, software queued in the driver, for A-MPDU or otherwise) then it's 802.11 + 802.11s + 802.3. That's easy, I don't have to care about it. * If it's coming in from if_transmit (ie, someone's queued an ethernet frame) then it'll be encapsulated as per normal. I don't have to care; that case is already taken care of. * If it's coming in from the receive path and we're retransmitting - it's already an 802.11 + 802.11s + 802.3 frame. We absolutely need to re-encapsulate the 802.11 bit before we queue it (because that's needed for the encryption handling, aggregation, etc.) We (at least now) won't have to deal with getting an 802.11s + 802.3 only frame this way. So, if we assume we _always_ get an 802.11+802.11s+802.3 frame, we can just do this: + re-encapsulate the 802.11 part + then if we need to do ampdu/amsdu/powersave staging, stage it as an 802.11 frame, rather than an 802.3 frame. .. but, the fast-frames code assumes it's getting two un-encapsulated 802.3 frames to assemble. And I think the amsdu support I'm going to write will assume the same thing. So the inefficient-but-sane thing to do may be this: + store the mesh control header as an mbuf tag - it's not that big, so I don't mind + strip the 802.11 bits + store the frame as an 802.3 frame - this then gets queued in the staging / powersave queues as per normal + then, when we pass it again through ieee80211_encap() to send it out, we restore the mesh control header and push it out. HOWEVER - this is why things are hairy - if we're going to encapsulate a frame for say, AMSDU or fast-frames support, we need to ensure that all the frames actually end up going to the same meshnode destination, as we only get one 802.11 header here. (ie, the AMSDU/FF support stores multiple 802.3 frames, not multiple 802.11 frames.) So we have to be careful when aggregating things. I don't know the right thing to do there except to be really paranoid and don't aggregate if there's a mesh header. (And thus for 11n we just do A-MPDU, no FF or AMSDU.) It'd be nice if we had a staging queue for AMSDU/FF aggregation per meshgate but .. that's messy. And let's ignore it for now. See what happens when I start thinking about these things? :-) Anyway - yes, we need to sort it out. mesh_forward() right now is just plain wrong ;-) -adrian From owner-freebsd-wireless@FreeBSD.ORG Tue Jul 9 01:59:00 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 62E5755F; Tue, 9 Jul 2013 01:59:00 +0000 (UTC) (envelope-from ganbold@gmail.com) Received: from mail-ie0-x230.google.com (mail-ie0-x230.google.com [IPv6:2607:f8b0:4001:c03::230]) by mx1.freebsd.org (Postfix) with ESMTP id 304131C94; Tue, 9 Jul 2013 01:59:00 +0000 (UTC) Received: by mail-ie0-f176.google.com with SMTP id ar20so11360867iec.21 for ; Mon, 08 Jul 2013 18:58:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=CQAVWmJWuEgqXyU0G4k6Lhk7giKNHbrzFTirE8ZkJm0=; b=tzyV/CP9TiewaVVchGbKAqGKBVFo0JqveS4J4Ja71w87RzaBaZ4Gc3qanIY3jbzNsh rY7KMW1D2M92lMeWCVepOxblz8hoCGxEhvO49yyGvx8mZQjsAWZHtvPelGVl5yGOxsrw eNnuaSuUb211IHsythe+otx6fb9CUdSXJu1Uac2srDou1cxENw4POLA/vMaUqK3jX2R5 JbCWVqOSsm2SljFhwlkgjCJByzQIvcBDCR7dF4tYaHL2spWOQ9duelDz31lJQNemWtIo 0afT1Uw0u2bv2TdQzvFTeLedPAhwaliMMiBvV4yhFkdlXyCio2Bm1RzuFvP1vPK8VP9Y exnQ== MIME-Version: 1.0 X-Received: by 10.50.107.2 with SMTP id gy2mr33085791igb.5.1373335139784; Mon, 08 Jul 2013 18:58:59 -0700 (PDT) Received: by 10.64.235.239 with HTTP; Mon, 8 Jul 2013 18:58:59 -0700 (PDT) In-Reply-To: References: Date: Tue, 9 Jul 2013 09:58:59 +0800 Message-ID: Subject: Re: I want to buy a wireless card From: Ganbold Tsagaankhuu To: XiaoQI Ge Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: "freebsd-arm@freebsd.org" , 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: Tue, 09 Jul 2013 01:59:00 -0000 On Mon, Jul 8, 2013 at 8:08 PM, XiaoQI Ge wrote: > I want to buy a wireless card, users CubieBoard (ARM) Internet connection > > I want to buy a wireless card, but if_rum seems only say that they support > WN321G, do not know or not to support [WN321G +] The wireless network card, > http://www.tp-link.com.cn/product_28.html > > === > Or is there a cheaper USB wireless network adapter recommend it? > I have Ralink based usb wifi (WLI-UC-GNM) like http://detail.tmall.com/item.htm?spm=a220m.1000858.1000725.15.3wfRJm&id=9672376 635&user_id=667433668&is_b=1&cat_id=2&q=buffalo+usb&rn=827b20043c8cb505bf428bbc 70d5a4c8 if_run in head should support it if I'm not mistaken and good thing is it supports AP mode. But I didn't test it yet on Cubieboard. Ganbold > > Thank you > === > Regards. > By: XiaoQI Ge; PGP:8B09D5F7 > WWW: https://www.7axu.com/ > Gtalk/E-Mail :ghw@7axu.com > _______________________________________________ > freebsd-arm@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" > From owner-freebsd-wireless@FreeBSD.ORG Tue Jul 9 21:38:37 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 59D42598; Tue, 9 Jul 2013 21:38:37 +0000 (UTC) (envelope-from jkwilborn@gmail.com) Received: from mail-pd0-x234.google.com (mail-pd0-x234.google.com [IPv6:2607:f8b0:400e:c02::234]) by mx1.freebsd.org (Postfix) with ESMTP id 31E401E79; Tue, 9 Jul 2013 21:38:37 +0000 (UTC) Received: by mail-pd0-f180.google.com with SMTP id 10so5597180pdi.39 for ; Tue, 09 Jul 2013 14:38:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Q/CmZ8+DCqYJc4NIgyoKtrAB/WdXa6+z7zjvUbIuFuQ=; b=EJodENiAqHxD/WTabUf659B3nslkZnXCfT1MrxJtyQhd6Plnz+SwkOzPOloLVupXY5 hQr2wtBUJ/AP4Wmd4y8D/gmAp4FHTqjiq91lJUBHTrWYndTl3OhdSgjx/elnFo/lAD0b jtlRqf8mdIUrIU31pTQDnNnyoiyzYmNIsn3JYiX8AYxXBPSZZ3bzT2Qgklchwd8etapO Oi76bZ+YXHAXmV61FAwE5ea8UmY6Oo7AjBqhsGly+bYZ0Iep7Cdvj67/Q25XMgdwHF39 F9Z3Yq7f4fZkB23W2CyYwri5+BHSEGUXpP4E2O/5+B4AGrX6ftpFVI1mrsWpDzLzZ/fc heiA== MIME-Version: 1.0 X-Received: by 10.66.153.140 with SMTP id vg12mr29867553pab.170.1373405916166; Tue, 09 Jul 2013 14:38:36 -0700 (PDT) Received: by 10.66.26.241 with HTTP; Tue, 9 Jul 2013 14:38:36 -0700 (PDT) In-Reply-To: References: Date: Tue, 9 Jul 2013 14:38:36 -0700 Message-ID: Subject: Re: I want to buy a wireless card From: Jack Wilborn To: Ganbold Tsagaankhuu Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: "freebsd-arm@freebsd.org" , 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: Tue, 09 Jul 2013 21:38:37 -0000 I would like to hear how you do with addition of a wifi USB dongle. You have happened to pick one of the hardest items to get working in Linux. Seems most of the wifi cards are proprietary in nature so you can't get the firmware to make them operate. You need to look at the newest and see if they are on the Debian list of supported devices. I have one of them that is a PCI card that is supported, if you like I'll dig up the number from TP-Link. But it's not a USB it's a PCI. I can't think if I have a USB one around or not, seems like I could never get the firmware to operate it properly. So that why I'm interested in if you make it operate properly and completely. It was my first problem with Linux and is still around even though I've learned to look up what they support or not, but I don't know how to really do it for the smaller embedded CPU's. Will be listening. Jack On Mon, Jul 8, 2013 at 6:58 PM, Ganbold Tsagaankhuu wrote: > On Mon, Jul 8, 2013 at 8:08 PM, XiaoQI Ge wrote: > > > I want to buy a wireless card, users CubieBoard (ARM) Internet connection > > > > I want to buy a wireless card, but if_rum seems only say that they > support > > WN321G, do not know or not to support [WN321G +] The wireless network > card, > > http://www.tp-link.com.cn/product_28.html > > > > === > > Or is there a cheaper USB wireless network adapter recommend it? > > > > > I have Ralink based usb wifi (WLI-UC-GNM) like > > http://detail.tmall.com/item.htm?spm=a220m.1000858.1000725.15.3wfRJm&id=9672376 > > 635&user_id=667433668&is_b=1&cat_id=2&q=buffalo+usb&rn=827b20043c8cb505bf428bbc > 70d5a4c8 > > if_run in head should support it if I'm not mistaken and good thing is it > supports AP mode. > But I didn't test it yet on Cubieboard. > > Ganbold > > > > > > > Thank you > > === > > Regards. > > By: XiaoQI Ge; PGP:8B09D5F7 > > WWW: https://www.7axu.com/ > > Gtalk/E-Mail :ghw@7axu.com > > _______________________________________________ > > freebsd-arm@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-arm > > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" > > > _______________________________________________ > freebsd-arm@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" > From owner-freebsd-wireless@FreeBSD.ORG Wed Jul 10 02:42:19 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id B5A0DCA0; Wed, 10 Jul 2013 02:42:19 +0000 (UTC) (envelope-from erichsfreebsdlist@alogt.com) Received: from alogt.com (alogt.com [69.36.191.58]) by mx1.freebsd.org (Postfix) with ESMTP id 8263F1D34; Wed, 10 Jul 2013 02:42:19 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=alogt.com; s=default; h=Content-Transfer-Encoding:Content-Type:Mime-Version:References:In-Reply-To:Message-ID:Subject:Cc:To:From:Date; bh=iTk5TkU5W7YeqzSCc+JR4fcDQ0Nyk0y24Yqn5uvUlms=; b=Oxb4WCXhB4zb+Xwxa2XSbyCoiQhswtRZoSU5AlMw2JFGCXmV8VZFqBWb3S1J6hSsbtVyzb3xmNNAoOhm1Fe4IhitVxBr07GrP0sTQCd+QoIxQ7UK1Piv9bYqoFHRDnP1frlGtyMPb0fb+L7nz8DoL3RpI8Unn7qB7NUm4PchH9A=; Received: from [182.7.54.108] (port=55682 helo=X220.ovitrap.com) by sl-508-2.slc.westdc.net with esmtpsa (SSLv3:DHE-RSA-AES128-SHA:128) (Exim 4.80.1) (envelope-from ) id 1UwkMD-003nss-Ah; Tue, 09 Jul 2013 20:42:18 -0600 Date: Wed, 10 Jul 2013 10:42:08 +0800 From: Erich Dollansky To: Jack Wilborn Subject: Re: I want to buy a wireless card Message-ID: <20130710104208.2ef72fdd@X220.ovitrap.com> In-Reply-To: References: X-Mailer: Claws Mail 3.9.2 (GTK+ 2.24.19; amd64-portbld-freebsd10.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - sl-508-2.slc.westdc.net X-AntiAbuse: Original Domain - freebsd.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - alogt.com X-Get-Message-Sender-Via: sl-508-2.slc.westdc.net: authenticated_id: erichsfreebsdlist@alogt.com X-Source: X-Source-Args: X-Source-Dir: Cc: "freebsd-arm@freebsd.org" , 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: Wed, 10 Jul 2013 02:42:19 -0000 Hi, On Tue, 9 Jul 2013 14:38:36 -0700 Jack Wilborn wrote: > I would like to hear how you do with addition of a wifi USB dongle. > You have happened to pick one of the hardest items to get working in > Linux. Seems most of the wifi cards are proprietary in nature so you > can't get the firmware to make them operate. You need to look at the > newest and see if they are on the Debian list of supported devices. > I have one of them that is a PCI card that is supported, if you like > I'll dig up the number from TP-Link. But it's not a USB it's a PCI. > I can't think if I have a USB one around or not, seems like I could > never get the firmware to operate it properly. So that why I'm > interested in if you make it operate properly and completely. It was > my first problem with Linux and is still around even though I've > learned to look up what they support or not, but I don't know how to > really do it for the smaller embedded CPU's. > > Will be listening. > where should be the problem? Just check with man what the drivers support. His problem might be ARM. But loading the firmware via ARM should not be that different. Erich > Jack > > > On Mon, Jul 8, 2013 at 6:58 PM, Ganbold Tsagaankhuu > wrote: > > > On Mon, Jul 8, 2013 at 8:08 PM, XiaoQI Ge wrote: > > > > > I want to buy a wireless card, users CubieBoard (ARM) Internet > > > connection > > > > > > I want to buy a wireless card, but if_rum seems only say that they > > support > > > WN321G, do not know or not to support [WN321G +] The wireless > > > network > > card, > > > http://www.tp-link.com.cn/product_28.html > > > > > > === > > > Or is there a cheaper USB wireless network adapter recommend it? > > > > > > > > > I have Ralink based usb wifi (WLI-UC-GNM) like > > > > http://detail.tmall.com/item.htm?spm=a220m.1000858.1000725.15.3wfRJm&id=9672376 > > > > 635&user_id=667433668&is_b=1&cat_id=2&q=buffalo+usb&rn=827b20043c8cb505bf428bbc > > 70d5a4c8 > > > > if_run in head should support it if I'm not mistaken and good thing > > is it supports AP mode. > > But I didn't test it yet on Cubieboard. > > > > Ganbold > > > > > > > > > > > > Thank you > > > === > > > Regards. > > > By: XiaoQI Ge; PGP:8B09D5F7 > > > WWW: https://www.7axu.com/ > > > Gtalk/E-Mail :ghw@7axu.com > > > _______________________________________________ > > > freebsd-arm@freebsd.org mailing list > > > http://lists.freebsd.org/mailman/listinfo/freebsd-arm > > > To unsubscribe, send any mail to > > > "freebsd-arm-unsubscribe@freebsd.org" > > > > > _______________________________________________ > > freebsd-arm@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-arm > > To unsubscribe, send any mail to > > "freebsd-arm-unsubscribe@freebsd.org" > > > _______________________________________________ > freebsd-wireless@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to > "freebsd-wireless-unsubscribe@freebsd.org"