Linux Netfilter discussions
 help / color / mirror / Atom feed
From: "Alexis" <alexis@tpys.com.ar>
To: netfilter <netfilter@lists.netfilter.org>
Subject: Re: DNAT problem
Date: Sat, 29 May 2004 12:36:37 -0300	[thread overview]
Message-ID: <000701c44592$bb254460$0200000a@heretic> (raw)
In-Reply-To: 20040529172536.6df75cca.leslie.polzer@gmx.net

i think it could be

- that the isp (if you're connecting to one isp trough ppp0) has a filter for
port 80 (it seems strange)

are you mangling some packets? what is the output for iptables -t mangle -L?



----- Original Message ----- 
From: "Patrick Leslie Polzer" <leslie.polzer@gmx.net>
To: <netfilter@lists.netfilter.org>
Sent: Saturday, May 29, 2004 12:25 PM
Subject: DNAT problem


>
> Hello again,
>
> a DNAT problem is coming up.
> My firewall setup (simplified for testing) is currently as follows:
>
>
> ### <snip> ###
>
> ##### FILTER table #####
> # policies
> $ipt -P FORWARD ACCEPT
> $ipt -P   INPUT ACCEPT
> $ipt -P  OUTPUT ACCEPT
>
> $ipt -F
> $ipt -F FORWARD
> $ipt -F   INPUT
> $ipt -F  OUTPUT
>
>
> ##### NAT table #####
> # flush chains
> $ipt -t nat -F  PREROUTING
> $ipt -t nat -F POSTROUTING
> $ipt -t nat -F      OUTPUT
>
> # masquerading on ppp0 and vortex
> $ipt -t nat -A POSTROUTING -o   ppp0 -j MASQUERADE
> $ipt -t nat -A POSTROUTING -o vortex -j MASQUERADE
>
> # dnat
> $ipt -t nat -A PREROUTING -i ppp0 -p tcp --dport 80 -j DNAT --to-destination
192.168.35.191:80
>
> ### </snip> ###
>
>
> The last line is working with
>
> --dport 8080
>
> but isn't with
>
> --dport 80
>
> What's going on there?
>
>
> Kind regards,
>
> Leslie
>
>



  reply	other threads:[~2004-05-29 15:36 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-29 15:25 DNAT problem Patrick Leslie Polzer
2004-05-29 15:36 ` Alexis [this message]
2004-05-29 16:03   ` Patrick Leslie Polzer
2004-05-30  1:00     ` Alexis
2004-05-30  7:56       ` OT: ISP Port filters (was: Re: DNAT problem) Patrick Leslie Polzer
     [not found] <45227670.8040702@mail.nankai.edu.cn>
2006-10-03 14:48 ` DNAT problem Marco Berizzi
     [not found] <4521C6A3.1040902@mail.nankai.edu.cn>
2006-10-03 10:11 ` Marco Berizzi
  -- strict thread matches above, loose matches on Subject: below --
2006-10-02  8:00 Stefan Friedel
2006-10-02  8:25 ` Marco Berizzi
2006-10-02 10:42   ` Pascal Hambourg
2006-10-02 12:01     ` Stefan Friedel
2006-10-02 12:51       ` Marco Berizzi
2006-10-02 13:14       ` Pascal Hambourg
2006-10-02 14:18         ` Stefan Friedel
2006-10-02 12:48     ` Marco Berizzi
2006-07-08 21:00 Antonio Di Bacco
2005-01-22 15:59 dnat problem Pablo Allietti
2005-01-22 19:45 ` Jason Opperisano
2005-01-23  0:26   ` Pablo Allietti
     [not found]     ` <20050125150114.GA25839@omega.lacnic.net.uy>
2005-01-25 15:24       ` Pablo Allietti
2005-01-25 15:25         ` Pablo Allietti
2004-06-10 11:03 DNAT problem Paul M. Goorskis
2004-04-27  5:57 [Fwd: Re: DNAT Problem] test
2004-04-27  7:20 ` DNAT Problem Rob Sterenborg
     [not found]   ` <1081.80.0.0.23.1083127867.squirrel@80.0.0.175>
     [not found]     ` <000901c42cef$68603d40$1202a8c0@admin>
2004-05-04  5:32       ` test
2004-04-19  5:07 test
2004-04-19 13:43 ` Joel Newkirk
2004-04-20  4:31   ` test
2004-04-22 10:40     ` test
2004-04-22 11:07       ` Antony Stone
     [not found]         ` <1589.80.0.0.23.1082637754.squirrel@80.0.0.175>
2004-04-22 12:47           ` Antony Stone
2004-04-22 13:06             ` test
2004-04-22 13:21               ` Antony Stone
2004-04-22 18:18                 ` test
2004-04-22 19:13                   ` Antony Stone
2004-04-23 12:22                     ` test
2003-03-30 14:58 DNAT problem Alexandru Coseru
2003-03-30 15:41 ` Joel Newkirk
2002-11-27 19:28 Geoff Silver
2002-11-19  8:07 HCLFM
2002-11-21 21:53 ` Rahul Jadhav
2002-05-21 20:53 dnat problem support
2002-06-13 17:28 ` Antony Stone

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='000701c44592$bb254460$0200000a@heretic' \
    --to=alexis@tpys.com.ar \
    --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