Hi Dave,
If the NetAPP target is misconfigured, why would it even allow any unknown
initiator to go beyond discovery session? It appears that a
semi-successful lun scan has happened or am mis reading the report?
If I read deeper into your comments, does the target support ACL's?
If yes, then
Andre Hedrick wrote:
Hi Dave,
If the NetAPP target is misconfigured, why would it even allow any
unknown
initiator to go beyond discovery session? It appears that a
semi-successful lun scan has happened or am mis reading the report?
I think you're misreading the report and/or don't understand
AJ Lewis wrote:
Nicholas A. Bellinger [EMAIL PROTECTED] writes:
The following is the first public release of the PyX Technologies iSCSI
Initiator Core Stack v1.6.1.20 for Linux 2.6.11-rc4. This is a full
featured iSCSI Initiator stack that is capable of mulitplexing coast to
coast across
On Thu, 24 Feb 2005 23:50:29 -0800, Nicholas A. Bellinger [EMAIL PROTECTED]
wrote:
On Thu, 2005-02-24 at 14:51 -0600, AJ Lewis wrote:
I've gotten this setup and
running, but I can't seem to talk to my iscsi target. The initiator
detects it, but it can't recognize the type:
On Fri, 2005-02-25 at 09:18 -0600, AJ Lewis wrote:
On Thu, 24 Feb 2005 23:50:29 -0800, Nicholas A. Bellinger [EMAIL
PROTECTED] wrote:
On Thu, 2005-02-24 at 14:51 -0600, AJ Lewis wrote:
I've gotten this setup and
running, but I can't seem to talk to my iscsi target. The initiator
Nicholas A. Bellinger [EMAIL PROTECTED] writes:
The following is the first public release of the PyX Technologies iSCSI
Initiator Core Stack v1.6.1.20 for Linux 2.6.11-rc4. This is a full
featured iSCSI Initiator stack that is capable of mulitplexing coast to
coast across multiple
Comments from an initial scan of the code. This does not include any
review of iSCSI interaction itself.
1) the TRACE stuff uses too much stack space
2) style: way too many interal headers; feel free to disagree, though,
this is maintainer's preference.
3) non-standard function definitions:
Hi Jeff,
On Wed, 2005-02-23 at 16:03 -0500, Jeff Garzik wrote:
Comments from an initial scan of the code. This does not include any
review of iSCSI interaction itself.
1) the TRACE stuff uses too much stack space
Aside from TRACE_ERROR, the other TRACE_ defs are not compiled in
per
8 matches
Mail list logo
