[prev in list] [next in list] [prev in thread] [next in thread] 

List:       linware
Subject:    Help: using mars_nwe with ipxd
From:       "Andrew S. Prior" <andrew () cs ! toronto ! edu>
Date:       1998-01-25 16:21:47
[Download RAW message or body]

 Hi,
   I've been looking into using mars_nwe for a little while, and there's
one main problem I've been having that's preventing it's use: I can't 
seem to get it to talk to anybody else when I'm using ipxd instead of
the internal RIP/SAP.  It seems like when RIP/SAP is turned off mars
tries to use the ethernet number as it's network number, and I think that's
what ipxd is also using as I get lots of error messages like:

NCPSERV  0:T_BIND ADR=net=0:0:0:3, node=0:0:c0:7f:47:d2, sock=04:51
NCPSERV  0:T_BIND ADR=net=0:0:0:3, node=0:0:c0:7f:47:d2, sock=41:12

  I had been trying to fiddle with the nwserv.conf file until I noticed
that sections 3 and 4 (the parts to specify the network number) aren't
processed with internal RIP/SAP turned off.  

  I would just use the RIP/SAP in mars, except that ipxd seems to go 10x
faster and I need ipx routing to be continuous while I'll be taking mars
up and down frequently.

  I've been looking at logs of ipxd to see if I can find anything.  The
following item seems to indicate that mars (TRINQ) is contacting ipxd:

     ADD SAP: type: 0004 name: TRINQ                                            
     hops: 1 addr: 00000003:0000C07F47D2:0451 10

but it never shows up on slist on the same machine that ipxd and mars are
running on.

  Can somebody tell me how to get this to work?  I haven't quite followed
enough of the code to just hardcode some network number in myself, which is
what I suspect the problem is.

                                                        Andrew

--------------------------------------------------
 Andrew Prior                PhD Student (Vision)
 Dept. of Computer Science, University of Toronto                   

[prev in list] [next in list] [prev in thread] [next in thread]