On Aug 8, 2013, at 1:14 AM, Darren Reed darr...@netbsd.org wrote:
A BPF program generated on Linux is just as valid as on Solaris or NetBSD.
Not necessarily - negative offsets in load and store instructions are supported
on Linux to access some metadata that's not in the packet data, but
Matthew Luckie wrote:
The motivation for this patch was to obtain something resembling the
timestamp closest to when a packet I generated and transmitted hit the
wire, to infer a more accurate RTT with an associated response packet.
That's certainly a worthy goal, but the patch might not help
Guy Harris wrote:
This is probably a pointless optimization,
This referring not to your change, but to having one time stamp call
per packet.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send
(Noise to defeat the duplicate-message detector for
[EMAIL PROTECTED])
Guy Harris wrote:
This is probably a pointless optimization,
This referring not to Bruce's proposed change, but to my proposed
change to have one time stamp call per packet
On Sep 8, 2004, at 2:26 AM, Bruce M Simpson wrote:
Here's a patch against 5.3 to add a per-instance switch which allows
the user to specify if captured packets should be timestamped (and,
if so, whether microtime() or the faster but less accurate
getmicrotime() call should be used).
This is
This commit reminded me one of my old ideas. Why not to make some
function that allow to change DLT on the fly?
Such as NetBSD's bpf_change_type()?
/*
* Change the data link type of a interface.
*/
void
bpf_change_type(ifp, dlt, hdrlen)
struct ifnet *ifp;
u_int dlt, hdrlen;
{
What are the chances of Phil Wood's patches getting ported?
If you mean the patches from
http://public.lanl.gov/cpw/
then the chances are no greater than the chances of memory mapping
being added to BPF. :-)
I.e., the patches support use of Linux's memory-mapped PF_PACKET socket
support;
On Tue, Oct 15, 2002 at 11:54:52AM +0100, Bruce M Simpson wrote:
This sounds very similar to the promiscuous cell receive option on ENI's
SpeedStream 5861 router. I found the raw hex cell output was essentially
a 4 byte ATM UNI header omitting the CRC byte, and the 48 bytes of the raw
AAL5
On Tue, Oct 15, 2002 at 01:01:05PM +0200, Harti Brandt wrote:
Does Sun still make ATM cards? As far as I remember I saw the last SBUS
cards a couple of years ago.
They still have a Web page for SunATM:
The problem is, that at attach time you
don't know what link-level encapsulation is used, because this can be
select when you establish the VCC (via the parameter 'z' (see en(4))).
So BPF_DLC_RFC1483 will not work without LLC/SNAP encapsulation.
The current CVS versions of libpcap and
10 matches
Mail list logo
