Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Andreas Jellinghaus <aj@dungeon.inka.de>
To: netfilter@lists.netfilter.org
Subject: netfilter and kernel 2.5.* ipsec
Date: 14 May 2003 18:35:26 +0200	[thread overview]
Message-ID: <1052930126.918.21.camel@simulacron> (raw)

Hi,

using setkey I can create rules based on
 - src ip, dst ip, src port, dest port, proto

using netfilter I can create rules on (but not limited to)
 - src ip, dst ip, src port, dest port, proto, state,
   incoming interface, outgoing interface, ...

so netfilter is a lot better. but netfilter cannot set
requirements for ipsec?

Is there any guide how to combine these two?

I could allow more or less anything with iptables
(only filter bogus packets etc.), and restrict access
to certain ports in the SPD database.

But isn't there a nicer way to do that?
I have real trouble with the combination of
SPD and dynamic ip: 
  my machine has a dynamic ip, and of course I want
  restrict access to most ports, unless an ipsec
  connection is used. using spdadd I need to specify
  my IP as target, so that is quite ugly. e.g.

spdadd 0.0.0.0/0 192.168.0.10[25] -P in deny;

I would need to change that rule everytime my ip changes,
so I don't like doing that.

Also good security is always about shutting everything down
and then making small holes where necessary. I don't want
to have a big fat hole in my iptables config, but I don't see
how else I can allow access to certain ports, but restrict
the access to ipsec connections.

With kernel 2.4.* the ipsec0 interface was used in rules
to match whether a packet is coming in via ipsec or not.
Is there a similiar way to do the same thing?

Regards, 

Andreas



                 reply	other threads:[~2003-05-14 16:35 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=1052930126.918.21.camel@simulacron \
    --to=aj@dungeon.inka.de \
    --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