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  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Date:	Fri, 27 Apr 2007 11:14:10 -0700
From:	Stephen Hemminger <>
To:	"Csillag Kristof" <>
Cc:	<>, <>
Subject: Re: wrong destination MAC in ethernet packets from sky2 ?

On Fri, 27 Apr 2007 11:33:18 +0200
"Csillag Kristof" <> wrote:

> Hi all!
> I have encountered a strange error, and I believe that
> the culprit might be the sky2 driver, so I hope you can help.
> The symptom is that sometimes the connection between my server box
> (which is based on a Foxconn g9657ma motherboard
> (which contains a "Yukon-EC Ultra (0xb4) rev 2" gigabit network adapter
> - 11ab:4364)) and the rest of the network gets ... screwed up.

That is the chip on Gigabyte motherboard that was so busted, I ended up
blacklisting it for 2.6.21. Please send full lspci -vvx for the motherboard

> Some things work, and some don't.
> Server can ping the client, but the client can not ping the server.
> An other client can not get a DHCP address.
> From the logs, I can see that the server _thinks_ that it has sent back
> some DHCP offers, but the client never received any.

The 88e8056 is sensitive to PCI timing issues. Not sure what is going on yet,
but for some reason it works on Asus, but on Gigabyte it shows all the signs
of not reading memory correctly, or doing out of order stuff.

Since I don't work for a hardware company and don't have all the bus
analyzer hooks to see what really is going on, it probably won't get fixed

That is why the 88e8056 is marked 'ifdef broken' until this is figured out.

> Since I ruled out any other software obstacles, I have done a network
> traffic capture (with wireshark) on both ends, and here is what I have found:
> - On the client end, it seems that the DHCP OFFER package was addressed to a 
>   different MAC address, not the one the DHCP DISCOVER originated from.
>   More precisely, the first two bytes of the six-byte MAX address is different,
>   and the last four byte matches.
> - Looking at the same traffic on the server side, it seems that the destination
>   MAC address is OK.
> - To decide which side is right, I have done a capture on a third machine.
>   (I can do this, thanks to a dump hub and promiscuous mode.)
>   It verified that the MAC address in the DHCP OFFER is indeed different.
> So, it looks like sometimes the first two bytes of the destination MAC address
> is screwed up in the ethernet packets coming out from my server.
>    * * *
> I am using debian 2.6.20-2 kernel, which is based on
> The version of the sky2 driver is 1.10.
> Since I suspected that this might be a driver error, I took the 1.13 version
> from 2.6.21-rc7, and "backported" it to my current kernel.
> (I had to comment out some vlan-specific parts, but I do not care for that
> now.)
> So now I am running sky2 v1.13, but the same error is still present.
> It is important to note that this error does not always occur.
> Sometime everything is all right, sometime messages just stop
> getting through.
> Unloading and reloading the sky2 module sometimes help.
  * * *
> Do you have any idea what can the root cause for this possibly be,
> or (more importantly) how can I fix this?
> This box is mission-critical to me.
> Thank you for your help:
>       Kristof Csillag

Are you using jumbo frames? probably not.

The driver in 2.6.21 enables store/forward on transmit and earlier drivers
did not.  Store/forward should help performance and eliminate any possible
bus latency issues.

Stephen Hemminger <>
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to
More majordomo info at

Powered by blists - more mailing lists