All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Ellis <eellis@mail.co.gilchrist.fl.us>
To: netfilter@lists.netfilter.org
Subject: IPtables FORWARD syntax question/error
Date: Fri, 09 Jul 2004 12:12:38 -0400	[thread overview]
Message-ID: <40EEC3F6.7050306@mail.co.gilchrist.fl.us> (raw)

I've just started messing with iptables so I can start walling off 
certain parts of my network from the rest of it.  Right now, I have a 
test bed set up with a slackware 10 install, packet forwarding on, and 
masquerading working, so I'm moving data fine, since the box that I use 
for daily work is behind this beta box.

I have installed Squid on the box so I can log all web requests done by 
my users on the back side of the firewall.  This too works, as I can 
tail -f the log and watch myself browse.

The problem is coming from the following item that I want to implement:
I have a webcache/external proxy on the network that I want to route all 
web traffic from Squid to.  I assumed the following to work:

iptables -t nat -A OUTPUT -p tcp --dport 80 -j DNAT --to-destination 
xx.xx.xx.xx:8080

the thing is that it gives me the error "invalid argument".  Here's what 
else I've tried, with errors:

root@firewall:/etc# iptables -t nat -A POSTROUTING -p tcp --dport 80 -j 
DNAT --to-destination xx.xx.xx.xx:8080
iptables: Invalid argument 

root@firewall:/etc# iptables -t nat -A OUTPUT -p tcp --dport 80 -j DNAT 
--to-destination xx.xx.xx.xx:8080
iptables: Invalid argument 

root@firewall:/etc# iptables -A OUTPUT -p tcp --dport 80 -j DNAT 
--to-destination xx.xx.xx.xx:8080
iptables: Invalid argument 

root@firewall:/etc# iptables -A OUTPUT -p tcp --dport 80 -j DNAT 
--to-destination xx.xx.xx.xx
iptables: Invalid argument 


All the above assumes that I should be treating Squid as a source on the 
box, which is why I'm using the OUTPUT chain.  If I'm wrong here, let me 
know.

The troubling thing that I'm having here is that I don't know what about 
the rule that I'm requesting to set up is borked, and I can't really 
find any material on it in the past few days that I've been looking.  It 
*appears* to be a valid rule, according to what I've read at 
http://iptables-tutorial.frozentux.net/ and other various 
documentation/HOW-TOs/newb help references.  I think I'm missing 
something *really* obvious, but I don't have the depth to find it.


/me sighs.  Thanks for your help in advance.


             reply	other threads:[~2004-07-09 16:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-09 16:12 Eric Ellis [this message]
2004-07-10  8:40 ` IPtables FORWARD syntax question/error Antony Stone
2004-07-11  2:21   ` Alistair Tonner

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=40EEC3F6.7050306@mail.co.gilchrist.fl.us \
    --to=eellis@mail.co.gilchrist.fl.us \
    --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 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.