Hi!
Did you check for MTU problems? Like: The router cannot handle MTUs that are
sent, and does not fragment, but discard them? Anyway tcpdump or wireshark
might help.
Regards,
Ulrich
Spike White spikewhit...@gmail.com schrieb am 21.06.2012 um 04:41 in
Nachricht
On 06/22/2012 12:45 AM, narender mehra wrote:
I read the latter half of your reply now. Yes, we have iscsi_sw_data_recv
as the recv_actor function. Thanks for the reply.
Hey, what? Are you sure it is called iscsi_sw_data_recv?
I was thinking it should only be either:
iscsi_sw_tcp_recv
or
On Friday, June 22, 2012 3:28:38 AM UTC+3, Mike Christie wrote:
If you run
iscsiadm -m session -P 3
do you see us connected?
Yep, that is the case :
Iface IPaddress: 172.16.1.1
Iface HWaddress: empty
Iface Netdev: empty
SID: 11
We have been told this is a target bug and will be fixed in a upcoming
version of their target.
On 06/20/2012 07:23 PM, Eddie Wai wrote:
Hello Mike,
We recently discovered a login interoperability issue using software
iSCSI (open-iscsi 872) connecting against the iSCSI software target that
Sorry for the confusion. It is iscsi_sw_tcp_recv.
On Fri, Jun 22, 2012 at 11:14 PM, Mike Christie micha...@cs.wisc.eduwrote:
On 06/22/2012 12:45 AM, narender mehra wrote:
I read the latter half of your reply now. Yes, we have iscsi_sw_data_recv
as the recv_actor function. Thanks for the
