Return-path: Received: from mail-wi0-f178.google.com ([209.85.212.178]:36124 "EHLO mail-wi0-f178.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933000AbbGHLsS (ORCPT ); Wed, 8 Jul 2015 07:48:18 -0400 Received: by widjy10 with SMTP id jy10so214714647wid.1 for ; Wed, 08 Jul 2015 04:48:17 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: References: <55965CF8.20208@thinktube.com> <559AD13B.7030105@thinktube.com> Date: Wed, 8 Jul 2015 12:48:17 +0100 Message-ID: (sfid-20150708_134823_087945_5CC89E5A) Subject: Re: mesh support on rtl8192cu From: Richard Palethorpe To: Taehee Yoo Cc: "linux-wireless@vger.kernel.org" , Bruno Randolf Content-Type: text/plain; charset=UTF-8 Sender: linux-wireless-owner@vger.kernel.org List-ID: On Wed, Jul 8, 2015 at 8:20 AM, Taehee Yoo wrote: > Richard, I do apologize for my mistake. > I found that the rtl8192cu can't send the beacon frame at mesh mode. > Sender side wireshark shows sending beacon frame. but receiver side > wireshark doesn't show the rtl8192cu's mesh beacon. > I think connection issue's cause is rtl8192cu's wrong beacon code. Thank you for looking into it Taehee. Using an adapter in monitor mode I can see that the rtl8192cu is sending out beacon frames and ARP packets over the air (if I use arping) in mesh mode.