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
---
package/network/services/dropbear/files/dropbear
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 a/package/network/services/dropbear/files/dropbear.ini
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 changed, 7 insertions(+),
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 batman-adv and
>> thought I would sta
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 feedback, detailed logs and testing
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 padding data to stdou
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 marker
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
- remov
Signed-off-by: Yousong Zhou
---
tools/padjffs2/src/padjffs2.c | 20
1 file changed, 16 insertions(+), 4 deletions(-)
diff --git a/tools/padjffs2/src/padjffs2.c b/tools/padjffs2/src/padjffs2.c
index 59c7625..6308292 100644
--- a/tools/padjffs2/src/padjffs2.c
+++ b/tools/padjf
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 1e61686..96b5a58 100644
--- a/target/linux/ar71xx/i
Signed-off-by: Yousong Zhou
---
target/linux/ar71xx/image/generic.mk | 23 ---
1 file changed, 12 insertions(+), 11 deletions(-)
diff --git a/target/linux/ar71xx/image/generic.mk
b/target/linux/ar71xx/image/generic.mk
index b8e70a4..1e61686 100644
--- a/target/linux/ar71xx/i
Hi Aaron,
On Sat, 2016-07-09 at 07:47 -0400, Aaron Z wrote:
> On Sat, Jul 9, 2016 at 4:37 AM, Alexey Brodkin
> wrote:
> >
> > 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
> > be
On Sat, Jul 9, 2016 at 4:37 AM, Alexey Brodkin
wrote:
> 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
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:
htt
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
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
Dear all
I found error on opkg update.
I just download imagebuilder from
https://downloads.lede-project.org/snapshots/targets/ipq806x/generic/lede-imagebuilder-ipq806x.Linux-x86_64.tar.bz2
When I run command make I got some error but make work ok.
But when I install firmware to router netgear r
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 c1f1cae..10c2aaa 100644
--- a/target/linux/ar71xx/i
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 marker
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: se
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
--- a/target/linux/ar71xx/image/
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:
- --
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
>>
>
> Thanks, Steven
>
> I a
On 9 July 2016 at 15:56, Steven Haigh wrote:
> Tested-by: Steven Haigh
>
Thanks, Steven
I am working on the jffs2 magic missing issue. Guess a RFCv3 will
follow shortly.
Cheers,
yousong
> On 9/07/2016 11:06 AM, Yousong Zhou wrote:
>> Signed-off-by: Yousong Zhou
>> ---
>> v2
Tested-by: Steven Haigh
On 9/07/2016 11:06 AM, Yousong Zhou wrote:
> Signed-off-by: Yousong Zhou
> ---
> v2 <- v1
>
> - Changed "DEVICE_VARS :=" to "DEVICE_VARS +="
>
> target/linux/ar71xx/image/generic.mk | 6 --
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/t
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(-)
>
> diff --git a/target/linux/ar71xx/image/generic.mk
> b/target/li
26 matches
Mail list logo
