From: Ramin Alidousti <ramin@cannon.eng.us.uu.net>
To: sshore@escape.ca
Cc: James Garrison <jhg@athensgroup.com>, netfilter@lists.samba.org
Subject: Re: DHCP and conntrack?
Date: Fri, 7 Jun 2002 15:36:10 -0400 [thread overview]
Message-ID: <20020607193610.GO29214@cannon.eng.us.uu.net> (raw)
In-Reply-To: <20020607173835.GA599@escape.ca>
On Fri, Jun 07, 2002 at 12:38:35PM -0500, sshore@escape.ca wrote:
> On Fri, Jun 07, 2002 at 12:00:19PM -0500, James Garrison wrote:
> > Does connection tracking understand incoming DHCP responses as
> > being related to recent outgoing broadcast DHCP requests? In other
> > words, if I configure iptables to allow outgoing DHCP broadcast
> > requests, do I have to explicitly open up a hole for the returning
> > response, or will conntrack do it for me with RELATED?
>
> Since dhcp requests go out on port 68, and responses come back on port 67,
> connection tracking will not relate them.
It's like you say, http traffic is not being tracked because the
outgoing packets go out on port 8 and the incoming packets come in
on port whatever like 1025. So, no, that's not the reason. The
reason could be this:
15:26:43.933324 vlan6 B 0.0.0.0.bootpc > 255.255.255.255.bootps: xid:0xdefebd43
15:26:43.981708 vlan6 > 10.0.6.1.bootps > 255.255.255.255.bootpc: xid:0xdefebd43
As you can see there is no "regular" src.port/dst.port relationship
here for the general conntrack module to catch this.
I hope that some guru someday will add this intelligence to the
code :-)
Ramin
> you'll need to explicitly open
> up a hole for the returning response.
>
> --
> Scottie Shore <sshore@escape.ca>
> "You haven't gamed until you've circle-strafed while barrel rolling."
> - Blair on the Logitech Cyberman II
prev parent reply other threads:[~2002-06-07 19:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-07 17:00 DHCP and conntrack? James Garrison
2002-06-07 17:38 ` sshore
2002-06-07 17:43 ` James Garrison
2002-06-07 19:36 ` Ramin Alidousti [this message]
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=20020607193610.GO29214@cannon.eng.us.uu.net \
--to=ramin@cannon.eng.us.uu.net \
--cc=jhg@athensgroup.com \
--cc=netfilter@lists.samba.org \
--cc=sshore@escape.ca \
/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