Linux Netfilter discussions
 help / color / mirror / Atom feed
From: <support@supsrv.com>
To: netfilter@lists.samba.org
Subject: dnat problem
Date: Tue, 21 May 2002 16:53:51 -0400	[thread overview]
Message-ID: <003e01c20109$9d514e40$6f01a8c0@ollie> (raw)

hello all,
this is my first time posting to this board.  i am having trouble
with my iptables rules.  my configuration consists of a linux
router as the main network gateway and firewall providing NAT and
ipsec.  i have compiled kernel 2.4.17 with freeS/WAN version
1.91.   i have a source nat rule set up so my non-routable
addresses can use the gateway to reach the internet.  i did not use
the MASQUERADE target.

here is my Source nat rule

iptables -t nat -A POSTROUTING -s 192.168.1.0/24 -o eth1 -j SNAT --to
w.x.y.z

I also have some destination nat rules set up.
iptables -t nat -A PREROUTING -d w.x.y.a -p tcp -m tcp --dport 80 -j
DNAT --to-destination 192.168.1.48

There are about 5 additional dnat rules that are basically the same
so I won't list them.

the problem i am having is that the internal private subnet
(192.168.1.0/24) on my network is unable to bring up sites that
have been setup using dnat rules.  external users have no problem
viewing the sites i have set up dnat rules for.

any help would be greatly appreciated.

thanks

---
Ollie Gallardo



             reply	other threads:[~2002-05-21 20:53 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-21 20:53 support [this message]
2002-06-13 17:28 ` dnat problem Antony Stone
  -- strict thread matches above, loose matches on Subject: below --
2002-11-19  8:07 DNAT problem HCLFM
2002-11-21 21:53 ` Rahul Jadhav
2002-11-27 19:28 Geoff Silver
2003-03-30 14:58 Alexandru Coseru
2003-03-30 15:41 ` Joel Newkirk
2004-04-19  5:07 DNAT Problem 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
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-05-29 15:25 DNAT problem Patrick Leslie Polzer
2004-05-29 15:36 ` Alexis
2004-05-29 16:03   ` Patrick Leslie Polzer
2004-05-30  1:00     ` Alexis
2004-06-10 11:03 Paul M. Goorskis
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
2006-07-08 21:00 DNAT problem Antonio Di Bacco
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
     [not found] <4521C6A3.1040902@mail.nankai.edu.cn>
2006-10-03 10:11 ` Marco Berizzi
     [not found] <45227670.8040702@mail.nankai.edu.cn>
2006-10-03 14:48 ` Marco Berizzi

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='003e01c20109$9d514e40$6f01a8c0@ollie' \
    --to=support@supsrv.com \
    --cc=netfilter@lists.samba.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