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>] [<thread-prev] [day] [month] [year] [list]
Message-ID:
 <PH7PR11MB8033DF1E5C218BB1888EDE18EF152@PH7PR11MB8033.namprd11.prod.outlook.com>
Date: Fri, 3 Jan 2025 03:29:32 +0000
From: <Arun.Ramadoss@...rochip.com>
To: <tharvey@...eworks.com>
CC: <Woojung.Huh@...rochip.com>, <UNGLinuxDriver@...rochip.com>,
	<andrew@...n.ch>, <davem@...emloft.net>, <edumazet@...gle.com>,
	<kuba@...nel.org>, <pabeni@...hat.com>, <netdev@...r.kernel.org>,
	<linux-kernel@...r.kernel.org>, <olteanv@...il.com>
Subject: RE: [PATCH net] net: dsa: microchip: ksz9477: fix multicast filtering

Hi Tim, 

> 
> Arun,
> 
> Can you confirm that prior to commit 331d64f752bb ("net: dsa:
> microchip: add the enable_stp_addr pointer in ksz_dev_ops") that packets in the bridge group were being forwarded to all ports and
> that the intention of the patch was to limit them to only go to 'only' the cpu port?

By Default, In the reserved multicast table, the forwarding port for the mac address 01:80:C2:00:00:00 (BPDU Mac address) is 10h. It means, the STP BPDU packet will be forwarded to Port 5. However, the CPU port varies depending on the board schematics. Hence to fix this, forwarding port needs to changed in reserved multicast table. 

Procedure for updating Override bit:
-  0x0424 = 0x8000_0000 | dev->cpu_port. (0x10 for lan9370 and 0x20 for lan9374)
-  0x41c   = 0x0000_0085 (write, reserved multicast table and start. Table Index is 0 which is the index for BPDU packet 01:80:c2:00:00:00)
- 0x41c = wait till start bit is cleared.
  
Let me know, if you need any more information. 

> 
> Do you have any comments on this patch with regards to how the other packet groups should be configured?
> 
> Best Regards,
> 
> Tim

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ