Return-path: Received: from mail-wi0-f179.google.com ([209.85.212.179]:33765 "EHLO mail-wi0-f179.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750717AbbGHHUL (ORCPT ); Wed, 8 Jul 2015 03:20:11 -0400 Received: by wiwl6 with SMTP id l6so335432277wiw.0 for ; Wed, 08 Jul 2015 00:20:10 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: References: <55965CF8.20208@thinktube.com> <559AD13B.7030105@thinktube.com> Date: Wed, 8 Jul 2015 16:20:10 +0900 Message-ID: (sfid-20150708_092016_354874_6B70704A) Subject: Re: mesh support on rtl8192cu From: Taehee Yoo To: Richard Palethorpe Cc: "linux-wireless@vger.kernel.org" , Bruno Randolf Content-Type: text/plain; charset=UTF-8 Sender: linux-wireless-owner@vger.kernel.org List-ID: 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.