Date: Mon, 31 Jan 2011 20:47:39 +1000 From: Da Rock <freebsd-questions@herveybayaustralia.com.au> To: freebsd-questions@freebsd.org Subject: Re: linux PF_PACKET compatibility Message-ID: <4D46934B.7060505@herveybayaustralia.com.au> In-Reply-To: <AANLkTikKRB-Mw2TEFFoi75xBJabEjaL64QYGh8FBgPxp@mail.gmail.com> References: <AANLkTikKRB-Mw2TEFFoi75xBJabEjaL64QYGh8FBgPxp@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 01/31/11 20:22, b. f. wrote: > Da Rock wrote: > ... > >> I've been chasing the answer to a FreeBSD version of this (approx. >> anyway), but I needed to find out what exactly PF_PACKET was first. >> Finally found this answer here: http://www.linuxjournal.com/article/4659 >> >> I looked up man socket and I can see possibilities (in my mind anyway), >> but I thought I'd be best to check if the gurus here might have a better >> idea. My reason for this is I'm attempting to build l2tpns (which >> supposedly builds on 7.2?! with no trouble), and I'm chasing the errors >> which appear to be linuxisms mostly. >> >> So in man socket simply looking at the list of protocol families I'd say >> network driver level would be PF_LINK link layer interface? Is there >> another man page I should be looking at as well? >> > In the past, those wishing to use similar functionality on FreeBSD > have turned to pcap(3), bpf(4), or ng_etf(4), and the underlying code. > This kind of question is better directed to the freebsd-hackers and > freebsd-net lists. > > I figured it might be. Having trouble with hackers atm though- can't subscribe... :( Thx
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4D46934B.7060505>