[LEDE-DEV] DHCP via bridge in case of IPv4

Hello, I was playing with quite simple bridged setup on different boards with very recent kernels (4.6.3 as of this writing) and found one interesting behavior that I cannot yet understand and googling din't help here as well. My setup is pretty simple: -   -- 

Re: [LEDE-DEV] [RFC v2 2/2] ar71xx: image: fix typo in MTDPARTS def for qihoo-c301

Tested-by: Steven Haigh On 9/07/2016 11:06 AM, Yousong Zhou wrote: > Reported-by: Syrone Wong > Signed-off-by: Yousong Zhou > --- > target/linux/ar71xx/image/generic.mk | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > >

Re: [LEDE-DEV] [RFC v2 1/2] ar71xx: image: fix making loader kernel for seama

Sorry - I thought that would be a separate patch. If its a modification of either of these two, I'll hold off until I've tested v3 of your changes. On 9/07/2016 6:09 PM, Yousong Zhou wrote: > On 9 July 2016 at 15:56, Steven Haigh wrote: >> Tested-by: Steven Haigh

Re: [LEDE-DEV] [RFC v3 0/3] ar71xx: image: fix making seama images

Just to bring everyone into the loop on this. Built with this patchset - however on flashing the factory image via the emergency bootloader recovery, it has lots of problems with the JFFS2 creation. I've already sent the logs to Yousong, however pasted them here for reference as well:

[LEDE-DEV] [RFC v3 0/3] ar71xx: image: fix making seama images

v3 <- v2 - pad-jffs2 after seama-factory and seama-sysupgrade - remove the head/tail 4-bytes hack on jffs2 eof marker - remove the current not-needed 09-fix-seama-header v2 <- v1 - Changed "DEVICE_VARS :=" to "DEVICE_VARS +=" Yousong Zhou (3): ar71xx: image:

[LEDE-DEV] [RFC v3 1/3] ar71xx: image: seama: fix making factory and sysupgrade image

Signed-off-by: Yousong Zhou --- target/linux/ar71xx/image/generic.mk | 19 --- 1 file changed, 8 insertions(+), 11 deletions(-) diff --git a/target/linux/ar71xx/image/generic.mk b/target/linux/ar71xx/image/generic.mk index b8e70a4..c1f1cae 100644 ---

[LEDE-DEV] [RFC v4 4/4] ar71xx: base-files: remove the now unneeded 09_fix-seama-header

It was intended as a workaround when jffs2 eof mark was included in the checksum calculation in seama header. When qihoo-c301 support was introduced the board name was not inserted into the case list (because I was not aware of it's existence), but the issue was fixed by excluding the jffs2

Re: [LEDE-DEV] Target Profile removed from image name?

Hi, On Fri, Jul 08, 2016 at 11:11:25AM -0600, Donald Chisholm wrote: > Hi all, > > I have several hundred nodes running Openwrt CC with batman-adv and > thought I would start testing LEDE. However, after the build I > noticed you have removed the target profile (i.e. tl-841v11) from the > image

Re: [LEDE-DEV] [RFC v3 3/3] ar71xx: base-files: remove the now unneeded 09_fix-seama-header

Still seems to give me JFFS2 errors. Log attached again. On 9/07/2016 7:33 PM, Yousong Zhou wrote: > It was intended as a workaround when jffs2 eof mark was included in the > checksum calculation in seama header. When qihoo-c301 support was > introduced the board name was not inserted into the

[LEDE-DEV] [RFC v4 0/4] ar71xx: image: fix making seama images

v4 <- v3 - patch padjffs2 to allow outputing padding data to stdout - introduce seama-pad-rootfs to replace pad-rootfs used in v3 v3 <- v2 - pad-rootfs after seama-factory and seama-sysupgrade - remove the head/tail 4-bytes hack on jffs2 eof marker -

[LEDE-DEV] [RFC v4 3/4] ar71xx: image: fix typo in MTDPARTS def for qihoo-c301

Reported-by: Syrone Wong Signed-off-by: Yousong Zhou --- target/linux/ar71xx/image/generic.mk | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/target/linux/ar71xx/image/generic.mk b/target/linux/ar71xx/image/generic.mk index

Re: [LEDE-DEV] Target Profile removed from image name?

Hi Baptiste, Thanks for responding. See inline comments. On Sat, Jul 9, 2016 at 4:12 AM, Baptiste Jonglez wrote: > Hi, > > On Fri, Jul 08, 2016 at 11:11:25AM -0600, Donald Chisholm wrote: >> Hi all, >> >> I have several hundred nodes running Openwrt CC with

[LEDE-DEV] [PATCH] dropbear: Fix append_port in IPv6 case

dropbear uses -p [ip6%phy]:port syntax, now correctly handled by append_port. Signed-off-by: Laurent GUERBY --- package/network/services/dropbear/files/dropbear.init | 10 +- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git

[LEDE-DEV] [PATCH] dropbear: Add IPPort parameter

The new IPPort parameter allows to pass unchanged parameters to dropbear, dropbear uses -p [ip6]:port for IPv6 and this was not supported with existing scripts. Signed-off-by: Laurent GUERBY --- package/network/services/dropbear/files/dropbear.init | 9 +++-- 1 file

Re: [LEDE-DEV] [RFC v4 0/4] ar71xx: image: fix making seama images

Tested-by: Steven Haigh Confirmed correct operation of these patches to make working factory images for the MyNET N750. Tests all passed - happy to report all working well. On 9/07/2016 10:15 PM, Yousong Zhou wrote: > v4 <- v3 > > - patch padjffs2 to allow outputing

Re: [LEDE-DEV] [RFC v4 0/4] ar71xx: image: fix making seama images

On 9 July 2016 at 21:46, Steven Haigh wrote: > Tested-by: Steven Haigh > > Confirmed correct operation of these patches to make working factory > images for the MyNET N750. > > Tests all passed - happy to report all working well. > Thanks for the patience and

[LEDE-DEV] [PATCH] dropbear: Fix append_port in IPv6 case (v2)

The new IPPort parameter allows to pass unchanged parameters to dropbear, dropbear uses -p [ip6]:port for IPv6 and this was not supported with existing scripts. Fix indentation and missing then of previous patch. Signed-off-by: Laurent GUERBY ---