From: "Brad Morgan" <B-Morgan@concentric.net>
To: pnelson@neatech.com, 'Netfilter List' <netfilter@lists.samba.org>
Subject: RE: Local rule for Port Forward
Date: Sat, 26 Apr 2003 09:44:36 -0600 [thread overview]
Message-ID: <002201c30c0a$c106cb00$0400a8c0@bradmorgan> (raw)
In-Reply-To: <1051344354.14942.2.camel@il.npn>
> I'm doing port forwarding to a server that runs jabber and everything
> works fine, I did notice that if I bring up a jabber client on the
> firewall itself I do not get connected. While this isn't really
> needed... I don't totally understand why it doesn't work. Being
> inquisitive... well I just gots to know why! Can anyone shed some
> light?
>
> My rules for the jabber port forward are:
>
> iptables -A FORWARD
> -i $ExIF -d $JabIP -p tcp --dport $JabPort
> -j ACCEPT
> iptables -A PREROUTING
> -t nat -d $ExIP -p tcp --dport $JabPort
> -j DNAT --to-destination $JabIP
> iptables -A POSTROUTING
> -t nat -d $JabIP -p tcp --dport $JabPort
> -j SNAT --to-source $InIP
The reason why jabber doesn't work on the firewall is because the PREROUTING
rule sends the packet to jabber server as requested. It never reaches the
INPUT chain or the client running on the firewall.
An excellent reference for how packets traverse the iptables chains can be
found at http://iptables-tutorial.frozentux.net by Oskar Andreasson. He
just posted a new version.
Regards,
Brad Morgan
next prev parent reply other threads:[~2003-04-26 15:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-25 16:45 Local rule for Port Forward Patrick Nelson
2003-04-25 21:12 ` David Gaudine
2003-04-26 8:05 ` Patrick Nelson
2003-04-26 15:44 ` Brad Morgan [this message]
2003-04-26 17:35 ` Andy Wood
2003-04-30 21:04 ` Patrick Nelson
2003-04-30 17:58 ` Problems removing rules Maurício S. Mudrik
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='002201c30c0a$c106cb00$0400a8c0@bradmorgan' \
--to=b-morgan@concentric.net \
--cc=netfilter@lists.samba.org \
--cc=pnelson@neatech.com \
/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.