Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Ramin Dousti <ramin@cannon.eng.us.uu.net>
To: Yoann <yoann.juet@ifrance.com>
Cc: George Vieira <georgev@citadelcomputer.com.au>,
	netfilter@lists.netfilter.org
Subject: Re: help bootp filters
Date: Mon, 16 Jun 2003 11:40:43 -0400	[thread overview]
Message-ID: <20030616154043.GC30628@cannon.eng.us.uu.net> (raw)
In-Reply-To: <003901c33408$8b802640$0101a8c0@cerbere>

If I recall correctly some DHCP servers operate on raw IP sockets
and bypass the normal path of the packet traversal. It takes the
requests off the wire and puts the replies on the wire. You can look
at the sources of your DHCP server to confirm this observation...

Ramin


> > Hi,
> >
> > I experiment trouble with netfilter/iptables on rh9. I configured a server
> with the following rules just to accept, for the moment, SSH sessions,
> everything else is dropped.
> >
> > $IPTABLES -P INPUT DROP
> > $IPTABLES -P FORWARD DROP
> > $IPTABLES -P OUTPUT DROP
> >
> > $IPTABLES -A INPUT -i $LO_IFACE -j ACCEPT
> > $IPTABLES -A OUTPUT -o $LO_IFACE -j ACCEPT
> >
> > $IPTABLES -A INPUT -p tcp --dport 22 -m state --state NEW,ESTABLISHED -j
> ACCEPT
> > $IPTABLES -A OUTPUT -p tcp --sport 22 -m state --state ESTABLISHED -j
> ACCEPT
> >
> > $IPTABLES -A INPUT -j LOG --log-level warning --log-prefix "DROP input
> packet died: "
> > $IPTABLES -A OUTPUT -j LOG --log-level warning --log-prefix "DROP output
> packet died: "
> >
> > It works fine, excepted for DHCP/BOOTP requests. In fact, the server
> (single interface with IP address 192.168.2.110) is also a DHCP server and
> responds to BOOTP requests as shown below :
> >
> > [root@pluton root]# tcpdump port 67 or 68
> > tcpdump: listening on eth0
> > 17:10:30.925605 0.0.0.0.bootpc > 255.255.255.255.bootps:  xid:0x9a499735
> flags:0x8000 [|bootp]
> > 17:10:31.005330 192.168.2.1.bootps > 255.255.255.255.bootpc:
> xid:0x9a499735 flags:0x8000 Y:192.168.2.110 S:192.168.2.1 ether
> 0:90:f5:c:80:a0 [|bootp] [tos 0x10]
> >
> > netfilter log messages are show below :
> >
> > Jun 12 17:28:29 pluton kernel: DROP input packet died: IN=eth0 OUT=
> MAC=ff:ff:ff:ff:ff:ff:00:90:f5:0c:80:a0:08:00 SRC=0.0.0.0
> DST=255.255.255.255 LEN=328 TOS=0x00 PREC=0x00 TTL=128 ID=55877 PROTO=UDP
> SPT=68 DPT=67 LEN=308
> > Jun 12 17:28:29 pluton kernel: DROP output packet died: IN= OUT=eth0
> SRC=192.168.2.1 DST=192.168.2.110 LEN=48 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF
> PROTO=ICMP TYPE=8 CODE=0 ID=63703 SEQ=0
> >
> > Can you explain me why a BOOTP response is sent even though such packets
> (seem to be) dropped by iptables rules ?
> >
> > Many thanks,
> > Regards,
> > Yoann.
> >
> >
> 
> 
> _____________________________________________________________________
> Envie de discuter en "live" avec vos amis ? T?l?charger MSN Messenger
> http://www.ifrance.com/_reloc/m la 1?re messagerie instantan?e de France
> 


  reply	other threads:[~2003-06-16 15:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-16 12:56 help bootp filters George Vieira
2003-06-16 13:09 ` Yoann
2003-06-16 15:40   ` Ramin Dousti [this message]
2003-06-16 14:41 ` Ramin Dousti

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=20030616154043.GC30628@cannon.eng.us.uu.net \
    --to=ramin@cannon.eng.us.uu.net \
    --cc=georgev@citadelcomputer.com.au \
    --cc=netfilter@lists.netfilter.org \
    --cc=yoann.juet@ifrance.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox