When switching variables to flags in r243185 a few cases were missed.
After r263152 this leaves unused variables if route(8) is compiled
without INET support.
Switch the remaining variable accesses to flags and remove now obsolete
variables.

Reviewed by:	glebius
MFC after:	1 week
Set oif only for outgoing packets.

PR:		188543
MFC after:	1 week
Sponsored by:	Yandex LLC
Use ETHER_ALIGN as argument to m_adj() to offset the beginning of packet
rather than the magic number 2.

While here fix a typo in a comment.

No functional changes.

MFC after:	1 week
Sponsored by:	DARPA/AFRL
Remove the libkse directory.  It was unhooked from the build and kernel
support removed in 2008 (prior to 8.0).

Approved by:	deischen, imp
MFC after:	3 days
Add kern.iscsi.fail_on_disconnection; this is required for gmultipath
to work.

Sponsored by:	The FreeBSD Foundation
Fix typo.

Sponsored by:	The FreeBSD Foundation
Make it possible for the initiator side to operate in both proxy
and normal mode; this makes it possible to compile with the former
by default, but use it only when neccessary.  That's especially
important for the userland part.

Sponsored by:	The FreeBSD Foundation
Fix VIRTUAL and PROF interval timers for short intervals, broken at r247903.

Due to the way those timers are implemented, we can't handle very short
intervals.  In addition to that mentioned patch caused math overflows
for short intervals.  To avoid that round those intervals to 1 tick.

PR:		kern/187668
MFC after:	1 week
Include opt_ddb.h in the list of SRCS, since we include it.

MFC after: 3d
Close the race in older code, that caused connection stuck after r264348.

Reviewed by:	trasz
MFC after:	2 weeks
Sponsored by:	iXsystems, Inc.
Do not set M_BESTFIT if a strategy has already been provided.  This
fixes problems when using M_FIRSTFIT.

Reviewed by:	jeff@
MFC after:	1 week
when watchdogd is asked to exit nicely (via SIGTERM) it will
stop timer. since watchdogd rc.d script is marked as 'shutdown'
it will exit (on shutdown) and stop timer. if system happens to
hung after watchdogd exited, manual reset is required. when one
operates in "lights-out" type of environments and without
readily available "remote hands" it could create a problem.

this provides ability to override "stop signal" for watchdogd.
default behavior is preserved, i.e. watchdogd will still be killed
via SIGTERM and timer will be stopped. in order to activate new
feature, one needs to put

watchdogd_sig_stop="KILL"

into /etc/rc.conf and also make sure watchdogd timeout is set
to long enough value allowing system to come back online before
timeout fires.

Obtained from:	Netflix
MFC after:	1 week
Sync with OpenBSD.

MFC after:	2 weeks
Minor style(9) cleanups

#define should be followed by a tab.

MFC after:	3 days
Remove unused variable.

PR:		173521
MFC after:	1 week
Sponsored by:	Yandex LLC
Add a missing break in the TCP case.

Reviewed by:	bms
MFC after:	1 week
Merge remote-tracking branch 'upstream/master' into hardened/current/aslr