Date: Tue, 24 Oct 1995 22:49:29 -0700 (PDT) From: Julian Elischer <julian@ref.tfs.com> To: msmith@atrad.adelaide.edu.au (Michael Smith) Cc: hackers@freebsd.org Subject: Re: AF_UNSPEC/SOCK_RAW and such... Message-ID: <199510250549.WAA17927@ref.tfs.com> In-Reply-To: <199510250423.NAA06939@genesis.atrad.adelaide.edu.au> from "Michael Smith" at Oct 25, 95 01:53:03 pm
next in thread | previous in thread | raw e-mail | index | archive | help
> > So I'm getting somewhere with the '485 multidrop stuff. My apologies for > being so clueless about the Big Picture 8( > > I'd _really_ like to be able to talk to it at a socket level, as this > will avoid toying around with pcap/bpf and the like. > > What I'm wondering is whether AF_UNSPEC/SOCK_RAW will just hand my > driver the packet as written, or whether it'll break something else. > > Obviously, suck it and see applies here, but some casual advice from those > that have gone before would be muchly appreciated 8) WARNING WARNING WARNING it's been a few years.. what protocol are you wanting to run? will your driver only be handling your packets? do you have your own protocol stack? you can do this but it really depends on you writing it int eh right way for it to work (duh!) coming up: You have to make sure your driver calls the correct protocol with the correct arguments going down: You have to make sure your protocol knows how to decide which interface to send it to.. it does work, but it (in general) requires you to fill in the missing pieces > > -- > ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ > ]] Genesis Software genesis@atrad.adelaide.edu.au [[ > ]] High-speed data acquisition and [[ > ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ > ]] My car has "demand start" -Terry Lambert UNIX: live FreeBSD or die! [[ >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199510250549.WAA17927>