Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!mips!apple!ksand From: ksand@Apple.COM (Kent Sandvik, 120dB or more) Newsgroups: comp.unix.aux Subject: Re: Raw (More or Less) Ethernet Access in A/UX? Message-ID: <13022@goofy.Apple.COM> Date: 12 Apr 91 03:10:31 GMT References: <10944@bunny.GTE.COM> Organization: Apple Computer Inc., Cupertino, CA Lines: 33 In article urlichs@smurf.sub.org (Matthias Urlichs) writes: >In comp.unix.aux, article <10944@bunny.GTE.COM>, > dcr0@harvey.gte.com (David Robbins) writes: >< We have a peculiar Ethernet protocol that I am considering porting to A/UX. >< Question: does there exist a capability to speak to the Ethernet driver on >< A/UX 2.0 at a level more primitive than a raw IP socket? Something along the >< lines of Sun's NIT or the Berkeley enetfilter (aka Ultrix 4.0 packetfilter)? >< Or has Apple carefully hidden the Ethernet interface behind TCP/IP in order to >< idiot-proof it (and, in the process, rendering it less useful for us weirdos)? >Hmm, the Device Driver's kit has source code to the Ethernet driver, which >has something called ETHERLINK in it, which seems to do what you want. Search >for ETHERLINK in the header files (/usr/include/*/*). >Caveat (from said source code): if you open an [AP]F_ETHERLINK socket, you'll >have to bind an IP address to it so that it can find the correct interface to >send to. Funny, I was reading the same stuff today, yes you could dive down all the way to the ethernet packet level with the example Ethernet device driver. A word of warning, the A/UX dev. driver kit is for A/UX 2.0, and u_phys has changed, and there are some header file changes. It could happen that the dev. driver kit works OK with most of the 2.0.1 headers/object files, but the object code will link together a 2.0 kernel, and that's not exactly what you want for testing on a 2.0.1 system. Kent -- Kent Sandvik, DTS junkie