- libblkid is now a hard dependency
- Don't set configure options matching the default
- Enable LTO
- Disable debug asserts at configure stage, drop the patch
- Compile with target optimizations instead of -O2
- Update package URL
Signed-off-by: Aleksey Vasilenko <aleksey.vasilenko@gmail.com>
Upstream repository[1] is now read-only.
It seems daemonlogger is no longer maintained.
[1] https://github.com/Cisco-Talos/Daemonlogger
Signed-off-by: Yanase Yuki <dev@zpc.st>
go1.22.7(released 2024-09-05)includes security fixes to the encoding/gob,
go/build/constraint, and go/parser packages,
as well as bug fixes to the fix command and the runtime.
Signed-off-by: Milinda Brantini <C_A_T_T_E_R_Y@outlook.com>
Bug fixes:
efahl/owut@6564aa2 owut: handle non-JSON responses
Enhancements:
efahl/owut@e0a0c49 owut: add age to build time output
efahl/owut@d811a24 examples: compress the manifest
Signed-off-by: Eric Fahlgren <ericfahlgren@gmail.com>
Makefile:
* remove pbr-iptables flavour
Init-script:
* improve detection of wireguard server and client instances
* integrate wg_server_and_client into init script
* remove traffic_killswitch() and trap() and related options/code
* remove internal nft_file_support variable as fw4 nft file is the only running mode
* improve debug() and is_supported_interface() functions
* improve detection of incompatible user script files
* double-quote some strings due to shellcheck errors
* flush ip rules from pbr tables instead of deleting last one
Other files:
* remove /usr/share/pbr/pbr.user.wg_server_and_client as obsolete
* remove references to the file above in config on update thru uci-defaults
* minor updates to netifd uci-defaults script
Signed-off-by: Stan Grishin <stangri@melmac.ca>
Adjust openssh's versioning to be compatible with apk:
8.9p1-r2 --> 8.9_p1-r2
"_p" is an allowed semantic suffix, so use that.
(Alternative might have been 8.9.1-r2)
Signed-off-by: Hannu Nyman <hannu.nyman@iki.fi>
The commit adds options for static mapping, which is essential for
464xlat(clat) usage. But be noted that routes and firewall rules have
to be configured manually, for now.
To use tayga as clat/nat46:
0. specify $ipv4_addr, $prefix, $map_{ipv4,ipv6} properly, and
set $noroutes to 1 to prevent creating routes for nat64
1. add custom IPv4 routes to tayga, possibly with a reasonable metric
for default route
2. add a SNAT firewall rule for processing IPv4 traffic destined for
tayga
3. add firewall rules to allow FORWARD traffic between tayga and WAN6
4. add a $map_ipv6 route to tayga for guiding return traffic
Signed-off-by: Hung-I Wang <whygowe@gmail.com>
Sometimes the wan connection needs time to be established (e.g. cold
boot after power loss) and the service may crash as the internet is
yet available. Add a trigger to reload the service once the wan
interface is up.
Signed-off-by: Tianling Shen <cnsztl@immortalwrt.org>