From owner-freebsd-stable Wed Oct 15 14:37:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA05859 for stable-outgoing; Wed, 15 Oct 1997 14:37:32 -0700 (PDT) (envelope-from owner-freebsd-stable) Received: from mail.wintek.com (mail.wintek.com [199.233.104.76]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA05821; Wed, 15 Oct 1997 14:37:21 -0700 (PDT) (envelope-from csg@wintek.com) Received: from mail.wintek.com (localhost.wintek.com [127.0.0.1]) by mail.wintek.com (8.8.7/1.34wintek(3.6davy)) with ESMTP id VAA15472; Wed, 15 Oct 1997 21:37:14 GMT Message-Id: <199710152137.VAA15472@mail.wintek.com> To: freebsd-stable@freebsd.org cc: julian@freebsd.org, ajk@wspout.com, ab@wspout.com, csg@wspout.com Subject: Re: netatalk still broken in 2.2-STABLE Date: Wed, 15 Oct 1997 16:37:13 -0500 From: "C. Stephen Gunn" Sender: owner-freebsd-stable@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <199710151811.NAA04074@argon.vapornet.com>, John Preisler writes: >I"ll try pulling the older .c files off tape and rebuilding. I tried pulling older versions of: sys/netatalk/at_control.c 1.14 sys/netatalk/ddp_output.c 1.4 Both of these versions are before some changes that julian@freebsd.org made to fix a problem with routing packets to hosts that were on a different net, but the same netrange as a given interface. In particular (this could be conjecture), the problem could be with the aa_claim_addr() routine in at_control.c. I'm not a big kernel hacker type, so I won't say any more. I also applied the patch from http://www.umch.edu/~rsug/netatalk/patches/ for MacOS 8 fixes. It might be a good idea to add this to the 1.4b2 port in ports/net/netatalk. It appears to work fine. - Steve -- C. Stephen Gunn Wintek Corporation E-mail: csg@wintek.com 427 N 6th Street Tel: +1 (765) 742-8428 Lafayette, IN 47901-1126 Fax: +1 (765) 742-0547 United States of America