Re: [OpenWrt-Devel] Inquery
Hi Alberto, On Wed, Dec 11, 2019 at 08:32:41PM +0100, Alberto Bursi wrote: > > > On 11/12/19 18:54, Daniel Golle wrote: > > On Wed, Dec 11, 2019 at 05:37:26PM +0100, WRT Burner wrote: > > > On 11/12/2019 15:22, Daniel Golle wrote: > > > > And it's even needless to say that > > > > replying to a spam email in which ever way will always make it worse. > > > > > > +1. There is no constructive value in replying to spam. Let's keep > > > openwrt-devel > > > nice and clean. > > > > > > On 11/12/2019 15:22, Daniel Golle wrote: > > > > You statement "suck it" (guess what) is also an obvious > > > > and disgusting example of a masculist culture which hurts our community > > > > as a whole and I strongly believe we should not tolerate that. > > > > > > -1. This is a software development mailing list, not tumblr.com. > > > > '-1'? So I get right, you are saying it's ok to be insulting other > > people because this mailing list is about software development? > > If that's really what you wanted to say, I'm glad that's only a single > > individual opinion coming from an email address which has never > > actually been used on this mailing list. > > And btw, this is your first 'contribution', and it's not even about > > software development... > > > > He is just disappointed at your pointing out the "masculinist culture" in a > place where he expected more maturity. Maybe I don't understand this level of maturity where it can be alright to use language which has the only purpose to deliberately hurt other people. Maybe I even hope I will never get that 'mature'. I pointed out the masculinist culture a statement like his originates from just because that's what it is. Correct me if I'm getting something wrong, but "suck it" basically says, "I'm the male in the room here, so your rights are limited to please me sexually". To me is not a border-line grey-zone of overdoing political correctness and forcing everybody to use lots of virtue signalling and a very specificly coded language changing every two weeks accoring to fashion standards. It's not that he failed to use gender-correct language or wrongly assumed someones identity or any of those things which happen a lot without any bad intention involved. But what Tom wrote was **meant** as an insult. > > Yours is mostly SJW-speak and I'm also not fond of it, I'll explain why. > It is a double-edged blade. > In this case your definition is technically correct, we all know what "suck > it" implies. > But this highly polarizing approach to life and people can (and does, > especially in its dens like tumblr.com as mentioned) slippery slope into > full blown hate and reverse oppression, which is equally bad. I guess I partially agree with you one that. I have never visited tumblr nor know much about what's happening there. To me, "social justice" sounds like something desireable, however, I can also see that the fight for that is also being misused to call-out on people who didn't intend to do any harm to anyone in some cases. However, I don't think we need this debate here in this case, as very clearly "suck it" is just very obviously not nice, ie. violates the rule #12 "be nice to each other". > > I'm not impressed by your reaction here, first thing you do is a blatant > strawman logical fallacy and then proceed to attack him on his personal > values as a person without even asking to clarify his position first. > He just posted a single short sentence, for heaven's sake. > > This is EXACTLY an example of slippery slope into blind hate rage as I said > above, and exactly why this kind of polarizing categorizations and > statements should be avoided at all costs in a serious and sane environment. > > We should really not jump at each other's throats on a moment's notice like > that, especially not in a software development mailing list. I did asked for claritication, because it wasn't clear to me (see my reply, there are some "if"s). I didn't make any assumptions on his values, I was surprised and hoping that this would turn out to be just a case of misunderstanding each other. Simply because it's hard for me to imagine a setting where it would be ok to write "suck it" just because this is about software development (and I still fail to follow that logic, maybe you can explain that to me off-list). I also agree that I don't want people to the scared to be super correct and this is not the place to discuss subtle language details, for the exact same reason that we will loose potential contributors. Needless to say that WRT_Burner showed up out of nowhere (let me guess what 'burner' means in that choice of a name) Cheers Daniel ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH] ca-certificates: provide ca-certs by both ca-certificates and ca-bundle
- both packages provide ca-certs - make ca-bundle the default provider This should allow easy transition between these two forms of CA certificates storage Signed-off-by: Maxim Storchak --- package/system/ca-certificates/Makefile | 6 -- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/package/system/ca-certificates/Makefile b/package/system/ca-certificates/Makefile index f449645c77..ea7d253fa2 100644 --- a/package/system/ca-certificates/Makefile +++ b/package/system/ca-certificates/Makefile @@ -8,7 +8,7 @@ include $(TOPDIR)/rules.mk PKG_NAME:=ca-certificates PKG_VERSION:=20190110 -PKG_RELEASE:=1 +PKG_RELEASE:=2 PKG_MAINTAINER:= PKG_SOURCE:=$(PKG_NAME)_$(PKG_VERSION).tar.xz @@ -24,6 +24,7 @@ define Package/ca-certificates CATEGORY:=Base system TITLE:=System CA certificates PKGARCH:=all + PROVIDES:=ca-certs endef define Package/ca-bundle @@ -31,6 +32,7 @@ define Package/ca-bundle CATEGORY:=Base system TITLE:=System CA certificates as a bundle PKGARCH:=all + PROVIDES:=ca-certs endef define Build/Install @@ -59,5 +61,5 @@ define Package/ca-bundle/install cat $(PKG_INSTALL_DIR)/usr/share/ca-certificates/*/*.crt >$(1)/etc/ssl/certs/ca-certificates.crt $(LN) /etc/ssl/certs/ca-certificates.crt $(1)/etc/ssl/cert.pem endef -$(eval $(call BuildPackage,ca-certificates)) $(eval $(call BuildPackage,ca-bundle)) +$(eval $(call BuildPackage,ca-certificates)) -- 2.24.0 ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Re: [OpenWrt-Devel] [PATCH] ramips: add support for JCG JHR-AC876M
Hi,
> + aliases {
> + led-boot = &led_wps;
> + led-failsafe = &led_wps;
> + led-running = &led_wps;
> + led-upgrade = &led_wps;
> + label-mac-device = &wifi2g;
This won't work (address not set explicitly in DTS). You will need to provide
the address in 02_network (see below).
> diff --git a/target/linux/ramips/image/mt7621.mk
> b/target/linux/ramips/image/mt7621.mk
> index d663aa29da..cbbda06822 100644
> --- a/target/linux/ramips/image/mt7621.mk
> +++ b/target/linux/ramips/image/mt7621.mk
> @@ -361,6 +361,19 @@ define Device/iodata_wnpr2600g
> endef
> TARGET_DEVICES += iodata_wnpr2600g
>
> +define Device/jcg_jhr-ac876m
> + MTK_SOC := mt7621
> + IMAGE_SIZE := 16064k
> + IMAGES += factory.bin
> + IMAGE/factory.bin := \
> +$$(sysupgrade_bin) | check-size (IMAGE_SIZE) | jcg-header 89.1
Won't $$(sysupgrade_bin) include the metadata not needed for the factory image?
> + JCG_MAXSIZE := 16449536
I'd prefer to have a substitution included in jcg-header, so we can use 16064k
here, too.
> + DEVICE_VENDOR := JCG
> + DEVICE_MODEL := JHR-AC876M
> + DEVICE_PACKAGES := kmod-mt7615e kmod-usb3 kmod-usb-ledtrig-usbport
> wpad-basic
> +endef
> +TARGET_DEVICES += jcg_jhr-ac876m
> +
> define Device/lenovo_newifi-d1
>MTK_SOC := mt7621
>IMAGE_SIZE := 32448k
> diff --git a/target/linux/ramips/mt7621/base-files/etc/board.d/02_network
> b/target/linux/ramips/mt7621/base-files/etc/board.d/02_network
> index bb6e41e06f..904e82e09a 100755
> --- a/target/linux/ramips/mt7621/base-files/etc/board.d/02_network
> +++ b/target/linux/ramips/mt7621/base-files/etc/board.d/02_network
> @@ -14,6 +14,7 @@ ramips_setup_interfaces()
> d-team,pbr-m1|\
> firefly,firewrt|\
> hiwifi,hc5962|\
> + jcg,jhr-ac876m|\
> mediatek,ap-mt7621a-v60|\
> mediatek,mt7621-eval-board|\
> mqmaker,witi|\
> @@ -223,6 +224,9 @@ ramips_setup_macs()
> wan_mac=$(mtd_get_mac_ascii u-boot-env wanaddr)
> label_mac=$wan_mac
> ;;
> + jcg,jhr-ac876m)
> + wan_mac=$(mtd_get_mac_binary factory 0x4)
What about 0xe006? If lan is 0xe000, I would expect the wan MAC address there.
Add here:
label_mac=$(mtd_get_mac_binary factory 0x4)
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
Re: [OpenWrt-Devel] Inquery
+1 11 Dec 2019 15:22:44 Daniel Golle : > Hi Tomislav, > > On Wed, Dec 11, 2019 at 11:24:21AM +0100, Tom Psyborg wrote: > > > suck it > > > > As a community, we decided to give our self a set of minimal rules[1]. > And even though it is in the last position, rule #12 "Be nice to each > other." is meant just as serious as all the other rules. > > So here, not for the first time, you are using language which has the > only purpose to hurt other people (for which reason ever, it doesn't > matter). This is therefore a very clear violation to the above > mentioned rule. You statement "suck it" (guess what) is also an obvious > and disgusting example of a masculist culture which hurts our community > as a whole and I strongly believe we should not tolerate that. > > And yes this was a spam mail. And it's even needless to say that > replying to a spam email in which ever way will always make it worse. > But that's not the point here and I will not engage in any discussion > on that matter. > > Please learn to behave or leave us alone. > > [1]: https://openwrt.org/rules > > > > > > > On 11/12/2019, rqgxfc wrote: > > > > > > > > > > > Hello Sir ? > > > > > > We are a trading company named Shaanxi Hao Zi Guan Materials Co.,Ltd . Now > > > we are very interested in your products , we will plan to sell your > > > products in the Chinese market . If you are interested in cooperation, > > > please send us a catalog and pricelist .w > > > Looking forward to receiving your reply . > > > > > > Best regards, > > > Catherina > > > > > > > ___ > > openwrt-devel mailing list > > openwrt-devel@lists.openwrt.org > > https://lists.openwrt.org/mailman/listinfo/openwrt-devel > > > > ___ > openwrt-devel mailing list > openwrt-devel@lists.openwrt.org > https://lists.openwrt.org/mailman/listinfo/openwrt-devel > ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
[OpenWrt-Devel] [PATCH V2] ramips: add support for JCG JHR-AC876M
JCG JHR-AC876M is an AC2600M router
Hardware specs:
SoC: MT7621AT
2.4GHz: MT7615N 4x4 @ PCIe0
5GHz: MT7615N 4x4 @ PCIe1
Flash: Winbond W25Q128JVSQ 16MiB
RAM: Nanya NT5CB128M16 256MiB
USB 2.0 and 3.0 ports
6 LEDs, 3 of which are connected to SoC GPIO
Reset and WPS buttons
Flash instructions:
Stock to OpenWrt:
Upload factory.bin in stock firmware's upgrade page,
do not preserve settings
OpenWrt to stock:
Push and hold the reset button for 5s while power cycling to
enter recovery mode;
Visit 192.168.1.1 and upload stock firmware
Signed-off-by: DENG Qingfang
---
Changes since V1:
Rebased and fixed label-mac
---
.../ramips/dts/mt7621_jcg_jhr-ac876m.dts | 146 ++
target/linux/ramips/image/mt7621.mk | 13 ++
.../mt7621/base-files/etc/board.d/02_network | 5 +
3 files changed, 164 insertions(+)
create mode 100644 target/linux/ramips/dts/mt7621_jcg_jhr-ac876m.dts
diff --git a/target/linux/ramips/dts/mt7621_jcg_jhr-ac876m.dts
b/target/linux/ramips/dts/mt7621_jcg_jhr-ac876m.dts
new file mode 100644
index 00..267043b5a1
--- /dev/null
+++ b/target/linux/ramips/dts/mt7621_jcg_jhr-ac876m.dts
@@ -0,0 +1,146 @@
+// SPDX-License-Identifier: GPL-2.0-or-later OR MIT
+/dts-v1/;
+
+#include "mt7621.dtsi"
+
+#include
+#include
+
+/ {
+ compatible = "jcg,jhr-ac876m", "mediatek,mt7621-soc";
+ model = "JCG JHR-AC876M";
+
+ aliases {
+ led-boot = &led_wps;
+ led-failsafe = &led_wps;
+ led-running = &led_wps;
+ led-upgrade = &led_wps;
+ };
+
+ chosen {
+ bootargs = "console=ttyS0,57600";
+ };
+
+ leds {
+ compatible = "gpio-leds";
+
+ usb3 {
+ label = "jhr-ac876m:blue:usb3";
+ gpios = <&gpio0 3 GPIO_ACTIVE_LOW>;
+ trigger-sources = <&xhci_ehci_port1>;
+ linux,default-trigger = "usbport";
+ };
+
+ usb2 {
+ label = "jhr-ac876m:blue:usb2";
+ gpios = <&gpio0 6 GPIO_ACTIVE_LOW>;
+ trigger-sources = <&ehci_port2>;
+ linux,default-trigger = "usbport";
+ };
+
+ led_wps: wps {
+ label = "jhr-ac876m:blue:wps";
+ gpios = <&gpio0 14 GPIO_ACTIVE_LOW>;
+ };
+ };
+
+ keys {
+ compatible = "gpio-keys";
+
+ reset {
+ label = "reset";
+ gpios = <&gpio0 16 GPIO_ACTIVE_LOW>;
+ linux,code = ;
+ };
+
+ wps {
+ label = "wps";
+ gpios = <&gpio0 18 GPIO_ACTIVE_LOW>;
+ linux,code = ;
+ };
+ };
+};
+
+&spi0 {
+ status = "okay";
+
+ flash@0 {
+ compatible = "jedec,spi-nor";
+ reg = <0>;
+ spi-max-frequency = <8000>;
+ m25p,fast-read;
+
+ partitions {
+ compatible = "fixed-partitions";
+ #address-cells = <1>;
+ #size-cells = <1>;
+
+ partition@0 {
+ label = "u-boot";
+ reg = <0x0 0x3>;
+ read-only;
+ };
+
+ partition@3 {
+ label = "u-boot-env";
+ reg = <0x3 0x1>;
+ read-only;
+ };
+
+ factory: partition@4 {
+ label = "factory";
+ reg = <0x4 0x1>;
+ read-only;
+ };
+
+ partition@5 {
+ compatible = "denx,uimage";
+ label = "firmware";
+ reg = <0x5 0xfb>;
+ };
+ };
+ };
+};
+
+&pcie {
+ status = "okay";
+};
+
+&pcie0 {
+ wifi@0,0 {
+ compatible = "mediatek,mt76";
+ reg = <0x 0 0 0 0>;
+ mediatek,mtd-eeprom = <&factory 0x0>;
+ ieee80211-freq-limit = <240 250>;
+
+ led {
+ led-active-low;
+ };
+ };
+};
+
+&pcie1 {
+ wifi@0,0 {
+ compatible = "mediatek,mt76";
+ reg = <0x 0 0 0 0>;
+ mediatek,mtd-eeprom = <&factory 0x8000>;
+ ieee80211-freq-limit = <500 600>;
+
+ led {
+ led-active-low;
+ };
+ };
+};
+
+ðernet {
+ mtd-mac-address = <&factory 0xe000>;
Re: [OpenWrt-Devel] [PATCH V2] ramips: add support for JCG JHR-AC876M
Hi again,
> -Original Message-
> From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org] On
> Behalf Of DENG Qingfang
> Sent: Donnerstag, 12. Dezember 2019 15:09
> To: openwrt-devel@lists.openwrt.org
> Subject: [OpenWrt-Devel] [PATCH V2] ramips: add support for JCG JHR-AC876M
>
> JCG JHR-AC876M is an AC2600M router
>
> Hardware specs:
> SoC: MT7621AT
> 2.4GHz: MT7615N 4x4 @ PCIe0
> 5GHz: MT7615N 4x4 @ PCIe1
> Flash: Winbond W25Q128JVSQ 16MiB
> RAM: Nanya NT5CB128M16 256MiB
> USB 2.0 and 3.0 ports
> 6 LEDs, 3 of which are connected to SoC GPIO
> Reset and WPS buttons
>
> Flash instructions:
> Stock to OpenWrt:
> Upload factory.bin in stock firmware's upgrade page,
> do not preserve settings
>
> OpenWrt to stock:
> Push and hold the reset button for 5s while power cycling to
> enter recovery mode;
> Visit 192.168.1.1 and upload stock firmware
Please add information about the MAC addresses to the commit message, as
suggested in the previous e-mail, something like
0x4*:00 wlan2g/wan/label
0x8004 *:01 wlan5g
0xe000 *:02 lan
0xe006 *:03 not used in stock FW
[...]
> +
> +&pinctrl {
> + state_default: pinctrl0 {
> + gpio {
> + ralink,group = "i2c", "uart3", "jtag", "wdt";
> + ralink,function = "gpio";
> + };
> + };
> +};
For mt7621, state_default is already defined in mt7621.dtsi. So, you may use it
directly:
+&state_default {
+ gpio {
+ ralink,group = "i2c", "uart3", "jtag", "wdt";
+ ralink,function = "gpio";
+ };
+};
> diff --git a/target/linux/ramips/image/mt7621.mk
> b/target/linux/ramips/image/mt7621.mk
> index d663aa29da..cbbda06822 100644
> --- a/target/linux/ramips/image/mt7621.mk
> +++ b/target/linux/ramips/image/mt7621.mk
> @@ -361,6 +361,19 @@ define Device/iodata_wnpr2600g
> endef
> TARGET_DEVICES += iodata_wnpr2600g
>
> +define Device/jcg_jhr-ac876m
> + MTK_SOC := mt7621
> + IMAGE_SIZE := 16064k
> + IMAGES += factory.bin
> + IMAGE/factory.bin := \
> +$$(sysupgrade_bin) | check-size (IMAGE_SIZE) | jcg-header 89.1
> + JCG_MAXSIZE := 16449536
I've built a patch to allow kilobytes here:
https://git.openwrt.org/?p=openwrt/staging/adrian.git;a=shortlog;h=refs/heads/staging
I'm currently built-testing it, maybe you can test with
JCG_MAXSIZE := 16064k
too.
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
Re: [OpenWrt-Devel] Inquery
On Thu, Dec 12, 2019 at 2:01 AM Daniel Golle wrote: > > Hi Alberto, > > On Wed, Dec 11, 2019 at 08:32:41PM +0100, Alberto Bursi wrote: > > > > > > On 11/12/19 18:54, Daniel Golle wrote: > > > On Wed, Dec 11, 2019 at 05:37:26PM +0100, WRT Burner wrote: > > > > On 11/12/2019 15:22, Daniel Golle wrote: > > > > > And it's even needless to say that > > > > > replying to a spam email in which ever way will always make it worse. > > > > > > > > +1. There is no constructive value in replying to spam. Let's keep > > > > openwrt-devel > > > > nice and clean. > > > > > > > > On 11/12/2019 15:22, Daniel Golle wrote: > > > > > You statement "suck it" (guess what) is also an obvious > > > > > and disgusting example of a masculist culture which hurts our > > > > > community > > > > > as a whole and I strongly believe we should not tolerate that. > > > > > > > > -1. This is a software development mailing list, not tumblr.com. > > > > > > '-1'? So I get right, you are saying it's ok to be insulting other > > > people because this mailing list is about software development? > > > If that's really what you wanted to say, I'm glad that's only a single > > > individual opinion coming from an email address which has never > > > actually been used on this mailing list. > > > And btw, this is your first 'contribution', and it's not even about > > > software development... > > > > > > > He is just disappointed at your pointing out the "masculinist culture" in a > > place where he expected more maturity. > > Maybe I don't understand this level of maturity where it can be > alright to use language which has the only purpose to deliberately > hurt other people. Maybe I even hope I will never get that 'mature'. > > I pointed out the masculinist culture a statement like his > originates from just because that's what it is. Correct me if I'm > getting something wrong, but "suck it" basically says, "I'm the male > in the room here, so your rights are limited to please me sexually". > To me is not a border-line grey-zone of overdoing political > correctness and forcing everybody to use lots of virtue signalling > and a very specificly coded language changing every two weeks accoring > to fashion standards. It's not that he failed to use gender-correct > language or wrongly assumed someones identity or any of those things > which happen a lot without any bad intention involved. > But what Tom wrote was **meant** as an insult. > > > > > Yours is mostly SJW-speak and I'm also not fond of it, I'll explain why. > > It is a double-edged blade. > > In this case your definition is technically correct, we all know what "suck > > it" implies. > > But this highly polarizing approach to life and people can (and does, > > especially in its dens like tumblr.com as mentioned) slippery slope into > > full blown hate and reverse oppression, which is equally bad. > > I guess I partially agree with you one that. I have never visited > tumblr nor know much about what's happening there. To me, "social > justice" sounds like something desireable, however, I can also see that > the fight for that is also being misused to call-out on people who > didn't intend to do any harm to anyone in some cases. > > However, I don't think we need this debate here in this case, as very > clearly "suck it" is just very obviously not nice, ie. violates the > rule #12 "be nice to each other". > > > > > I'm not impressed by your reaction here, first thing you do is a blatant > > strawman logical fallacy and then proceed to attack him on his personal > > values as a person without even asking to clarify his position first. > > He just posted a single short sentence, for heaven's sake. > > > > This is EXACTLY an example of slippery slope into blind hate rage as I said > > above, and exactly why this kind of polarizing categorizations and > > statements should be avoided at all costs in a serious and sane environment. > > > > We should really not jump at each other's throats on a moment's notice like > > that, especially not in a software development mailing list. > > I did asked for claritication, because it wasn't clear to me (see my > reply, there are some "if"s). I didn't make any assumptions on his > values, I was surprised and hoping that this would turn out to be just > a case of misunderstanding each other. Simply because it's hard for me > to imagine a setting where it would be ok to write "suck it" just > because this is about software development (and I still fail to follow > that logic, maybe you can explain that to me off-list). > > I also agree that I don't want people to the scared to be super correct > and this is not the place to discuss subtle language details, for the > exact same reason that we will loose potential contributors. > > Needless to say that WRT_Burner showed up out of nowhere (let me guess > what 'burner' means in that choice of a name) It's a spam message. The response by Tom may have been heavy but it's nothing to cause commotion over. That is
[OpenWrt-Devel] Православная видеоэнциклопедия - уникальное издание в отличном качестве. 05_08_2019 02_10 199508
The sender domain has a DMARC Reject/Quarantine policy which disallows sending mailing list messages using the original "From" header. To mitigate this problem, the original message has been wrapped automatically by the mailing list software.--- Begin Message --- ПРАВОСЛАВНАЯ ВИДЕОЭНЦИКЛОПЕДИЯ Видеоэнциклопедия призвана ознакомить с основами христианского вероучения, наиболее полно осветить и объяснить догматы и каноны Православия, прикоснуться к священному смыслу Таинств и обрядов Церкви. Православная видеоэнциклопедия является специализированным справочным изданием, ставящим перед собой задачу дать всеобъемлющую информацию по двухтысячелетней истории и современному состоянию вселенского Православия. Вам предлагается одно из самых полных сводов знаний по Православию и истории религии. Эта видеоэнциклопедия станет добрым помощником для учителей воскресных школ, для родителей, воспитывающих своих детей в православной вере, и для всех, кто хочет поближе познакомиться с христианским учением. Вся информация в видеоэнциклопедии представлена в интересной и увлекательной форме, рассчитанной на широкий круг зрителей. Мы убеждены, что после просмотра вы откроете что-то новое и важное для себя и сможете объяснить это своим детям или ученикам. Энциклопедия была создана и издается по благословению Патриарха Московского и всея Руси Кирилла. ! Список серий вы можете увидеть в прикреплённом к письму файле ! Видеоэнциклопедия состоит из 244 серий. Записана на внешний USB накопитель (флешка). Проблем с воспроизведением не возникнет, можно смотреть на компьютере, планшете, смартфоне, телевизоре и т.д. Запись на внешний USB накопитель имеет ряд преимуществ в сравнении с обычными DVD дисками, USB накопитель гораздо легче, занимает меньше места, обладает высокой надёжностью сохранности записей, а это значит, что наша коллекция будет радовать Вас много лет. Мы гарантируем отличное качество всех записей. На самом носителе создана продуманная структура, все записи разнесены по каталогам, имеются плейлисты, прописаны теги, а также полный список вошедших записей, поэтому проблем с поиском и навигацией не возникнет. Стоимость коллекции на внешнем USB накопителе — 6500 (Шесть Тысяч Пятьсот) Рублей. Продаются только вместе. Доставка включена в стоимость. Доставка и оплата коллекции осуществляется только по России — почтой, наложенным платежом, никакой предоплаты не требуется, оплата только в момент получения на почте, доставка включена в стоимость. Сроки доставки зависят от расстояния и степени загрузки почты, но как правило это 7-14 суток с момента отправки. Напоминаем, что у нас нет курьерской доставки — только почтой, в том числе и по Москве. Для оформления заказа просьба не забывать указывать: --- Ваш почтовый индекс (пишите правильный индекс — это ускорит доставку); --- Ваш город и точный адрес (название улицы, номер дома и номер квартиры); --- Ф.И.О. получателя и ОБЯЗАТЕЛЬНО номер контактного телефона (лучше сотовый); Заказы\вопросы направляйте по адресу: pravoslavnoevi...@cwhflash.ru Мы очень ответственно относимся к качеству нашего товара, поэтому перед отправкой всё дополнительно проверяется, как следствие отправка бракованной продукции сведена к нулю. Товар упаковывается в специальный ударостойкий материал, что в значительной степени уменьшает риск повреждения при транспортировке. Если вдруг с полученным товаром возникнут проблемы, то все наши покупатели всегда могут рассчитывать на квалифицированную техническую поддержку. Мы никогда не отказываемся от гарантийных обязательств, в случае проблемы Вы можете рассчитывать на замену, почтовые расходы мы берём на себя. По вашему желанию, данная коллекция может быть записана на DVD диски. Для записи используются надёжные DVD диски со специальным покрытием, которое повышает устойчивость диска к механическим повреждениям, таким как трещины и царапины, а это значит, что наша коллекция будет радовать Вас много лет. Коллекция упакована в пластиковые боксы (slim-dvd), имеет красивые и продуманные обложки, с обратной стороны которых указан список вошедших на каждый диск серий и другая полезная информация, поэтому проблем с поиском и навигацией не возникнет. Если хотите приобрести коллекцию, записанную на DVD дисках, то в этом случае просьба сообщить нам об этом в своей заявке, цена прежняя, как у версии на внешнем USB накопителе (флешка) — 6500 (Шесть Тысяч Пятьсот) Рублей. Если вы не хотите больше получать от нас письма, отправьте нам письмо с темой “deletemail” и Ваш адрес навсегда будет удален автоматически. 05_08_2019 02_10 199508 openwrt-devel@lists.openwrt.org 01 - Î Ïðàâîñëàâèè 02 - Âåðà â Áîãà. Î Áîãå Òðîèöå 03 - Áîæèé ìèð è Áîæåñòâåííîå îòêðîâåíèå 04 - Ñâÿùåíîå Ïèñàíèå. Áèáëèÿ 05 - Ñâÿùåíîå Ïðåäàíèå 06 - Î ìèðå 07 - Î Áîãå 08 - Î ñâîéñòâàõ Áîæèèõ 09 - Ñâîéñòâà Áîæèè 10 - Áåñåäà î 1 ÷àñòè Ñèìâîëà Âåðû 11 - Áåñåäà î 2 ÷àñòè Ñèìâîëà Âåðû 12 - Áåñåäà î 3 ÷àñòè Ñèìâîëà Âåðû 13 - Áåñåäà î 4 ÷àñòè Ñèìâîëà Âåðû 01 - Î Ïðàâîñëàâ
[OpenWrt-Devel] [PATCH] zones: enforce forward policy with zone_NAME_src_POLICY
E.g. traffic entering zone_lan_forward must match "-i br-lan". That is, forward policy of zone X applies to those traffics from zone X and to be forwarded to other zones The iptables target for zone policy enforcement should be zone_NAME_src_POLICY to match "-i br-lan", not zone_NAME_dest_POLICY that matches "-o br-lan" Fixes FS#2525 Signed-off-by: Yousong Zhou --- zones.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/zones.c b/zones.c index 310583d..f268615 100644 --- a/zones.c +++ b/zones.c @@ -317,11 +317,11 @@ fw3_load_zones(struct fw3_state *state, struct uci_package *p) resolve_cthelpers(state, e, zone); fw3_setbit(zone->flags[0], fw3_to_src_target(zone->policy_input)); - fw3_setbit(zone->flags[0], zone->policy_forward); + fw3_setbit(zone->flags[0], fw3_to_src_target(zone->policy_forward)); fw3_setbit(zone->flags[0], zone->policy_output); fw3_setbit(zone->flags[1], fw3_to_src_target(zone->policy_input)); - fw3_setbit(zone->flags[1], zone->policy_forward); + fw3_setbit(zone->flags[1], fw3_to_src_target(zone->policy_forward)); fw3_setbit(zone->flags[1], zone->policy_output); list_add_tail(&zone->list, &state->zones); @@ -659,7 +659,7 @@ print_zone_rule(struct fw3_ipt_handle *handle, struct fw3_state *state, fw3_ipt_rule_append(r, "zone_%s_input", zone->name); r = fw3_ipt_rule_new(handle); - fw3_ipt_rule_target(r, "zone_%s_dest_%s", zone->name, + fw3_ipt_rule_target(r, "zone_%s_src_%s", zone->name, fw3_flag_names[zone->policy_forward]); fw3_ipt_rule_append(r, "zone_%s_forward", zone->name); ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
