Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!simtel!pravda.aa.msen.com!spool.mu.edu!howland.reston.ans.net!swrinde!tank.news.pipex.net!pipex!news.mathworks.com!newsfeed.internetmci.com!news.sprintlink.net!in2.uu.net!globalcenter.net!egmac219.globalvillag.com!user From: leo_cazares@globalvillage.com (Leo Cazares) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: CAP or NetAtalk supported in FreeBSD? Date: 24 Oct 1995 16:56:49 GMT Organization: Global Village Communication Lines: 40 Message-ID: <leo_cazares-2410950956150001@egmac219.globalvillag.com> References: <46fdpa$h6m@staff.cs.su.oz.au> <46ivgl$9ma@molnir.brunel.ac.uk> NNTP-Posting-Host: egmac219.globalvillag.com In article <46ivgl$9ma@molnir.brunel.ac.uk>, Nik.Clayton@brunel.ac.uk (Nik Clayton) wrote: > CAP up to v6 pl105 definitely works, because I use it. I haven't made it > into a port yet because I don't have the time, and because there are a > few problems I'm having with it. These problems could very well be due > to my less than optimal understanding of the finer points of Mac > networking. I have the latest CAP patches, but they won't help if you have an ep0 network device. The CAP documentation says that CAP will only work with the ed0 device...something about Multicast support... Unfortunately, CAP builds and runs fine when I run Linux, but there are problems for those of us with an ep0 network device. > Last time I looked at Netatalk (which various people have recommended to > me) it listed itself as only working with SunOS 4.1.3 and Ultrix. I > haven't put any effort into getting it to work with FreeBSD yet. I think that the same (or related?) problem exists with netatalk. It should work fine if you have an ed0 device. I built the latest netatalk on my FreeBSD 2.0.5 machine, but it doesn't work and I have not found out why. Steven G. Kargl forwarded some patches to the FreeBSD ep0 driver, but it didn't work for me and I have not had any time to try and figure out why it is not working. Patching the ep0 driver and rebuilding the kernel was trivial, but the netatalk programs get some kind of "network device not configured" error and give up. My network device is fine because I can communicate with other machines using TCP/IP (and it runs CAP when I boot Linux). > I'll cheerfully share my configuration notes on CAP with you. Mail me as > nik@blueberry.co.uk for more info if you need it. > > N It would be useful if documentation regarding known problems with ep0. I would like to hear from people running netatalk (preferably) or CAP on a 2.0.5 BSD system using the ep0 device. - Leo