From owner-freebsd-hackers@FreeBSD.ORG Tue Dec 14 18:22:09 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9188716A4CF for ; Tue, 14 Dec 2004 18:22:09 +0000 (GMT) Received: from grsu.by (grsu.by [194.158.202.115]) by mx1.FreeBSD.org (Postfix) with SMTP id 0A0B243D45 for ; Tue, 14 Dec 2004 18:22:07 +0000 (GMT) (envelope-from grog@grsu.by) Received: (qmail 71471 invoked from network); 14 Dec 2004 18:19:57 -0000 Received: from unknown (HELO ?10.31.16.99?) (grog@10.31.16.99) by grsu.by with SMTP; 14 Dec 2004 18:19:57 -0000 Message-ID: <41BF2EE7.8050201@grsu.by> Date: Tue, 14 Dec 2004 20:20:23 +0200 From: Yury Tarasievich User-Agent: Mozilla Thunderbird 0.9 (X11/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Subject: IPX, Netware functionality? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Dec 2004 18:22:09 -0000 Is somebody still working on IPX, Netware functionality? I'm having quite unexpected problems on 4.10-RELEASE when trying to mount netware volumes. In former 4-releases, I could a) add IPX+ef to kernel, b) recompile, c) run IPXrouted and d) make ifconfig f[0-3] ipx , then everything worked. Now, I don't see f[0-3] pseudo-interfaces anymore. ifconfig ipx, however, works. After using it, I can have either one several (aliased) ipx entries in my ifconfig. And tcpdump confirms there *is* at least SAP traffic from netware servers I'm interested in. Now, everything netware-related fails with "protocol not supported" diagnostic. I digged a bit in ncplist, and found that the ipx listening socket fails to receive anything with ETIMEDOUT. IPX socket not working?? Could anything be done? Also, there's some peculiar logic in ipx addresses checking in libncp routines, e.g., ipx_nullnet checking of host addrs. For my digging, I had to circumvent it, as without doing so, perfectly reasonable configuration just generated error, without even trying to listen to the network.