From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Lunn Subject: Re: marvell switch Date: Thu, 5 Apr 2018 22:46:22 +0200 Message-ID: <20180405204622.GE17495@lunn.ch> References: <20180405122223.GC12178@lunn.ch> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: netdev@vger.kernel.org To: Ran Shalit Return-path: Received: from vps0.lunn.ch ([185.16.172.187]:52025 "EHLO vps0.lunn.ch" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751442AbeDEUqY (ORCPT ); Thu, 5 Apr 2018 16:46:24 -0400 Content-Disposition: inline In-Reply-To: Sender: netdev-owner@vger.kernel.org List-ID: > > Hi Ran > > > > The Marvell driver makes each port act like a normal Linux network > > interface. So if you want to enable a port, do > > > > ip link set lan0 up > > > > Want to add an ip address to a port > > > > ip addr add 10.42.42.42/24 dev lan0 > > > > Want to bridge two ports > > > > ip link add name br0 type bridge > > ip link set dev br0 up > > ip link set dev lan0 master br0 > > ip link set dev lan1 master br0 > > > > Just treat them as normal interfaces. > > > > If I may please ask, > What is the purpose of using bridge for configuring switch interfaces. > Is it in order to isolate some ports from others? > I ask because according to my understanding the default configuration of > the driver is to enable switch in "flat" configuration, i.e. as if all > ports are connected to each other. Please think about what i said. They are standard Linux network interfaces. Do standard Linux network interfaces bridge themselves together by default? No, you need to configure a bridge. Andrew