# HELP realtek_poe_switch_info information about the poe controller
# TYPE realtek_poe_switch_info gauge
realtek_poe_switch_info{mcu="ST Micro ST32F100 Microcontroller",firmware="v22.4"} 1
# HELP realtek_poe_switch_budget_watts overall power budget
# TYPE realtek_poe_switch_budget_watts gauge
realtek_poe_switch_budget_watts 77
# HELP realtek_poe_switch_consumption_watts overall power consumption
# TYPE realtek_poe_switch_consumption_watts gauge
realtek_poe_switch_consumption_watts 5
# HELP realtek_poe_port_priority poe priority of port
# TYPE realtek_poe_port_priority gauge
realtek_poe_port_priority{device="lan1"} 1
realtek_poe_port_priority{device="lan2"} 1
[...]
# HELP realtek_poe_port_consumption_watts per port power consumption
# TYPE realtek_poe_port_consumption_watts gauge
realtek_poe_port_consumption_watts{device="lan1"} 0
realtek_poe_port_consumption_watts{device="lan2"} 0
[...]
# HELP realtek_poe_port_state per port poe state
# TYPE realtek_poe_port_state gauge
realtek_poe_port_state{device="lan1",state="Disabled"} 0
realtek_poe_port_state{device="lan1",state="Searching"} 1
[...]
(states: Disabled, Searching, Delivering power, Fault, Other fault, Requesting power)
# HELP realtek_poe_port_mode per port poe mode
# TYPE realtek_poe_port_mode gauge
realtek_poe_port_mode{device="lan1",mode="PoE"} 0
realtek_poe_port_mode{device="lan1",mode="PoE+"} 1
[...]
(modes: PoE, Legacy, pre-PoE+, PoE+)
Nick Hainke [Sun, 7 Aug 2022 07:18:17 +0000 (09:18 +0200)]
gnutls: update to 3.7.7
- libgnutls: Fixed double free during verification of pkcs7 signatures.
Reported by Jaak Ristioja (#1383). [GNUTLS-SA-2022-07-07, CVSS: medium]
[CVE-2022-2509]
- libgnutls: gnutls_hkdf_expand now only accepts LENGTH argument less than or
equal to 255 times hash digest size, to comply with RFC 5869 2.3.
- libgnutls: Length limit for TLS PSK usernames has been increased
from 128 to 65535 characters (#1323).
- libgnutls: AES-GCM encryption function now limits plaintext
length to 2^39-256 bits, according to SP800-38D 5.2.1.1.
- libgnutls: New block cipher functions have been added to transparently
handle padding. gnutls_cipher_encrypt3 and gnutls_cipher_decrypt3 can be
used in combination of GNUTLS_CIPHER_PADDING_PKCS7 flag to automatically
add/remove padding if the length of the original plaintext is not a multiple
of the block size.
- libgnutls: New function for manual FIPS self-testing.
API and ABI modifications:
- gnutls_fips140_run_self_tests: New function
- gnutls_cipher_encrypt3: New function
- gnutls_cipher_decrypt3: New function
- gnutls_cipher_padding_flags_t: New enum
luajit: patch: PPC/e500 SPE: use soft float instead of failing
makes LuaJit builds for mpc85xx targets with SPE ISA extension
enabled possible
Quoting inner commit message:
This allows building LuaJit for systems with Power ISA SPE
extension[^1] support by using soft float on LuaJit side.
While e500 CPU cores support SPE instruction set extension
allowing them to perform floating point arithmetic natively,
this isn't required. They can function with software floating
point to integer arithmetic translation as well,
just like FPU-less PowerPC CPUs without SPE support.
Therefore I see no need to prevent them from running LuaJit
explicitly.
realtek-poe: Add package to control PoE for Realtek 838x devices
The realtek-poe package is used to configure the Power-over-Ethernet
controller found on Realtex 838x based switches. On many such
switches, the PoE doesn't work without this package.
Signed-off-by: Stijn Segers <redacted> Signed-off-by: Alexandru Gagniuc <redacted>
- add package apinger-rrd for RRD graphs
- add RPC to get an overview and update graphs
- fix interface hotplug to restart apinger instance
- add patch to split alarms list in the status
Sebastian Kemper [Sat, 23 Jul 2022 14:43:28 +0000 (16:43 +0200)]
erlang: workaround LibreSSL-3.5.0 compat issues
Cherry-pick four upstream commits that prevent building of
otp_test_engine when LibreSSL-3.5.0 is used.
Since OpenWrt bumped LibreSSL to 3.5.3 the erlang host builds fail to
complete.
CC ../priv/obj/x86_64-pc-linux-gnu/otp_test_engine.o
otp_test_engine.c: In function 'test_engine_md5_init':
otp_test_engine.c:144:34: error: dereferencing pointer to incomplete type 'EVP_MD_CTX' {aka 'struct env_md_ctx_st'}
#define data(ctx) ((MD5_CTX *)ctx->md_data)
^~
The decision to switch the default to wolfSSL was taken because of
hostapd back from when curl was in base. Unfortunately, not only is
wolfSSL bigger but it has also been causing issues recently. There's
also no relation between hostapd and curl.
Javier Marcet [Thu, 21 Jul 2022 14:35:14 +0000 (16:35 +0200)]
docker-compose: Update to version 2.7.0
What's Changed:
- Enhancements:
- add support of environment secret during build step by @glours
- Fixes:
- networks: prevent issues due to duplicate names by @milas
- Use appropriate dependency condition for one-shot containers when
running compose up --wait by @laurazard
- Fix environment variable expansion by @ulyssessouza in
compose-spec/compose-go#276
- Validate depended-on services exist in consistency check by
@laurazard in compose-spec/compose-go#281
- Fix hash usage in environment values by @ulyssessouza in
compose-spec/compose-go#283
- build: respect dependency order for classic builder by @milas
- fix: panic caused by empty string argument by @nicksieger
- (re)start should not impact one-off containers by @ndeloof
- Fix issue with close networks name on up and down command by
@glours
- keep the container reference when volumes_from target a container
and not a service by @glours
- build.go: initialize CustomLabels map if nil by @paroque28
Stijn Tintel [Sun, 9 Jan 2022 16:13:15 +0000 (18:13 +0200)]
glib2: disable fortify source
The glib2 package fails to build when CONFIG_PKG_FORTIFY_SOURCE_1 or
CONFIG_PKG_FORTIFY_SOURCE_2 is enabled in the OpenWrt config:
In file included from ../glib/libcharset/localcharset.c:28:
/home/stijn/Development/OpenWrt/openwrt/staging_dir/toolchain-powerpc64_e5500_gcc-11.2.0_musl/include/fortify/stdio.h: In function 'snprintf':
/home/stijn/Development/OpenWrt/openwrt/staging_dir/toolchain-powerpc64_e5500_gcc-11.2.0_musl/include/fortify/stdio.h:101:9: error: format not a string literal, argument types not checked [-Werror=format-nonliteral]
101 | return __orig_snprintf(__s, __n, __f, __builtin_va_arg_pack());
| ^~~~~~
/home/stijn/Development/OpenWrt/openwrt/staging_dir/toolchain-powerpc64_e5500_gcc-11.2.0_musl/include/fortify/stdio.h: In function 'sprintf':
/home/stijn/Development/OpenWrt/openwrt/staging_dir/toolchain-powerpc64_e5500_gcc-11.2.0_musl/include/fortify/stdio.h:110:17: error: format not a string literal, argument types not checked [-Werror=format-nonliteral]
110 | __r = __orig_snprintf(__s, __b, __f, __builtin_va_arg_pack());
| ^~~
/home/stijn/Development/OpenWrt/openwrt/staging_dir/toolchain-powerpc64_e5500_gcc-11.2.0_musl/include/fortify/stdio.h:114:17: error: format not a string literal, argument types not checked [-Werror=format-nonliteral]
114 | __r = __orig_sprintf(__s, __f, __builtin_va_arg_pack());
| ^~~
Disable fortify source for the package as a workaround.
This removes the guard "CONFIG_BUILD_PATENTED" for the ffmpeg build
feature for mpd-full. ffmpeg was already unconditionally registered as a
dependency (at line 51).
The ffmpeg package already handles whether or not to include patented
codecs internally using the same config flag, so guarding its use as a
dependency here does not appear necessary anymore.
(For reference: guard "BUILD_PATENTED" was introduced in 44eb12f for
ffmpeg, then partially removed by 326c973).
Since the OpenWrt's stub libiconv implementation is now gone,
we can build against musl's internal one or the external libiconv
implementation.
This needs minor adjustements in the makefile to allow PHPs build
to choose the right path when cross-compiling.
git.99rst.org / openwrt-packages.git / log