From: Peter Hoare <Peter.Hoare@signal.qinetiq.com>
To: netfilter-devel@lists.netfilter.org
Subject: changing packets with libipq
Date: Thu, 12 Dec 2002 12:12:12 +0000 [thread overview]
Message-ID: <3DF87D1C.B276B46@signal.qinetiq.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1021 bytes --]
We are having problems in trying to use the userspace libipq to change
incoming packets to the kernel. We are picking up UDP packets off the
pre-routing queue, changing the packet header and checksums and then
accepting the new packet back through the ipq_set_verdict() call with
NF_ACCEPT.
This new packet is being delivered quite happily to an end-user
application on the local machine but if the packet is to be forwarded
through this host to another machine it appears to be dropped by the
kernel. Is there a limit to what we are allowed to change in the packet
through libipq? (There are some hints in the documentation to do with
caching fields in the skb that may be the cause of our problem). Our
guess is that because we are significantly changing the header that the
new packet is no longer being recognised as related to the old one?
Is what we are doing not possible using libipq? If not do we have to
write a kernel module to do it or is there any other way to do it in
userspace?
Thank you
Peter Hoare
[-- Attachment #2: Card for Peter Hoare --]
[-- Type: text/x-vcard, Size: 928 bytes --]
begin:vcard
n:Hoare;Peter
tel;fax:+44 1684 894389
tel;work:+44 1684 896438
x-mozilla-html:TRUE
url:www.qinetiq.com
org:QinetiQ;Sensors and Information Processing
version:2.1
email;internet:peteh@signal.qinetiq.com
title:Principal Scientist
adr;quoted-printable:version:2.1;;E204 =0D=0AQinetiQ=0D=0ASt Andrews Road;Malvern;Worcs;WR14 3PS;UK
note;quoted-printable:The Information contained in this e-mail and any subsequent =0D=0Acorrespondence is private and is intended solely for the =0D=0Aintended recipient(s). For those other than the intended recipient =0D=0Aany disclosure, copying, distribution, or any action taken or =0D=0Aomitted to be taken in reliance on such information is prohibited =0D=0Aand may be unlawful.=0D=0A=0D=0AThe views expressed above are entirely those of the writer and =0D=0Ado not represent the views, policy or understanding of any other =0D=0Aperson or official body.
fn:Pete Hoare
end:vcard
reply other threads:[~2002-12-12 12:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3DF87D1C.B276B46@signal.qinetiq.com \
--to=peter.hoare@signal.qinetiq.com \
--cc=netfilter-devel@lists.netfilter.org \
--cc=peteh@signal.qinetiq.com \
/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.