On 25 September 2014 12:06, 张钊 wrote:
> I’ve built a firmware from git.openwrt.org/openwrt.git known as CHAOS
> CALMER (Bleeding Edge, r42657) for my MTK7620n board, it works well except
> this weird problem.
>
> When I enable wifi, then trying to use iw dev wlan0 scan or trying to add
> secondar
I’ve built a firmware from git.openwrt.org/openwrt.git known as CHAOS CALMER
(Bleeding Edge, r42657) for my MTK7620n board, it works well except this weird
problem.
When I enable wifi, then trying to use iw dev wlan0 scan or trying to add
secondary AP from luci interface, my board will reboot
Il 25/09/2014 01:31, Bill ha scritto:
>
> OK, at least I know what I need to do... does anyone know if all the Ubiquiti
> "M" devices are going to become "XW" models?
>
Yes, no more XM revision are being manufactured. The SoC previously in use
stopped production somewhere at the end of 2013.
St
Nico-
You are completely correct - thank you!
I booted one up in AirOS and it says the firmware version is XW5.5.9.
OK, at least I know what I need to do... does anyone know if all the
Ubiquiti "M" devices are going to become "XW" models?
Thanks again,
Bill
On 9/24/2014 9:54 AM, cholin wro
Ben-
Thank you!
I did try the NanoStation image, with the same results. Normally either
image will flash onto the LOCO, but the NanoStation image has the
"extra" Ethernet port enabled, which creates a bit of confusion.
Besides, I believe the LOCO is a 1x1 (like the Bullet), not a 2x2 (like
t
On 09/24/2014 10:57 PM, Łukasz Baj wrote:
> Right now these libraries are in oldpackages repository. Currently I'm
> working with some project which uses this stuff to handle Apple devices
> in OpenWrt environment. I was able to update all that libraries and I
> can take care of maintain them.
>
>
Right now these libraries are in oldpackages repository. Currently I'm
working with some project which uses this stuff to handle Apple devices in
OpenWrt environment. I was able to update all that libraries and I can take
care of maintain them.
Is anybody interested?
Regards,
Lukasz
> Whats the size increase due to that?
>
> ~ Jow
Here is a brief comparison about binary and package size
Tested on AR9330, mips, TL MR3220v2
Before applying sha2-hmac patch
root@OpenWrt:~# du -sh $(which dropbear)
161.5K /usr/sbin/dropbear
After applying sha2-hmac patch
root@OpenWrt:~# du -sh
Am 24.09.2014 um 16:15 schrieb Cristian Morales Vega:
> It's needed for OpenSSL to find them.
>
> Signed-off-by: Cristian Morales Vega
> ---
> package/system/ca-certificates/Makefile | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/package/system/ca-certificates/Makefile
> b/package
Il 24/09/2014 18:30, Gert Doering ha scritto:
>
> "OpenVPN Upstream" would recommend to go up to HEAD in git/master, aka
> 9048d50b0a27a724ad088dc4904eb4888b0bca87 - this is all "openvpn-devel"
> anyway, but what we have in-tree right now has seen some more minor
> bugfixes in SSL land (nothing sec
Maybe you have one of these new Loco M5 XW? Support for that device has
been added with r42549 (9 days ago) [1] and is only available in current
trunk (unfortunately not in barrier breaker rc3).
Regards
Nico
[1]
http://git.openwrt.org/?p=openwrt.git;a=commit;h=3d217029ea89de6520e01a471b6dc31924f1
I've been flashing the Nanostation Loco M5's just fine with the Nanostation
M image for 3 years without issue, and I never tried the Bullet M image.
Although, the Loco M5's I've flashed are at least 1.5years old at present.
Can you try flashing
openwrt-ar71xx-generic-ubnt-nano-m-squashfs-factory.bi
Hi,
On Wed, Sep 24, 2014 at 01:01:42AM +0200, Stefano De Carlo wrote:
> r35529 updated polarssl to v1.2.x, introducing a compiling regression in
> package openvpn-devel-polarssl.
>
> This patch updates openvpn-devel to the commit that added support for the API
> changes introduced in PolarSSL-1
I just got 5 LOCO M5 units that won't run OpenWRT. They are datestamped
1422K; when I try to flash them, they give me:
received ERROR
I am using the Bullet M image
(openwrt-ar71xx-generic-ubnt-bullet-m-squashfs-factory.bin), flashing
with tftp in binary mode.
I have one other LOCO M5 with
On 24 September 2014 15:15, Cristian Morales Vega wrote:
> It gives us the tools to work with certificates.
Ignore it, has some problems. It worked on my machine because it was
using my system copy of openSSL.
I will send new patches.
___
openwrt-devel
On 2014-09-20 03:05, Nikos Mavrogiannopoulos wrote:
On Fri, 2014-09-19 at 18:39 -0700, David Lang wrote
Well being used to something bad, doesn't mean things cannot get better.
Routers (to which I have some experience at), rarely have processes
running that wouldn't matter if they are randomly
Sorry, for the typo in my last mail. Must be 0x30 not 0x300
Current VG3503J image is not working because of a too small kernel
partition.
This will fix it.
Signed-off-by: Joerg Hollmann
diff -Naur a/target/linux/lantiq/dts/VG3503J.dtsi
b/target/linux/lantiq/dts/VG3503J.dtsi
--- a/tar
Current VG3503J image is not working because of a too small kernel
partition.
This will fix it.
Signed-off-by: Joerg Hollmann
diff -Naur a/target/linux/lantiq/dts/VG3503J.dtsi
b/target/linux/lantiq/dts/VG3503J.dtsi
--- a/target/linux/lantiq/dts/VG3503J.dtsi 2014-09-24
14:56:08.117424013
Signed-off-by: Cristian Morales Vega
---
package/network/utils/curl/Makefile | 1 +
1 file changed, 1 insertion(+)
diff --git a/package/network/utils/curl/Makefile
b/package/network/utils/curl/Makefile
index 0bb8323..2c6e6ea 100644
--- a/package/network/utils/curl/Makefile
+++ b/package/network
It's needed for OpenSSL to find them.
Signed-off-by: Cristian Morales Vega
---
package/system/ca-certificates/Makefile | 3 +++
1 file changed, 3 insertions(+)
diff --git a/package/system/ca-certificates/Makefile
b/package/system/ca-certificates/Makefile
index cd29c0a..492cbb5 100644
--- a/pac
It gives us the tools to work with certificates.
Signed-off-by: Cristian Morales Vega
---
package/libs/openssl/Makefile | 19 +++
1 file changed, 19 insertions(+)
diff --git a/package/libs/openssl/Makefile b/package/libs/openssl/Makefile
index 4b386ab..df962fc 100644
--- a/packa
.crt is a generic extension that doesn't specify the encoding.
OpenSSL's c_rehash expects the .pem extension.
Signed-off-by: Cristian Morales Vega
---
package/system/ca-certificates/Makefile| 2 +-
.../patches/010-pem_extension.patch| 41 ++
2 fil
Hello there,
not sure how it works with patches in OpenWRT, so I try all channels… I noticed
that unexporting GPIOs is broken on ramips (gpio-ralink.c). There is a trac
issue with some more details, and I already added the patch there:
https://dev.openwrt.org/ticket/14309
Here it is again for
El 22/09/14 09:54, Luca Olivetti ha escrit:
> El 22/09/14 01:51, Claudio Leite ha escrit:
>
>> I'm not sure the MediaTek driver still uses the old format from the
>> Ralink driver. If so, this might be helpful:
>>
>> https://github.com/WRTnode/openwrt-packages/blob/master/ralink/ralink-wifi/files/
The build system sets a make variable TAR_OPTIONS to the unpacking
command, i.e. "-xf -". Now if an environment variable with the same
name is set, the make variable is automatically exported to the
environment. The make variable is added to the tar command in the
makefile, and tar adds the environ
25 matches
Mail list logo
