From: Eric Bauman <baumane@livejournal.dk>
To: netfilter@vger.kernel.org
Subject: Re: Problem with rdate and iptables
Date: Mon, 26 Apr 2010 23:02:56 +1000 [thread overview]
Message-ID: <4BD58F00.5090102@livejournal.dk> (raw)
In-Reply-To: <4BD578E0.4040606@plouf.fr.eu.org>
On 26/04/2010 21:28, Pascal Hambourg wrote:
> Could you capture the time query and reply packets (port 37) with a
> packet sniffer such as tcpdump or wireshark ?
Yes, I just tried that, and I think it shows the problem. It turns out
that a TIME request is being made to IP A, but the response is coming
from IP B! So I'm not surprised iptables isn't matching it as
established or related.
That leads me to ask, who is in the wrong? Should iptables be matching
the response, should the TIME server be responding with the address from
which it receives a query, or is it my fault for not knowing that a
request/response IP mismatch is legal behaviour and crafting an
appropriate rule?
Cheers,
Eric
next prev parent reply other threads:[~2010-04-26 13:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-23 19:54 Problem with rdate and iptables Eric Bauman
2010-04-25 11:54 ` Pascal Hambourg
2010-04-26 9:54 ` Eric Bauman
2010-04-26 11:28 ` Pascal Hambourg
2010-04-26 13:02 ` Eric Bauman [this message]
2010-04-26 13:06 ` Jan Engelhardt
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=4BD58F00.5090102@livejournal.dk \
--to=baumane@livejournal.dk \
--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 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.