From: Lawrence MacIntyre <lpz@ornl.gov>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] routing query
Date: Thu, 04 Sep 2003 17:33:29 +0000 [thread overview]
Message-ID: <marc-lartc-106269689206185@msgid-missing> (raw)
In-Reply-To: <marc-lartc-106264270917225@msgid-missing>
[-- Attachment #1: Type: text/plain, Size: 2227 bytes --]
Payal:
What subnet are your users' machines on? Is there a third ethernet
address on the linux machine where the user machines connect or are they
connected to one of the two given ethernet interfaces (eth0 or eth1)?
On Thu, 2003-09-04 at 22:33, Payal Rathod wrote:
> Hi,
> I have a simple question. I asked a friend about it but he was also not
> clear. So, I thought of mailing the list.
>
> I have a linux box (RH 7.2) which will have 2 net cards. I have 2 types
> of connections to that box. One RF at eth0 and 1 ISDN at eth1.
> Now I told 10 people from the company to give eth1 as their default
> gateway and the rest as eth0. Ok, so far? Now my understanding that with
> the routing table below, all traffic coming to eth0 will be routed thru'
> RF router and all traffic coming to eth1 will be routed through ISDN
> router. Am I right? S, if ISDN fails only 10 people will suffer but the
> rest can continue using RF line. Same case with RF line, if it fails the
> 10 people can use ISDN without any glitch. This is no load balancing
> network. Just a simple routing decision.
>
> I have,
> route add default gw <ISDN router ip> dev eth1
> route add default gw <RF router ip> dev eth0
>
>
> Destination Gateway Genmask Flags Metric Ref Use Iface
> 127.0.0.0 * 255.0.0.0 U 0 0 0 lo
> 125.0.0.0 * 255.0.0.0 U 0 0 0 eth1
> 125.0.0.0 * 255.0.0.0 U 0 0 0 eth1
> default 203.124.123.111 0.0.0.0 UG 0 0 0 eth0
> default 125.125.125.3 0.0.0.0 UG 0 0 0 eth1
> default * 0.0.0.0 U 0 0 0 eth0
>
> Can anyone comment whether I am right in my analysis?
>
> My friend's comments are given below,
>
> | I still say that should be necessary. I believe you need to echo 0
> | at some files found by /proc/sys/net/ipv4/conf/*/send_redirects.
> | Otherwise devices won't route through your box, they'll be
> | redirected straight to one of the routers (at random, as far as I
> | know).
>
> With warm regards,
> -Payal
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-09-04 17:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-04 2:31 [LARTC] routing query Payal Rathod
2003-09-04 6:58 ` Manish Singh
2003-09-04 7:42 ` Manish Singh
2003-09-04 17:33 ` Lawrence MacIntyre [this message]
2003-09-04 18:47 ` Payal Rathod
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-106269689206185@msgid-missing \
--to=lpz@ornl.gov \
--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.