Date: Tue, 15 Oct 2002 07:43:09 +0200 (SAT) From: John Hay <jhay@icomtek.csir.co.za> To: roelof@eboa.com (Roelof Osinga) Cc: stable@FreeBSD.ORG (stable) Subject: Re: Wee bit of trouble with IPX Message-ID: <200210150543.g9F5h9Mi079745@zibbi.icomtek.csir.co.za> In-Reply-To: <3DAB39D1.9010001@eboa.com> from Roelof Osinga at "Oct 14, 2002 11:40:33 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
> Nothing much really. Just that it don't actually work. Is all. > > I just cvsupped to 4.7, activated all the trimmings for IPX. Things > like NWFS just to be sure and IPX as well as NCP. Since it was for > accessing a Netware 3.11 kldloaded if_ef.ko too. > > Next I checked the NW 3.11 console to find that the NE-2000 (the real > thing actually <g>) was set to NET=CCC. The workstations accessing > the box had internal net set to "00000000". > > However, when I enter this: > > "ifconfig ep0 ipx 00000000 up; ifconfig ep0f1 ipx 00000000 up ; ifconfig ep0f1 ; IPXrouted -t -q" > > all I get are things like this: > > Received bogus packet from ccc#0:0:1b:37:ea:b2 > Received bogus packet from ccc#0:0:1b:37:ea:b2 Yup, that is to be expected. It basically means wrong network address. > The following when trying CCC: > > frl:~# ifconfig ep0 ipx 0xccc up; ifconfig ep0f1 ipx 0xccc up ; ifconfig ep0f1 ; IPXrouted -t -q Why do you try to configure both ep0 and ep0f1? And with the same ipx network number? I think you only need to configure ep0f1. > ep0f1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 > ipx ccc.60971431a7 > ether 00:60:97:14:31:a7 > Adding route to interface ep0 > action dst ccc#0:0:0:0:0:0, router ccc#0:60:97:14:31:a7, metric 0, ticks 0, flags UP state INTERFACE|CHANGED > REQUEST to ccc#ff:ff:ff:ff:ff:ff#0: > net ffffffff metric 16 ticks 65535 > REQUEST to ccc#ff:ff:ff:ff:ff:ff#452: > RESPONSE received ccc#0:0:1b:37:ea:b2#452: > service 0004 OA addr a#0:0:0:0:0:1.0451 metric 1 > service 0047 OA-PSERVER addr a#0:0:0:0:0:1.8060 metric 2 > Received a sap RESP packet. > ^Cfrl:~# > > frl:~$ ncplist s OA > Could not find server OA > frl:~$ ncplist s > Can't find any file server > > Anyone know why it can see OA yet not contact it in an usable manner? You probably confused it with the same network number on two interfaces. John -- John Hay -- John.Hay@icomtek.csir.co.za / jhay@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200210150543.g9F5h9Mi079745>