From: Phil C <flah@hell.com>
To: netfilter@lists.netfilter.org
Subject: Re: help accepting unbound addresses
Date: Fri, 14 May 2004 23:32:49 -0400 [thread overview]
Message-ID: <20040515033249.GW78829@adsl195.cofs.net> (raw)
In-Reply-To: <20040515002908.GU78829@adsl195.cofs.net>
As a follow up to my initial questions, I began looking into the possible
viability of using libipq and the QUEUE target. Right now I'm using the
example provided in the man page, but with the same results... The packets are
looping and eventually producing icmp in-transit timeouts.
I thought that doing an ipq_set_verdict() would allow the packet to actually
be accepted, short circuiting the rest of the kernel processing of the
packet... It appears that this is not the case, or am I missing something?
Again, all I really need to do it accept traffic for addresses that aren't
bound to any interfaces, without modifying the original destination address.
It seems that one way or another, this must be possible.
--
<flah@hell.com>
\x104\x97\x108\x102
next prev parent reply other threads:[~2004-05-15 3:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-15 0:29 help accepting unbound addresses Phil C
2004-05-15 3:32 ` Phil C [this message]
2004-05-15 18:51 ` Phil C
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=20040515033249.GW78829@adsl195.cofs.net \
--to=flah@hell.com \
--cc=netfilter@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox