From: Jeff Largent <jlargent@imagelinks.com>
To: Sasa Ugrenovic <borg@linuks.org>
Cc: linux-admin@vger.kernel.org
Subject: Re: Port forwarding how ??
Date: Wed, 15 Jan 2003 12:16:57 -0500 [thread overview]
Message-ID: <3E259789.5070802@imagelinks.com> (raw)
In-Reply-To: <1042586197.28248.11.camel@marvin.bl.gozostudios.com>
One of the best tools for debuging is tcpdump. Run one copy on the
machine your trying to connect from, two on the machine with iptables
and a final copy on the machine you forwarding to.
on machine trying to connect from.
tcpdump src port 3306
on machine with iptables
tcpdump src host <ip of above machine> dest port 3306
and
tcpdump src host <ip of this machine> dest host 192.168.0.14 dest port 3306
on 192.168.0.14
tcpdump scr host <ip of above machine> dest port 3306
on the machine with iptables you should see the connect from the machine
you are trying to connect from, and see it go out to 192.168.0.14
on the machine connecting from make sure any response you get back is
from the ip of the machine running iptables and not the 192.168.0.14 ip.
Jeff
Sasa Ugrenovic wrote:
> Anyone configured port forwarding that worked ?
>
> I was reading lot's of howto documents, but i was unable to configure
> that thing.
>
>
> iptables -t nat -A PREROUTING -i $OUTSIDE -p tcp --dport 3306 -j DNAT
> --to 192.168.0.14
>
> This is how i configured it .. but it doesn't work .. anyone have any
> idea or something .. ?
>
> Thanks.
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-admin" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
--
Jeff Largent ImageLinks, Inc.
Sr System Admin Melbourne, Fl 32935
(321) 253-0011 fax:(321) 253-5559
prev parent reply other threads:[~2003-01-15 17:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-14 23:16 Port forwarding how ?? Sasa Ugrenovic
2003-01-14 23:44 ` Scott Taylor
[not found] ` <1042589738.28248.16.camel@marvin.bl.gozostudios.com>
2003-01-15 15:01 ` Scott Taylor
2003-01-15 17:10 ` Jeff Largent
2003-01-15 15:04 ` Scott Taylor
2003-01-15 17:06 ` Sasa Ugrenovic
2003-01-15 17:41 ` Jeff Largent
2003-01-15 18:24 ` Sasa Ugrenovic
2003-01-15 20:09 ` urgrue
2003-01-15 20:37 ` Sasa Ugrenovic
2003-01-15 20:58 ` urgrue
2003-01-15 21:15 ` Sasa Ugrenovic
2003-01-15 21:07 ` Scott Taylor
2003-01-15 17:16 ` Jeff Largent [this message]
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=3E259789.5070802@imagelinks.com \
--to=jlargent@imagelinks.com \
--cc=borg@linuks.org \
--cc=linux-admin@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).