Thread (1 message) 1 message, 1 author, 2018-04-05
  • (off-list ancestor, not in this archive)
  • Re: marvell switch · Andrew Lunn <andrew@lunn.ch> · 2018-04-05

Re: marvell switch

From: Andrew Lunn <andrew@lunn.ch>
Date: 2018-04-05 18:04:24

On Thu, Apr 05, 2018 at 05:26:37PM +0000, Ran Shalit wrote:
בתאריך יום ה׳, 5 באפר׳ 2018, 19:09, מאת Andrew Lunn ‏[off-list ref]:
quoted
quoted
Is there a wiki which explains switch configuration ?
Nope. The whole idea is that they behave like normal linux
interfaces. So there is no need to document them. You already know how
to use them.
quoted
Is it possible to open socket and send/recieve on switch ports (lan0
for example) ?
Sure. It is as normal interface. Give is an IP address and then do
TCP/IP as usual.
There is something I don't fully understand.
I thought that ports in switch which are not connected to the manage cpu
are only configured by cpu and then can coomunicate with each other.

What does it mean to open socket in such port (not the cpu port) and send
data (ethernet frames) ? Does it mean that the cpu port is sending data
directly to that port ?
The CPU port is configured to use {E}DSA tagging. Frames ingressing on
the CPU port contain an extra header. That header tells the switch
which port to send the frame out of. The switch can also send frames
received on a port out the CPU port to the host, again, with a
header. The host can tell from the header which port the frame
ingressed.

Using this, we can make ports look like normal Linux interfaces.

      Andrew
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help