query on VLAN with linux DSA ports

query on VLAN with linux DSA ports

[SIMON BABY]

Hello Team,

Can I know what is the best way of  implementing VLAN on linux DSA user ports ?

I would like to know if I can go with VLAN interface or VLAN filtering
on bridge interface. I am using Marvel DSA  (88E6390) running on Linux
6.1 kernel.

Below is my requirement.

eth0 (conduit interface)

lan1 ----VLAN 10    192.168.1.1/24
lan2 ----VLAN 10

lan3 -----VLAN 20   192.168.2.1/24

lan4------VLAN 30    192.168.3.1/24

Do I need to create a separate bridge interface for each port which
belongs to different subnets?

Is it better to use a VLAN aware bridge (with vlan_filitering = 1) or
create multiple vlan interfaces ?


Thanks, Simon

Re: query on VLAN with linux DSA ports

[Andrew Lunn]

On Thu, Oct 24, 2024 at 07:14:28AM -0700, SIMON BABY wrote:
> Hello Team,
> 
> Can I know what is the best way of  implementing VLAN on linux DSA user ports ?

Ignore the fact these are ports on a switch. How would you do this if
for any sort of linux interface?

	Andrew

Re: query on VLAN with linux DSA ports

[SIMON BABY]

Thank you.

I have the below query specific to linux.

I read that there are two approaches for VLAN configuration in Linux.

The traditional way of creating a vlan interface and assigning an IP
address to the interface and the vlan aware bridge. Do you recommend a
better way from these two approaches? Any advantages of using vlan
aware bridges?

option 1:

ip link set dev eth0 up
ip link add link eth0 name eth0.10 up type vlan id 10
ip addr add dev eth0.10 192.0.2.2/24
ip route add default via 192.0.2.1 dev eth0.10

option 2:

ip link add name br0 type bridge vlan_filtering 1
ip link set dev eth0 master br0
ip link set br0 up
bridge vlan add vid 10 dev br0 pvid untagged self
bridge vlan add vid 10 dev eth0 pvid
ip addr add 192.0.2.2/24 dev br0
ip route add default via 192.0.2.1



Regards
Simon

On Thu, Oct 24, 2024 at 7:29 AM Andrew Lunn <andrew@lunn.ch> wrote:
>
> On Thu, Oct 24, 2024 at 07:14:28AM -0700, SIMON BABY wrote:
> > Hello Team,
> >
> > Can I know what is the best way of  implementing VLAN on linux DSA user ports ?
>
> Ignore the fact these are ports on a switch. How would you do this if
> for any sort of linux interface?
>
>         Andrew

Re: query on VLAN with linux DSA ports

[Vladimir Oltean]

On Thu, Oct 24, 2024 at 08:15:50AM -0700, SIMON BABY wrote:
> Any advantages of using vlan aware bridges?

Bridges can have more than one lower interface, unlike VLAN (8021q) interfaces.
The lower interfaces of a bridge will forward packets between each other
according to the destination MAC address (optionally + VLAN ID), which is
something VLANs don't do.

I don't believe that a bridge with a single lower interface (port), as in
your example, is exactly "intended use".

Re: query on VLAN with linux DSA ports

[SIMON BABY]

Thank you Vladimir.

Regards
Simon

On Tue, Oct 29, 2024 at 8:36 AM Vladimir Oltean <olteanv@gmail.com> wrote:
>
> On Thu, Oct 24, 2024 at 08:15:50AM -0700, SIMON BABY wrote:
> > Any advantages of using vlan aware bridges?
>
> Bridges can have more than one lower interface, unlike VLAN (8021q) interfaces.
> The lower interfaces of a bridge will forward packets between each other
> according to the destination MAC address (optionally + VLAN ID), which is
> something VLANs don't do.
>
> I don't believe that a bridge with a single lower interface (port), as in
> your example, is exactly "intended use".

Re: query on VLAN with linux DSA ports

[SIMON BABY]

Hello Team,

Do we have any patch available for linux DSA interface for configuring
QOS in marvel 88E6390 switch hardware?

Regards
Simon


On Tue, Oct 29, 2024 at 8:36 AM Vladimir Oltean <olteanv@gmail.com> wrote:
>
> On Thu, Oct 24, 2024 at 08:15:50AM -0700, SIMON BABY wrote:
> > Any advantages of using vlan aware bridges?
>
> Bridges can have more than one lower interface, unlike VLAN (8021q) interfaces.
> The lower interfaces of a bridge will forward packets between each other
> according to the destination MAC address (optionally + VLAN ID), which is
> something VLANs don't do.
>
> I don't believe that a bridge with a single lower interface (port), as in
> your example, is exactly "intended use".