From: Padraig Brady <padraig.brady@corvil.com>
To: netfilter@lists.netfilter.org
Subject: Re: UDP connection tracking problem
Date: Mon, 10 Nov 2003 15:17:57 +0000 [thread overview]
Message-ID: <3FAFAC25.8010808@corvil.com> (raw)
In-Reply-To: <3FAFA135.9050707@draigBrady.com>
P@draigBrady.com wrote:
> Hi, I've a very simple rule set as follows, and in summary
> it looks to me like udp connection tracking info
> is only being updated for traffic comming into the box?
>
> Chain INPUT (policy DROP)
> target prot opt source destination
> ACCEPT all -- 127.0.0.1 anywhere
> ACCEPT all -- anywhere anywhere state
> RELATED,ESTABLISHED
> ACCEPT all -- 172.18.1.170 anywhere
>
> Chain OUTPUT (policy ACCEPT)
> target prot opt source destination
> ACCEPT all -- anywhere anywhere state
> NEW,RELATED,ESTABLISHED
>
> The problem is that I can't initiate udp from this box.
> If I allow udp in, I can do tftp fine.
> Then removing the udp rule I can tftp fine for
> variable amount of time 0s, 30s, 180s.
>
> I'm using linux 2.4.20 and iptables v1.2.7a
Ah hang on, when the UDP is sent out, the following
is added to /proc/net/ip_conntrack as expected:
udp 17 22 src=172.18.1.55 dst=172.18.1.14 sport=32769 dport=69
[UNREPLIED] src=172.18.1.14 dst=172.18.1.55 sport=69 dport=32769 use=1
However the response packet doesn't use 69 as the sport.
It seems to use an ephemeral one (33118) :-(
FYI the tftpd is "tftp-hpa 0.34, with remap, with tcpwrappers"
Hmm: http://www.zytor.com/pipermail/syslinux/2003-April/001851.html
Pádraig.
next prev parent reply other threads:[~2003-11-10 15:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-10 14:31 UDP connection tracking problem P
2003-11-10 15:17 ` Padraig Brady [this message]
2003-11-10 16:05 ` P
[not found] ` <20031110175435.GC22483@cannon.eng.us.uu.net>
2003-11-10 17:26 ` P
2003-11-10 19:53 ` TFTP " Ramin Dousti
2003-11-10 23:51 ` Goetz Bock
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=3FAFAC25.8010808@corvil.com \
--to=padraig.brady@corvil.com \
--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