| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Spotted by: Ivan Voras
MFC after: 1 week
|
|
|
|
|
|
|
|
|
|
|
| |
The name trunk is misused as the networking term trunk means carrying multiple
VLANs over a single connection. The IEEE standard for link aggregation (802.3
section 3) does not talk about 'trunk' at all while it is used throughout IEEE
802.1Q in describing vlans.
The lagg(4) driver provides link aggregation, failover and fault tolerance.
Discussed on: current@
|
|
|
|
|
| |
Submitted by: rdivacky
MFC after: 1 week
|
| |
|
|
|
|
|
|
|
| |
correct test to -ge 5. Without this change an RFC3442 encoded default
route would be ignored.
Reported by: Cedric Jonas <cedric at decemplex dot net>
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
tolerance. This driver allows aggregation of multiple network interfaces as
one virtual interface using a number of different protocols/algorithms.
failover - Sends traffic through the secondary port if the master becomes
inactive.
fec - Supports Cisco Fast EtherChannel.
lacp - Supports the IEEE 802.3ad Link Aggregation Control Protocol
(LACP) and the Marker Protocol.
loadbalance - Static loadbalancing using an outgoing hash.
roundrobin - Distributes outgoing traffic using a round-robin scheduler
through all active ports.
This code was obtained from OpenBSD and this also includes 802.3ad LACP support
from agr(4) in NetBSD.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
out more than size bytes to the caller's buffer.
PR: bin/111191
Reviewed by: pb
MFC after: 1 week
|
|
|
|
|
|
|
|
|
| |
which size is not multiple of sector size.
Reported by: Eric Anderson <anderson@centtech.com>
- Improve wording in error message. I'm sorry, I don't remember who
submitted this one.
|
|
|
|
|
|
| |
parameter like everything else
MFC after: 2 weeks
|
|
|
|
| |
MFC after: 3 days
|
|
|
|
|
|
|
|
| |
hardware drivers. Unlike pseudo-device drivers, which just attach
to the cloning framework and wait for "ifconfig create", h/w drivers
create interfaces for installed cards as soon as loaded. The issue
of devd(8) involuntarily reloading modules should be dealt with in a
different way.
|
|
|
|
|
|
| |
PR: bin/110705
Reported by: Tom Judge
MFC after: 2 weeks
|
|
|
|
|
|
|
|
|
| |
new interface. In other cases loading the module is unwanted and
can lead to ill side effects. One such effect found is as follows:
"kldunload if_foo" tells the module to kill all its interfaces,
which results in messages sent to devd; the module unloads. Then
devd starts processing the messages, which ends up in a etc script
running ifconfig fooX, which reloads the module.
|
| |
|
|
|
|
|
|
|
|
|
| |
unit w/o suffix is specified. It had better be an empty
string as it will be passed to a printf-like function that
builds the command line to run.
PR: kern/109863
MFC after: 1 week
|
|
|
|
|
|
|
|
|
|
|
| |
<sys/extattr.h> to <ufs/ufs/extattr.h>. Move description
of extended attributes in UFS from man9/extattr.9 to
man5/fs.5.
Note that restore will not compile until <sys/extattr.h>
and <ufs/ufs/extattr.h> have been updated.
Suggested by: Robert Watson
|
|
|
|
|
|
|
|
| |
This is for better compatibility with other environments (Linux, Solaris,
HP-UX, AIX and Tru64 support these options).
PR: bin/109924
MFC after: 1 week
|
|
|
|
|
|
|
|
| |
to problems when the geli device is used with file system or as a swap.
Hopefully will prevent problems like kern/98742 in the future.
MFC after: 1 week
|
|
|
|
|
|
|
| |
course! It won't protect against reply attacks - try harder to explain
them correctly.
MFC after: 1 week
|
|
|
|
| |
Submitted by: Eric Anderson <anderson@freebsd.org>
|
|
|
|
| |
o warn when we skip an interface because it's name is too long
|
| |
|
|
|
|
| |
Spotted by: des
|
| |
|
|
|
|
| |
errors fixed.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
arrangement that has no intrinsic internal knowledge of whether devices
it is given are truly multipath devices. As such, this is a simplistic
approach, but still a useful one.
The basic approach is to (at present- this will change soon) use camcontrol
to find likely identical devices and and label the trailing sector of the
first one. This label contains both a full UUID and a name. The name is
what is presented in /dev/multipath, but the UUID is used as a true
distinguishor at g_taste time, thus making sure we don't have chaos
on a shared SAN where everyone names their data multipath as "Fred".
The first of N identical devices (and N *may* be 1!) becomes the active
path until a BIO request is failed with EIO or ENXIO. When this occurs,
the active disk is ripped away and the next in a list is picked to
(retry and) continue with.
During g_taste events new disks that meet the match criteria for existing
multipath geoms get added to the tail end of the list.
Thus, this active/passive setup actually does work for devices which
go away and come back, as do (now) mpt(4) and isp(4) SAN based disks.
There is still a lot to do to improve this- like about 5 of the 12
recommendations I've received about it, but it's been functional enough
for a while that it deserves a broader test base.
Reviewed by: pjd
Sponsored by: IronPort Systems
MFC: 2 months
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
the restore program to restore all dumped extended attributes.
If the restore is running as root, it will always be able
to restore all extended attributes. If it is not running
as root, it makes a best effort to set them. Using the -v
command line flag or the `verbose' command in interactive
mode will display all the extended attributes being set on
files (and at the end on directories) that are being restored.
It will note any extended attributes that could not be set.
The extended attributes are placed on the dump image immediately
following each file's data. Older versions of restore can work
with the newer dump images. Old versions of restore will
correctly restore the file data and then (silently) skip
over the extended attribute data and proceed to the next file.
This resolves PR 93085 which will be closed once the code
has been MFC'ed.
Note that this code will not compile until these header
files have been updated: <protocols/dumprestore.h> and
<sys/extattr.h>.
PR: bin/93085
Comments from: Poul-Henning Kamp and Robert Watson
MFC after: 3 weeks
|
|
|
|
|
| |
Reviewed by: bms
MFC after: 1 month
|
|
|
|
| |
Spotted by: Tomasz Dudzisz
|
|
|
|
| |
MFC: 1 week
|
|
|
|
|
|
|
|
| |
Assume '-a' and '-t malloc' flags for '-s <size>' (malloc ramdisk) if not
specified.
Reviewed by: phk (some time ago)
MFC: 1 week
|
|
|
|
|
|
|
|
|
| |
mdconfig -f image
works like a charm.
Reviewed by: phk (some time ago)
MFC: 1 week
|
| |
|
| |
|
| |
|
|
|
|
|
| |
image and sliced/partitioned memory disks.
MFC after: 1 week
|
|
|
|
|
|
|
| |
Other requests made in the PR were already solved in the past.
PR: bin/66763
MFC after: 1 week
|
|
|
|
| |
Approved by: glebius (mentor)
|
|
|
|
|
|
|
| |
Examples of use can be found in the PR text.
PR: 103501
MFC after: 1 week
|
| |
|
|
|
|
| |
This allows ``ffsinfo -o - -l1 /tmp'' to run a lot quicker.
|
| |
|
|
|
|
| |
Submitted by: ru
|
| |
|