You might try supplying the target IP address manually instead of using the one
obtained by discovery.
paul
On Mar 10, 2011, at 3:24 PM, ravi brounstein wrote:
> the server side is NAT actually. soi am hitting snags as it scans the wan ip,
> finds the target, but as a NAT ip (local) not WAN ... so when I try to
> connect it fails.
>
> Thank You,
>
> Ravi Brounstein
> Helpdesk Team
> Deus Machine, LLC
> http://www.deusmachine.com
> Tel. 877.840.6024 x 101
>
> On Mar 10, 2011, at 12:13 PM, "Paul Koning" <[email protected]> wrote:
>
>> iSCSI over WAN doesn't make much sense.
>>
>> You're right, the discovery machinery sends IP addresses, which won't work
>> if the target is behind NAT. If you can tell the client to connect
>> directory to a configured target IP address, that might work.
>>
>> It sounds like your client side has NAT; I don't see why that would be a
>> problem.
>>
>> Still, you might want to change to some other protocol that's optimized for
>> WAN use. While in theory nothing prevents iSCSI from working there, it was
>> certainly never considered a reasonable scenario.
>>
>> paul
>>
>> On Mar 9, 2011, at 6:00 PM, ravi brounstein wrote:
>>
>>> Hey there,
>>>
>>> I have seen many places offering iSCSI storage over WAN.
>>>
>>> Currently I am using openfiler, and my question is what must be done
>>> to make iSCSI work in this way?
>>>
>>> Currently what I experience is that the iSCSI target shows up as the
>>> LAN address (I am behind NAT) so it fails to connect at the WAN
>>> address.
>>
--
You received this message because you are subscribed to the Google Groups
"open-iscsi" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/open-iscsi?hl=en.
