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] [thread-next>] [day] [month] [year] [list]
Date:	Tue, 16 Oct 2007 15:43:13 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Konstantin Kalin <konstantin.kalin@...il.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: NVIDIA Ethernet & invalid MAC

On Tue, 16 Oct 2007 18:10:53 +0400
Konstantin Kalin <konstantin.kalin@...il.com> wrote:

> Hello,
> 
> Recently we've got some computers with new motherboard having NVidia 
> chipset. The motherboard has nforce12 & nforce13 Ethernet cards. I've 
> noticed that MAC address is setup random each boot. I debugged the 
> driver and found that these cards have right-byte order of MAC address 
> but the driver is expecting incorrect byte-order for these models.

The only obvious thing I can think of to try would be to read the MAC
address both ways around.

The first 3 bytes of the resulting MAC should always be the Nvidia
allocation as I understand it and if so you can then decide which way
around is correct. 

ie if it starts 00:04:0B then you know which way around it goes. (there
is one address that is the same either way around but clearly that one
doesn't matter).

So perhaps do that and for the afflicted parts add an EITHER_WAY_AROUND
flag ?

Alan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ