RFC2326 specifies the attribute client_port as the RTP/RTCP port pair on
which the client has chosen to receive media data and control info;
however some clients (mostly STBs) embed the client_port value in the
destination attribute in the form of destination=<address:port> without
specifying the client_port attribute in the SETUP message.
To support such clients check if the destination attribute contains a
port value and use it as port value for the expected RTP connection.
Signed-off-by: Hans Dedecker <dedeckeh@gmail.com>
Changes:
- added folder /etc/netdata/customs-plugins.d
which is set in netdata.conf as 2nd plugin directory
Signed-off-by: Josef Schlehofer <pepe.schlehofer@gmail.com>
Simpler and easier to bump the version in the future.
Signed-off-by: Rosen Penev <rosenp@gmail.com>
Signed-off-by: Jonathan McCrohan <jmccrohan@gmail.com>
Since https://git.openwrt.org/d0e0b7049f88774e67c3d5ad6b573f7070e5f900,
OpenWrt SDKs ship the appropriate sources for building usbip userspace
packages, so special nonshared handling is not required anymore.
Sucessfully tested by compiling usbip utilities for various architectures
using self built SDKs after applying the change linked above.
Signed-off-by: Jo-Philipp Wich <jo@mein.io>
Currently uscan fails on this as it tries to look for a download link in the
wrong location. Switching it to a GitHub tarball will probably fix it.
Signed-off-by: Rosen Penev <rosenp@gmail.com>
The package seems to link to -lpam even when using --without-pam. Set
ac_cv_search_pam_end=no to avoid it.
Signed-off-by: Eneas U de Queiroz <cote2004-github@yahoo.com>
Unbound struggles with boot ifup, so procd triggers changed to push
outside of this noise. Unbound has run in /var/lib/unbound/, so chroot
(jail) protects /etc/, and it can save flash wear. Compiled defaults
reflect this now, so Unbound tools are easier run on the command line.
Signed-off-by: Eric Luehrsen <ericluehrsen@gmail.com>
In the description point to installation guide on OpenWrt Wiki to
make it easier for new users to find and to understand how to use
gitolite on OpenWrt.
Signed-off-by: Daniel F. Dickinson <cshored@thecshore.com>
The user defined in order to own and admin gitolite directories needs
to not be expired else logins such SSH access will not be allowed for
that user. So we unexpire user git by default.
Signed-off-by: Daniel F. Dickinson <cshored@thecshore.com>
Practicalities of life have intervened and I am no longer able to
dedicate the time required to look after this package.
Signed-off-by: Kevin Darbyshire-Bryant <ldir@darbyshire-bryant.me.uk>