Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Jason Opperisano <opie@817west.com>
To: netfilter@lists.netfilter.org
Subject: Re: FTP Forwarding
Date: Tue, 18 Jan 2005 11:40:39 -0500	[thread overview]
Message-ID: <1106066439.3725.2.camel@hubcap.ljm.dom> (raw)
In-Reply-To: <000701c4fc66$9a3d7840$0200a8c0@etpi>

On Mon, 2005-01-17 at 02:31, TestMail wrote:
> I'm sorry but i think this rule will not be the solution to my problem cause
> my ftp server is inside my internal network and automatically my gateway
> will "only" be the source from the -s $PublicIPAdd Forward rule parameter...
> i think???

either you or i misunderstands what $PublicIPAdd stands for.

> Below is my schematic on how i want it to be ..
>     1. only 202...1 ip address in my branch office should be allowed to use
> my ftp server in my head office
> 
>         so incoming ftp request should be filtered and only 202....1 ip
> address that is coming from my branch office should be allowed.
> 
> | Branch | eth0 202. .1       < external
>        |
>        |
> | WAN  |
>        |
>        |
> |gateway:firewall:FCore2|  eth0 192.168...  < internal <<<<<<
>        |                                 eth1 202........    <external
>        |
>        |
> |Ftp Server:FCore2| eth0 192.168.0.5 < Internal

now that you've provided some more details:

iptables -A FORWARD -i eth1 -o eth0 -p tcp --syn \
  -s 202.x.x.1 -d 192.168.0.5 --dport 21 -j ACCEPT

-j

--
"To alcohol: the cause of, and solution to, all of life's problems."
	--The Simpsons



  reply	other threads:[~2005-01-18 16:40 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-28 17:19 FTP Forwarding umar draz
2004-12-28 17:30 ` Jason Opperisano
2005-01-14  8:57   ` Test Mail
2005-01-14 11:38     ` Deepak Seshadri
2005-01-14 14:27       ` Jason Opperisano
2005-01-14 14:43         ` Deepak Seshadri
2005-01-14 14:23     ` Jason Opperisano
2005-01-17  7:31       ` TestMail
2005-01-18 16:40         ` Jason Opperisano [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-01-18 15:49 Hudson Delbert J Contr 61 CS/SCBN
     [not found] <FD8F124A387AD6119F7900A0D218B321541403@hslex01.hslbz.local>
2002-11-22 12:02 ` Rob Sterenborg
2002-11-22 13:02   ` Roy Sigurd Karlsbakk
2002-11-22 10:08 Bantam
2002-11-22 10:24 ` Alexey Sheshka
2002-11-22 10:26 ` Alexey Sheshka
2002-11-22 10:31 ` Stewart Thompson
2002-11-22 10:37   ` Wasim Bashir
2002-11-22 11:08     ` Stewart Thompson
2002-11-22 11:47       ` Wasim Bashir
2002-11-22 10:34 ` Rob Sterenborg
2002-11-22 11:53 ` Erdal Mutlu
2002-11-18  9:47 ftp forwarding Wasim Bashir

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=1106066439.3725.2.camel@hubcap.ljm.dom \
    --to=opie@817west.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox