On Wed, Apr 2, 2014 at 4:05 PM, Nikos Mavrogiannopoulos <nmav at gnutls.org> wrote: > Is it the UDP socket you worry about? In that case would it make sense > to allow setting an arbitrary address to bind on, or should the client > just bind the UDP socket to the same one TCP is using (see attached > patch)? A worry about both - TCP and UDP. For example if host has got 2 IP 10.0.0.1 and 10.0.0.100 (on one or many interface) you should be able to choose which one is source for all outgoing packets. My idea is to see in openconnect similar option to wget's --bind-address=ADDRESS
