From: Andrew Lunn <andrew@lunn.ch>
To: Egil Hjelmeland <privat@egil-hjelmeland.no>
Cc: vivien.didelot@savoirfairelinux.com, f.fainelli@gmail.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next 2/2] net: dsa: lan9303: Add basic offloading of unicast traffic
Date: Sat, 23 Sep 2017 16:31:23 +0200 [thread overview]
Message-ID: <20170923143123.GA21228@lunn.ch> (raw)
In-Reply-To: <2c5fec6d-18b3-97e9-dd64-85560382d2f7@egil-hjelmeland.no>
> The point is: Once both external ports are in "forwarding", I see no way
> to prevent traffic flowing directly between the external ports.
Generally, there are port vectors. Port X can send frames only to Port
Y.
If you don't have that, there are possibilities with VLANs. Each port
is given a unique VLAN. All incoming untagged traffic is tagged with
the VLAN. You just need to keep the VLAN separated and add/remove the
VLAN tag in the dsa tag driver.
Andrew
next prev parent reply other threads:[~2017-09-23 14:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-21 9:41 [PATCH net-next 0/2] lan9303: Add basic offloading of unicast traffic Egil Hjelmeland
2017-09-21 9:41 ` [PATCH net-next 1/2] net: dsa: lan9303: Move tag setup to new lan9303_setup_tagging Egil Hjelmeland
2017-09-21 14:40 ` Vivien Didelot
2017-09-21 9:41 ` [PATCH net-next 2/2] net: dsa: lan9303: Add basic offloading of unicast traffic Egil Hjelmeland
2017-09-21 14:21 ` Andrew Lunn
2017-09-22 7:06 ` Egil Hjelmeland
2017-09-22 20:08 ` Andrew Lunn
2017-09-23 9:58 ` Egil Hjelmeland
2017-09-23 14:31 ` Andrew Lunn [this message]
2017-09-24 22:02 ` Egil Hjelmeland
2017-09-21 14:26 ` Vivien Didelot
2017-09-22 7:23 ` Egil Hjelmeland
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=20170923143123.GA21228@lunn.ch \
--to=andrew@lunn.ch \
--cc=f.fainelli@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=privat@egil-hjelmeland.no \
--cc=vivien.didelot@savoirfairelinux.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