Re: virt-manager broken by bind(0) in net-next.
From: Herbert Xu <herbert@gondor.apana.org.au>
Date: 2009-01-30 12:59:07
Possibly related (same subject, not in this thread)
- 2009-02-01 · Re: virt-manager broken by bind(0) in net-next. · David Miller <davem@davemloft.net>
- 2009-02-01 · Re: virt-manager broken by bind(0) in net-next. · Evgeniy Polyakov <hidden>
- 2009-02-01 · Re: virt-manager broken by bind(0) in net-next. · Eric Dumazet <hidden>
- 2009-02-01 · Re: virt-manager broken by bind(0) in net-next. · Evgeniy Polyakov <hidden>
- 2009-02-01 · Re: virt-manager broken by bind(0) in net-next. · Evgeniy Polyakov <hidden>
Evgeniy Polyakov [off-list ref] wrote:
So it is not explicit bind call, but port autoselection in the connect(). Can you check what errno is returned? Did I understand it right, that connect fails, you try different address, but then suddenly all those sockets become 'alive'?
Yes, I think a good strace vs. a bad strace would be really helpful in these cases. Thanks, -- Visit Openswan at http://www.openswan.org/ Email: Herbert Xu ~{PmV>HI~} [off-list ref] Home Page: http://gondor.apana.org.au/~herbert/ PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt