From: Andre Valentin <avalentin@marcant.net>
To: DENG Qingfang <dqfext@gmail.com>, Vladimir Oltean <olteanv@gmail.com>
Cc: "Andrew Lunn" <andrew@lunn.ch>,
"Vivien Didelot" <vivien.didelot@gmail.com>,
"Florian Fainelli" <f.fainelli@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
"Jakub Kicinski" <kuba@kernel.org>,
"Russell King" <linux@armlinux.org.uk>,
"open list:NETWORKING DRIVERS" <netdev@vger.kernel.org>,
"open list" <linux-kernel@vger.kernel.org>,
"Ansuel Smith" <ansuelsmth@gmail.com>,
"Jonathan McDowell" <noodles@earth.li>,
"Michal Vokáč" <vokac.m@gmail.com>,
"Christian Lamparter" <chunkeey@gmail.com>,
"Nishka Dasgupta" <nishkadg.linux@gmail.com>,
"John Crispin" <john@phrozen.org>,
"Stefan Lippers-Hollmann" <s.l-h@gmx.de>,
"Hannu Nyman" <hannu.nyman@iki.fi>,
"Imran Khan" <gururug@gmail.com>,
"Frank Wunderlich" <frank-w@public-files.de>,
"Nick Lowe" <nick.lowe@gmail.com>
Subject: Re: [RFC net-next 2/3] net: dsa: qca8k: enable assisted learning on CPU port
Date: Tue, 10 Aug 2021 19:27:05 +0200 [thread overview]
Message-ID: <0072b721-7520-365d-26ef-a2ad70117ac2@marcant.net> (raw)
In-Reply-To: <20210808160503.227880-1-dqfext@gmail.com>
On Sun, Aug 08, 2021 at 1805, DENG Qingfang wrote:
> On Sun, Aug 08, 2021 at 01:25:55AM +0300, Vladimir Oltean wrote:
>> On Sat, Aug 07, 2021 at 08:07:25PM +0800, DENG Qingfang wrote:
>>> Enable assisted learning on CPU port to fix roaming issues.
>>
>> 'roaming issues' implies to me it suffered from blindness to MAC
>> addresses learned on foreign interfaces, which appears to not be true
>> since your previous patch removes hardware learning on the CPU port
>> (=> hardware learning on the CPU port was supported, so there were no
>> roaming issues)
The issue is with a wifi AP bridged into dsa and previously learned
addresses.
Test setup:
We have to wifi APs a and b(with qca8k). Client is on AP a.
The qca8k switch in AP b sees also the broadcast traffic from the client
and takes the address into its fdb.
Now the client roams to AP b.
The client starts DHCP but does not get an IP. With tcpdump, I see the
packets going through the switch (ap->cpu port->ethernet port) and they
arrive at the DHCP server. It responds, the response packet reaches the
ethernet port of the qca8k, and is not forwarded.
After about 3 minutes the fdb entry in the qca8k on AP b is
"cleaned up" and the client can immediately get its IP from the DHCP server.
I hope this helps understanding the background.
next prev parent reply other threads:[~2021-08-10 17:30 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-07 12:07 [RFC net-next 0/3] qca8k bridge flags offload DENG Qingfang
2021-08-07 12:07 ` [RFC net-next 1/3] net: dsa: qca8k: offload bridge flags DENG Qingfang
2021-08-07 20:45 ` Vladimir Oltean
2021-08-07 12:07 ` [RFC net-next 2/3] net: dsa: qca8k: enable assisted learning on CPU port DENG Qingfang
2021-08-07 22:25 ` Vladimir Oltean
2021-08-08 16:05 ` DENG Qingfang
2021-08-08 21:10 ` Vladimir Oltean
2021-08-10 17:27 ` Andre Valentin [this message]
2021-08-10 17:53 ` Vladimir Oltean
2021-08-10 21:09 ` Andre Valentin
2021-08-10 23:33 ` Vladimir Oltean
2021-08-07 12:07 ` [RFC net-next 3/3] net: dsa: tag_qca: set offload_fwd_mark DENG Qingfang
2021-08-07 22:57 ` Vladimir Oltean
2021-08-08 16:12 ` DENG Qingfang
2021-08-08 21:14 ` Vladimir Oltean
2021-08-10 6:57 ` [RFC net-next 0/3] qca8k bridge flags offload Jonathan McDowell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0072b721-7520-365d-26ef-a2ad70117ac2@marcant.net \
--to=avalentin@marcant.net \
--cc=andrew@lunn.ch \
--cc=ansuelsmth@gmail.com \
--cc=chunkeey@gmail.com \
--cc=davem@davemloft.net \
--cc=dqfext@gmail.com \
--cc=f.fainelli@gmail.com \
--cc=frank-w@public-files.de \
--cc=gururug@gmail.com \
--cc=hannu.nyman@iki.fi \
--cc=john@phrozen.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=nick.lowe@gmail.com \
--cc=nishkadg.linux@gmail.com \
--cc=noodles@earth.li \
--cc=olteanv@gmail.com \
--cc=s.l-h@gmx.de \
--cc=vivien.didelot@gmail.com \
--cc=vokac.m@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).