From: Cord Seele <Seele@emlix.com>
To: linux-kernel@vger.kernel.org
Subject: getsockopt() with IP_PKTINFO not working?
Date: Wed, 20 Dec 2000 17:44:34 +0100 [thread overview]
Message-ID: <3A40E1F2.2C8E0127@emlix.com> (raw)
I am trying to get the destination address of an incoming udp packet
with getsockopt().
According to the man pages flag IP_PKTINFO should do that. But it
doesn't work:
struct in_pktinfo pktinfo;
socklen_t optlen;
struct in_addr local_addr;
optlen=(socklen_t)sizeof(pktinfo);
syslog (LOG_ERR, "ERR %d",
getsockopt(fd, SOL_IP, IP_PKTINFO, &pktinfo, &optlen));
syslog (LOG_ERR, "LENGTH %d %d", (int)optlen, sizeof(pktinfo));
local_addr=pktinfo.ipi_addr;
syslog (LOG_ERR,"ADDR %s",inet_ntoa(local_addr));
results in /var/log/messages:
Dec 19 19:27:49 coda tftpd[20081]: ERR 0
Dec 19 19:27:49 coda tftpd[20081]: LENGTH 4 12
Dec 19 19:27:49 coda tftpd[20081]: ADDR 232.252.255.191
While getsockopt() returns no error, the resulting length is too short
and the addr is
definitely invalid. I would expect either getsockopt() to return -1, it
this is not
implemented or return at least 12 valid bytes.
(I am running a 2.2.16 kernel with glibc 2.1.3.)
I even tried the 'hard way' using recvmsg() but the resulting
msg_controllen == 0.
Background:
If a machine has more than one address in a single network, i.e.
eth0 192.168.0.10
eth0:1 192.168.0.20
a call to bind() normally assigns the primary ip address (.10) to the
socket.
If the server was addressed on his second address (.20) the request is
not answered
and fails. I have this problem with tftpd.
Or is there a better way to get the destination address of an incoming
udp packet?
Thanks for any help.
Cord Seele
PS: Please CC me since I am not an the list.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next reply other threads:[~2000-12-20 17:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-20 16:44 Cord Seele [this message]
2000-12-20 17:23 ` Andi Kleen
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=3A40E1F2.2C8E0127@emlix.com \
--to=seele@emlix.com \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®