netdev - tg3 + HP iLO2 -> IPv6 broken

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-next>] [day] [month] [year] [list]

Message-ID:  <gbu10u$uvr$1@ger.gmane.org>
Date:	Tue, 30 Sep 2008 20:09:02 +0000 (UTC)
From:	Bernhard Schmidt <berni@...kenwald.de>
To:	netdev@...r.kernel.org
Subject:  tg3 + HP iLO2 -> IPv6 broken

Hello,

I have an interesting bug here which I just can't put my finger on. 

I have just bought a HP Proliant DL320 G5p. It features an integrated
out-of-band controller called iLO2, which shares a physical ethernet
connection with one of the two BCM5715 GigE ports of the system. 

Basic problem:
I cannot get native IPv6 to work on the first (shared) GigE port.
The system does not autoconfigure an address and does not respond to
incoming neighbor solicitations for it's link-local address. Unless I
either

a) reboot the iLO2 by e.g. adjusting anything in the network settings
   (just switching the "use WINS servers from DHCP reply" is enough to
   restart it). This fixes my issues up until the next reboot of Linux,
   which breaks things again

_OR_

b) set the port to promiscous mode and leave it set.

The second GigE port using the same network chip does not have this
problem. 

Now I think this points to an issue with the iLO2, and indeed HP has
recently announced version 1.60 of the iLO2 firmware which is supposed
to fix an issue with dualstacked IPv4/IPv6 operation of the host, but
this version is installed. And IMHO, if the iLO2 would be the (sole)
culprit setting promisc mode should not help, should it?

Problem exists with both 2.6.26-1-amd64 from Debian lenny and vanilla
2.6.27-rc8 from kernel.org (same config). 

Does anyone have enough insight into how this ethernet port and the iLO
are connected which could help blaming either the driver or the iLO (or
both)?  I'll try to kick HP as well but since I don't have a support
contract for this (private) system other than the hardware warranty it
might take a while.

.config and dmesg available on request, I don't think they are helpful
here.

Regards,
Bernhard

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html