Re: [OpenWrt-Devel] how enable the scp service ?

2014-03-12 Thread Alan.Hoo
PS, the winscp program login successfully but exit very soon. From: openwrt-devel-boun...@lists.openwrt.org [mailto:openwrt-devel-boun...@lists.openwrt.org] On Behalf Of Alan.Hoo Sent: Thursday, March 13, 2014 2:43 PM To: 'OpenWrt Development List' Subject: [OpenWrt-Devel] how enable the sc

[OpenWrt-Devel] how enable the scp service ?

2014-03-12 Thread Alan.Hoo
hello everyone I've encountered a error during use winscp for login to my router. it's seems scp service disbled. what's the name of scp service on OpenWRT ? BR Alan.Hoo,Code Monkey MSFT ___ openwrt-devel mailing list openwrt-de

Re: [OpenWrt-Devel] [PATCH] dropbear: update to 2014.63

2014-03-12 Thread Catalin Patulea
ping?? On Sat, Mar 1, 2014 at 4:05 AM, Catalin Patulea wrote: > ping > > On Mon, Feb 24, 2014 at 1:02 AM, Catalin Patulea wrote: >> Upstream changelog: >> https://matt.ucc.asn.au/dropbear/CHANGES >> >> This adds elliptic curve cryptography (ECC) support as an option, disabled >> by default. >> >

Re: [OpenWrt-Devel] Buildbot confused?

2014-03-12 Thread Travis Kemen
I have been working on getting some new infrastructure brought online and needed to change the configuration. It appears there is a bug in this version of buildbot when doing a reconfig. I have restarted it now so we should be back in business. Thanks, Travis On Wed, Mar 12, 2014 at 2:10 PM, Ha

[OpenWrt-Devel] [PATCH] ath10k: update firmware and allow choice between AP and STA firmwares

2014-03-12 Thread Matti Laakso
This patch updates ath10k firmware to the latest version, changes the default firmware to be the one optimized for access point operation, and introduces a configuration option to choose the client-optimized firmware instead during build time. Signed-off-by: Matti Laakso --- Index: trunk/package

[OpenWrt-Devel] Buildbot confused?

2014-03-12 Thread Hannu Nyman
Looks like the buildbot is confused... There are only a few March 12th build attemps and still several buildslaves sit idle. Compared to the status a few hours ago, it looks like all not yet started builds have been removed from the queue and then buildbot simply waits and says that 22.5 hours

Re: [OpenWrt-Devel] [RFC] netifd: Reload proto on bridge member add/remove

2014-03-12 Thread Felix Fietkau
On 2014-03-12 14:03, Helmut Schaa wrote: > Main use-case is to renew/restart DHCP if a bridge member is added/removed. > > Signed-off-by: Helmut Schaa > --- > > Maybe it is worth to add another PROTO_CMD_RENEW or something that is more > lightweight instead of running a full setup again? Yes, pl

Re: [OpenWrt-Devel] bridge operation without physical port, 'bridge_empty'

2014-03-12 Thread Conor O'Gorman
On 12/03/14 12:54, Conor O'Gorman wrote: I'm trying to get a 'virtual' bridge up to support vlan tagging. But I am having great difficulty in making this work. I tried trunk for the 'bridge_empty' setting, but it's not doing it for me. Can I use some other sort of dummy interface to force it up?

[OpenWrt-Devel] [RFC] netifd: Reload proto on bridge member add/remove

2014-03-12 Thread Helmut Schaa
Main use-case is to renew/restart DHCP if a bridge member is added/removed. Signed-off-by: Helmut Schaa --- Maybe it is worth to add another PROTO_CMD_RENEW or something that is more lightweight instead of running a full setup again? bridge.c| 4 device.h| 3 +++ interface.c | 3 +

[OpenWrt-Devel] bridge operation without physical port, 'bridge_empty'

2014-03-12 Thread Conor O'Gorman
Hi, I'm trying to get a 'virtual' bridge up to support vlan tagging. But I am having great difficulty in making this work. I tried trunk for the 'bridge_empty' setting, but it's not doing it for me. Problem is with 'br-lan' not wanting to change to up state: config interface 'lan' op

Re: [OpenWrt-Devel] [PATCHv2] openssl: Fix x86_64 build on some 64bit host systems

2014-03-12 Thread Felix Fietkau
On 2014-03-11 17:42, Helmut Schaa wrote: > On some build hosts openssl fails to install since openssl installs itself > into > lib64 while the openwrt Makefile expects the libs to end up in lib. > > install -m0644 > .../openwrt/build_dir/target-x86_64_uClibc-0.9.33.2/openssl-1.0.1e/ipkg-install/

Re: [OpenWrt-Devel] [PATCH] [lantiq] V2: add support for Astoria ARV7519RW.

2014-03-12 Thread José Vázquez
2014-03-12 9:31 GMT+01:00, John Crispin : > hi, > > i am starting to wonder if we should to runtime detection of the fw blob > to use ... i.e. indicate in the dts file if we want 11g or 22fe firmware > and let the code figure out the version > > John > > > On 12/03/2014 09:29, José Vázquez Fern

Re: [OpenWrt-Devel] [PATCH] [lantiq] Add support for Astoria ARV7519RW.

2014-03-12 Thread José Vázquez
2014-03-12 9:40 GMT+01:00, José Vázquez : > 2014-03-10 12:26 GMT+01:00, José Vázquez Fernández > : >> Add support for Astoria ARV7519RW. >> >> These patches add support for the Astoria ARV7519RW aka Livebox 2.1 >> The PCI and PCIe interfaces have been disabled. Also, because there are >> two revisi

Re: [OpenWrt-Devel] [PATCH] [lantiq] Add support for Astoria ARV7519RW.

2014-03-12 Thread José Vázquez
2014-03-10 12:26 GMT+01:00, José Vázquez Fernández : > Add support for Astoria ARV7519RW. > > These patches add support for the Astoria ARV7519RW aka Livebox 2.1 > The PCI and PCIe interfaces have been disabled. Also, because there are > two revisions of this board with differen GPHY firmwares, two

Re: [OpenWrt-Devel] [PATCH] [lantiq] V2: add support for Astoria ARV7519RW.

2014-03-12 Thread John Crispin
hi, i am starting to wonder if we should to runtime detection of the fw blob to use ... i.e. indicate in the dts file if we want 11g or 22fe firmware and let the code figure out the version John On 12/03/2014 09:29, José Vázquez Fernández wrote: > Add support for Astoria ARV7519RW. > > Thes

[OpenWrt-Devel] [PATCH] [lantiq] V2: add support for Astoria ARV7519RW.

2014-03-12 Thread José Vázquez Fernández
Add support for Astoria ARV7519RW. These patches add support for the Astoria ARV7519RW aka Livebox 2.1 The PCI and PCIe interfaces have been disabled. Also, because there are two revisions of this board with different GPHY firmwares, two targets were defined. V2: rewrote partitions to work with an