netdev - Re: [PATCH 3/3] bnx2i: Add bnx2i iSCSI driver.

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: <483D1C05.70101@suse.de>
Date:	Wed, 28 May 2008 10:47:01 +0200
From:	Hannes Reinecke <hare@...e.de>
To:	Jeff Garzik <jeff@...zik.org>
Cc:	Michael Chan <mchan@...adcom.com>,
	David Miller <davem@...emloft.net>, rdreier@...co.com,
	anilgv@...adcom.com, michaelc@...wisc.edu,
	netdev <netdev@...r.kernel.org>, linux-scsi@...r.kernel.org,
	open-iscsi@...glegroups.com
Subject: Re: [PATCH 3/3] bnx2i: Add bnx2i iSCSI driver.

Hi all,

Jeff Garzik wrote:
> Michael Chan wrote:
>> If we change the implementation to use a separate IP address and
>> separate MAC address for iSCSI, will it be acceptable?  The iSCSI IP/MAC
>> addresses will be unknown to the Linux TCP stack and so no sharing of
>> the 4-tuple space will be needed.
>>
>> The patches will be very similar, except that all inet calls and
>> notifiers will be removed.
> 
> 
> IMO a totally separate MAC and IP would definitely be preferred...
> 
And as it happens, the machines I have here claim to use a different
MAC address for iSCSI anyway. So we should be using them.

Cheers,

Hannes
-- 
Dr. Hannes Reinecke		      zSeries & Storage
hare@...e.de			      +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: Markus Rex, HRB 16746 (AG Nürnberg)
--
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