From: Patrick McHardy <kaber@trash.net>
To: Tim Vandermeersch <tim.vandermeersch@pandora.be>
Cc: Netfilter-devel <netfilter-devel@lists.netfilter.org>
Subject: Re: Problems determining the correct tcp header size
Date: Fri, 28 Mar 2003 01:05:10 +0100 [thread overview]
Message-ID: <3E8391B6.1040301@trash.net> (raw)
In-Reply-To: <3E8386EE.6040701@pandora.be>
I haven't followed the whole thread but if you use your target in
LOCAL_IN/PRE_ROUTING/FORWARD skb->h.th does not point to
the tcp header. to get the start of the tcp header, use:
tcph = (struct tcphdr *)((u_int32_t*)skb->nh.iph + skb->nh.iph->ihl)
Patrick
Tim Vandermeersch wrote:
> Hi,
>
> At the moment I'm using '-p TCP' to make sure that all packets are
> TCP, the final version will look at the protocol in the iphdr.
>
> With the following function you can compare the tcp header lenght from
> the (*pskb)->h.th with the one calculated using
> (*pskb)->data[some_math..]
>
> static unsigned int ipt_mytarget_target(struct sk_buff **pskb,
> unsigned int hooknum,
> const struct net_device *in, const struct net_device *out,
> const void *targetinfo, void *userinfo)
> {
> struct iphdr *iph = (struct iphdr *) (*pskb)->nh.iph;
> struct tcphdr *tcph = (struct tcphdr *) (*pskb)->h.th;
> int i;
>
> printk("tcp_len = %d, tcp_len = %d\n",
> ((*pskb)->data[iph->ihl*4+12]>>4)*4, tcph->doff*4);
> for (i=0; i<40; i++) {
> printk("%2.2X ", (char *) (*pskb)->data[i]);
> }
> printk("\n\n");
> return IPT_CONTINUE;
> }
>
> This produces the following output:
>
> tcp_len = 32, tcp_len = 52
> 45 00 00 34 19 D8 40 00 32 06 73 C5 D9 11 21 0A C0 A8 00 63 1A 0B 0C
> 29 7E 44 0B 5F B9 54 D1 59 80 10 81 FA AF DC 00 00 tcp_len = 32,
> tcp_len = 52
> 45 00 00 61 55 FC 40 00 32 06 37 74 D9 11 21 0A C0 A8 00 63 1A 0B 0C
> 29 7E 44 0B 5F B9 54 D1 59 80 18 82 18 60 97 00 00 tcp_len = 32,
> tcp_len = 48
> 45 00 00 34 2C 24 40 00 3F 06 54 79 C0 A8 00 63 D9 11 21 0A 0C 29 1A
> 0B B9 54 D1 59 7E 44 0B 8C 80 10 87 C0 A9 C9 00 00 ...
>
> 32 is the correct size, but why do i get 52, 48, ... from tcph->doff*4 ?
>
> I allready downloaded the kernel source (from linux.org) and compiled
> a new kernel again. Does any one know what might be causing these
> incorrect header sizes?
>
>
> Thanks in advance,
> Tim Vandermeersch
>
>
prev parent reply other threads:[~2003-03-28 0:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-19 20:04 Problems determining the correct tcp header size qber66
2003-03-26 15:35 ` Harald Welte
2003-03-27 23:19 ` Tim Vandermeersch
2003-03-28 0:05 ` Patrick McHardy [this message]
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=3E8391B6.1040301@trash.net \
--to=kaber@trash.net \
--cc=netfilter-devel@lists.netfilter.org \
--cc=tim.vandermeersch@pandora.be \
/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.