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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <483CD3F3.6070308@garzik.org>
Date:	Tue, 27 May 2008 23:39:31 -0400
From:	Jeff Garzik <jeff@...zik.org>
To:	Michael Chan <mchan@...adcom.com>
CC:	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.

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...

	Jeff


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