From: raido <raido@elin.ttu.ee>
To: netfilter@lists.netfilter.org
Cc: Adam Majer <adamm@galacticasoftware.com>
Subject: Re: DNAT forwarding problems
Date: Thu, 5 Aug 2004 15:32:47 +0300 [thread overview]
Message-ID: <200408051525.38235.raido@elin.ttu.ee> (raw)
In-Reply-To: <411166D5.30105@galacticasoftware.com>
Hi!
> external IP addresses: [A], [B]
> internal IP address: [C] - not the NAT box
>
> I want all udp port 53 traffic from [A]->[C] and from [B]->[C]. So I set
> up the following rules
>
> When the packet comes over interface[B], it also gets to the PREROUTING
> chain, but it never gets to the FORWARD chain and thus never even gets
> to [C]. It just dissapears into thin air. My routing seems correct..
> PS. kernel 2.6.7, iptables 1.2.9
I wrote few days ago about my problem which seems to be alike, in this list. I
have same configuration and I need to DNAT all traffic from [A] to [C] and
packets also disapear in PREROUTING chain. I have also 2.6.7 kernel and
iptables 1.2.9. Next I plan to upgrade to iptables 1.2.10. If this does not
help, maybe it is time to make a bug report?
Raido
next prev parent reply other threads:[~2004-08-05 12:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-04 22:44 DNAT forwarding problems Adam Majer
2004-08-05 12:32 ` raido [this message]
2004-08-05 16:55 ` Adam Majer
2004-08-09 2:45 ` raido
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=200408051525.38235.raido@elin.ttu.ee \
--to=raido@elin.ttu.ee \
--cc=adamm@galacticasoftware.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 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.