From: XiChimos <xichimos@plobe.com>
To: Henrik Nordstrom <henrik@marasystems.com>
Cc: Netfilter Development Mailinglist <netfilter-devel@lists.netfilter.org>
Subject: Re: Buffer size
Date: Tue, 20 Jan 2004 21:47:18 -0500 [thread overview]
Message-ID: <400DE836.8050604@plobe.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0401210325200.30308-100000@filer.marasystems.com>
Well, basically one that contains the payload and IP header, which is
returned by ipq_read. Basically my question is if I am casting the
payload of the ipq packet msg structure into a data-type, what is the
maximum size that this type should be? Or in other words, what is the
largest value of the ipq packet msg structure's data length field? I
thought it should be 2^16 bytes, but when I saw that in the example code
they had ipq_read only needing a buffer of size 2046 bytes, I started to
question myself.
Henrik Nordstrom wrote:
>What buffer are you referring to?
>
>Regars
>Henrik
>
>On Tue, 20 Jan 2004, XiChimos wrote:
>
>
>
>>The application adds an IP option to every TCP packet that it sees.
>>
>>Henrik Nordstrom wrote:
>>
>>
>>
>>>On Tue, 20 Jan 2004, XiChimos wrote:
>>>
>>>
>>>
>>>
>>>
>>>>I was looking at the code for a userspace application and noticed that
>>>>the buffer size was 2048.
>>>>
>>>>
>>>>
>>>>
>>>What kind of userspace application?
>>>
>>>Regards
>>>Henrik
>>>
>>>
>>>
>>>
>>
>>
next prev parent reply other threads:[~2004-01-21 2:47 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030725173900.E6E952C2AE@lists.samba.org>
[not found] ` <200307251756.VAA12609@dub.inr.ac.ru>
2004-01-11 13:01 ` MASQUERADE: Route sent us somewhere else (was Re: Fw: Rusty's brain broke!) Harald Welte
2004-01-11 13:55 ` Julian Anastasov
2004-01-11 21:11 ` Henrik Nordstrom
2004-01-17 11:09 ` Future of CONNMARK (was " Harald Welte
2004-01-17 17:50 ` Henrik Nordstrom
2004-01-17 12:54 ` IP Options with libipq XiChimos
2004-01-21 13:44 ` Harald Welte
2004-01-18 13:20 ` Future of CONNMARK (was Re: MASQUERADE: Route sent us somewhere else (was Re: Fw: Rusty's brain broke!) Harald Welte
2004-01-18 17:16 ` Henrik Nordstrom
2004-01-19 23:15 ` Herve Eychenne
2004-01-19 23:48 ` Henrik Nordstrom
2004-01-20 1:13 ` Herve Eychenne
2004-01-20 7:05 ` Henrik Nordstrom
2004-01-20 7:12 ` Henrik Nordstrom
2004-01-20 23:21 ` Herve Eychenne
2004-01-20 18:34 ` Buffer size XiChimos
2004-01-21 0:45 ` Henrik Nordstrom
2004-01-20 19:58 ` XiChimos
2004-01-21 2:25 ` Henrik Nordstrom
2004-01-21 2:47 ` XiChimos [this message]
2004-01-21 8:45 ` Henrik Nordstrom
2004-01-20 23:55 ` Future of CONNMARK (was Re: MASQUERADE: Route sent us somewhere else (was Re: Fw: Rusty's brain broke!) Henrik Nordstrom
2004-01-21 23:49 ` Harald Welte
2004-01-20 13:01 ` Harald Welte
2004-01-21 0:17 ` extensions manpage, howto etc Henrik Nordstrom
2004-01-21 22:02 ` Harald Welte
2004-01-21 0:44 ` iptables error reporting Henrik Nordstrom
2004-01-21 2:16 ` iptables extensions manpage Henrik Nordstrom
2004-01-21 22:00 ` Harald Welte
2004-02-02 23:40 ` [patch, resent] Updated CONNMARK Henrik Nordstrom
2004-02-03 8:20 ` Harald Welte
2004-02-03 9:03 ` Henrik Nordstrom
2004-02-03 9:50 ` Harald Welte
2004-01-18 19:14 ` iptables extension manpages Henrik Nordstrom
2004-01-17 18:46 ` Future of CONNMARK (was Re: MASQUERADE: Route sent us somewhere else (was Re: Fw: Rusty's brain broke!) Tom Eastep
2004-01-17 23:40 ` Henrik Nordstrom
2004-01-18 0:20 ` Tom Eastep
2004-01-12 1:07 ` Patrick McHardy
2004-01-12 4:30 ` Rusty Russell
2004-01-13 4:30 ` Patrick McHardy
2004-01-13 8:21 ` Julian Anastasov
2004-01-13 11:54 ` Harald Welte
2004-01-14 5:20 ` Rusty Russell
2004-01-12 11:08 ` Julian Anastasov
2004-01-14 16:11 ` kuznet
2004-01-14 23:42 ` Julian Anastasov
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=400DE836.8050604@plobe.com \
--to=xichimos@plobe.com \
--cc=henrik@marasystems.com \
--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.