From: Ian Zapczynski <ianz@quarterleaf.com>
To: helmut djurkin <helmut.djurkin@chello.at>
Cc: linux-admin@vger.kernel.org
Subject: Re: unable to route traffic between two networks on Red Hat 6.2
Date: Wed, 10 Apr 2002 08:48:05 -0400 [thread overview]
Message-ID: <3CB43485.2CAADA76@quarterleaf.com> (raw)
In-Reply-To: 1018389664.1692.355.camel@igor3
[-- Attachment #1: Type: text/plain, Size: 2533 bytes --]
Thanks again, all, for your thoughts and suggestions.
You're right - the static routes were overkill. I have since removed them,
but for some reason I am still unable to route between the two networks.
Indeed I have set my router as the default gateway for my client machines
using the 192.168.1.1 address that they can contact it on. When a client
machine tries to ping a 10.1.1.0 address, I can see via Ethereal that the
request goes to my router. I just still stumped as to why it won't forward
the traffic on to the proper host!
Being somewhat green on Linux administration, I even went to the bookstore
last night to check out a Red Hat admin book. It seems to tell me pretty
much what you kind folks have already told me.
Hmmm... when I figure this out, I know it's going to be something I'll want
to slap myself over. ;-)
-Ian
helmut djurkin wrote:
> On Tue, 2002-04-09 at 15:44, Ian Zapczynski wrote:
> > Hello all.
> >
> > I am a Sun administrator needing to get a router set up on Red Hat 6.2.
> > I am simply trying to join two private networks, 192.168.0.0 and
> > 10.1.1.0. The router I have configured has eth0 at 10.1.1.100 and eth1
> > at 192.168.1.1. I do not need to be able to route traffic to the
> > internet using NAT -- I only need a DHCP server on my 192.168.0.0
> > network to give out IP addresses on that network (this works fine) that
> > will allow users to access the 10.1.1.0 network.
> >
> > On my router, currently I can ping an address on the 10.1.1.0 network,
> > but not when I use something like ping -I 192.168.1.1 10.1.1.1 to do
> > so. This should work, right?
> >
> > /etc/sysconfig/network looks like:
> >
> > NETWORKING=yes
> > HOSTNAME=myhost.mydomain
> > GATEWAYDEV=eth0
> > GATEWAY=10.1.1.1
> > FORWARD_IPV4=YES
> >
> > /etc/sysconfig/static-routes has:
> >
> > eth1 net 192.168.0.0 netmask 255.255.0.0 gw 192.168.1.1
> > eth0 net 10.1.1.0 netmask 255.255.255.0 gw 10.1.1.100
>
> no need to set static-routes. your interface config do these settings in
> /etc/sysconf/network-scripts/ifup-routes automatic.
>
> with your settings in static-routes you have double entries in the
> output from /sbin/route.
>
> the correct entrys from /sbin/route -n would be somethink like this:
> 10.1.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
> 192.168.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth1
> 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
> 0.0.0.0 10.1.1.1 0.0.0.0 UG 0 0 0 eth0
>
> bye,
> helmut
>
[-- Attachment #2: Card for Ian Zapczynski --]
[-- Type: text/x-vcard, Size: 269 bytes --]
begin:vcard
n:Zapczynski;Ian
tel;work:215-283-4877 x120
x-mozilla-html:FALSE
url:http://www.quarterleaf.com/
org:The Sycamore Group
adr:;;;;;;
version:2.1
email;internet:ianz@quarterleaf.com
title:Sun Certified System/Network Administrator
fn:Ian Zapczynski
end:vcard
next prev parent reply other threads:[~2002-04-10 12:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-09 13:44 unable to route traffic between two networks on Red Hat 6.2 Ian Zapczynski
[not found] ` <3CB2F3D4.4080306@imagelinks.com>
2002-04-09 14:19 ` Ian Zapczynski
2002-04-09 17:04 ` Camelia NASTASE
2002-04-09 17:27 ` Ian Zapczynski
[not found] ` <a05100300b8d8dc4908ba@[192.168.13.3]>
2002-04-09 18:11 ` Ian Zapczynski
2002-04-09 21:58 ` Glynn Clements
2002-04-09 22:01 ` helmut djurkin
2002-04-10 12:48 ` Ian Zapczynski [this message]
2002-04-10 12:55 ` Glynn Clements
2002-04-10 13:01 ` Ian Zapczynski
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=3CB43485.2CAADA76@quarterleaf.com \
--to=ianz@quarterleaf.com \
--cc=helmut.djurkin@chello.at \
--cc=linux-admin@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.