rtpengine

1006 Commits

293 Branches

2.5 GiB

Tree: 05302c265f

Commit Graph

Author	SHA1	Message	Date
Richard Fuchs	6d3865b971	Mass update - manual merge of rfuchs/socket-rework branch This brings master up to date with branch `rfuchs/socket-rework` at commit `b1bcc096b7`. The branches have diverged too much for a proper merge, so this is a manual (squashed) merge. The old master before this merge can be found in branch `old-master-before-socket-rework` (commit `82199216b2`). This is a complete rewrite of all socket handling routines. The most important functional change is that sockets aren't indiscriminately bound to INADDR_ANY (or rather in6addr_any), but instead are always bound to their respective local interface address and with the correct address family. Side effects of this are that in multi-homed environments, multiple sockets must be opened (one per interface address and family) which must be taken into account when considering RLIMIT_NOFILE values. As a benefit, this change allows rtpengine to utilize the full UDP port space per interface address, instead of just one port space per machine. The socket abstraction also makes it possible to support RTP over TCP in the future. Change-Id: If6cf4f42136229490186d2d2482fb4fc140c2b53	10 years ago

Author

SHA1

Message

Date

Richard Fuchs

6d3865b971

Mass update - manual merge of rfuchs/socket-rework branch

This brings master up to date with branch `rfuchs/socket-rework` at
commit `b1bcc096b7`. The branches have diverged too much for a proper
merge, so this is a manual (squashed) merge.

The old master before this merge can be found in branch
`old-master-before-socket-rework` (commit `82199216b2`).

This is a complete rewrite of all socket handling routines. The most
important functional change is that sockets aren't indiscriminately
bound to INADDR_ANY (or rather in6addr_any), but instead are always
bound to their respective local interface address and with the correct
address family.

Side effects of this are that in multi-homed environments, multiple
sockets must be opened (one per interface address and family) which must
be taken into account when considering RLIMIT_NOFILE values. As a
benefit, this change allows rtpengine to utilize the full UDP port space
per interface address, instead of just one port space per machine.

The socket abstraction also makes it possible to support RTP over TCP in
the future.

Change-Id: If6cf4f42136229490186d2d2482fb4fc140c2b53

10 years ago

1 Commits (05302c265f7787890728abf367fb09218cb31218)