d56f51ea7d
As part of this, we import bpf_filter.c from NetBSD. Even though that file is part of the NetBSD kernel, it is also used by userland (as is clear here). Our LWIP service has its own bpf_filter.c implementation but that implementation has certain limits (e.g. on program size) that are fine for a system service but should not apply to userland. The libpcap code has a number of blocks guarded by __NetBSD__, but none of those blocks apply to MINIX 3. In particular, some of the alignment logic used for NetBSD may in fact not work in our case. Change-Id: Ib187e22d627c929e111d5d4a991c3bee3c0154cb
20 lines
760 B
Bash
Executable File
20 lines
760 B
Bash
Executable File
#! /bin/sh
|
|
|
|
#
|
|
# Unfortunately, Mac OS X's devfs is based on the old FreeBSD
|
|
# one, not the current one, so there's no way to configure it
|
|
# to create BPF devices with particular owners or groups.
|
|
# This startup item will make it owned by the admin group,
|
|
# with permissions rw-rw----, so that anybody in the admin
|
|
# group can use programs that capture or send raw packets.
|
|
#
|
|
# Change this as appropriate for your site, e.g. to make
|
|
# it owned by a particular user without changing the permissions,
|
|
# so only that user and the super-user can capture or send raw
|
|
# packets, or give it the permissions rw-r-----, so that
|
|
# only the super-user can send raw packets but anybody in the
|
|
# admin group can capture packets.
|
|
#
|
|
chgrp admin /dev/bpf*
|
|
chmod g+rw /dev/bpf*
|