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: Wed, 12 Jun 2019 11:05:22 +0200 [thread overview]
Message-ID: <93127324-0b09-7ea7-d54a-42d247570e73@eks-engel.de> (raw)
In-Reply-To: <20190611132746.GA22832@lunn.ch>
>> I captured a ping from my device to my computer to look if outgoing is working
>> (captured on both devices). Here is the output from my device where i started the:
>>
>> 00:24:24.752057 ARP, Request who-has 192.168.10.2 tell 192.168.10.1, length 28
>> 0x0000: 0001 0800 0604 0001 6a2a ad79 def5 c0a8 ........j*.y....
>> 0x0010: 0a01 0000 0000 0000 c0a8 0a02 ............
>>
>> and here the output of the receiver:
>>
>> 14:49:06.725940 MEDSA 0.2:0: ARP, Request who-has benjamin-HP tell 192.168.10.1, length 42
>> 0x0000: 0000 4010 0000 0806 0001 0800 0604 0001 ..@.............
>> 0x0010: 6a2a ad79 def5 c0a8 0a01 0000 0000 0000 j*.y............
>> 0x0020: c0a8 0a02 0000 0000 0000 0000 0000 0000 ................
>> 0x0030: 0000
>>
>> I'm really stuck at the moment because I don't know what to do further. I think,
>> I did everything what is needed.
>> And I know when I configure the switch manually via MDIO the connection is working.
>> When I'm looking for traffic in ifconfig on all ports there is everywhere 0 bytes
>> except for eth0.
>> Do you have any ideas?
> I would start simple and build up. Don't use a bridge. Just put the IP
> address 192.168.10.1 on the slave interface for port 2.
>
> So something like:
>
> ip link set eth0 up
> ip addr add 192.168.10.1/24 dev lan2
> ip link set lan2 up
>
> then you can try ping 192.168.10.2.
>
> Then trace the packet along the path. Does the ARP request make it to
> 192.168.10.2? Is a reply sent? ethtool -S lan2 will show you the
> packet counts. Do the counters show the ARP going out and the reply
> coming back?
>
> Andrew
Hi Andrew,
it is finally running in DSA mode. Thanks so much, Andrew. I can set an
IP address to all ports individually and running it now in a bridge with
all 4 copper ports. Set an IP address to the bridge and get a ping reply
from all ports. So far, that is all what I have to test, for now.
I warned you before, I will go back to another custom board. But now with
more experience thanks to you.
Cheers,
Benjamin
prev parent reply other threads:[~2019-06-12 9:05 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
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 [this message]
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=93127324-0b09-7ea7-d54a-42d247570e73@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).