All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ashok N N <nalkunda@cse.msu.edu>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Router
Date: Fri, 22 Nov 2002 16:34:24 +0000	[thread overview]
Message-ID: <marc-lartc-103798320615217@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103797801108811@msgid-missing>

On Friday 22 November 2002 10:33 am, Stef Coene wrote:
> On Friday 22 November 2002 16:08, Rimas wrote:
> > Hi guys,
> >
> > I'm asking the same question again (it's very urgent for me).
> >
> > How to build a router on Linux box?
> >
> > I have a Linux box (Redhat 7.3) with two network cards.
> > eth0 is connection to my wireless ISP and eth1 to my FWs.
> > I want to route eth0<-->eht1. Both NIC have real Internet IP as well like
> > FWs.
> > I need no NAT (no needs to hide my real IP, because it have to be seen 
from
> > Internet).
> > Do I have to use ip route or iptables or combination of it.
> If the box is up and running with 2 nic's configured, try this :
> 
> echo 1 > /proc/sys/net/ipv4/ip_forward
> 
> Stef
> 

Just to enable routing (without any firewall stuff) the above command would be 
sufficient. To make it permanent, add the following to /etc/sysctl.conf:
# Enables packet forwarding
net.ipv4.ip_forward=1

You could also add the following to enable route verification:
# Enables source route verification
net.ipv4.conf.default.rp_filter = 1

Thanks,
Ashok
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

      parent reply	other threads:[~2002-11-22 16:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-22 15:08 [LARTC] Router Rimas
2002-11-22 15:19 ` David Boreham
2002-11-22 15:33 ` Stef Coene
2002-11-22 16:34 ` Ashok N N [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=marc-lartc-103798320615217@msgid-missing \
    --to=nalkunda@cse.msu.edu \
    --cc=lartc@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 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.