Received: by 2002:a25:8b12:0:0:0:0:0 with SMTP id i18csp1301143ybl; Wed, 21 Aug 2019 13:13:18 -0700 (PDT) X-Google-Smtp-Source: APXvYqx+0aEF6s8rD1KkLmYQ+VR8X7YzcI0sw3oJGMjPZ3Kun/Gtffm8Ib4gVu144XVLcJZ9oUCI X-Received: by 2002:a62:7503:: with SMTP id q3mr38899334pfc.151.1566418397972; Wed, 21 Aug 2019 13:13:17 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1566418397; cv=none; d=google.com; s=arc-20160816; b=CF2fWesjcAViuNVEc2ShCAVVnDfj4HszRg9PHe2mNVed0S+pcIiWlduHrhNM+3U7+8 CUhSgOIfaIBpII6driLq1CHNUo2VGX5BK8+lSk/2ilkhonymQl1b3EMcICnWJJmLTYvc hQSOp0kCNcDLcTwqz1E+e2M36JpsDP4t6/z9SBz1qkf1h+8Z28MHWITQrur1wjyFs8l0 IoANfhgWIu3/Z5tJZoIxToDrUVaF3DsfRpSBx/39+esik3YT2dRuaaM1h3wBKP71W0qO 27jG0ZIiLgU777sYssfIGU9KgByflODX8NfV/zcBZJdS9jHc2GARy2XNiCfLLDKbZJb2 0zEA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :user-agent:references:in-reply-to:date:cc:to:from:subject :message-id; bh=sXFWjTJAtzMcOBfbuEcl1/P0BHKrXAQUXm5ra9yaRPA=; b=S475Bk95RtPOxvHKQSbEpzyllINrYZX6X/EoKsmdBbk3raT6bAT1eOwRYB2WoDsvwY tj07rXoQIdmCMypoiWsl1HPwBu7aj44HUre7r7EqgY7yU99vb2m9s20Kgrnuy7GEdDDv ny8OfdH/eFKN4cCy8QWmMzKYGvr8qy1uM0LIvmnnj1pLPF1MAjnADZ6rEstPEzXWyoWo pur95wUagM9jYHbukv+BQx2KhZsG68dnhphMue+nRyd+jVvtwqACnMFjgpxlbHrFy8VI Ml6g4bbRez6CK9A3lR4m5vN1W78df7YmRA1jBI7FuMsWeBfj0QykifrH+YfPLnNkKOlK FjdA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-wireless-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id b2si7020221plz.15.2019.08.21.13.13.03; Wed, 21 Aug 2019 13:13:17 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-wireless-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-wireless-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727316AbfHUUMd (ORCPT + 99 others); Wed, 21 Aug 2019 16:12:33 -0400 Received: from s3.sipsolutions.net ([144.76.43.62]:45472 "EHLO sipsolutions.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726330AbfHUUMd (ORCPT ); Wed, 21 Aug 2019 16:12:33 -0400 Received: by sipsolutions.net with esmtpsa (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1i0Wy6-0004YW-Nc; Wed, 21 Aug 2019 22:12:31 +0200 Message-ID: <6efb9b56c77cd9ea945f89c3371b49c301dc2b4e.camel@sipsolutions.net> Subject: Re: Implementing Mikrotik IE From: Johannes Berg To: Josef Miegl Cc: Sebastian Gottschall , linux-wireless Date: Wed, 21 Aug 2019 22:12:26 +0200 In-Reply-To: References: <20190815152844.k5mmddvbwrohkzr6@pepin-laptop.localdomain> <3a079683-6f57-3b42-f909-90c46e14f14f@newmedia-net.de> <20190816111044.4ntizgmpa3twbzcg@pepin-laptop.localdomain> <20190816113818.ohktykc4fyetzyvq@pepin-laptop.localdomain> <9985fddfb059640f36665efc9c1ef2dc0bdb7662.camel@sipsolutions.net> <20190819113706.ujsz67sxcwt2ulmt@pepin-laptop.localdomain> Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.30.5 (3.30.5-1.fc29) MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-wireless-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-wireless@vger.kernel.org On Wed, 2019-08-21 at 22:04 +0200, Josef Miegl wrote: > > The vendor elements are added at the very end of the frame. In fact I > tried moving the RSN IE to the end of the frame so that the frame is > similar to the one ubnt airos produces. No luck either. One thing I've > learned is that ubnt airos assoc req frames have the WMM/WME IE placed > before HT Capabilities. But I'm not sure how to move it and also not > sure if it would actually work. > > I am getting 4WAY_HANDSHAKE_TIMEOUT. From capturing I can see the > station sends Key (msg 2 of 4) and a bunch of acknowledgements, but it > never sends Key (msg 4 of 4) afterwards. > > I feel like I'm stuck.. What could be the reason for this behaviour? What AP are you trying to connect to? Have you tried adding some other random vendor IE, with an OUI that the AP is almost certain to not know? Maybe it's actually interpreting this somehow? Would you be willing to show sniffer captures so we could take a look? johannes