Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.hawaii.edu!ames!night.primate.wisc.edu!caen!math.ohio-state.edu!howland.reston.ans.net!nntp.crl.com!crl4.crl.com!not-for-mail From: ggrant@crl.com (Gary E. Grant) Newsgroups: comp.os.386bsd.questions Subject: Re: Ethernet on FreeBSD 2.0 with Netware Date: 23 Feb 1995 23:27:44 -0800 Organization: CRL Dialup Internet Access (415) 705-6060 [Login: guest] Lines: 34 Message-ID: <3ik1pg$bb7@crl4.crl.com> References: <9502210842436@horizon.org> <3idq6j$em@terrazzo.lm.com> NNTP-Posting-Host: crl4.crl.com In article <3idq6j$em@terrazzo.lm.com>, fredh <fredh@telerama.lm.com> wrote: >Blade Runner (blade.runner@horizon.org) wrote: >> I am using FreeBSD 2.0 with a 3COM 3C509-TP Ethernet Adaptor. I am >> using ep0 in the FreeBSD Machine. I have a simular card on a netware >> 3.12 server with IP bound to Frame Type ETHERNET_II and other Frame >> types have IPX bound to the same card. > >> The Two Machines cannot see each other when Pinging the other. When >> Pinging the Netware Box from the FreeBSD Box, I see the activity light >> on the concentrator go off, so I know FreeBSD is communicating with ep0 >> to try and find the Netware Box. > >> Does anyone know if FreeBSD is using a Frame Type Other than ETHERNET_II >> or if FreeBSD has any problems having packets of other frame types being >> on the same wire? This is driving me nuts and I am considering using >> Two seperate 10Base2 Cards to communicate between these two machines if >> this is going to be what is required. > >> Any Help is Appriciated. > >> blade.runner@horizon.org > >RESPONSE: > >The standard FRAME is 802.3, set the Netware server to 802.3 and it will >work. > >FredH > How you do this in a client is add the line FRAME=802.3 to the net.cfg file. In the NW 3.12 Server ti the autoexec.ncf file