From owner-freebsd-questions Fri Jul 19 11:19:46 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id LAA11401 for questions-outgoing; Fri, 19 Jul 1996 11:19:46 -0700 (PDT) Received: from zibbi.mikom.csir.co.za (zibbi.mikom.csir.co.za [146.64.24.58]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id LAA11395 for ; Fri, 19 Jul 1996 11:19:37 -0700 (PDT) Received: (from jhay@localhost) by zibbi.mikom.csir.co.za (8.7.5/8.7.3) id UAA02586; Fri, 19 Jul 1996 20:19:20 +0200 (SAT) From: John Hay Message-Id: <199607191819.UAA02586@zibbi.mikom.csir.co.za> Subject: Re: Scanning for Interfaces! To: tcg@ime.net Date: Fri, 19 Jul 1996 20:19:19 +0200 (SAT) Cc: questions@freebsd.org In-Reply-To: <31EFADF9.7E3E@ime.net> from Gary Chrysler at "Jul 19, 96 11:47:05 am" X-Mailer: ELM [version 2.4ME+ PL16 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Hiya all. > > I'm working on hacking up a Linux IPX program, LinWare (lwared-0.95) > I've got it compiling, It runs, It dosn't work! :( > No connection to the interface yet. > > The problem: Several. :( > In hopes of: Help! > Reason : It's over my head. :( > And would like very much to change this! > Only way is to dive in! I have, I need some > assitance. > > System 2.1.0-R, fbsd-ipx patch. (2.1.5 when I get the CD) > > [....] > > BTW: I added two things to sockaddr_ipx in sys/netipx/ipx.h > struct sockaddr_ipx { > u_char sipx_len; > u_char sipx_family; > struct ipx_addr sipx_addr; > char sipx_zero[2]; > u_char sipx_type; /* tcg */ > u_long sipx_network; /* tcg */ > }; > I see Garrett has already answered the other questions, so I will just comment on this one. Defining sipx_network there will probably not work, because the kernel part of ipx will expect it inside sipx_addr. Maybe you can make a #define to make getting to it easier, eg. #define sipx_network (*(union ipx_net_u *)&sipx_addr.x_net)).long_e Note that this may not be correct because I have been looking at a -current ipx.h file. I'm not sure what the purpose of the sipx_type field is. Is it the ipx type that should be used in the type field of the packet? Because that is set with a setsockopt(....., SO_DEFAULT_HEADERS, ...) call. You can get an example of that in IPXrouted/main.c John -- John Hay -- John.Hay@mikom.csir.co.za