From: Ian Zapczynski <ianz@quarterleaf.com>
To: linux-admin@vger.kernel.org
Subject: Re: unable to route traffic between two networks on Red Hat 6.2
Date: Tue, 09 Apr 2002 10:19:42 -0400 [thread overview]
Message-ID: <3CB2F87E.B709A817@quarterleaf.com> (raw)
In-Reply-To: 3CB2F3D4.4080306@imagelinks.com
[-- Attachment #1: Type: text/plain, Size: 2060 bytes --]
Thanks very much for the suggestion. This was indeed something I missed and
will make a note of.
I set /etc/sysctl.conf, rebooted, and confirmed that
/proc/sys/net/ipv4/ip_forward contained "1", but I still can't do a ping -I
192.168.1.1 10.1.1.1 nor a traceroute -i eth1 10.1.1.1.
I hope it's just one other minor piece I'm missing.
Thanks,
-Ian
Jeff Largent wrote:
> echo 1 > /proc/sys/net/ipv4/ip_forward
>
> and to make it take effect everytime the sys boots edit
> /etc/sysctl.conf change
> net.ipv4.ip_forward = 0
> to
> net.ipv4.ip_forward = 1
>
> 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
> >
> > Can anyone please point out what I am missing or otherwise doing wrong?
> > Even if the answer is "buy a book", a suggestion on which one might help
> > me is welcome also.
> >
> > Again, I don't need to be concerned about NAT, firewalls or security at
> > this point, which is why I haven't touched ipchains for this purpose. I
> > assume I don't need it only to route traffic between two networks, no?
> >
> > Thanks much in advance!
> >
> > -Ian
[-- 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-09 14:19 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 [this message]
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
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=3CB2F87E.B709A817@quarterleaf.com \
--to=ianz@quarterleaf.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).