From: Ulysses Almeida <munky@maluco.com.br>
To: Netfilter Devel <netfilter-devel@lists.netfilter.org>
Subject: libipq/payload doubt
Date: Wed, 19 May 2004 02:20:32 -0400 [thread overview]
Message-ID: <20040519062032.GA32401@maluco.com.br> (raw)
First, thanks to all, for last answers, I think I am starting to
understand how I can handle with libipq.
But yet, I have some doubts:
What I could see from ip_queue.c, ipq_packet_msg->payload, comes
from skb->data. Where can i find (which files) where skb->data is
filled. 'Cose till now, I don't know what info I can get from
ipq_packet_msg->payload.
I alredy create my first daemon with libipq, I mixed libipq man
example, intercept.c (from netfilter cvs), and get some ideas from
tcp_ipv4.c (kernel). This daemon, just look for tcp packges, and print
some infos on stdout. It's printing IP src and dst address, and now
i'm trying to print src and dst TCP port address, but, I don't know
why, when I print those info, I can't get expected ports. port 80 is
showed as 20480.
Do I have to convert something before printing in human readable
format?
The source is on http://www.glug.ucdb.br/~ulysses/first.c
Thanks in advance (again).
[]s
--
.~. Ulysses Almeida
/ V \ munky@maluco.com.br
/ ( ) \ Seja livre, use GNU/Linux!
^^-^^
next reply other threads:[~2004-05-19 6:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-19 6:20 Ulysses Almeida [this message]
2004-05-19 6:47 ` libipq/payload doubt Mike-Ro-Chanel
2004-05-19 6:53 ` Chandrakanth Chereddi
2004-05-19 10:02 ` Richard Bishop
2004-05-20 0:03 ` Ulysses Almeida
2004-05-20 2:11 ` Ulysses Almeida
2004-05-20 13:33 ` Scott MacKay
2004-05-20 15:02 ` Henrik Nordstrom
2004-05-20 16:24 ` Scott MacKay
2004-05-20 14:58 ` Henrik Nordstrom
2004-05-20 2:11 ` Richard Bishop
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=20040519062032.GA32401@maluco.com.br \
--to=munky@maluco.com.br \
--cc=netfilter-devel@lists.netfilter.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.