From: Benjamin Beckmeyer <beb@eks-engel.de>
To: Andrew Lunn <andrew@lunn.ch>
Cc: <netdev@vger.kernel.org>
Subject: Re: DSA with MV88E6321 and imx28
Date: Tue, 11 Jun 2019 09:36:16 +0200 [thread overview]
Message-ID: <635c884a-185d-5b3b-7f91-ce058d9726f4@eks-engel.de> (raw)
In-Reply-To: <20190607124750.GJ20899@lunn.ch>
>> So all ports are now in forwarding mode (Switch port register 0x4 of all ports
>> are 0x7f), but I don't reach it over ping.
> Hi
>
> The most common error for people new to DSA is forgetting to bring
> the master interface up.
>
> The second thing to understand is that by default, all interfaces are
> separated. So the switch won't bridge frames between ports, until you
> add the ports to a Linux bridge. But you can give each interface its
> own IP address.
>
> Andrew
Hi Andrew,
thanks for your help again. Sorry for the late reply we had a stats day yesterday.
What interface do you mean with master interface? I assume, you mean eth0 (cpu port)?
I deleted the IP address of this interface and tried to add it to the bridge:
brctl addif bridge0 eth0
brctl: bridge bridge0: Invalid argument
I tried this with all lan1-4 interfaces and they just work and directly after
I added them I got some information about the port:
brctl addif br0 lan4
[ 156.085842] br0: port 4(lan4) entered blocking state
[ 156.091022] br0: port 4(lan4) entered disabled state
After I brought up the bridge with:
ip link set br0 up
[ 445.313697] br0: port 4(lan4) entered blocking state
[ 445.318896] br0: port 4(lan4) entered forwarding state
So I gave my eth0 an IP address and started tcpdump on eth0:
tcpdump -i eth0
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 65535 bytes
01:11:36.040006 ARP, Request who-has 192.168.10.1 tell 192.168.10.2, length 46
01:11:37.062283 ARP, Request who-has 192.168.10.1 tell 192.168.10.2, length 46
01:11:38.086465 ARP, Request who-has 192.168.10.1 tell 192.168.10.2, length 46
How you can see, I get the ARP request but no reply from my device. No ping is
working. All interfaces are up:
ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,ALLMULTI,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
link/ether 6a:d0:d5:9c:fe:f3 brd ff:ff:ff:ff:ff:ff
inet 192.168.10.201/24 brd 192.168.10.255 scope global eth0
valid_lft forever preferred_lft forever
3: Serdes0@eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop switchid 00000000 state DOWN group default qlen 1000
link/ether 6a:d0:d5:9c:fe:f3 brd ff:ff:ff:ff:ff:ff
4: Serdes1@eth0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop switchid 00000000 state DOWN group default qlen 1000
link/ether 6a:d0:d5:9c:fe:f3 brd ff:ff:ff:ff:ff:ff
5: lan1@eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master br0 switchid 00000000 state UP group default qlen 1000
link/ether 6a:d0:d5:9c:fe:f3 brd ff:ff:ff:ff:ff:ff
6: lan2@eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue master br0 switchid 00000000 state LOWERLAYERDOWN group default qlen 1000
link/ether 6a:d0:d5:9c:fe:f3 brd ff:ff:ff:ff:ff:ff
7: lan3@eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue master br0 switchid 00000000 state LOWERLAYERDOWN group default qlen 1000
link/ether 6a:d0:d5:9c:fe:f3 brd ff:ff:ff:ff:ff:ff
8: lan4@eth0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue master br0 switchid 00000000 state LOWERLAYERDOWN group default qlen 1000
link/ether 6a:d0:d5:9c:fe:f3 brd ff:ff:ff:ff:ff:ff
9: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether 6a:d0:d5:9c:fe:f3 brd ff:ff:ff:ff:ff:ff
Am I doing something wrong or maybe I forget something?
Cheers,
Benjamin
next prev parent reply other threads:[~2019-06-11 7:44 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-04 13:07 DSA with MV88E6321 and imx28 Benjamin Beckmeyer
2019-06-04 13:50 ` Andrew Lunn
2019-06-05 4:52 ` Benjamin Beckmeyer
2019-06-05 12:24 ` Andrew Lunn
2019-06-05 13:12 ` Benjamin Beckmeyer
2019-06-05 13:31 ` Andrew Lunn
2019-06-05 13:54 ` Benjamin Beckmeyer
2019-06-05 18:47 ` Andrew Lunn
2019-06-06 9:39 ` Benjamin Beckmeyer
[not found] ` <c27f2b9b-90d7-db63-f01c-2dfaef7a014b@eks-engel.de>
[not found] ` <20190606122437.GA20899@lunn.ch>
2019-06-06 13:27 ` Benjamin Beckmeyer
2019-06-06 13:35 ` Andrew Lunn
2019-06-06 13:47 ` Benjamin Beckmeyer
2019-06-06 13:59 ` Andrew Lunn
2019-06-07 9:41 ` Benjamin Beckmeyer
2019-06-07 12:47 ` Andrew Lunn
2019-06-11 7:36 ` Benjamin Beckmeyer [this message]
2019-06-11 12:19 ` Andrew Lunn
2019-06-11 13:09 ` Benjamin Beckmeyer
2019-06-11 13:27 ` Andrew Lunn
2019-06-12 9:05 ` Benjamin Beckmeyer
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=635c884a-185d-5b3b-7f91-ce058d9726f4@eks-engel.de \
--to=beb@eks-engel.de \
--cc=andrew@lunn.ch \
--cc=netdev@vger.kernel.org \
/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).