From: "Randy Grimshaw" <rgrimsha@syr.edu>
To: netfilter@lists.netfilter.org
Subject: ebtables iptables DNAT something missing
Date: Wed, 14 Dec 2005 09:43:07 -0500 [thread overview]
Message-ID: <s39fe950.070@gwia201.syr.edu> (raw)
I thought I followed the recipe for DNAT on a transparent firewall correctly with the statement below, and sniffing shows that the traffic is redirected. But although the client receives the return responses from the server at the dnat destination - the client basically ignores it. (possibly as unexpected noise). What am I missing?
iptables -t nat -D PREROUTING -p tcp --dport 80 -m physdev --physdev-in eth1 -m mark --mark 9 -j DNAT --to-destination 192.168.12.12:80
Thank you
<><Randy
<><Randall Grimshaw
Room 203 Machinery Hall
Syracuse University
Syracuse, NY 13244
315-443-5779
rgrimsha@syr.edu
next reply other threads:[~2005-12-14 14:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-14 14:43 Randy Grimshaw [this message]
2005-12-14 16:21 ` ebtables iptables DNAT something missing Jörg Harmuth
2006-01-03 7:21 ` Jan Engelhardt
-- strict thread matches above, loose matches on Subject: below --
2005-12-15 16:10 Randy Grimshaw
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=s39fe950.070@gwia201.syr.edu \
--to=rgrimsha@syr.edu \
--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