| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <CAEFUPH1q9MPNBrfzhSmCawM4y+A6SKe47Pc1PjqShy-0Oo4-2w@mail.gmail.com>
Date: Thu, 25 Apr 2024 10:37:38 -0700
From: SIMON BABY <simonkbaby@...il.com>
To: netdev@...r.kernel.org, Andrew Lunn <andrew@...n.ch>
Subject: ping test with DSA ports failing
Hello team,
My test setup with DSA ports is below. Please confirm if it is a valid test
case for ping.
Ping is failing most of the time but succeeds sometimes. Attached is the
Wireshark capture from my laptop and the tcpdump from sama7 processor.
__________
_______________ 192.168.0.119/24 192.168.0.155/24
_________
| |
| |____________lan1__________________
____| |
| SAMA7 | eth0 (RGMII) | marvel 88e6390
|___________ lan2 |
laptop |
| gmac0|---------------------------------------|port0 (RGMII)
|___________ lan3
|________ |
|_________|
| |___________ lan4
|
|___________ lan5
| |___________ lan6
|______________ |
eth0 – DSA master interface, gmac0 of sama7 and port0 of marvel are RGMII
connected. For the testing I have connected via a PHY on both sides with an
ethernet cable. No IP address configured on this master interface and
interface is UP.
lan1, lan2, lan3 … etc are the DSA slave ports
lan1 is directly connected to a laptop.
lan1 ip address: 192.168.0.119/24
laptop ip address: 192.168.0.115/24
ping from sama7 processor to laptop ip address. I believe it should go from
CPU to eth0 and then lan1 to laptop.
Ping is failing most of the times. Interestingly it is passing sometime.
Below are the logs.
root@...a7g5ek-sd:~# ifconfig lan1 192.168.0.119/24 up
mv88e6085 e2800000.ethernet-ffffffff:10 lan1: configuring for phy/gmii link
mode
root@...a7g5ek-sd:~# mv88e6085 e2800000.ethernet-ffffffff:10 lan1: Link is
Up - 1Gbps/Full - flow control rx/tx
IPv6: ADDRCONF(NETDEV_CHANGE): lan1: link becomes ready
root@...a7g5ek-sd:~# ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1504
inet6 fe80::691:62ff:fef2:fd1c prefixlen 64 scopeid 0x20<link>
ether 04:91:62:f2:fd:1c txqueuelen 1000 (Ethernet)
RX packets 128 bytes 13882 (13.5 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 40 bytes 5052 (4.9 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 172
lan1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.0.119 netmask 255.255.255.0 broadcast 192.168.0.255
inet6 fe80::691:62ff:fef2:fd1c prefixlen 64 scopeid 0x20<link>
ether 04:91:62:f2:fd:1c txqueuelen 1000 (Ethernet)
RX packets 118 bytes 11744 (11.4 KiB)
RX errors 0 dropped 4 overruns 0 frame 0
TX packets 18 bytes 1456 (1.4 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
root@...a7g5ek-sd:~# ping 192.168.0.115
PING 192.168.0.115 (192.168.0.115) 56(84) bytes of data.
>From 192.168.0.119 icmp_seq=1 Destination Host Unreachable
>From 192.168.0.119 icmp_seq=2 Destination Host Unreachable
>From 192.168.0.119 icmp_seq=3 Destination Host Unreachable
64 bytes from 192.168.0.115: icmp_seq=6 ttl=128 time=1.04 ms
64 bytes from 192.168.0.115: icmp_seq=7 ttl=128 time=1.28 ms
64 bytes from 192.168.0.115: icmp_seq=10 ttl=128 time=1.19 ms
64 bytes from 192.168.0.115: icmp_seq=14 ttl=128 time=0.822 ms
64 bytes from 192.168.0.115: icmp_seq=24 ttl=128 time=11.2 ms
64 bytes from 192.168.0.115: icmp_seq=26 ttl=128 time=0.770 ms
64 bytes from 192.168.0.115: icmp_seq=28 ttl=128 time=0.769 ms
64 bytes from 192.168.0.115: icmp_seq=32 ttl=128 time=0.757 ms
>From 192.168.0.119 icmp_seq=71 Destination Host Unreachable
>From 192.168.0.119 icmp_seq=72 Destination Host Unreachable
>From 192.168.0.119 icmp_seq=73 Destination Host Unreachable
>From 192.168.0.119 icmp_seq=74 Destination Host Unreachable
>From 192.168.0.119 icmp_seq=75 Destination Host Unreachable
>From 192.168.0.119 icmp_seq=76 Destination Host Unreachable
>From 192.168.0.119 icmp_seq=77 Destination Host Unreachable
>From 192.168.0.119 icmp_seq=78 Destination Host Unreachable
>From 192.168.0.119 icmp_seq=79 Destination Host Unreachable
64 bytes from 192.168.0.115: icmp_seq=80 ttl=128 time=1.49 ms
64 bytes from 192.168.0.115: icmp_seq=81 ttl=128 time=0.821 ms
64 bytes from 192.168.0.115: icmp_seq=83 ttl=128 time=0.788 ms
64 bytes from 192.168.0.115: icmp_seq=87 ttl=128 time=0.774 ms
64 bytes from 192.168.0.115: icmp_seq=92 ttl=128 time=0.892 ms
64 bytes from 192.168.0.115: icmp_seq=96 ttl=128 time=0.887 ms
64 bytes from 192.168.0.115: icmp_seq=99 ttl=128 time=1.13 ms
64 bytes from 192.168.0.115: icmp_seq=102 ttl=128 time=0.962 ms
64 bytes from 192.168.0.115: icmp_seq=111 ttl=128 time=16.2 ms
64 bytes from 192.168.0.115: icmp_seq=115 ttl=128 time=1.61 ms
64 bytes from 192.168.0.115: icmp_seq=118 ttl=128 time=0.817 ms
root@...a7g5ek-sd:~# ip route
192.168.0.0/24 dev lan1 proto kernel scope link src 192.168.0.119
root@...a7g5ek-sd:~#
My device tree used for DSA is below:
&gmac0 {
phy-mode = "rgmii-id";
phy-handle = <&switch0cpu>;
status = "okay";
fixed-link {
speed = <1000>;
full-duplex;
};
mdio {
status = "okay";
switch: switch@10 {
compatible = "marvell,mv88e6190";
reg = <0x10>;
ports {
#address-cells = <1>;
#size-cells = <0>;
switch0cpu: port@0 {
reg = <0>;
ethernet = <&gmac0>;
phy-mode = "rgmii";
fixed-link {
speed = <1000>;
full-duplex;
};
};
port@1 {
reg = <0x1>;
label = "lan1";
};
port@2 {
reg = <0x2>;
label = "lan2";
};
port@3 {
reg = <0x3>;
label = "lan3";
};
port@4 {
reg = <0x4>;
label = "lan4";
};
port@5 {
reg = <0x5>;
label = "lan5";
};
port@6 {
reg = <0x6>;
label = "lan6";
};
};
};
};
};
Regards
Simon
Content of type "text/html" skipped
View attachment "tcpdump_sama7_eth0_lan1_withping_from_laptop.txt" of type "text/plain" (26196 bytes)
Download attachment "wireshark_dsa.pcapng" of type "application/octet-stream" (14220 bytes)
Powered by blists - more mailing lists