From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ian Zapczynski Subject: Re: unable to route traffic between two networks on Red Hat 6.2 Date: Tue, 09 Apr 2002 13:27:01 -0400 Sender: linux-admin-owner@vger.kernel.org Message-ID: <3CB32465.E4624D57@quarterleaf.com> References: <20020409195855.B53955-100000@bofh.dnt.ro> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="------------F337629BD3A527A56AD57FAF" List-Id: To: linux-admin@vger.kernel.org This is a multi-part message in MIME format. --------------F337629BD3A527A56AD57FAF Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Yes, if I do not indicate the source interface, I can traceroute to 10.1.1.1 (or any other machine on the 10.1.1.0 network) from the router successfully. I can also ping/traceroute to the 192.168.0.0 machines from the router. I will add that I can also traceroute/ping the router's 10.1.1.100 interface from the other machines on the 192.168.0.0 network, but using Ethereal on my router, I see that ping requests from 192.168.0.0 clients to other 10.1.1.0 addresses come to the router but go no further. I have pasted the output you requested below. I am very grateful for your time and assistance. -Ian /sbin/route -n: Destination Gateway Genmask Flags Metric Ref Use Iface 10.1.1.0 10.1.1.100 255.255.255.0 UG 0 0 0 eth0 10.1.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 192.168.0.0 192.168.1.1 255.255.0.0 UG 0 0 0 eth1 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 eth0 Link encap:Ethernet HWaddr 00:50:DA:10:E6:E7 inet addr:10.1.1.100 Bcast:10.1.1.255 Mask:255.255.255.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:68380 errors:0 dropped:0 overruns:0 frame:0 TX packets:21254 errors:0 dropped:0 overruns:0 carrier:5 collisions:199 txqueuelen:100 Interrupt:10 Base address:0xe400 eth1 Link encap:Ethernet HWaddr 00:04:5A:6A:86:33 inet addr:192.168.1.1 Bcast:192.168.255.255 Mask:255.255.0.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:6423 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:11211 dropped:0 overruns:0 carrier:20183 collisions:0 txqueuelen:100 Interrupt:5 Base address:0xe000 Camelia NASTASE wrote: > > > > 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. > > > > but without indicating the source interface, does your traceroute work? > > you could give us the output from "/sbin/route -n" and "/sbin/ifconfig". > it might help. > > best regards, > camelia > -- --------------F337629BD3A527A56AD57FAF Content-Type: text/x-vcard; charset=us-ascii; name="ianz.vcf" Content-Transfer-Encoding: 7bit Content-Description: Card for Ian Zapczynski Content-Disposition: attachment; filename="ianz.vcf" 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 --------------F337629BD3A527A56AD57FAF--