summaryrefslogtreecommitdiff
path: root/bpf-interface.scm
AgeCommit message (Collapse)Author
2016-03-04Apparently even nonblocking reads are blocking in a way(?!) and we will get ↵Peter Bex
multiple packets off the iface. The actual packet data is preceded by a "struct bpf_hdr" header we need to skip. Because of that, passing a raw buffer is not going to be very useful, so bpf-read-packet! can be removed from the API.
2016-03-04Switch to nonblocking I/O and get rid of bpf-read-timeout since it is ↵Peter Bex
useless for nonblocking I/O...
2016-03-04Make ioctl interface a little less verbose by generating some stuff that's ↵Peter Bex
always the same in a macro. This should also inline it
2016-03-04Implement filter settingPeter Bex
2016-03-04Add stats procedurePeter Bex
2016-03-04Implement timeout IOCTLPeter Bex
2016-03-04Expose flush ioctl and add listing/getter/setter of datalink types.Peter Bex
For now, we just work with the underlying integer values. Maybe later we'll translate these to symbols?
2016-03-04Don't try to print details of closed BPF objectsPeter Bex
2016-03-04Implement buffer-length option, and export the interface setting/getting ↵Peter Bex
procedures as well as the procedure to retrieve the buffer length. Switch to c-pointer and use LOCATION to get pointers from scheme objects.
2016-03-04Add setup file, copyright and BPF device interfacePeter Bex
Add an initial opaque record type holding a connection to the BPF device. At least this now allows us to open a BPF device onto a network interface and request which network device we're connected to.