Age | Commit message (Collapse) | Author |
|
From danh@, ok aja@ giovanni@
|
|
|
|
dot sourceforge dot net.
|
|
|
|
Francoise.
|
|
|
|
|
|
|
|
exception of a few messages specific to softraid(4) CRYPTO, there should
be no functional change for drivers that do not yet implement the interface
(which is currently all of them).
|
|
|
|
by design.
ok henning pyr
|
|
while here, failed stats should count against the limit too.
ok deraadt sthen stsp
|
|
Change the successes from LOG_INFO to LOG_DEBUG as well.
|
|
and myself, with help from jmc@ and feedback from phessler@.
|
|
ok jmc@, millert@
|
|
create ffs partitions with invalid fsize and bsize values newfs
will croak on. However, they should be able to set them to whatever
consistent values they want, not just make them smaller.
Also tweak some verbiage.
|
|
ok yasuoka@
|
|
compatible equipment provided that the physical interface and other layer 2
devices involved support and are configured to use jumbo frames.
Manpage to follow; typical use is to request 1500 MTU for pppoe, this
requires 1508+ MTU on the physical interface, e.g. "ifconfig em0 mtu 1508;
ifconfig pppoe0 mtu 1500". Known to be usable in the UK with some ISPs
(e.g. aaisp) using BT FTTC backhaul.
From Matt Dainty, originally based on support in NetBSD, changed to
decouple pppoe from physical interface MTU. Tested with UK FTTC by Matt,
no regressions on my standard UK ADSL setup or yasuoka@'s setup (in Japan,
NTT uses 1452 byte MTU for PPPoE and 1500 byte MTU for IPv6 on the same
network).
ok yasuoka@
|
|
extract xauth data so that it can't be used to play local shell
metacharacter games. Report from r00t_ati at ihteam.net, ok markus.
|
|
ok guenther@
|
|
ok stsp@
|
|
Found by LLVM/Clang Static Analyzer.
ok henning@ markus@
|
|
|
|
ok millert@
support from mcbride@ and others
|
|
Check if the node was already cached first. Duplicate nodes aren't reachable
from the node cache's RB tree, so they leak and mess up node cache accounting.
As more and more nodes leak the global nodes counter keeps increasing,
eventually reaching the limit and hovering there. The system then constantly
tries to clean the node cache, sending de-auth frames to stations in the
process, even if the actual number of associated stations is small.
ok jsg@
|
|
only scanning for networks). These were never put into COLLECT state and
were thus never evicted from the node cache in hostap mode.
ok jsg@
|
|
Based on code from FreeBSD.
Tested by myself (full release/install cycle on i386 and sparc64) and ajacoutot.
Man page help from jmc.
|
|
- network events (CONNECT/CLOSE)
- commands (QUIT/RSET)
ok gilles@ eric@
|
|
|
|
scratch, it uses parser.c derived from ikectl(8) to have OpenBSD's
fashion. This includes related changes listed below:
- changed npppd control IPC heavyly.
- support IPv6 as tunnel source address.
- deleted support changing the configuration of npppd_ctl on running.
Because it is not so needed but it requires privilege operations.
- refactors.
man page helps from jmc. tested by sebastia.
ok deraadt sebastia sthen
|
|
ok sebastia sthen
|
|
a packet that is passed to the userland has not incremented, `pipex' passed
the packet mistakenly with invalid ack number. Then `npppd' will drop these
packets, so that caused the problem.
tested jmatthew
ok jmatthew
|
|
up to 3 times slower than the C code most of the time. This was
brought up by DragonflyBSD guys initially.
ok deraadt, guenther. miod will not miss it.
|
|
|
|
|
|
|
|
|
|
to DEV_NAME. No functional change.
|
|
i.e. when rounding off various values.
ok deraadt@ sthen@
|
|
first member of each ioctl data structure. This will allow for future
changes to bio(4) status handling.
|
|
|
|
any assembly. This avoids a panic when attempting to assemble a RAID 1 (or
other) volume as a RAID 0 volume. Also reorder some of the other checks and
diagnostics performed during assembly.
|
|
|
|
|
|
diff from Alexis Fouilhe; help/ok sobrado
|
|
|
|
|
|
|
|
signalled using the "Long" format, like pgrep.
Original diff from FreeBSD, modified somewhat on tech@, with feedback from nicm@
Man page input from jmc@
|
|
errors up to a maximum of 127, then to do not increment anymore,
though programme execution continues.
Use 127 as a maximum because error codes above this are:
1. bad because of signed bugs in programs.
2. used as the traditional shell $? representation of "kill by signal"
where $? = 128 + signal.
(from deraadt@ and guenther@ respectively)
|