| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
layer order from bottom to top.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
and protocol-independent host mode multicast. The code is written to
accomodate IPv6, IGMPv3 and MLDv2 with only a little additional work.
This change only pertains to FreeBSD's use as a multicast end-station and
does not concern multicast routing; for an IGMPv3/MLDv2 router
implementation, consider the XORP project.
The work is based on Wilbert de Graaf's IGMPv3 code drop for FreeBSD 4.6,
which is available at: http://www.kloosterhof.com/wilbert/igmpv3.html
Summary
* IPv4 multicast socket processing is now moved out of ip_output.c
into a new module, in_mcast.c.
* The in_mcast.c module implements the IPv4 legacy any-source API in
terms of the protocol-independent source-specific API.
* Source filters are lazy allocated as the common case does not use them.
They are part of per inpcb state and are covered by the inpcb lock.
* struct ip_mreqn is now supported to allow applications to specify
multicast joins by interface index in the legacy IPv4 any-source API.
* In UDP, an incoming multicast datagram only requires that the source
port matches the 4-tuple if the socket was already bound by source port.
An unbound socket SHOULD be able to receive multicasts sent from an
ephemeral source port.
* The UDP socket multicast filter mode defaults to exclusive, that is,
sources present in the per-socket list will be blocked from delivery.
* The RFC 3678 userland functions have been added to libc: setsourcefilter,
getsourcefilter, setipv4sourcefilter, getipv4sourcefilter.
* Definitions for IGMPv3 are merged but not yet used.
* struct sockaddr_storage is now referenced from <netinet/in.h>. It
is therefore defined there if not already declared in the same way
as for the C99 types.
* The RFC 1724 hack (specify 0.0.0.0/8 addresses to IP_MULTICAST_IF
which are then interpreted as interface indexes) is now deprecated.
* A patch for the Rhyolite.com routed in the FreeBSD base system
is available in the -net archives. This only affects individuals
running RIPv1 or RIPv2 via point-to-point and/or unnumbered interfaces.
* Make IPv6 detach path similar to IPv4's in code flow; functionally same.
* Bump __FreeBSD_version to 700048; see UPDATING.
This work was financially supported by another FreeBSD committer.
Obtained from: p4://bms_netdev
Submitted by: Wilbert de Graaf (original work)
Reviewed by: rwatson (locking), silence from fenner,
net@ (but with encouragement)
|
|
|
|
|
|
|
|
| |
when in -i mode so that each file gets a clean context of its own.
Add a regression test for the bug.
Tested with: regression tests
|
|
|
|
| |
Submitted by: edwin@
|
|
|
|
|
|
| |
cpp, not a shell script.
Pointy hat to: grog
|
|
|
|
|
|
| |
Submitted by: edwin@
PR: bin/113275
MFC after: 2 weeks
|
|
|
|
| |
Submitted by: Carl Johan Gustavsson
|
|
|
|
|
| |
the mapping from number to name differs between systems,
and will cause tests to fail.
|
|
|
|
| |
Document the procedure for obtaining an appropriately old version of sa.
|
|
|
|
| |
Submitted by: Carl Johan Gustavsson
|
|
|
|
| |
Submitted by: Larry Rosenman (who also provided access to a testing host)
|
| |
|
|
|
|
| |
exclusions list for header checking.
|
|
|
|
| |
in kern_acct.c.
|
|
|
|
|
|
|
|
|
|
| |
Four tests currently fail:
test_ether_line_bad_1() and test_ether_line_bad_2() due to bugs in
ether_line(3).
test_ether_ntohost() and test_ether_hostton() due to not being fully
implemented tests.
|
|
|
|
|
|
|
| |
on socket buffers is interruptible or not, which detacts the regression I
introduced recently in 7-CURRENT (spotted by alfred). This test passes
in older -CURRENT, and with the as-yet uncommitted sx_xlock_sig and
sblock fix patches.
|
|
|
|
| |
regarding RFC3542 compliance.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
each file independently from other files. The new semantics are
desired in the most of practical cases, e.g.: delete lines 5-9
from each file.
Keep the previous semantics of -i under a new option, -I, which
uses a single continuous address space covering all files to edit
in-place -- they are too cool to just drop them.
Add regression tests for -i and -I.
Approved by: dds
Compared with: GNU sed
Discussed on: -hackers
MFC after: 2 weeks
|
| |
|
| |
|
|
|
|
| |
The correct format specifier for ssize_t is %zd.
|
|
|
|
| |
than a page size and nbytes=0.
|
|
|
|
|
|
|
| |
Detailed description and instructions are in the README file.
This work had been basically done during GSoC 2006.
Approved by: brooks (mentor)
|
| |
|
|
|
|
|
|
| |
[Since the change to strict refcounting for in_multi objects, this test
began to fail; formerly the refcount was a count of the number of requests
for a given address, NOT a count of pointers to the object.]
|
|
|
|
| |
RFC 3678 (Source-specific Multicast API) brings to FreeBSD.
|
|
|
|
|
|
| |
- Close the new file objects created during socketpair() if the copyout of
the new file descriptors fails.
- Add a test to the socketpair regression test for this edge case.
|
|
|
|
| |
sys/kern/uipc_syscall.c.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
and had no chance to match it by the 2nd address precisely.
Otherwise the unclosed range would bogusly extend to the end
of stream.
Add a basic regression test for the bug fixed. (This change
also fixes the more complex case 5.3 from `multitest.t'.)
Compared with: SUN and GNU seds
Tested by: regression tests
MFC after: 1 week
|
|
|
|
|
|
| |
in a more reasonable way than BSD sed does: they properly
close the range even if we branched over its end. No doubt,
the range `1,5' should not match lines from 9 through 14.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
them are related to the `c' function's need to know if we are at
the actual end of the address range. (It must print the text not
earlier than the whole pattern space was deleted.) It appears the
only sed function with this requirement.
There is `lastaddr' set by applies(), which is to notify the `c'
function, but it can't always help because it's false when we are
hitting the end of file early. There is also a bug in applies()
due to which `lastaddr' isn't set to true on degenerate ranges such
as `$,$' or `N,$' if N appears the last line number.
Handling early EOF condition in applies() could look more logical,
but it would effectively revert sed to the unreasonable behaviour
rev. 1.26 of main.c fought against, as it would require lastline()
be called for each line within each address range. So it's better
to call lastline() only if needed by the `c' function.
Together with this change to sed go regression tests for the bugs
fixed (c1-c3). A basic test of `c' (c0) is also added as it helped
me to spot my own error.
Discussed with: dds
Tested by: the regression tests
MFC after: 1 week
|
|
|
|
| |
Added tests for aes-ctr which were not present before.
|
|
|
|
|
|
| |
networks involved, as opposed to two hosts on one network.
MFC after: 1 week
|
|
|
|
|
| |
Add comments to the test for IPv4 with IPsec.
MFC after: 1 week
|
|
|
|
| |
the regression suite.
|
| |
|
|
|
|
| |
testing framework and protocol.
|
|
|
|
|
|
|
|
|
| |
I have verified these with GNU sed 4.1.5 (and in some cases with Solaris
sed) and they are identical, with the following exceptions:
5.3: The result is unspecified and BSD sed behaves differently.
6.3: GNU sed gets it wrong
7.1: GNU sed gets it wrong
7.8: BSD sed gets it wrong
|
|
|
|
|
| |
- Update platform-conditional tests to reflect current reality
- Fix conditional for test 7.8: it is the fault of BSD sed
|
|
|
|
| |
- Test 7.8 fails for GNU sed not BSD.
|
| |
|
| |
|
|
|
|
|
|
| |
GNU sed 4.1.5.
Almost all of the tests that were skipped for BSD or GNU sed
now appear to work.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
According to IEEE Std 1003.1, 2004 "Whenever the pattern space is
written to standard output or a named file, sed shall immediately
follow it with a <newline>."
An attempt at the same correction might have been made with r1.3,
which is however identical with r1.2.
|
| |
|
| |
|