Re: [OpenWrt-Devel] HTTPS with 'letsencrypt.org' on OpenWrt

2015-09-25 Thread Joris de Vries
I would be interested in this as well, although I'm not sure how useful this is 
without configuring a good hostname for routers, also maybe automatically. That 
said, from what I can see there are two options to achieve this.

The first and probably the easiest would be to port their tool to OpenWrt. It 
has a list of required modules 
(https://github.com/letsencrypt/letsencrypt/blob/master/setup.py 
) and I'm not 
sure how one would go about building it. Furthermore, it is built in Python, 
although I'm unsure if that builds to an acceptable size? Although to be honest 
it seems that about 50% of the routers in the ToH have at least 8 MB (capitals) 
of storage which I guess might fit.

The second option would be to implement the standard they use (ACME, 
https://github.com/letsencrypt/acme-spec 
) in an OpenWrt specific tool. This 
might have the added advantage of being easier to integrate with the http 
server OpenWrt uses, as I understand that one of the ways to verify a domain is 
to create a resource at some path on the server.

Cheers,

Joris

> On 25 Sep 2015, at 15:48, Sami Olmari  wrote:
> 
> I have not, I am waiting eagerly to lets encrypt go fully public. That being 
> said I have no deep knowledge of inner workings of the tool(s), but I do hope 
> that some day openwrt would also have package for this, or some method to 
> achieve this :) Will allpha and beta test for sure should there ever be baked 
> something for this! Mine .2
> 
>  Sami Olmari
> 
> On Fri, Sep 25, 2015 at 11:32 AM, Bastian Bittorf  > wrote:
> has anyone played with let's encrypt and their API?
> http://letsencrypt.readthedocs.org/en/latest/api.html 
> 
> 
> at the moment they are doing really complicated stuff,
> but maybe it's possible to hack something simply with
> the built JSON-tools and curl?
> 
> bye, bastian
> ___
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org 
> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel 
> 
> 
> ___
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel


Re: [OpenWrt-Devel] SVN to GIT transition

2015-10-11 Thread Joris de Vries

> On 11 Oct 2015, at 14:48, John Crispin  wrote:
> 
> patches will linger in mailing list until someone has time to look at
> them. the version control system used is completely irrelevant

Which is true enough if the switch just encompasses moving to another VCS. 
However, what has not been made explicit enough is that switching to git _and_ 
a git web interface like Github/Gitlab may make it easier to contribute. My 
understanding is that it would be much easier to test proposed changes as 
people can simply do a checkout on a pull request and run the proposed code. 
Currently (unless I am missing something which is unfortunately quite 
possible), one would have to manually insert the patches to test.

Someone said earlier that switching to github for the packages made a positive 
difference in contributions. I would like to see that supported by some 
numbers, or possibly a contributor can elaborate a bit on the process and 
whether they perceive any benefits. That way, the migration of the packages 
might show a practical use case in the context of this project and its 
workflows.

Joris___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel


Re: [OpenWrt-Devel] SDK vs. Toolchain+

2016-01-05 Thread Joris de Vries

> On 05 Jan 2016, at 16:04, Daniel Dickinson  
> wrote:
> 
> am of two minds about how to deal with the issue that having to build the 
> toolchain for an SDK before being able use the SDK is rather painful (or at 
> least it tests my patience; don't know about other people).
To be honest, it is more of a one-time time cost than a continuous cost. That 
is, I don't typically rebuilt the entire toolchain on every compile. Perhaps 
some of your frustration can be alleviated by using a slightly different 
workflow?

Joris___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel


Re: [LEDE-DEV] [PATCH v2] ipq806x: add kernel 4.14 support

2018-05-17 Thread Joris de Vries
Can confirm that my TP-Link Archer C2600 sysupgraded without trouble after 
updating the kernel partition to 4MB (of which a patch is in patchwork).

> On 17 May 2018, at 21:32, Stefan Lippers-Hollmann  wrote:
> 
> Hi
> 
> On 2018-05-17, John Crispin wrote:
>> On 17/05/18 13:47, Ram Chandra Jangir wrote:
>>> Thanks  Michael for confirming this,
>>> 
>>> Can you please help to update the kernel partition size to 4MB for R7800 
>>> and send it as patch to community (lede-...@lists.infradead.org)?
>>> This will help to enable kernel v4.14 for all ipq806x based boards.  
>> 
>> hang on, that would break sysupgrade or not ?
> 
> At least for the NAND based devices with a 2 MB kernel partition:
> 
> - Netgear Nighthawk X4 D7800
> - Netgear Nighthawk X4 R7500
> - Netgear Nighthawk X4 R7500v2
> - Netgear Nighthawk X4S R7800
> 
> SPI-NOR based devices should migrate transparently:
> 
> - TP-Link Archer C2600
> - TP-Link Archer VR2600v
> 
> Not affected:
> 
> - Compex WPQ864 (merged ubi on NAND)
> - Linksys EA8500 (kernel partition 3 MB on NAND)
> - Qualcomm IPQ8064/DB149 (merged firmware partition, SPI-NOR)
> - ZyXEL NBG6817 (kernel partition 4 MB on eMMC/ GPT partitions)
> 
> Unknown, probably not affected:
> 
> - Qualcomm IPQ8064/AP148 (NAND, partitioning derived from qcom-smem)
> 
> The Netgear/ NAND devices will need installing the differently 
> partitioned image via tftp, therefore it might make sense to migrate
> ipq806x to qca8k/ dsa around the same time, given that the existing
> configs can't be kept over the upgrade anyways.
> 
> https://github.com/dissent1/openwrt/commit/5c17ab1f8673d6fb69163052ac7e3f71bf385405
> 
> Devices successfully tested with this patch/ kernel 4.14:
> 
> - Netgear Nighthawk X4S R7800
>  tftp 'recovery' needed to apply the new partitioning, patches for
>  DTS and image code needed
>  tested by: Michael Yartys 
>  Message-ID: 
> - TP-Link Archer C2600
>  smooth transition, patches for DTS and tplink-safeloader needed
>  tested by: Joris de Vries 
>  Message-Id: 
> - ZyXEL NBG6817
>  smooth sysupgrade, no patches or other changes needed
>  tested by: Stefan Lippers-Hollmann 
>  Message-ID: <20180504214003.61bbd2be@mir>
> 
> I've been running my nbg6817 successfully on kernel 4.14 for a bit over 
> two weeks now, no issues at all.
> 
> It is still possible to drop the kernel size to 2'097'152 byte by
> 
> - 
> https://git.openwrt.org/?p=openwrt/staging/nbd.git;a=commitdiff;h=9e6c25f6940dbb294a7ba8cf8c72b659ec444ebf
>  - CONFIG_OPTIMIZE_INLINING=y
> - CONFIG_CC_OPTIMIZE_FOR_SIZE=y
> 
> But that's exactly on the limit for 2 MB, so it will overflow sooner
> than later, probably at the most inconvenient time. While
> [PATCH] ipq806x: cleanup kernel config
> Message-Id: <1526561729-32032-1-git-send-email-rjan...@codeaurora.org>
> should extend the headroom a bit more, extending the size of the kernel
> partition for the affected Netgear devices will be needed in the future
> either way, probably with the next minor kernel bump at the latest.
> 
> Regards
>   Stefan Lippers-Hollmann


___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
http://lists.infradead.org/mailman/listinfo/openwrt-devel


Re: [OpenWrt-Devel] Designated Driver

2015-04-08 Thread Joris de Vries
+1
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel


[OpenWrt-Devel] [PATCH] build: remove breaking commas from ubi calls

2013-10-15 Thread Joris de Vries
The extra commas get output by the shell resulting in errors since
the commands that get called with those extra commas are then
malformed.

Signed-off-by: Joris de Vries 
---
include/image.mk |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/include/image.mk b/include/image.mk
index c79d823..8f895a3 100644
--- a/include/image.mk
+++ b/include/image.mk
@@ -125,7 +125,7 @@ ifneq ($(CONFIG_TARGET_ROOTFS_UBIFS),)
$(STAGING_DIR_HOST)/bin/mkfs.ubifs \
$(if $($(PROFILE)_UBIFS_OPTS), \
$(shell echo $($(PROFILE)_UBIFS_OPTS)), \
-   $(shell echo $(UBIFS_OPTS)), \
+   $(shell echo $(UBIFS_OPTS)) \
) \
$(if 
$(CONFIG_TARGET_UBIFS_FREE_SPACE_FIXUP),--space-fixup) \
$(if 
$(CONFIG_TARGET_UBIFS_COMPRESSION_NONE),--force-compr=none) \
@@ -143,7 +143,7 @@ ifneq ($(CONFIG_TARGET_ROOTFS_UBIFS),)
$(STAGING_DIR_HOST)/bin/ubinize \
$(if $($(PROFILE)_UBI_OPTS), \
$(shell echo $($(PROFILE)_UBI_OPTS)), \
-   $(shell echo $(UBI_OPTS)), \
+   $(shell echo $(UBI_OPTS)) \
) \
-o $(KDIR)/root.ubi \
ubinize.cfg \
-- 
1.7.10.4
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel


[OpenWrt-Devel] [PATCH] build: Set owner root for all files on ubifs creation

2013-10-16 Thread Joris de Vries
When creating an image it makes no sense to have files owned by
the uid and gid on the host (and even creates a bug when for
example dropbear authorized_keys is included via env/files).

Signed-off-by: Joris de Vries 
---
include/image.mk |1 +
1 file changed, 1 insertion(+)

diff --git a/include/image.mk b/include/image.mk
index 729929f..c7da060 100644
--- a/include/image.mk
+++ b/include/image.mk
@@ -139,6 +139,7 @@ ifneq ($(CONFIG_TARGET_ROOTFS_UBIFS),)
$(if 
$(CONFIG_TARGET_UBIFS_COMPRESSION_LZO),--force-compr=lzo) \
$(if 
$(CONFIG_TARGET_UBIFS_COMPRESSION_ZLIB),--force-compr=zlib) \
--jrn-size=$(CONFIG_TARGET_UBIFS_JOURNAL_SIZE) \
+   --squash-uids \
-o $(KDIR)/root.ubifs \
-d $(TARGET_DIR)
endif
-- 
1.7.10.4
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel


[OpenWrt-Devel] [PATCH] ar71xx: Enable nand-driver for WNDR4300

2013-10-28 Thread Joris de Vries
This is based on previous patches by Stefan Agner. The kernel config
now includes the relevant lines for the ar934x nand driver, and
selects the kmod-ar934x-nand when building for the WNDR4300.

Signed-off-by: Joris de Vries 
---
target/linux/ar71xx/config-3.10 |6 +-
target/linux/ar71xx/generic/profiles/netgear.mk |2 +-
2 files changed, 6 insertions(+), 2 deletions(-)

diff --git a/target/linux/ar71xx/config-3.10 b/target/linux/ar71xx/config-3.10
index f88d008..ff1e0a0 100644
--- a/target/linux/ar71xx/config-3.10
+++ b/target/linux/ar71xx/config-3.10
@@ -207,10 +207,14 @@ CONFIG_MTD_M25P80=y
# CONFIG_MTD_MAP_BANK_WIDTH_1 is not set
# CONFIG_MTD_MAP_BANK_WIDTH_4 is not set
CONFIG_MTD_MYLOADER_PARTS=y
-# CONFIG_MTD_NAND_AR934X_HW_ECC is not set
+CONFIG_MTD_NAND=y
+CONFIG_MTD_NAND_AR934X=y
+CONFIG_MTD_NAND_AR934X_HW_ECC=y
+CONFIG_MTD_NAND_ECC=y
CONFIG_MTD_PHYSMAP=y
CONFIG_MTD_REDBOOT_DIRECTORY_BLOCK=-2
CONFIG_MTD_REDBOOT_PARTS=y
+# CONFIG_MTD_SM_COMMON is not set
CONFIG_MTD_SPLIT_FIRMWARE=y
CONFIG_MTD_SPLIT_SEAMA_FW=y
CONFIG_MTD_SPLIT_SQUASHFS_ROOT=y
diff --git a/target/linux/ar71xx/generic/profiles/netgear.mk 
b/target/linux/ar71xx/generic/profiles/netgear.mk
index c5adc0d..d5510ff 100644
--- a/target/linux/ar71xx/generic/profiles/netgear.mk
+++ b/target/linux/ar71xx/generic/profiles/netgear.mk
@@ -30,7 +30,7 @@ $(eval $(call Profile,WNDR3700))

define Profile/WNDR4300
NAME:=NETGEAR WNDR4300
-   PACKAGES:=kmod-usb-core kmod-usb-ohci kmod-usb2 kmod-ledtrig-usbdev
+   PACKAGES:=kmod-usb-core kmod-usb-ohci kmod-usb2 kmod-ledtrig-usbdev 
kmod-nand-ar934x
endef

define Profile/WNDR4300/Description
-- 
1.7.10.4
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel


Re: [OpenWrt-Devel] [PATCH] ar71xx: Enable nand-driver for WNDR4300

2013-10-30 Thread Joris de Vries
Hello all,

I just discovered that the addition to the kernel config is not strictly 
necessary, but then make prompts to confirm the CONFIG_MTD_NAND_AR934X_HW_ECC 
option. I am unsure how to fix that, maybe one of the readers can shine a light 
on that?

Thanks!

Joris

On 28 Oct 2013, at 20:53 , Joris de Vries  wrote:

> This is based on previous patches by Stefan Agner. The kernel config
> now includes the relevant lines for the ar934x nand driver, and
> selects the kmod-ar934x-nand when building for the WNDR4300.
> 
> Signed-off-by: Joris de Vries 
> ---
> target/linux/ar71xx/config-3.10 |6 +-
> target/linux/ar71xx/generic/profiles/netgear.mk |2 +-
> 2 files changed, 6 insertions(+), 2 deletions(-)
> 
> diff --git a/target/linux/ar71xx/config-3.10 b/target/linux/ar71xx/config-3.10
> index f88d008..ff1e0a0 100644
> --- a/target/linux/ar71xx/config-3.10
> +++ b/target/linux/ar71xx/config-3.10
> @@ -207,10 +207,14 @@ CONFIG_MTD_M25P80=y
> # CONFIG_MTD_MAP_BANK_WIDTH_1 is not set
> # CONFIG_MTD_MAP_BANK_WIDTH_4 is not set
> CONFIG_MTD_MYLOADER_PARTS=y
> -# CONFIG_MTD_NAND_AR934X_HW_ECC is not set
> +CONFIG_MTD_NAND=y
> +CONFIG_MTD_NAND_AR934X=y
> +CONFIG_MTD_NAND_AR934X_HW_ECC=y
> +CONFIG_MTD_NAND_ECC=y
> CONFIG_MTD_PHYSMAP=y
> CONFIG_MTD_REDBOOT_DIRECTORY_BLOCK=-2
> CONFIG_MTD_REDBOOT_PARTS=y
> +# CONFIG_MTD_SM_COMMON is not set
> CONFIG_MTD_SPLIT_FIRMWARE=y
> CONFIG_MTD_SPLIT_SEAMA_FW=y
> CONFIG_MTD_SPLIT_SQUASHFS_ROOT=y
> diff --git a/target/linux/ar71xx/generic/profiles/netgear.mk 
> b/target/linux/ar71xx/generic/profiles/netgear.mk
> index c5adc0d..d5510ff 100644
> --- a/target/linux/ar71xx/generic/profiles/netgear.mk
> +++ b/target/linux/ar71xx/generic/profiles/netgear.mk
> @@ -30,7 +30,7 @@ $(eval $(call Profile,WNDR3700))
> 
> define Profile/WNDR4300
>   NAME:=NETGEAR WNDR4300
> - PACKAGES:=kmod-usb-core kmod-usb-ohci kmod-usb2 kmod-ledtrig-usbdev
> + PACKAGES:=kmod-usb-core kmod-usb-ohci kmod-usb2 kmod-ledtrig-usbdev 
> kmod-nand-ar934x
> endef
> 
> define Profile/WNDR4300/Description
> -- 
> 1.7.10.4
> ___
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel


Re: [OpenWrt-Devel] Interest in a openwrt router database to partially replace TOH?

2013-12-09 Thread Joris de Vries
> What I really wish the TOH listing had is some indication of whether
> the hardware is known to be out of production. Looking for
> hardware to buy to run OpenWRT is... less than straightforward.

This is so absolutely true. I have gone as far as to create a snippet (link 
included, please don't click, it's horrible) that I run from Chrome's DevTools 
in order to hide all the routers that have less than certain amounts of flash 
and ram (https://gist.github.com/Zsub/7868748), but more comprehensive 
filtering would be very welcome!

Joris___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel


Re: [OpenWrt-Devel] menuconfig and deselect ('1 click' packages selection)

2014-01-23 Thread Joris de Vries
Based on an email sent by Weedy [1] I have a config file that deselects 
packages I don’t need or want via 'CONFIG_PACKAGE_ppp=n’ or similar lines. In 
that same fashion, you can select via ‘CONFIG_PACKAGE_nano=y’ (provided nano is 
installed via the packages feed).

Then you can copy that file to be the main .config file, and 'make defconfig && 
make’.

[1] https://lists.openwrt.org/pipermail/openwrt-devel/2013-November/022653.html

On 23 Jan 2014, at 19:55, etienne.champet...@free.fr wrote:

> Hi
> 
> For AA I have a package that select and deselect everything I need,
> like deselect wpad-mini and select wpad (full)
> 
> In BB deselect isn't supported anymore,
> so how can i do a '1 click' packages selection in BB
> 
> the relevant commits:
> f6a0204436d51e2227a1b9c8f0463936a9c03f0a
> build: add new menuconfig code based on linux 3.9
> r36361 18/04/13 nbd
> 
> 927764abf2c7710c29a100332587e4235fb36cf2
> add 'deselect' property for menuconfig
> r6647 23/03/2007 nbd
> 
> Exemple of what i'm doing in AA (in a Makefile):
> ##
> 
> include $(TOPDIR)/rules.mk
> 
> PKG_NAME:=aa-all
> PKG_VERSION:=1
> PKG_RELEASE:=0
> 
> include $(INCLUDE_DIR)/package.mk
> 
> define Package/aa-all
>   SECTION:=etienne
>   CATEGORY:=Etienne
>   DEPENDS:=
>   TITLE:=Tous ce qu'il faut pour AA
>   MAINTAINER:=Etienne CHAMPETIER 
>   PKGARCH:=all
> endef
> 
> define Package/aa-all/config
>   select BUSYBOX_CONFIG_FEATURE_DATE_NANO
>   select PACKAGE_openvpn
>   deselect PACKAGE_wpad-mini
>   select PACKAGE_wpad
>   deselect WPA_SUPPLICANT_INTERNAL
>   select WPA_SUPPLICANT_OPENSSL
> 
> <..>
> 
> endef
> 
> define Build/Compile
> endef
> 
> define Build/Install
> endef
> 
> $(eval $(call BuildPackage,aa-all))
> 
> ##
> ___
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel