All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Benny Butler" <benny.butler@nexusitg.com>
To: netfilter@lists.samba.org
Subject: Multiple source question
Date: Wed, 19 Jun 2002 08:31:57 -0500	[thread overview]
Message-ID: <000101c21795$aff6d3b0$0205a8c0@maxima> (raw)

Ok, after much hacking together the rule below I finally get the machine
at 192.168.2.70 to access 10.46.210.5.  Great, but if I run the same
rule on any more internal IP addresses, still only 2.70 works.  I'm
pretty sure after reading the docs that my problem is because my rule is
being matched and it's not allowing anything after the first.  I got
desperate and tried -A PREROUTING and -A FORWARD and -j ACCEPT, none of
which helped (usually made it worse.)

I also tried multiple source addresses in one rule, but either that's
not acceptable or it's not , or ; delimited.

And you may ask why sudo, it's cause this whole thing runs out of a php
script as the apache user.

Does anyone have any tips for this?

Thanks


sudo /sbin/iptables -t nat -A POSTROUTING -o eth0 -s 192.168.2.70 -d /
10.46.210.5 -p tcp --dport 80 -j MASQUERADE



[root@localhost html]# iptables -t nat -L
Chain PREROUTING (policy ACCEPT)
target     prot opt source               destination

Chain POSTROUTING (policy ACCEPT)
target     prot opt source               destination
MASQUERADE  tcp  --  192.168.2.70         10.46.210.5        tcp
dpt:http

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination
[root@localhost html]#




 
_______________________
Benny Butler
334-340-8345
http://www.nexusitg.com



             reply	other threads:[~2002-06-19 13:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-19 13:31 Benny Butler [this message]
2002-06-19 13:41 ` Multiple source question Antony Stone
2002-06-19 14:01   ` Benny Butler
2002-06-19 14:14     ` 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='000101c21795$aff6d3b0$0205a8c0@maxima' \
    --to=benny.butler@nexusitg.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.