All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: staenker@rhcs.de
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: iptables bug using dhcpd3 on debian sarge 2.6.8
Date: Tue, 08 Mar 2005 16:45:59 +0100	[thread overview]
Message-ID: <422DC8B7.6060801@trash.net> (raw)
In-Reply-To: <6642317$1110205335422c6397f21926.15822394@config8.schlund.de>

staenker@rhcs.de wrote:
> hello,
> at first nice weekend! and now to to my problem.
> i tried to set up a firewall on my dsl gate. i want to use policy drop
> for input and output chain. so, if i was right, i have to write some
> rules for the dhcpd3 server, ssh, dns,... ok, i wrote the rules for
> sshd using port 64385. works fine. if i don't use this rules, sshd is
> not reachable. also fine. but i realised that my dhcp server works fine
> even though that i do not iplement any accept rules for dhcp. i know
> that sounds strange, thatswhy i put a date between the iptables calls
> that it looks a bit like i was not lying. and i wish i where - but
> wishes are wishes and reality is hard to accept. so pleasy believe me,
> that i was not lying! ok, here the output:

ISC DHCP uses AF_PACKET sockets on Linux by default, which receive
packets before iptables. There are some compile-time options to make it
use normal UDP sockets.

Regards
Patrick

  parent reply	other threads:[~2005-03-08 15:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-07 14:44 iptables bug using dhcpd3 on debian sarge 2.6.8 staenker
2005-03-08 13:28 ` richard hauswald
2005-03-08 15:45 ` Patrick McHardy [this message]
2005-03-10  8:10   ` richard hauswald
2005-03-10  9:35     ` Sven Schuster

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=422DC8B7.6060801@trash.net \
    --to=kaber@trash.net \
    --cc=netfilter-devel@lists.netfilter.org \
    --cc=staenker@rhcs.de \
    /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.