This is the mail archive of the systemtap@sourceware.org mailing list for the systemtap project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: UDP 4-tuple problems

From: fche at redhat dot com (Frank Ch. Eigler)
To: "Born, Kenton P." <born2 at llnl dot gov>
Cc: "systemtap at sourceware dot org" <systemtap at sourceware dot org>
Date: Thu, 05 May 2011 10:13:10 -0400
Subject: Re: UDP 4-tuple problems
References: <3E5C34D3A9379847A659935F1C45AA5919D6430EEE@NSPEXCCR-A.the-lab.llnl.gov>

born2 wrote:

> While there seems to be several ways of obtaining address and port informat=
> ion for TCP, I have been unable to locate anything for UDP. [...]

With connectionless UDP, the 4-tuple is not really defined on a
per-socket basis, but rather on a per-message basis.  Based upon a
glance at the code, the local (IP,port) is in the inet_sock struct
(the same as for TCP); the message's destination/origin is in
msghdr->msg_name (recast as sockaddr_in*).

- FChE

References:
- UDP 4-tuple problems
  - From: Born, Kenton P.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]