I think user error on my part caused my followup replies to post with the
wrong email address (one that has not joined this group). Maybe that's why
I don't see them in this thread? Sorry about that. Let me try again...
On Monday, January 12, 2015 at 12:54:38 PM UTC-8, Mike Christie wrote:
...
>
> Thomas, let me know if your question was for functionality you needed or
> just looking through the code and were curious.
>
>
It's functionality that I really want. In fact, I'm here in this forum
because strace on iscsid showed it was never calling bind(), and when I
went to add the bind() call myself I discovered all the code I wanted was
already there but disabled. I have an environment where a single interface
has multiple different IP addresses configured. For example:
# ip addr show eth0
3: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state
UP qlen 1000
link/ether 00:50:56:9f:4c:5d brd ff:ff:ff:ff:ff:ff
inet 10.108.53.143/21 scope global eth0
inet 10.108.53.243/21 scope global secondary eth0
inet6 fe80::250:56ff:fe9f:4c5d/64 scope link
valid_lft forever preferred_lft forever
In this example, my target will only accept logins from 10.108.53.243.
Unless we call bind(), there's no way to make this work. SO_BINDTODEVICE
and bind() are two very different things, for two very different purposes.
One cannot be used as a substitute for the other.
How does this proposal sound:
If the administrator configures an explicit interface name with
iface.net_ifacename, use SO_BINDTODEVICE.
If the administrator configures an explicit IP address with
iface.ipaddress, use bind().
If the administrator configures both of the above, use both of the above.
If the administrator configures neither, use neither.
I think this would give administrators all the flexibility they need. Is
there a downside to this proposal that I'm not seeing?
Thanks,
Tom.III
--
You received this message because you are subscribed to the Google Groups
"open-iscsi" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to open-iscsi+unsubscr...@googlegroups.com.
To post to this group, send email to open-iscsi@googlegroups.com.
Visit this group at http://groups.google.com/group/open-iscsi.
For more options, visit https://groups.google.com/d/optout.
