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: <alpine.LNX.1.10.0811111624170.26561@bizon.gios.gov.pl>
Date:	Tue, 11 Nov 2008 16:49:30 +0100 (CET)
From:	Krzysztof Oledzki <ole@....pl>
To:	"Brandeburg, Jesse" <jesse.brandeburg@...el.com>
cc:	"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
	"kaber@...sh.net" <kaber@...sh.net>,
	"e1000-devel@...ts.sourceforge.net" 
	<e1000-devel@...ts.sourceforge.net>,
	"Graham, David" <david.graham@...el.com>
Subject: RE: e1000 kills IPMI on 82541GI (Dell PE1425SC) + small 2.6.27
 regression

Hello,

On Sat, 1 Nov 2008, Krzysztof Oledzki wrote:

>
> On Fri, 31 Oct 2008, Brandeburg, Jesse wrote:
>
>> <modified the mail list a bit>
>> 
>> Krzysztof Oledzki wrote:
>>> I have started implementing IPMI on my servers and there is some
>>> inconvenience with e1000+82541GI (Dell PE1425SC).

<CUT>

>> What if the IPMI traffic was *not* on a vlan but you had vlans enabled in 
>> your network?
>
> Good question, I'll check this.

OK, putting IPMI on a default, untagged vlan makes it working.

> > 1) 2.6.26 kernel with vlan enabled IPMI breaks doesn't work until 
> > driver is loaded?
>
> I have a non-modular kernel with the driver build statically into it. IPMI 
> obviously works before I booted a Linux kernel, not sure if making th driver 
> modular changes anything (I hope not). With the statically linked driver I 
> have:
>
> <=2.6.26:
> - non-vlan host -> works
> - vlan host -> works with the dummy vlan
>
>> =2.6.27:
> - works only with the dummy vlan
>
> I'll retest with a modular configuration and let you know.

Just like I thought: vlan enabled IPMI *works* before the driver gets 
loaded, runing "modprobe e1000; ifconfig eth0 up" kills IPMI on 2.6.27 
and also kills it on older kernels when a first vlan is attached = when 
"VLAN filter" becomes enabled.

Best regards,

 				Krzysztof Olędzki

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ