Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
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@
|
|
Found by LLVM/Clang Static Analyzer.
ok henning@ markus@
|
|
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@
|
|
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.
|
|
|
|
|
|
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.
|
|
|
|
particularly the "consume the signal you just sent" hang, and putting
the wait queues in userspace.
Do cancellation handling in pthread_cond_*wait(), pthread_join(),
and sem_wait().
Add __ prefix to thr{sleep,wakeup,exit,sigdivert}() syscalls; add
'abort" argument to thrsleep to close cancellation race; make
thr{sleep,wakeup} return errno values via *retval to avoid touching
userspace errno.
|
|
than the autoconfprivacy bit, as per by RFC3484. Prevents privacy addresses
from being erroneously used as source address if the destination address is
in a different scope. Privacy addresses are still preferred over other source
addresses from the same scope.
Problem found by sthen, fix suggested by sperreault; ok sperreault
|
|
make their argument list shorter. Also fix a bug where pf_walk_option6()
used the outer header in the pd2 case.
ok henning@ mikeb@
|
|
to locate the root via DUID.
ok krw@
|
|
their types to fit the iopools api rather than doing awful typecasts to
shove them into iopool_init.
|
|
this prevents backup to failover back to master immediately
after getting link back on carpdev interface if underlying
pfsync interface went down as well. instead pfsync will
request a bulk update to get new states from the master.
sthen and mpf like the idea, ok dlg
|
|
so always show as writable to poll()/select().
Behavior pointed out by Fernando Gont. ok deraadt@
|
|
latter is called from pf packet logging. This resulted in normalization
and reassembly of bad packets to be logged. So rearrange the code
and move the call to pf_test().
ok henning@
|
|
with different bugs the host bridge is used to determine which path
to take. As pointed out by Chris Cappuccio we need to expand
this list to cover newer chips SiS have inflicted on the world.
From and tested by Loganaden Velvindron (on SiS 968).
|
|
ok dlg@
|
|
|
|
|
|
|
|
|
|
ok mpi@
|
|
|
|
|
|
select root.
|
|
|
|
The reassembly state will be dropped after timeout, all related
fragments are dropped until that. This is conforming to RFC 5722.
- Sort pf_fragment fields while there.
- If the fr_queue is empty, we had overlapping fragments, don't add
new ones.
- If we detect overlapping IPv6 fragments, flush the fr_queue and
drop all fragments immediately.
- Rearrange debug output, to make clear what happens.
- An IPv4 fragment that is totaly overlapped does not inclease the
bad fragment counter.
- Put an KASSERT into pf_isfull_fragment() to make sure that the
fr_queue is never emtpy there.
discussed with Fernando Gont; ok henning@
|
|
failures to be neglected; ok markus
|
|
would prepend another vlan tag 0 to all frames containing 802.1Q
tags rendering vlans unusable.
ok jsg, deraadt
|
|
from Alexey Suslikov
reviewed by marco
|
|
|
|
skinny variant of mfi(4) from Alexey Suslikov
|
|
|
|
from Michael W. Bombardieri; ok henning@
|
|
|
|
renamed.
|
|
Fix a white space bug while there. No functional change.
ok mikeb@ robert@ henning@
|
|
ok mikeb@
|
|
ok miod@
|
|
root on softraid possible, although the kernel still needs to be loaded
from a non-softraid partition.
|
|
is the DUID that we booted from, which is not always going to be the same
as the DUID that we mount root on.
|
|
via the boot device. This allows root on softraid to work on most
architectures. For architectures that cannot clearly identify their boot
device, the DUID of the boot disk can still be passed from the boot loader,
as is already done for amd64 and i386.
Based on a suggestion from kettenis@
ok krw@
|
|
us to play some tricks in setroot().
|