Mike Christie wrote: >> basically, since the connection establishment framework is IP based, I would >> be happy >> to just get some source ip in the kernel when ep_connect is called. I saw the >> comment on why bind_src_by_address is problematic, but this doesn't apply to >> IB/iser.
> Which comment are you talking about? Are you talking about bind() not > doing what you would want for iscsi_tcp (target sometimes sends data to > the wrong port) or are you talking about if you were to use DHCP and so > the IPs could change over boots? I wasn't a ware that the issue is IP changing across boots, thanks for elaborating on this. I was referring to the comment above bind_src_by_address saying "This is not supported for now, because it is not exactly what we want. It also turns out that targets will send packets to other interfaces causing all types of weird things to happen". > So is there anything in there that is static and can be used to identify the > port? YES. the 64 bit GUID is in this respect the equivalent of the Ethernet MAC which comes from the provider, both are unique per device/port and on each reboot will be shown. In the example I sent the GUID for ib0 was 00:02:c9:03:00:02:6b:df and for ib1 00:02:c9:03:00:02:6b:e0 > That iscsi code actually uses the same sys/lib calls as ifconfig mmm, I just realized that the net helpers code is embedded in the open-iscsi sources, this means that basically we can change it to look on suffix of the HW address which in the ethernet case will be the full address (48 bits) and in the IPoIB case just the GUID (64 bits out of the 128 bits). Or. -- 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.
