All of lore.kernel.org
 help / color / mirror / Atom feed
From: "umar" <vramnarayan@triniti.com>
To: netfilter@lists.samba.org
Subject: nat problem.
Date: Mon, 17 Jun 2002 16:28:57 +0530	[thread overview]
Message-ID: <01f701c215ed$fca7c100$9300a8c0@edapter.com> (raw)
In-Reply-To: 030001c215b7$dc4d7f20$870110ac@samsi

Hi, 
 
Trying out  a very simple configuration of a firewall here, but having some problems.
The firewall  has two NIC's and have enabled ip forwarding. 

I want the internal machines to connect to the internet,  So have enabled NAT : 
Runing squid - transparent proxy on port 3232. Clients have been onfigured to connect to internet directly. 
eth0 is my external interface.
 
Following are the nat rules conigured on the firewall
 
iptables -t nat -A PREROUTING -i eth0  -p tcp --dport 80 -j REDIRECT --to-port 3232
 
iptables -t nat -A POSTROUTING -o eth0 -j SNAT --to-source x.x.x.x ( public IP of the other netwrok card )

I can ping to the gateway ( private IP ) and the other network card havng the public IP , but nothing beyond that, Why ?? 
And my clients are also not able to connect to the internet ?? 
I have tried removing the first rule and disabling squid, so that clients could connect to the intenet directly. 
That also failed, and the result is the same. All the default poilicies of all rules are set to ACCEPT.

Runing rh 7.2 with 2.4.7-10 kernel.

Please help. 

Warm Regards, 
Kumar. 

  reply	other threads:[~2002-06-17 10:58 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-15 22:14 Completely NAT an ISP: A practical possibility? Brian Capouch
2002-06-15 22:33 ` Antony Stone
2002-06-15 22:54   ` Brian Capouch
2002-06-15 23:17   ` Nick Drage
2002-06-15 23:30     ` Antony Stone
2002-06-17  4:25     ` Sathi
2002-06-17 10:58       ` umar [this message]
2002-06-17 15:46         ` (no subject) skmail
2002-06-17 18:11         ` nat problem Antony Stone
2002-06-18 17:16     ` Completely NAT an ISP: A practical possibility? Rodrigo Senra
2002-06-18 18:50       ` Ramin Alidousti
2002-06-18 20:22         ` Rodrigo Senra
2002-06-18 22:50           ` Ramin Alidousti
2002-06-19 14:36             ` Rodrigo Senra
2002-06-19 15:20               ` Ramin Alidousti
2002-06-20  9:48             ` Antony Stone
2002-06-20 19:37               ` Rodrigo Senra
2002-06-21  0:19                 ` Ramin Alidousti
2002-06-24 18:42                   ` Rodrigo Senra
  -- strict thread matches above, loose matches on Subject: below --
2004-07-13 20:40 nat problem Frans Luteijn
2004-07-13 21:06 ` Antony Stone
2004-07-13 22:21   ` Frans Luteijn
2004-07-13 22:53     ` Antony Stone
2004-07-13 23:11       ` Nick Taylor
2004-07-14  1:02       ` Frans Luteijn
2004-07-14  8:53         ` Antony Stone
2004-07-14 23:30           ` Frans Luteijn
2004-07-15  8:21             ` Antony Stone
2004-07-19  1:26               ` Frans Luteijn
2004-07-05 16:33 Frans Luteijn
2004-07-07 13:07 ` Antony Stone
2003-10-06 12:30 NAT problem Jose Pascual
2003-10-06 13:19 ` Venkatesh. K
2003-10-06 13:33   ` Cedric Blancher
2003-10-06 20:38 ` Joel Newkirk
2002-11-22 22:52 nat problem Yogini Parkhi
2002-11-15 20:45 Rahul Jadhav
2002-10-21 13:04 NAT problem saravanan sakthi
2002-10-21 15:15 ` Antony Stone
2002-10-20 23:20 NAT Problem Morgan
2002-06-24 11:11 Nat PROBLEM lcef
2002-06-24 13:34 ` Antony Stone
2002-05-09  4:41 NAT problem Tyler Kemp
2002-06-13 16:03 ` 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='01f701c215ed$fca7c100$9300a8c0@edapter.com' \
    --to=vramnarayan@triniti.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 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.