netdev - Re: Support needed for integrating Marvel 88e6390 with microchip SAMA7 processor (DSA)

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <c8134442-0080-4a63-9812-8d1d23339f3c@lunn.ch>
Date: Mon, 22 Apr 2024 19:15:53 +0200
From: Andrew Lunn <andrew@...n.ch>
To: SIMON BABY <simonkbaby@...il.com>
Cc: netdev@...r.kernel.org
Subject: Re: Support needed for integrating Marvel 88e6390 with microchip
 SAMA7 processor (DSA)

On Mon, Apr 22, 2024 at 09:43:11AM -0700, SIMON BABY wrote:
> Hello Andrew,
> 
> I was doing some traffic related tests with dsa slave ports. I have connected
> the lan2 port to my laptop and configured an IP address (same network). However
> I could not ping the addresses. Do I have to change the MAC address of the lan2
> interface as well? I can see lan2 is transmitting packets but nothing Rx. The
> MAC addresses of both the CPU port and lan2 are the same. 

The MAC address should be fine.

What does tcpdump/wireshark on your laptop show? Does it receive the packets?
Does it reply?
 
> eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1504
>         inet 192.162.0.111  netmask 255.255.255.0  broadcast 192.162.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 0  bytes 0 (0.0 B)
>         RX errors 24  dropped 0  overruns 0  frame 24

RX errors and frame errors does not look good. You should investigate
that. Maybe wireshark will give you a clue.

>         TX packets 74  bytes 8301 (8.1 KiB)
>         TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
>         device interrupt 172
> 
> lan2: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
>         inet 192.168.0.120  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 0  bytes 0 (0.0 B)
>         RX errors 0  dropped 0  overruns 0  frame 0
>         TX packets 25  bytes 2092 (2.0 KiB)
>         TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

Developers stopped using ifconfig many years ago.

	Andrew