netdev - Re: Fwd: Bad permanent address 00:10:00:80:00:10 using r8168 module on some cards

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: <220be845-230b-8c49-c748-e507eb4c36f5@gmail.com>
Date:   Thu, 31 Oct 2019 22:06:11 +0100
From:   Heiner Kallweit <hkallweit1@...il.com>
To:     Luc Novales <luc.novales@...c.fr>, netdev@...r.kernel.org
Subject: Re: Fwd: Bad permanent address 00:10:00:80:00:10 using r8168 module
 on some cards

On 31.10.2019 14:04, Luc Novales wrote:
> Hi,
> 
> I have no answer from realtek, could you help me for debugging and determine if problem is hardware or software and howto solve it ?
> 
> In complement, howto get more information about module parameters ?
> 
> Best regards
> 
> Luc Novales.
> 
> 
> -------- Message transféré --------
> Sujet :     Bad permanent address 00:10:00:80:00:10 using r8168 module on some cards
> Date :     Tue, 29 Oct 2019 11:28:09 +0100
> De :     Luc Novales <luc.novales@...c.fr>
> Pour :     nicfae@...ltek.com
> 
> 
> 
> Hi,
> 
> I am Luc Novales from ENAC in France.
> 
> We have some problems using tp-link PCI express network adapter (model : TG-3468(UN) ver:3.0, P/N:0152502214) under Debian Linux.
> 
> We uses this adapters on about 50 training computers.
> 
> Using r8168 compiled kernel driver, randomly and for unknown reasons bad address 00:10:00:80:00:10 is chosen at boot on some cards, causing some hardware address conflict on the network.
> 
[...]
Regarding the vendor driver r8168: You have the source code. That's all support you can get.

> 
> 
> For information, we can't use stock kernel driver r8169 because card fails in a state which it doesn't auto-negotiate and doesn't establish any link with the switch (standby power must be remove to unlock the adapter).
> 
A full dmesg output would be helpful, and please try also with a recent kernel.
The described failure refers to the cards with the MAC address issue, or to all cards?

> Best regards
> 
> Luc Novales.
> 
> 
Heiner