All of lore.kernel.org
 help / color / mirror / Atom feed
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 13:27:01 -0400	[thread overview]
Message-ID: <3CB32465.E4624D57@quarterleaf.com> (raw)
In-Reply-To: 20020409195855.B53955-100000@bofh.dnt.ro

[-- Attachment #1: Type: text/plain, Size: 2576 bytes --]

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
> --

[-- 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

  reply	other threads:[~2002-04-09 17:27 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 [this message]
     [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=3CB32465.E4624D57@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 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.