linux-kernel - Re: forcedeth ?

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, 31 Jul 2007 00:17:22 +0200
From:	Gabriel C <nix.or.die@...glemail.com>
To:	Sasa Ostrouska <casaxa@...il.com>
CC:	Avuton Olrich <avuton@...il.com>, linux-kernel@...r.kernel.org
Subject: Re: forcedeth ?

Sasa Ostrouska wrote:
> On 7/31/07, Gabriel C <nix.or.die@...glemail.com> wrote:
>> Sasa Ostrouska wrote:
>>> On 7/30/07, Avuton Olrich <avuton@...il.com> wrote:
>>>> On 7/30/07, Sasa Ostrouska <casaxa@...il.com> wrote:
>>>>> Hi people,
>>>>>
>>>>> I'm using this on a x86-64 amd machine. During boot of the last
>>>>> 2.6.22.1 kernel I get this error:
>>>> Somewhat unrelated, but I had a similar forcedeth problem, I took the
>>>> latest git forcedeth.c and put it into 2.6.22.1 and it worked for me.
>>>>
>>>> Good luck!
>>>> --
>>>> avuton
>>> Ok, maybe I can try that. In any case I noticed another strange thing.
>>> I have 2 nics in that machine.
>>> One is a nvidia MPC61 using the forcedeth.c the other one is a Realtec
>>> RTL8029 using the
>>> ne2k_pci.
>>> Now, whenever I compile them both as modules each reboot the cards get
>>> inversed eth assignement. Suppose first boot, the forcedeth is eth0 ,
>>> the next boot it is eth1 , this is very anoying as one cant make only
>>> one boot, probably this is someway related to the bios.
>>> Now I configured them one in the kernel and the other as a module so
>>> they get each time assigned the same name. But when powerloss happens
>>> (unplug the cable) the next boot they do not work. I see them assigned
>>> the correct name, ifconfig shows the IP's but ping results in a
>>> destination unreachable.
>>>
>>> Any ideas ?
>> Udev rules ?
>>
>>
> Gabriel, hmm, shouldnt udev be able to autoconfigure that ? But I need
> to check that, thx for the tip.

Yes udev does this based on the MAC address but AFAIK forcedeth is 'special' for some reason 
( which I can really remember now and gets on each boot a new MAC address or alike )

You could try to make your rules based on the pci bus id instead of the MAC address. ( at least I think this should work )

> Rgds
> Sasa
> 

Gabriel
-
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/