| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
| |
socket options. This includes managing the correspoing stat counters.
Add the SCTP_DETAILED_STR_STATS kernel option to control per policy
counters on every stream. The default is off and only an aggregated
counter is available. This is sufficient for the RTCWeb usecase.
MFC after: 1 week
|
|
|
|
| |
exposed to userland. Therefore no MFC.
|
|
|
|
|
|
|
|
|
| |
* Remove non working code related to SHA224.
* Remove support for non-standardised HMAC-IDs using SHA384 and SHA512.
* Prefer SHA256 over SHA1.
* Minor cleanup.
MFC after: 2 weeks
|
|
|
|
|
|
| |
Bump __FreeBSD_version to 1000048 since the
modified structure is user visible and used
by netstat, for example.
|
|
|
|
| |
FreeBSD code base.
|
|
|
|
|
|
| |
Submitted by: kevlo
Reviewed by: md5(1)
MFC after: 2 months
|
|
|
|
|
|
|
|
| |
on INET and/or INET6 to be defined and in-tune with how the kernel
was compiled.
MFC after: 3 days
Discussed with: rrs
|
|
|
|
| |
MFC after: 3 days
|
|
|
|
| |
MFC after: 3 days
|
|
|
|
| |
MFC after: 3 days
|
|
|
|
|
|
| |
as required by RFC 6458.
MFC after: 3 days
|
|
|
|
| |
MFC after: 3 days
|
|
|
|
|
|
| |
as specified in RFC 6525.
MFC after: 3 days
|
|
|
|
| |
MFC after: 3 days
|
|
|
|
|
|
| |
found by Irene Ruengeler.
MFC after: 1 week
|
|
|
|
|
|
| |
Reported by Irene Ruengeler.
MFC after: 3 days
|
|
|
|
|
|
|
| |
for backwards compatibility.
Spotted by Irene Ruengeler.
MFC after: 3 days
|
| |
|
|
|
|
|
|
| |
compliant to RFC6525.
MFC after: 1 month
|
|
|
|
|
|
| |
While there, fix some whitespace issues.
MFC after: 3 months.
|
|
|
|
|
|
| |
like in all other structures. This avoids alignment problems.
MFC after: 3 months.
|
|
|
|
|
|
| |
like in all other structures. This avoids alignment problems.
MFC after: 3 days.
|
|
|
|
|
|
|
| |
Retire the the now unused sctp_udp_tunneling_for_client_enable
sysctl variable.
MFC after: 3 months.
|
|
|
|
|
|
|
|
| |
socket option. Backwards compatibility is provided by still
supporting the spp_ipv4_tos field.
Approved by: re@
MFC after: 2 months.
|
|
|
|
|
|
|
|
|
|
|
| |
* Decouple the path supervision using a separate HB timer per path.
* Add support for potentially failed state.
* Bring back RTO.min to 1 second.
* Accept packets on IP-addresses already announced via an ASCONF
* While there: do some cleanups.
Approved by: re@
MFC after: 2 months.
|
|
|
|
|
|
| |
which is used the the SCTP_AUTH_KEY socket option.
MFC after: 1 month.
|
|
|
|
|
|
| |
This constant is defined in the socket API ID.
MFC after: 2 months.
|
|
|
|
|
|
|
| |
Fix the SCTP_DEFAULT_SNDINFO socket option: Don't clear the
PR SCTP policy when setting sinfo_flags.
MFC after: 1 month.
|
|
|
|
|
|
|
| |
* Add support for SCTP_SENDV_NOINFO.
* Improve the error handling of sctp_sendv() and sctp_recv().
MFC after: 1 month
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In particular add support for:
* SCTP_SNDINFO, SCTP_PRINFO, SCTP_AUTHINFO, SCTP_DSTADDRV4, and
SCTP_DSTADDRV6 cmsgs.
* SCTP_NXTINFO and SCTP_RCVINFO cmgs.
* SCTP_EVENT, SCTP_RECVRCVINFO, SCTP_RECVNXTINFO and SCTP_DEFAULT_SNDINFO
socket option.
* Special association ids (SCTP_FUTURE_ASSOC, ...)
* sctp_recvv() and sctp_sendv() functions.
MFC after: 1 month.
|
|
|
|
|
|
|
|
|
|
|
| |
1) Add four new points that allow you to get more information
to cc algo's
2) Fix the case where user changes module on a existing TCB, in
such a case, the initialization module needs to be called on all nets.
3) Move htcp_cc structure to a union that other modules can use.
4) Add 5th point for get/set socket options for cc_module specific options
MFC after: 2 months
|
|
|
|
|
| |
2) Mass update to all copyrights.
MFC after: 3 Months
|
|
|
|
|
|
|
|
|
|
| |
sends were being accounted for. The
counting was such that we counted only
when we queued a chunk, not when we sent it.
Now keep an additional counter for queuing and
one for sending.
MFC after: 1 week
|
|
|
|
|
|
| |
This work is based on a patch received from Robin Seggelmann.
MFC after: 3 months.
|
|
|
|
|
|
| |
state's in destination (i.e. ACTIVE/INACTIVE/UNCONFIRMED)
MFC after: 1 week
|
|
|
|
| |
MFC after: 3 months.
|
|
|
|
|
|
| |
groundwork for future dtrace points (rwnd flightsize etc).
MFC after: 2 months
|
|
|
|
|
|
| |
of an association.
MFC after: 3 days.
|
|
|
|
|
| |
PR: bin/148894
Submitted by: olgeni
|
|
|
|
|
|
| |
sendinfo for SCTP send calls.
MFC after: 4 weeks.
|
|
|
|
|
|
| |
may be useful since it gets rid of atomics but I want it to
remain an option until I can do further testing on if it really
speeds things up.
|
|
|
|
|
| |
Obtained from: Bruce Cran
MFC after: 1 week
|
|
|
|
|
| |
values to match those in linux and the I-D
just released to the IETF.
|
|
|
|
|
|
| |
Get rid of unused MD5 code.
MFC after: 1 week
|
|
|
|
|
|
| |
in the official speciication of the SCTP socket API.
Approved by:re, rrs (mentor)
|
|
|
|
|
|
|
| |
socket-api draft. Two fields were uint32_t when they
should have been uint16_t.
Reported by Jonathan Leighton at U-del.
|
| |
|
|
|
|
|
|
| |
help us be able to keep ABI compatibility between
8 and 9.
MFC after: Never
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- PR-SCTP had major issues when skipping through a multi-part message.
o Did not look at socket buffer.
o Did not properly handle the reassmebly queue.
o The MARKED segments could interfere and un-skip a chunk causing
a problem with the proper FWD-TSN.
o No FR of FWD-TSN's was being done.
- NR-Sack code was basically disabled. It needed fixes that
never got into the real code.
- CMT code had issues when the two paths were NOT the same b/w. We
found a few small bugs, but also the critcal one here was not
dividing the rwnd amongst the paths.
Obtained from: Michael Tuexen and myself at the IETF hack-fest ;-)
|
|
|
|
|
|
| |
testing..
MFC after: 1 month
|