Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Antony Stone <Antony@Soft-Solutions.co.uk>
To: netfilter@lists.netfilter.org
Subject: Re: Forwarding packets to another private gateway.
Date: Thu, 24 Jun 2004 15:51:22 +0100	[thread overview]
Message-ID: <200406241551.22322.Antony@Soft-Solutions.co.uk> (raw)
In-Reply-To: <s0daa508.020@mail.toolsnottoys.com>

On Thursday 24 June 2004 3:08 pm, Reginald NALLARATNAM wrote:

> Hello,
>
> I have Linux box @ 192.168.3.1 with acts as a firewall, there is another
> firewall @ 192.168.1.1 which acts as a vpn to another network 192.168.2.0
>
> I have a citrix server on 192.168.3.11 with a default gateway of
> 192.168.3.1. I need to access other machines in the 192.168.2.0 subnet
> remotely from this citirx server. My question is what rule must I add in
> the 192.168.3.1 Linux firewall to forward any trafic going to 192.168.2.0
> network to 192.168.1.1.

route add -net 192.168.2.0 netmask 255.255.255.0 gw 192.168.1.1

Regards,

Antony.

-- 
"When you talk about Linux versus Windows, you're talking about which 
operating system is the best value for money and fit for purpose. That's a 
very basic decision customers can make if they have the information available 
to them. Quite frankly if we lose to Linux because our customers say it's 
better value for money, tough luck for us."

 - Steve Vamos, MD of Microsoft Australia

                                                     Please reply to the list;
                                                           please don't CC me.



      reply	other threads:[~2004-06-24 14:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-24 14:08 Forwarding packets to another private gateway Reginald NALLARATNAM
2004-06-24 14:51 ` Antony Stone [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=200406241551.22322.Antony@Soft-Solutions.co.uk \
    --to=antony@soft-solutions.co.uk \
    --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