[2433] in linux-net channel archive
Re: IGRP
daemon@ATHENA.MIT.EDU (ATPlack@scj.com)
Tue Apr 9 19:54:50 1996
From: ATPlack@scj.com
Date: 9 Apr 96 12:39:06 -0500
To: linux-net@vger.rutgers.edu, linux-ppp@vger.rutgers.edu
Cc: csd@microplex.com
Novell Server-----\
199.250.250.152 E
t
h-----Linux Box....PPP Link...Shiva---------E
e 199.250.250.150 152.72.252.Y t
Workstation-------r 152.72.252.173 h
199.250.250.100 n e
e r
t All----------router----n
NT Box------------/ points 152.72.252.X e
199.250.250.151 beyond t
Trying to ping from Workstation to router.
To date, I found routed loaded which is providing the RIP. I have replaced
this with gated in my rc.inet2 file.
If I ping from Linux to any valid address, life is good.
If I ping from Workstation to router or Shiva, I have no answer.
TCPDUMP on the eth0 line is showing the packets from the workstation are
rejected.
TCPDUMP on the ppp line shows nothing.
The RIP packet shows only 199.250.250.150 and 172.52.252.Y. I do have
152.72.0.0 and the default route in the route table.
I recompiled the kernel and ensured that I had gateway/forwarding as Y and
firewalling as N. I now have loaded with the new kernel (1.2.13).
I got the same thing so I figured that maybe setting up a proxy arp to the
Shiva would help. (By the way, whoever determined that the proxyarp option
in pppd should only work if the two sides are on the same subnet, needs to
rethink why this is.)
Now, TCPDUMP on the ppp line shows the ICMP packet passing to the Shiva but
no returned packet coming back.
I am still assuming that this is because there is no RIP packets on the
152.72.0.0 networks (except mine now).
Here is the bait. If I can get this to fully function, NT is history (This
will make a nice X box for me). So all you Microsoft bashers who are good
at this, join in.
I am willing to face the issue that this network which the Shiva is on will
not work with my current environment, I just want to make sure.
kernel routing table
Destination Gateway Genmask Flags Metric Ref Use
Iface
127.0.0.1 0.0.0.0 255.255.255.255 UH 0 0 0 lo
152.72.252.Y 0.0.0.0 255.255.255.255 UH 0 0 47 ppp0
152.72.252.174 0.0.0.0 255.255.255.255 UH 0 0 0 lo
199.250.250.0 0.0.0.0 255.255.255.0 U 0 0 2989 eth0
152.72.0.0 0.0.0.0 255.255.0.0 U 0 0 14 ppp0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 753 lo
0.0.0.0 152.72.252.126 0.0.0.0 UG 0 0 1121 ppp0
lo Link encap:Local Loopback
inet addr:127.0.0.1 Bcast:127.255.255.255 Mask:255.0.0.0
UP BROADCAST LOOPBACK RUNNING MTU:2000 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0
TX packets:1152 errors:0 dropped:0 overruns:0
ppp0 Link encap:Point-Point Protocol
inet addr:152.72.252.174 P-t-P:152.72.252.Y Mask:255.255.0.0
UP POINTOPOINT RUNNING MTU:256 Metric:1
RX packets:910 errors:0 dropped:0 overruns:0
TX packets:1235 errors:0 dropped:0 overruns:0
eth0 Link encap:10Mbps Ethernet HWaddr 00:60:8C:BB:84:55
inet addr:199.250.250.150 Bcast:199.250.250.255
Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:6398 errors:0 dropped:0 overruns:0
TX packets:3395 errors:0 dropped:0 overruns:0
Interrupt:10 Base address:0x300
----------
From: csd@microplex.com
To: Plack, Anthony, T.
Cc: csd@microplex.com; linux-net@vger.rutgers.edu;
linux-ppp@vger.rutgers.edu
Subject: Re: IGRP
Date: Thursday, April 04, 1996 12:36AM
X-Mailer: ELM [version 2.4 PL23]
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Length: 3590
Could you send a little map of IP addresses configured for these machines
and the ip address you're trying to ping ? Also send a netstat -rn result
from your linux box and a ifconfig result. That should make it easier to
help you.
Cheers,
Christian.
BTW: Some process *has* to be generating the RIP packets in your Linux
box if you're seeing them on the network. Check your processes.
> >
> I have one NT box, one Novell server (set up as a IP router), one
> Workstation (WFW 3.11), and one Linux box.
>
> The Novell server, workstation and NT box have the default route as the
> Linux box. The Linux box has the default route through the PPP link.
>
> gated is not running.
>
> I am not able to Ping from the NT, Novell, or Workstation to the other
side
> of the Linux box.
>
> When I do an IPtrace from the workstation, I can see the RIP from the
Novell
> server and the Linux box (and some stupid NETBIOS broadcasts from the NT
> box).
>
> I have enabled packet forwarding on the kernel and recompiled. The RIP
> packets look correct from the Linux box.
>
> During a PING on the NT box, it returns a message that indicates the Linux
> box rejecting that route as unreachable.
>
> A ping from the Linux box across the link works okay. Only the Linux box
> can communicate across the link.
>
> According to the NET-2 How-To. I do not see any other piece that should
be
> needed.
>
> Why is the Linux box not routing the packets?
>
> Since I see the RIP packets, why would I need gated?
> ----------
> From: csd@microplex.com
> To: Plack, Anthony, T.
> Cc: linux-net@vger.rutgers.edu; linux-ppp@vger.rutgers.edu
> Subject: Re: IGRP
> Date: Tuesday, March 26, 1996 3:55AM
>
> X-Mailer: ELM [version 2.4 PL24 ME7]
> Mime-Version: 1.0
> Content-Type: text/plain; charset=US-ASCII
> Content-Transfer-Encoding: 7bit
> Precedence: bulk
>
> > I have a great connection to the network now through the PPP link.
> However,
> > that is only on my linux machine.
> >
> > I assume that gated will help get the route available to the other
> machines
> > on my local Ethernet segment. If not, someone let me know. I am going
to
>
> > try this this week.
> It shouldn't. Host computers should not get their routing info from
> routing protocol updates. Gated is there to make routers talk to
> themselves. You'll probably need to configure at least the default
> gateway on the other machines. The rest should sort itself out from there
>
> > My primary concern is that I might need to support IGRP. See the
network
> > guys here have disabled RIP on all networks at our sight in favor of
IGRP
> > from Cisco.
> >
> > Any ideas on support for this through Linux.
> >
> As far as I know, IGRP is proprietary and cisco has patents on some
> portions of it, so I don't think you'll get Linux boxes talking IGRP
> anytime soon.
> (Could someone confirm/deny this info that I have?)
>
> cheers,
>
> Christian.
>
> --
> ----------------------------------------------------------------
> Christian Daudt (csd@microplex.com) Software Engineer
> Microplex Systems Ltd. URL: http://www.microplex.com/
> "You can tell how far we have to go, when FORTRAN is the language of
> supercomputers." -- Steven Feiner
>
>
>
>
>
>
--
----------------------------------------------------------------
Christian Daudt (csd@microplex.com) Software Engineer
Microplex Systems Ltd. URL: http://www.microplex.com/
"You can tell how far we have to go, when FORTRAN is the language of
supercomputers." -- Steven Feiner
