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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f14f1078-311e-47ff-ad5f-01d2fd9ea40d@lunn.ch>
Date: Tue, 2 Dec 2025 16:41:49 +0100
From: Andrew Lunn <andrew@...n.ch>
To: René Rebe <rene@...ctco.de>
Cc: netdev@...r.kernel.org, Heiner Kallweit <hkallweit1@...il.com>,
	nic_swsd@...ltek.com
Subject: Re: [PATCH] r8169: fix RTL8117 Wake-on-Lan in DASH mode

> While at it, enable wake on magic packet by default, like most other
> Linux drivers do.

Please give examples, because i think that is false.

You should have the option to enable any WoL mode the hardware
supports, but none should be enabled by default.

> There is still another issue that should be fixed: the dirver init
> kills the OOB BMC connection until if up, too. We also should probaly
> not even conditionalize rtl8168_driver_stop on wol_enabled as the BMC
> should always be accessible. IMHO even on module unload.

Is there any way to know there is a BMC connected?

   Andrew

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ