SUMMARY: 4.1.3 machine won't forward packets

From: Christopher M. Chin (chris@advent.com)
Date: Mon Apr 08 1996 - 16:49:57 CDT


Many thanks to those who responded:

   Michael J. Shon <mshon@sunrock.East.Sun.COM>
   Mike Salehi <mrs@cadem.mc.xerox.com>
   Cheryl L. Southard <cld@astro.caltech.edu>
   aub@ide.com
   Alexander Finkel <afinkel@pfn.com>

The most common suggestions were to ensure that packet forwarding
was turned on and to ensure that routed was advertising properly.

Unfortunately, both of these were the case. The problem is still
not resolved. The packets are landing at that machine, but are not
being forwarded. I had to rely on another host (Sparc20/4.1.4) to
handle the routing that I wanted to do.

I'll probably have to wait until a good time to tear this system
down apart to see if it's a hardware of software issue.

Thanks for the helpful suggestions,
 - Christopher

======================

My original query:

> Date: Thu, 28 Mar 1996 10:32:31 -0800 (PST)
> From: Christopher M. Chin <chris@Advent.COM>
> To: Sun Managers Mailing List <sun-managers@ra.mcs.anl.gov>
> Subject: 4.1.3 machine won't forward packets
>
> Hi, all,
>
> I've got a Sparc10 running 4.1.3 with two network interfaces
> acting as a router.
>
>
> 204.x.x.0 | | 206.x.x.0
> | |
> -------------------
> | le0 le1 |
> | Sparc10 |
> -------------------
>
>
> Before I go much further, I have to admit that I'm doing
> something bad .... both of these networks reside on the
> same (switched) Ethernet segment.
>
> I know this is a silly thing to do, but I also know that
> it works. We've used a Sparc20 running 2.4 to do the
> very same thing in the past.
>
> While we do have plans to segregate the networks, we
> planned on putting up with the noise and redundancy on
> the line until that time. So when I say networks, I
> really mean network numbers.
>
> Anyway, from this machine (router), I can ping hosts
> on both networks, but I can't ping from one network to
> the other.
>
> routed is running just as 'in.routed' .... no -s, but
> since both interfaces are up, the router is advertising
> itself correctly, and when I do a 'netstat -nr' on other
> hosts, I can see the proper route.
>
> However, the packets are landing at the router, and going
> nowhere. On the router 'netstat -s' shows the packets as
> being "non-forwardable":
>
> ip:
> 39768 total packets received
> 0 bad header checksums
> 0 with size smaller than minimum
> 0 with data size < data length
> 0 with header length < data size
> 0 with data length < header length
> 624 fragments received
> 248 fragments dropped (dup or out of space)
> 57 fragments dropped after timeout
> 0 packets forwarded
> 5003 packets not forwardable
> 0 redirects sent
> 0 ip input queue drops
>
>
> However, packet forwarding is indeed enabled:
>
> # adb -k -w /vmunix /dev/mem
> physmem 7f89
> ip_forwarding?
> _ip_forwarding:
> _ip_forwarding: 10000 = unimp 0x10000
>
> Am I missing something here? Like I've said I've got
> a similar situation running on a Sparc20 running Solaris
> 2.x, and that's working without any hitches.
>
> Thanks,
> - Christopher
>
> =========================================================================
> Christopher M. Chin (415) 543-7696 (voice)
> UNIX/Network Administrator (415) 896-1327 (fax)
> Advent Software, Inc.
> 301 Brannan Street chris@Advent.COM
> San Francisco, CA 94107-1849
> =========================================================================
>
>
>
>



This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:10:57 CDT