Intentionally do the wrong thing in using the initial DHCP values for

ifconfig, essentially stealing the lease until the user goes and changes
it.  The alternative, sadly, is total dysfunction since bpf isn't in
GENERIC and network connectivity would otherwise fail completely on first
bootup when DHCP configuration was attempted again.

The ultimate answer here is to make either bpf a loadable kernel module
(which security conscious admins will be able to simply remove from /modules)
or come up with a lighter weight mechanism just for dhcp and other apps that
need to see broadcast packets but not otherwise sniff the wire in full
bpf glory.

0 files changed, 0 insertions, 0 deletions