Received: by 2002:a25:c205:0:0:0:0:0 with SMTP id s5csp2121546ybf; Mon, 2 Mar 2020 02:22:32 -0800 (PST) X-Google-Smtp-Source: APXvYqxzH8asj1SUAdaBIPOoth3iivcFvy+m09lsFhcLgn3UrvpfSvmZ5OTV4ns0WPT4AiEv99ZN X-Received: by 2002:a05:6830:1652:: with SMTP id h18mr10006245otr.278.1583144552187; Mon, 02 Mar 2020 02:22:32 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1583144552; cv=none; d=google.com; s=arc-20160816; b=bON5MEEmo6hsOAtB/6dAoN+jsvT9nf0RjQ5rRBmmJhECGxr276aOV/L/0xTyfKSh8U DqCtvabg2aQSsxUDIjM4QjRSeEl5/zKtceQZUCneOuMmwdAnllZIHm3Qkexh9FOojIAx uwDrkH5bzAKUKBvfPd82YlfZQNdEbBMJ0Ep7wOhPA6B9gr/Vu71A/hQqfaDpKGDRETbT OUsq3nY30yZXGmq8K9Ui8pZV2LfLrhv6OQdn8FPkEPQqmuppdY+EyKtkJh3w3w9cKowN XLUVdvA51pywpfBgb00lGEg+LUaL7dqNO4tNzAi3Q1T9d9/iMIPicq/w99oX1oZOSapY riMQ== 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:in-reply-to :mime-version:user-agent:date:message-id:from:references:cc:to :subject:dkim-signature; bh=eJJnMgKzTKTuQ0iHt8vATte6TCkcL/MNJArqXUFoEKg=; b=yVf2Ipk7mtE3zGjTeFgLWV42Jn4+jgRdEwutNpxedIwbO0imAA1XPWHWxMGLWm0HIF sXYIsAPGivXK68yvBZdOP5DI74N7R2vgKIXEYkfQ9hLwMUrvo4NmReYare7kt7N1wUga zEoYwuyArdvxI46CEorih7iJm4IR7qEwRYpc5CSSxLW1zOLFme4DDo2yeuQPJz8v65uJ mjgDK+zt4H4vk4LWQjK7afKjsrfshbUALwf5Q+wYeAatqlkLagPQG/lTBJ+dvQjMwzC2 ORzbBWn76kLqwRGMPBd0x7FYUWiwQRLPrXzSZlc832xeKFIPkvgLLKzB2X/dxz7ZuXfo t5cQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@dd-wrt.com header.s=mikd header.b=YYFWlhYX; 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; dmarc=pass (p=NONE sp=REJECT dis=NONE) header.from=dd-wrt.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id q3si1336705otc.141.2020.03.02.02.22.10; Mon, 02 Mar 2020 02:22:32 -0800 (PST) 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; dkim=pass header.i=@dd-wrt.com header.s=mikd header.b=YYFWlhYX; 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; dmarc=pass (p=NONE sp=REJECT dis=NONE) header.from=dd-wrt.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726889AbgCBKWB (ORCPT + 99 others); Mon, 2 Mar 2020 05:22:01 -0500 Received: from webmail.newmedia-net.de ([185.84.6.166]:39047 "EHLO webmail.newmedia-net.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726654AbgCBKWB (ORCPT ); Mon, 2 Mar 2020 05:22:01 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=dd-wrt.com; s=mikd; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:MIME-Version:Date:Message-ID:From:References:Cc:To:Subject; bh=eJJnMgKzTKTuQ0iHt8vATte6TCkcL/MNJArqXUFoEKg=; b=YYFWlhYXSkcXV6LwTZuTuPMZm9dOJhyRbV7dtfmqTZWpbuvpkx50cH9wElj8gGdSESMVDTyuXP2a00JvXRO7U9XliBtJeEloHmydl2h3BHslMo3l7XtopmkKwambC9uhbZu5l/ktx4A0N+40tLt8UtvtW6wgAf5JZPaK7ni1MV0=; Subject: Re: [mac80211]: wds link and Radius authentication issue To: Cedric VONCKEN , Johannes Berg , Steve deRosier Cc: "linux-wireless@vger.kernel.org" References: From: Sebastian Gottschall Message-ID: <9a1cdd80-aca3-256f-1355-5762fb340a06@dd-wrt.com> Date: Mon, 2 Mar 2020 11:21:56 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:68.0) Gecko/20100101 Thunderbird/68.5.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit X-Received: from [2a01:7700:8040:a100:7cfe:1070:e1b2:ff3c] by webmail.newmedia-net.de with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.72) (envelope-from ) id 1j8iAJ-00063V-TJ; Mon, 02 Mar 2020 11:19:11 +0100 Sender: linux-wireless-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-wireless@vger.kernel.org its likelly not hostapd. i do use wds sta and wds ap modes with latest hostapd. i have a different idea. hostapd is creating a ap vlan type interface for each wds station associating and there was a issue i had with a patch in mac80211 a while ago since something was changed regarding vlan ap handling in mac80211 take a look on the following patches the second one broke wds sta operation for me completelly. i never checked the second one. my advise. revert them both and try it again and report if its working then. i was originally complaining already on this mailinglist about the breakage, but it seems that my comment was ignored at the end https://git.kernel.org/pub/scm/linux/kernel/git/jberg/mac80211-next.git/commit/?id=33d915d9e8ce811d8958915ccd18d71a66c7c495 https://git.kernel.org/pub/scm/linux/kernel/git/jberg/mac80211-next.git/commit/?id=db3bdcb9c3ffc628c5284d7ed03a704295ba1214 Am 02.03.2020 um 09:28 schrieb Cedric VONCKEN: > Yes I'm running mac80211 on both side. > > I progress in understanding to this issue. After checked, the issue is different with different mac80211 version. With the backport 5.4-rc8-1, the driver level seem worked correctly. The hostapd (in AP side) didn't include the sta in the bridge when the security policy is WPA-PSK or WPA-EAP. With none policy the sta is correctly included. > > Now I'm searching in hostpad. > > -----Message d'origine----- > De : Johannes Berg > Envoyé : vendredi 28 février 2020 10:37 > À : Steve deRosier ; Cedric VONCKEN > Cc : linux-wireless@vger.kernel.org > Objet : Re: [mac80211]: wds link and Radius authentication issue > > On Thu, 2020-02-27 at 17:26 -0800, Steve deRosier wrote: >> On Thu, Feb 27, 2020 at 9:37 AM Cedric VONCKEN wrote: >>> Where can I found some information on how the wds system should >>> work? I looked in 802.11-2012 standard and I didn't found any >>> informations. >>> >> I think Wikipedia says it best: >> "WDS may be incompatible between different products (even occasionally >> from the same vendor) since the IEEE 802.11-1999 standard does not >> define how to construct any such implementations or how stations >> interact to arrange for exchanging frames of this format. The IEEE >> 802.11-1999 standard merely defines the 4-address frame format that >> makes it possible." > I think really what Cedric is asking is how this is/should be done with mac80211's 4-addr client/AP mode(s)? > > Cedric, are you running mac80211 on both sides of the link, the AP and the (4-addr) client? > > johannes >