From: Wichert Akkerman <wichert@wiggy.net>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: netdev@oss.sgi.com
Subject: Re: sendmsg ignoring bind?
Date: Fri, 20 May 2005 15:20:09 +0200 [thread overview]
Message-ID: <20050520132009.GD4151@wiggy.net> (raw)
In-Reply-To: <20050520101749.GA8661@gondor.apana.org.au>
Previously Herbert Xu wrote:
> This could be a cmsg option that overrode the bind address. Please
> decode it so that we know what it's doing.
I had to hack strace a bit to decode that. The cmsg option turns out
to be somewhat useless:
cmsg_type=IP_PKTINFO, {ifindex=0,ipi_spec_dst=inet_addr("0.0.0.0"),ipi_addr=("0.0.0.0")}}, msg_flags=0},
Wichert.
--
Wichert Akkerman <wichert@wiggy.net> It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
next prev parent reply other threads:[~2005-05-20 13:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-20 8:18 sendmsg ignoring bind? Wichert Akkerman
2005-05-20 10:17 ` Herbert Xu
2005-05-20 13:20 ` Wichert Akkerman [this message]
2005-05-20 13:24 ` Herbert Xu
2005-05-20 13:31 ` Wichert Akkerman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050520132009.GD4151@wiggy.net \
--to=wichert@wiggy.net \
--cc=herbert@gondor.apana.org.au \
--cc=netdev@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).