OpenWrt 19.07.4 service release
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, The OpenWrt community is proud to announce the newest service release in the 19.07 stable series: OpenWrt 19.07.4. It focuses on stability and device support. Selected highlights of this service release are: * fix regression in libubox causing some services to fail to start * fix regression in the LuCI web interface: the menu was not showing newly installed opkg packages * fix a bug in musl that could crash applications in rare circumstances. Fastd, a VPN daemon, seems to be particularly affected by this bug * fix support for several devices that failed to boot * many other fixes and improvements to device support * update core components (linux kernel, mac80211, ath10k-ct-firmware) Full release notes and upgrade instructions are available at https://openwrt.org/releases/19.07/notes-19.07.4 In particular, make sure to read the regressions and known issues before upgrading: https://openwrt.org/releases/19.07/notes-19.07.4#regressions For a very detailed list of all changes since 19.07.3, refer to https://openwrt.org/releases/19.07/changelog-19.07.4 We now have a forum topic where you can report your upgrading experience: https://forum.openwrt.org/t/openwrt-19-07-4-service-release/73829 - --- To stay informed of new OpenWrt releases and security advisories, there are new channels available: * a low-volume mailing list for important announcements: https://lists.openwrt.org/mailman/listinfo/openwrt-announce * a dedicated "announcements" section in the forum: https://forum.openwrt.org/c/announcements/14 * other announcement channels (such as RSS feeds) might be added in the future, they will be listed at https://openwrt.org/contact - --- For latest information about the 19.07 series, refer to the wiki at: https://openwrt.org/releases/19.07/ To download a OpenWrt 19.07.4 firmware image for your device, head to the Table of Hardware: https://openwrt.org/toh/start Or navigate directly in the list of firmware images: https://downloads.openwrt.org/releases/19.07.4/targets/ As always, a big thank you goes to all our active package maintainers, testers, documenters, and supporters. Have fun! The OpenWrt Community -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEjVflzZuxNlVFbt5QvgHsIqBOLkYFAl9Zyn0ACgkQvgHsIqBO LkZQ/g/+LwZqKZuw/9S64ZpLT5ZDJcYnqv9DkoEVlg85YteGmZOMs+M/4BTUuxRc 4wl+nJFmMbXrV8HRG97tHa3ZCVhjCS/yka/EATdn2ixLqe2VSffJYdq9wRmWk3bN SlDT0ihmWEk5ZM1OW8KKMAn4l3Z0rR1vmUI6il6ft69AfBpxJClgD6pW2+aMn3pt YsTu+RY1VquvKEasLR8kZ5TRvxflbxWKHe/SITIWpEukdiNXQp3DBkMcdKrc76jX rJY78N/kXzlZRBywSNWhNjAl3hZrYMRzy4PqF84lwSXIRVZG8QcUdAqWK496oqvj FSm8LuqsdLBjJ5EeX1BnroYtKAEWkNqx/kfe8IOd+BwWUE3KsaoPlkaXmXk4qCaZ wNS1dD6oHHIE2BFYDQ/s+hlVhK13Z7IuyeMM73W1bOeuRygXMJ/W61WOfeSYFTZT PDZl4imgk/iEO4qSGj/6XXcYFMbI7+3/9rkdmxz1JHQT3EIDqgePgt6KhlHSvNbn vY8iihd1qsVC8qArdQmpWN1NQV/fiW4B9tg6nPfaeM8ymE4Hpo9EaKv+3PxmMwhX iZj8MJw1eLpoAOiLfCIPyj6yBk3sCqC0OJNLlFtZv4fLhAafv6TRyoPH34VUwYJ/ o1AJUpx0U9EMbh/wOuhJd5NzPqGle41KrgHLltbSZBHa6A+X/vU= =V3bj -END PGP SIGNATURE- ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[PATCH] libcxxabi: fix compilation under the SDK
Under the SDK, the path for base packages is different. Signed-off-by: Rosen Penev --- package/libs/libcxxabi/Makefile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/package/libs/libcxxabi/Makefile b/package/libs/libcxxabi/Makefile index 90547561b2..e663fafc8e 100644 --- a/package/libs/libcxxabi/Makefile +++ b/package/libs/libcxxabi/Makefile @@ -58,7 +58,7 @@ TARGET_CXXFLAGS += -flto TARGET_LDFLAGS += -Wl,--gc-sections,--as-needed define Build/Prepare - $(MAKE) -C $(TOPDIR)/package/libs/libcxx prepare + $(MAKE) -C $(TOPDIR)/$(if $(CONFIG_IN_SDK),feeds/base/)package/libs/libcxx prepare $(call Build/Prepare/Default) endef -- 2.17.1 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [PATCHv3] mdadm: revised mdadm config & init logic
Ping. Is there any chance of this being merged? On Wed, Jan 22, 2020 at 6:57 PM Rosen Penev wrote: > > From: Joseph Tingiris > > This is a significant revision of /etc/init.d/mdadm. It adds new > features, support for new configuration options, safer error > handling, (configurable) verbose output, and contains multiple bug > fixes. > > Most notably, mdadm was being started with the --config flag and > that prevented it from using its built in Auto Assembly features. > Users were required to put a correct uuid in /etc/config/mdadm. > > The new default startup mode is now to automatically assemble all > RAID arrays attached to the machine using device scans, rather than > configuation options. > > A new UCI section, config mdadm global, was added with new options that > are supported by the accompanying /etc/init.d/mdadm. Documentation for all > new (and previous) options was added as well. See the > /etc/config/mdadmin or mdadm.init file itself for more details. > > Additionally, a new stateful 'auto' feature was added that functions > similarly to the stateless Auto Assembly feature. The benefits of > stateful auto assembly are to support features that mdadm 4.0 will only > read from a configuration file, such as setting the MAILFROM value. The > new mdadm_conf_auto() function will also aid users in troubleshooting. > When verbose is turned on it provides tips and better visibility for what's > actually happening. > > Backward compatibility was retained. Stateful UCI only configurations are > supported. All previously existing configurations will work in this mode. > However, these users will now have to explicitly turn it on. > > A new reload_service() function was added to prevent reloads from > stopping mdadm. Reloads will now be ignored, though the stage is set for > reloads to trigger scans for new devices. Explicit restarts still work as > expected. > > The start_service() function was enhanced to query new UCI mdadm.global > options: alert_program, config, email, email_from, monitor_frequency, > and verbose. Each option is documented in /etc/mdadm/config (config.init) and > some additional code comments were added. > > Finally, error handling and verbose output was enhanced. Users will > know what's going on (if verbose is turned on). > > Strict reliance on a shell global ($CONF) was removed and replaced with a > single global ($TMP_FILE) that's for development convenience. When/if a > config > file is not specified in the UCI config, it will fall back to using $TMP_FILE > as the > configuration file. > > Incremented PKG_RELEASE from 1 to 2 > > Signed-off-by: Joseph Tingiris > (rebased and ran through shellcheck) > Signed-off-by: Rosen Penev > --- > v3: Simplified several sections > v2: Rebased after sysmacro patches > package/utils/mdadm/Makefile | 2 +- > package/utils/mdadm/files/mdadm.config | 162 +++- > package/utils/mdadm/files/mdadm.init | 552 ++--- > 3 files changed, 643 insertions(+), 73 deletions(-) > > diff --git a/package/utils/mdadm/Makefile b/package/utils/mdadm/Makefile > index f20a58b704..d5ea91eeed 100644 > --- a/package/utils/mdadm/Makefile > +++ b/package/utils/mdadm/Makefile > @@ -9,7 +9,7 @@ include $(TOPDIR)/rules.mk > > PKG_NAME:=mdadm > PKG_VERSION:=4.1 > -PKG_RELEASE:=2 > +PKG_RELEASE:=3 > > PKG_SOURCE:=$(PKG_NAME)-$(PKG_VERSION).tar.xz > PKG_SOURCE_URL:=@KERNEL/linux/utils/raid/mdadm > diff --git a/package/utils/mdadm/files/mdadm.config > b/package/utils/mdadm/files/mdadm.config > index 50afbc2ab6..0c78c964a8 100644 > --- a/package/utils/mdadm/files/mdadm.config > +++ b/package/utils/mdadm/files/mdadm.config > @@ -1,18 +1,154 @@ > -config mdadm > +# > +# The mdadm 'global' section is for options that apply to all sections. > +# > + > +config mdadm global > + > + # > + # option 'alert_program' values may be a path to a valid, executable > binary. > + # > + # The default 'alert_program' is not set. > + # > + # When mdadm detects an event it will execute this program with 3 > arguments, see https://linux.die.net/man/8/mdadm > + # $1 = will be the event > + # $2 = will be the meta device > + # $3 = may be a related component (if one exists) > + # > + # * alert_program runs independently from sendmail. > + # * If both options alert_program and email are set, and both work, > then an email and a > + # custom alert will be generated. > + # * no alert program is included in mdadm 4.0-4. > + # > + # Lots of possibilities exist, i.e. scripts for netdata, slack, etc. > + # > + #option alert_program /usr/sbin/mdadm_alerts > + > + > + # > + # option 'config' values may be one of the following. > + # > + # The default 'config' is none (stateless auto assembly). > + # > + # auto - stateful, dynamically generated mdadm.conf via > block info, > + #
RE: [PATCH v4] gemini: Bring up DSA switches
Hi, > -Original Message- > From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org] > On Behalf Of Linus Walleij > Sent: Mittwoch, 9. September 2020 23:10 > To: Roman Yeryomin ; Sebastian Luft > ; Hans Ulli Kroll ; > Hauke Mehrtens ; Christian Lamparter > > Cc: Pawel Dembicki ; Linus Walleij > ; Florian Fainelli ; openwrt- > de...@lists.openwrt.org > Subject: [PATCH v4] gemini: Bring up DSA switches > > First group the interfaces on the DSA switch into the right LAN/WAN groups. > Tested successfully on the D-Link DIR-685 with the RTL8366RB DSA switch. > > The RTL8366RB is DSA custom tagged and now handled by the kernel tag > parser. (Backported.) > > The Vitesse switches are not capable of supporting DSA per-port tagging. We > suspect they must be handled using some custom VLAN set-up. > > Cc: Pawel Dembicki > Signed-off-by: Linus Walleij > --- > ChangeLog v3->v4: > - Rebased patch. > - This now works as expected on the D-Link DIR-685 > with the upstream DSA patches. > - For the Vitesse routers > I don't know what to do, but it should be "something > like this" eventually. I think it looks better with > this script than without it actually. > ChangeLog v2->v3: > - Actually remove the eth1 from the lan list as well on > the Gemini SL93512r. > ChangeLog v1->v2: > - Remove the eth1 from the LAN bridge in both the > Vitesse switch devices, instead bring up each ethernet > master interface independently with "none" protocol. > --- > .../gemini/base-files/etc/board.d/02_network | 27 > +++ > 1 file changed, 27 insertions(+) > create mode 100755 target/linux/gemini/base- > files/etc/board.d/02_network > > diff --git a/target/linux/gemini/base-files/etc/board.d/02_network > b/target/linux/gemini/base-files/etc/board.d/02_network > new file mode 100755 > index ..e2fce015fb44 > --- /dev/null > +++ b/target/linux/gemini/base-files/etc/board.d/02_network > @@ -0,0 +1,27 @@ > +#!/bin/sh > + > +. /lib/functions/uci-defaults.sh > + > +board_config_update > + > +case "$(board_name)" in > +storlink,gemini324) Devices should be sorted alphabetically here. Best Adrian > + # These are all connected to eth1 thru VSC7385 > + ucidef_set_interface "eth" ifname "eth1" protocol "none" > + ucidef_set_interfaces_lan_wan "lan1 lan2 lan3 lan4" "eth0" > + ;; > +itian,sq201) > + # These are all connected to eth1 thru VSC7395 > + ucidef_set_interface "eth" ifname "eth1" protocol "none" > + ucidef_set_interfaces_lan_wan "lan1 lan2 lan3 lan4" "eth0" > + ;; > +dlink,dir-685) > + # These are all connected to eth0 thru RTL8366RB > + ucidef_set_interface "eth" ifname "eth0" protocol "none" > + ucidef_set_interfaces_lan_wan "lan0 lan1 lan2 lan3" "wan" > + ;; > +esac > + > +board_config_flush > + > +exit 0 > -- > 2.26.2 > > > ___ > openwrt-devel mailing list > openwrt-devel@lists.openwrt.org > https://lists.openwrt.org/mailman/listinfo/openwrt-devel openpgp-digital-signature.asc Description: PGP signature ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[PATCH v4] gemini: Bring up DSA switches
First group the interfaces on the DSA switch into the right LAN/WAN groups. Tested successfully on the D-Link DIR-685 with the RTL8366RB DSA switch. The RTL8366RB is DSA custom tagged and now handled by the kernel tag parser. (Backported.) The Vitesse switches are not capable of supporting DSA per-port tagging. We suspect they must be handled using some custom VLAN set-up. Cc: Pawel Dembicki Signed-off-by: Linus Walleij --- ChangeLog v3->v4: - Rebased patch. - This now works as expected on the D-Link DIR-685 with the upstream DSA patches. - For the Vitesse routers I don't know what to do, but it should be "something like this" eventually. I think it looks better with this script than without it actually. ChangeLog v2->v3: - Actually remove the eth1 from the lan list as well on the Gemini SL93512r. ChangeLog v1->v2: - Remove the eth1 from the LAN bridge in both the Vitesse switch devices, instead bring up each ethernet master interface independently with "none" protocol. --- .../gemini/base-files/etc/board.d/02_network | 27 +++ 1 file changed, 27 insertions(+) create mode 100755 target/linux/gemini/base-files/etc/board.d/02_network diff --git a/target/linux/gemini/base-files/etc/board.d/02_network b/target/linux/gemini/base-files/etc/board.d/02_network new file mode 100755 index ..e2fce015fb44 --- /dev/null +++ b/target/linux/gemini/base-files/etc/board.d/02_network @@ -0,0 +1,27 @@ +#!/bin/sh + +. /lib/functions/uci-defaults.sh + +board_config_update + +case "$(board_name)" in +storlink,gemini324) + # These are all connected to eth1 thru VSC7385 + ucidef_set_interface "eth" ifname "eth1" protocol "none" + ucidef_set_interfaces_lan_wan "lan1 lan2 lan3 lan4" "eth0" + ;; +itian,sq201) + # These are all connected to eth1 thru VSC7395 + ucidef_set_interface "eth" ifname "eth1" protocol "none" + ucidef_set_interfaces_lan_wan "lan1 lan2 lan3 lan4" "eth0" + ;; +dlink,dir-685) + # These are all connected to eth0 thru RTL8366RB + ucidef_set_interface "eth" ifname "eth0" protocol "none" + ucidef_set_interfaces_lan_wan "lan0 lan1 lan2 lan3" "wan" + ;; +esac + +board_config_flush + +exit 0 -- 2.26.2 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[PATCH v2] hostapd: enable background scanning in wpa_supplicant_full
Activation of autoscanning enables a a wifi client to select the best accesspoint based on rssi. This feature is useful in case you have multiple access points in your range and you do not want to stick the client on the first one it connected to. Especially when used with 802.11r this allows seamless transition to the optimal accesspoints. Setting the config value bgscan to -65 will tell wpa_supplicant to try to connect to an access points with better rssi. Example config: config wifi-iface 'default_radio1' option device 'radio1' option mode 'sta' option ssid 'openwrt' option encryption 'psk2' option key 'mykey' option network 'wlan' option roam_rssi_threshold '-65' The ipk sizes for mipsel_24kc change like this: old: wpad-openssl_2020-06-08-5a8b3662-4_mipsel_24kc.ipk 550133 new: wpad-openssl_2020-06-08-5a8b3662-5_mipsel_24kc.ipk 551961 Signed-off-by: André Valentin --- package/network/services/hostapd/files/hostapd.sh | 7 +++ package/network/services/hostapd/files/wpa_supplicant-full.config | 6 +++--- package/network/services/hostapd/Makefile | 1 +- 3 files changed, 11 insertions(+), 4 deletions(-) diff --git a/package/network/services/hostapd/files/hostapd.sh b/package/network/services/hostapd/files/hostapd.sh index 88113cd7ce..85299234c2 100644 --- a/package/network/services/hostapd/files/hostapd.sh +++ b/package/network/services/hostapd/files/hostapd.sh @@ -272,6 +272,8 @@ hostapd_common_add_bss_config() { config_add_array operator_icon config_add_array hs20_conn_capab config_add_string osu_ssid hs20_wan_metrics hs20_operating_class hs20_t_c_filename hs20_t_c_timestamp + + config_add_string roam_rssi_threshold } hostapd_set_vlan_file() { @@ -1178,6 +1180,11 @@ wpa_supplicant_add_network() { [ -n "$bssid_blacklist" ] && append network_data "bssid_blacklist=$bssid_blacklist" "$N$T" [ -n "$bssid_whitelist" ] && append network_data "bssid_whitelist=$bssid_whitelist" "$N$T" + [ -n "$roam_rssi_threshold" ] && { + json_get_vars roam_rssi_threshold + append network_data "bgscan=\"simple:120:${roam_rssi_threshold}:600\"" "$N$T" + } + [ -n "$basic_rate" ] && { local br rate_list= for br in $basic_rate; do diff --git a/package/network/services/hostapd/files/wpa_supplicant-full.config b/package/network/services/hostapd/files/wpa_supplicant-full.config index 982f4d5534..d39ee74a8d 100644 --- a/package/network/services/hostapd/files/wpa_supplicant-full.config +++ b/package/network/services/hostapd/files/wpa_supplicant-full.config @@ -527,9 +527,9 @@ CONFIG_WNM=y # # Enabling directly a module will enable autoscan support. # For exponential module: -#CONFIG_AUTOSCAN_EXPONENTIAL=y +CONFIG_AUTOSCAN_EXPONENTIAL=y # For periodic module: -#CONFIG_AUTOSCAN_PERIODIC=y +CONFIG_AUTOSCAN_PERIODIC=y # Password (and passphrase, etc.) backend for external storage # These optional mechanisms can be used to add support for storing passwords @@ -600,7 +600,7 @@ CONFIG_IBSS_RSN=y # operations for roaming within an ESS (same SSID). See the bgscan parameter in # the wpa_supplicant.conf file for more details. # Periodic background scans based on signal strength -#CONFIG_BGSCAN_SIMPLE=y +CONFIG_BGSCAN_SIMPLE=y # Learn channels used by the network and try to avoid bgscans on other # channels (experimental) #CONFIG_BGSCAN_LEARN=y diff --git a/package/network/services/hostapd/Makefile b/package/network/services/hostapd/Makefile index 8f94dce782..8c264854d7 100644 --- a/package/network/services/hostapd/Makefile +++ b/package/network/services/hostapd/Makefile @@ -7,7 +7,7 @@ include $(TOPDIR)/rules.mk PKG_NAME:=hostapd -PKG_RELEASE:=5 +PKG_RELEASE:=6 PKG_SOURCE_URL:=http://w1.fi/hostap.git PKG_SOURCE_PROTO:=git ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[PATCH] hostapd: enable background scanning in wpa_supplicant_full
Activation of autoscanning enables a a wifi client to select the best accesspoint based on rssi. This feature is useful in case you have multiple access points in your range and you do not want to stick the client on the first one it connected to. Especially when used with 802.11r this allows seamless transition to the optimal accesspoints. Setting the config value bgscan to -65 will tell wpa_supplicant to try to connect to an access points with better rssi. Example config: config wifi-iface 'default_radio1' option device 'radio1' option mode 'sta' option ssid 'openwrt' option encryption 'psk2' option key 'mykey' option network 'wlan' option bgscan '-65' The ipk sizes for mipsel_24kc change like this: old: wpad-openssl_2020-06-08-5a8b3662-4_mipsel_24kc.ipk 550133 new: wpad-openssl_2020-06-08-5a8b3662-5_mipsel_24kc.ipk 551961 Signed-off-by: André Valentin --- package/network/services/hostapd/files/hostapd.sh | 7 +++ package/network/services/hostapd/files/wpa_supplicant-full.config | 6 +++--- package/network/services/hostapd/Makefile | 1 +- 3 files changed, 11 insertions(+), 4 deletions(-) diff --git a/package/network/services/hostapd/files/hostapd.sh b/package/network/services/hostapd/files/hostapd.sh index 88113cd7ce..85299234c2 100644 --- a/package/network/services/hostapd/files/hostapd.sh +++ b/package/network/services/hostapd/files/hostapd.sh @@ -272,6 +272,8 @@ hostapd_common_add_bss_config() { config_add_array operator_icon config_add_array hs20_conn_capab config_add_string osu_ssid hs20_wan_metrics hs20_operating_class hs20_t_c_filename hs20_t_c_timestamp + + config_add_string roam_rssi_threshold } hostapd_set_vlan_file() { @@ -1178,6 +1180,11 @@ wpa_supplicant_add_network() { [ -n "$bssid_blacklist" ] && append network_data "bssid_blacklist=$bssid_blacklist" "$N$T" [ -n "$bssid_whitelist" ] && append network_data "bssid_whitelist=$bssid_whitelist" "$N$T" + [ -n "$roam_rssi_threshold" ] && { + json_get_vars roam_rssi_threshold + append network_data "bgscan=\"simple:120:${roam_rssi_threshold}:600\"" "$N$T" + } + [ -n "$basic_rate" ] && { local br rate_list= for br in $basic_rate; do diff --git a/package/network/services/hostapd/files/wpa_supplicant-full.config b/package/network/services/hostapd/files/wpa_supplicant-full.config index 982f4d5534..d39ee74a8d 100644 --- a/package/network/services/hostapd/files/wpa_supplicant-full.config +++ b/package/network/services/hostapd/files/wpa_supplicant-full.config @@ -527,9 +527,9 @@ CONFIG_WNM=y # # Enabling directly a module will enable autoscan support. # For exponential module: -#CONFIG_AUTOSCAN_EXPONENTIAL=y +CONFIG_AUTOSCAN_EXPONENTIAL=y # For periodic module: -#CONFIG_AUTOSCAN_PERIODIC=y +CONFIG_AUTOSCAN_PERIODIC=y # Password (and passphrase, etc.) backend for external storage # These optional mechanisms can be used to add support for storing passwords @@ -600,7 +600,7 @@ CONFIG_IBSS_RSN=y # operations for roaming within an ESS (same SSID). See the bgscan parameter in # the wpa_supplicant.conf file for more details. # Periodic background scans based on signal strength -#CONFIG_BGSCAN_SIMPLE=y +CONFIG_BGSCAN_SIMPLE=y # Learn channels used by the network and try to avoid bgscans on other # channels (experimental) #CONFIG_BGSCAN_LEARN=y diff --git a/package/network/services/hostapd/Makefile b/package/network/services/hostapd/Makefile index 8f94dce782..8c264854d7 100644 --- a/package/network/services/hostapd/Makefile +++ b/package/network/services/hostapd/Makefile @@ -7,7 +7,7 @@ include $(TOPDIR)/rules.mk PKG_NAME:=hostapd -PKG_RELEASE:=5 +PKG_RELEASE:=6 PKG_SOURCE_URL:=http://w1.fi/hostap.git PKG_SOURCE_PROTO:=git -- 2.20.1 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [PATCH] ath25: fix preinit Ethernet port configuration
On Wed, Sep 9, 2020 at 6:08 PM Adrian Schmutzler wrote: > > - vconfig add eth0 1 > > + ip link add dev eth0.1 link eth0 type vlan id > > 1 > > Are you sure this is correct? Yes, I tested this command with an OpenWrt ip package :) > I only find the following syntax: > > ip link add link eth0 name eth0.1 type vlan id 1 > According to ip-link(8) a user should use 'name' argument for a new interface, but in fact the iplink.c have the following code in the interface creation handler: > /* Allow "ip link add dev" and "ip link add name" */ >if (!name) >name = dev; -- Sergey ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
AW: Upcoming 19.07.4 and 18.07.9 stable releases
> Von: openwrt-devel Im > Auftrag von Thomas Endt > Gesendet: Mittwoch, 9. September 2020 17:10 > I will update the dataentries this evening. Dataentry update to 19.07.4 is running right now. Time for the long awaited announcement message! 😊 Thomas ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
AW: Upcoming 19.07.4 and 18.07.9 stable releases
> Von: Baptiste Jonglez > Gesendet: Dienstag, 8. September 2020 22:11 > Images for 19.07.4 have been built. Thomas, could you update the ToH > accordingly? When the download page is also updated, I will announce it, > probably tomorrow. > > 18.06.9 will follow soon. I will update the dataentries this evening. Thomas ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
RE: [PATCH] ath25: fix preinit Ethernet port configuration
Hi, > - vconfig set_name_type > DEV_PLUS_VID_NO_PAD > ip link set eth0 up > - vconfig add eth0 1 > + ip link add dev eth0.1 link eth0 type vlan id 1 Are you sure this is correct? I only find the following syntax: ip link add link eth0 name eth0.1 type vlan id 1 Best Adrian openpgp-digital-signature.asc Description: PGP signature ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[PATCH] build: allow file modes per binary package
Currently the global variable PKG_FILE_MODES is used for all ipkg creations. This works for Makefiles which output a single package, or variants of a single package. But if a Makefile outputs multiple packages that each contain different files, setting PKG_FILE_MODES causes build failure when any of the files in the variable do not exist in the folder that is currently being packaged. Example: /openwrt/staging_dir/host/bin/fakeroot -l /openwrt/staging_dir/host/lib/libfakeroot.so -f /openwrt/staging_dir/host/bin/faked /openwrt/scripts/ipkg-build -m "/usr/lib/mariadb/plugin/auth_pam_tool_dir:root:376:0750" /openwrt/build_dir/target-mips_24kc_musl/mariadb-10.4.13/ipkg-mips_24kc/mariadb-server-plugin-disks /openwrt/bin/packages/mips_24kc/packages +chown: cannot access '/openwrt/build_dir/target-mips_24kc_musl/mariadb-10.4.13/ipkg-mips_24kc/mariadb-server-plugin-disks//usr/lib/mariadb/plugin/auth_pam_tool_dir': No such file or directory This commit changes the file mode handling a bit. The file mode can now be set either globally via PKG_FILE_MODES (no behavior change) or on a per-package basis via FILE_MODES. This way specific file modes can be used for any particular package. This behavior is already used for other OpenWrt variables, hence it is familiar: PKG_MAINTAINER vs MAINTAINER PKG_SOURCE_SUBDIR vs SUBDIR PKG_LICENSE vs LICENSE ... Signed-off-by: Sebastian Kemper --- include/package-defaults.mk | 1 + include/package-ipkg.mk | 2 +- 2 files changed, 2 insertions(+), 1 deletion(-) diff --git a/include/package-defaults.mk b/include/package-defaults.mk index 2fed72b1a4..2a04bc17e9 100644 --- a/include/package-defaults.mk +++ b/include/package-defaults.mk @@ -59,6 +59,7 @@ define Package/Default ALTERNATIVES:= LICENSE:=$(PKG_LICENSE) LICENSE_FILES:=$(PKG_LICENSE_FILES) + FILE_MODES:=$(PKG_FILE_MODES) endef Build/Patch:=$(Build/Patch/Default) diff --git a/include/package-ipkg.mk b/include/package-ipkg.mk index 62cda5b936..0bca8ae84d 100644 --- a/include/package-ipkg.mk +++ b/include/package-ipkg.mk @@ -260,7 +260,7 @@ $(_endef) endif $(INSTALL_DIR) $$(PDIR_$(1)) - $(FAKEROOT) $(SCRIPT_DIR)/ipkg-build -m "$(PKG_FILE_MODES)" $$(IDIR_$(1)) $$(PDIR_$(1)) + $(FAKEROOT) $(SCRIPT_DIR)/ipkg-build -m "$(FILE_MODES)" $$(IDIR_$(1)) $$(PDIR_$(1)) @[ -f $$(IPKG_$(1)) ] $(1)-clean: -- 2.26.2 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [PATCH] wireguard-tools: bump to 1.0.20200827
On Tue, Sep 8, 2020 at 6:30 PM Jason A. Donenfeld wrote: > > * ipc: split into separate files per-platform > > This is in preparation for FreeBSD support, which I had hoped to have this > release, but we're still waiting on some tooling fixes, so hopefully next > wg(8) will support that. Either way, the code base is now a lot more amenable > to adding more kernel platform support. > > * man: wg-quick: use syncconf instead of addconf for strip example > > Simple documentation fix. > > * pubkey: isblank is a subset of isspace > * ctype: use non-locale-specific ctype.h > > In addition to ensuring that isalpha() and such isn't locale-specific, we also > make these constant time, even though we're never distinguishing between bits > of a secret using them. From that perspective, though, this is markedly better > than the locale-specific table lookups in glibc, even though base64 characters > span two cache lines and valid private keys must hit both. This may be useful > for other projects too: https://git.zx2c4.com/wireguard-tools/tree/src/ctype.h > --- > package/network/utils/wireguard-tools/Makefile | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) > > diff --git a/package/network/utils/wireguard-tools/Makefile > b/package/network/utils/wireguard-tools/Makefile > index fb7c0b6..a5264a5 100644 > --- a/package/network/utils/wireguard-tools/Makefile > +++ b/package/network/utils/wireguard-tools/Makefile > @@ -11,12 +11,12 @@ include $(INCLUDE_DIR)/kernel.mk > > PKG_NAME:=wireguard-tools > > -PKG_VERSION:=1.0.20200513 > +PKG_VERSION:=1.0.20200827 > PKG_RELEASE:=2 > > PKG_SOURCE:=wireguard-tools-$(PKG_VERSION).tar.xz > PKG_SOURCE_URL:=https://git.zx2c4.com/wireguard-tools/snapshot/ > -PKG_HASH:=e73409a9fb8c90506db241d1e1a4e7372a60dbfa400e37f4ab2fd70a92ba495f > +PKG_HASH:=51bc85e33a5b3cf353786ae64b0f1216d7a871447f058b6137f793eb0f53b7fd > > PKG_LICENSE:=GPL-2.0 > PKG_LICENSE_FILES:=COPYING > -- > 2.28.0 Signed-off-by: Jason A. Donenfeld ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel