Linux Netfilter discussions
 help / color / mirror / Atom feed
From: DI Roman Fiedler <roman.fiedler@telbiomed.at>
To: netfilter@vger.kernel.org
Subject: Connection intercept
Date: Tue, 15 Jan 2008 17:43:29 +0100	[thread overview]
Message-ID: <478CE2B1.2000806@telbiomed.at> (raw)

Hi all,

I want to create an iptables setup that routes all packets that would be 
dropped to a gateway on a separate interface. I try to do it by marking 
these packets with a INTERCEPT connmark (and ACCEPT them) and use a 
different routing table (std. policy routing) with a default route to 
the separate interface.  The problem: I want to use the filter tables to 
do the filtering, but the packets are already routed when they reach the 
filter tables. So I cannot route the first packet of a connection to 
this special interface, hence no real connection intercept is possible.

Setup:

Inet  - Firewall - Internal Zone
                 |
              Intercept host


The intercept host will answer for all IPs (Honeypot like), so that 
connections that would have been refused are openen and can be analysed. 
Example: Host xxxx from internal zone tries to reach nonstandard mail 
exchange, mail connection is automatically routed to the intercept host 
and mail is captured to see if xxxxx is just malconfigured or if some 
malware tries to send out some data.


Any ideas for workarounds to realise such an fw setup, e.g. exotic 
netfilter targets that can push back a packet to the beginning of the 
filter process so that it runs through the whole filter again, this time 
with the correct connmark so that it uses the alternate interface

greets, Roman







             reply	other threads:[~2008-01-15 16:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-15 16:43 DI Roman Fiedler [this message]
2008-01-16  7:01 ` Connection intercept Josh Cepek
2008-01-16  9:37   ` DI Roman Fiedler
2008-01-16 15:36     ` Grant Taylor

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=478CE2B1.2000806@telbiomed.at \
    --to=roman.fiedler@telbiomed.at \
    --cc=netfilter@vger.kernel.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