All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ryan Johnson" <rjohnson@espgroup.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Linux router configuration??
Date: Fri, 26 Sep 2003 03:46:49 +0000	[thread overview]
Message-ID: <marc-lartc-106454783224552@msgid-missing> (raw)
In-Reply-To: <marc-lartc-106452893510255@msgid-missing>

I am going to assume you want the most basic router, just two interfaces.

1.) Make sure both network cards have been detected.
ifconfig eth0
ifconfig eth1
2.) Set up each interface on its own network, make sure the interface has been activated, you can use ifconfig for this.
3.) issue the command
echo 1 > /proc/sys/net/ipv4/ip_forward
to enable ip fowarding, w/o this the kernel will not send packets between interfaces
4.) set the clients behind the router to point to the internal ip of your router

Any changes made to the system will have to be initialized during the boot process.

Of course if you have ip addresses that you would like to nat/masq behind the router, you will have to use iptables.

You really should be more specific on your needs.

Good luck.


> Good morning at all, thanks for previous help, but I have another ask. I have a few experience of Linux world's, and I need to configure a Linux PC as router, what are the steps? What do I do?
> Thanks.

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

  parent reply	other threads:[~2003-09-26  3:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-25 22:25 [LARTC] Linux router configuration?? Blu
2003-09-25 23:12 ` Damion de Soto
2003-09-25 23:39 ` Derek
2003-09-26  0:04 ` Daniel Chemko
2003-09-26  3:46 ` Ryan Johnson [this message]
2003-09-26  6:29 ` Ronny Aasen
2003-09-26  7:44 ` Raghuveer
2003-09-29  1:36 ` Steve Wright
2003-10-01  8:54 ` Raghuveer

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-106454783224552@msgid-missing \
    --to=rjohnson@espgroup.net \
    --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.