Re: [OpenWrt-Devel] OpenWrt /etc/hotplug.d/button/00-wps

Hi, I have changed the script as below: MYDEV='eth0.2' ["$ACTION" = "pressed" -a "$BUTTON" = "BUT_2" -a "INTERFACE" = 'wan'] && { devstatus "$MYDEV" | grep '"up": true' && { echo "255" > /sys/devices/platform/leds-gpio/leds/db120:green:status/brightness }

Re: [OpenWrt-Devel] OpenWrt /etc/hotplug.d/button/00-wps

Hi, I have tried script: *["$ACTION" = "pressed" -a "$BUTTON" = "BUT_2"] && { ["${ACTION}" = "ifup" -a "${INTERFACE}" = "wan"] && {echo "" > /dev/console echo "SWITCH TO RJ45" > /dev/consoleecho "255" > /sys/devices/platform/leds-gpio/leds/db120:green:status/brightness

[OpenWrt-Devel] AR9344 OpenWRT LED Handling

Hi Everyone, I have configured the /etc/config/system file as below: config led 'led_status' option name 'STATUS' option interval '50' option sysfs 'db120:green:status' option default '0' option trigger 'netdev' option mode 'link' option dev 'eth0.2' so It is working fine whenever i connect

Re: [OpenWrt-Devel] Questions about "binutils: add binutils 2.25.1"

On 09/14/2015 02:24 PM, Alexey Brodkin wrote: > Hi Hauke, > > I noticed your change made in "toolchain/binutils" recently: > ->8- > http://git.openwrt.org/?p=openwrt.git;a=commit;h=fece50d94033c1dcfc3f290acbd428f9125c30aa > > binutils: add binutils 2.25.1 > > This

Re: [OpenWrt-Devel] r46816, remove unused crypt() algorithms -> switch to sha512?

Hi, Le 15 sept. 2015 01:40, "Felix Fietkau" a écrit : > > On 2015-09-15 00:22, Etienne Champetier wrote: > > Hi Felix, > > > > Maybe we should keep sha512 and switch to it? md5 is not best security > > practice these days. > I don't see the point. It's true that for file

Re: [OpenWrt-Devel] OpenWrt /etc/hotplug.d/button/00-wps

Please can anyone reply On Tue, Sep 15, 2015 at 2:16 PM, John kerry wrote: > Hi, > > I have written the following condition in /etc/hotplug.d/button/50-wps file > if [ "$ACTION" = "pressed" -a "$BUTTON" = "lanwifi" ]; then > echo "" > /dev/console > echo

Re: [OpenWrt-Devel] OpenWrt /etc/hotplug.d/button/00-wps

On 15 September 2015 at 09:17, John kerry wrote: > Please can anyone reply Is someone here your paid support with 1h response time? ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org

Re: [OpenWrt-Devel] OpenWrt /etc/hotplug.d/button/00-wps

* John kerry [15.09.2015 08:52]: > I have to write some condition in > /etc/hotplug.d/button/50-wps/ file > > I have to configure cat /etc/hotplug.d/button/00-wps file for following > condition: > if [ "$BUTTON" = "BTN_2" ] && [ "$ACTION" = "pressed" ]; then > > I have to

Re: [OpenWrt-Devel] OpenWrt /etc/hotplug.d/button/00-wps

Hi, I have written the following condition in /etc/hotplug.d/button/50-wps file if [ "$ACTION" = "pressed" -a "$BUTTON" = "lanwifi" ]; then echo "" > /dev/console echo "SWITCH TO RJ45" > /dev/console echo "255" >

Re: [OpenWrt-Devel] r46816, remove unused crypt() algorithms -> switch to sha512?

On 2015-09-15 08:20, Etienne Champetier wrote: > Hi, > > Le 15 sept. 2015 01:40, "Felix Fietkau" > a écrit : >> >> On 2015-09-15 00:22, Etienne Champetier wrote: >> > Hi Felix, >> > >> > Maybe we should keep sha512 and switch to it? md5 is not best

Re: [OpenWrt-Devel] [PATCH] extra configuration options for OpenVPN in init script

On 09/15/2015 07:20 AM, John Crispin wrote: > this package is maintained on github. please send a properly formatted > PR via github. also you patch is missing the SoB line and it is attached > and not inline. It seems the OpenVPN init script is not maintained in the packages [0] repository on

[OpenWrt-Devel] OpenWrt /etc/hotplug.d/button/00-wps

Hi, I have to write some condition in /etc/hotplug.d/button/50-wps/ file I have to configure cat /etc/hotplug.d/button/00-wps file for following condition: if [ "$BUTTON" = "BTN_2" ] && [ "$ACTION" = "pressed" ]; then I have to check eth0.1 if link is up then have ON status led otherwise OFF.

Re: [OpenWrt-Devel] OpenWrt /etc/hotplug.d/button/00-wps

On 15/09/2015 09:27, Rafał Miłecki wrote: > On 15 September 2015 at 09:17, John kerry wrote: >> Please can anyone reply > > Is someone here your paid support with 1h response time? although i find this emails annoying and funny at the same time we can probably assume that

[OpenWrt-Devel] Project specific settings

Hello, I'm quite new to OpenWrt and being faced with an existing build tree here. After reading nearly everything I could force Google to bubble it up to the top result pages, I'm still struggling with a simple question. Our build tree is full of custom patches to different packages, mainly in

Re: [OpenWrt-Devel] Project specific settings

On 15/09/2015 20:32, Rüdiger, Christoph wrote: > Hello, > > I'm quite new to OpenWrt and being faced with an existing build tree here. > After reading nearly everything I could force Google to bubble it up to the > top result pages, I'm still struggling with a simple question. > > Our build

Re: [OpenWrt-Devel] [PATCH] ar71xx: fix ar724x clock calculation

On Wed, 9 Sep 2015 11:19:31 +0800 Weijie Gao wrote: Hi, I'm working a bit on mainline support for the ATH79 and I would really like to see such patch making it there. I added this patch to my tree[1] with a few fixes to the log message. Would you mind submitting it to

Re: [OpenWrt-Devel] r46816, remove unused crypt() algorithms -> switch to sha512?

On 2015-09-15 10:00, Felix Fietkau wrote: > On 2015-09-15 08:20, Etienne Champetier wrote: >> Hi, >> >> Le 15 sept. 2015 01:40, "Felix Fietkau" > > a écrit : >>> >>> On 2015-09-15 00:22, Etienne Champetier wrote: >>> > Hi Felix, >>> > >>> > Maybe we

Re: [OpenWrt-Devel] [PATCH] ar71xx: add TP-LINK TL-WDR3320 v2 support

Oh, that's a mistake. 2015-09-15 4:03 GMT+08:00 John Crispin : > Hi, > > On 09/09/2015 16:56, Weijie Gao wrote: > > Signed-off-by: Weijie Gao > > this line should be the last line and not the first, i manually fixed > this during the merge > >

Re: [OpenWrt-Devel] i2c device not in /dev

2015-09-15 13:57 GMT+02:00 Baptiste Clenet : > 2015-09-14 20:17 GMT+02:00 John Crispin : >> >> >> On 14/09/2015 20:09, Daniel Golle wrote: >>> On Mon, Sep 14, 2015 at 07:47:08PM +0200, John Crispin wrote: On 14/09/2015 19:28, Baptiste Clenet wrote:

Re: [OpenWrt-Devel] [PATCH procd] move /dev/shm to /tmp/shm

I see procd got an update. Any reason this patch was left out? On Fri, 2015-09-11 at 13:05 -0700, Daniel Gimpelevich wrote: > Is there an ETA for merging this? > > On Sun, 2015-07-19 at 19:14 -0700, Daniel Gimpelevich wrote: > > I'm intending for this fix to be backported to CC as well. > > > >

[OpenWrt-Devel] [PATCH 1/2] oxnas: drop some unused sysupgrade code

First of all platform_do_upgrade_phase2 doesn't seem to be defined anywhere. Other than that platform_do_upgrade is not likely to be ever called. There is a call to nand_do_platform_check which triggers nand_upgrade_stage1 call with "exit 0" in it. Signed-off-by: Rafał Miłecki

[OpenWrt-Devel] [PATCH 2/2] oxnas: add platform_pre_upgrade for sysupgrade

We're in process of cleaning nand_do_platform_check. Currently is leaves a special mark in /tmp/sysupgrade-nand-path triggering some diffent code path in nand_upgrade_stage1. This can be a bit confusing. The plan is to have the check function only check the image and nothing else. Then platform

Re: [OpenWrt-Devel] OpenWrt /etc/hotplug.d/button/00-wps

Hi, I have added following condition but its not working: MYDEV='eth0' if [ "$ACTION" = "pressed" -a "$BUTTON" = "BUT_2" ] && { devstatus "$MYDEV" | grep '"up": true' && { echo "255" > /sys/devices/platform/leds-gpio/leds/db120:green:status/brightness } } fi Am i doing any mistake or

[OpenWrt-Devel] [PATCH] imx6: add platform_pre_upgrade for sysupgrade

We're in process of cleaning nand_do_platform_check. Currently is leaves a special mark in /tmp/sysupgrade-nand-path triggering some diffent code path in nand_upgrade_stage1. This can be a bit confusing. The plan is to have the check function only check the image and nothing else. Then platform

Re: [OpenWrt-Devel] OpenWrt /etc/hotplug.d/button/00-wps

Hi, If i am configuring below config under /etc/config/system file , The STATUS LED working fine based on eth0 link up/down. config led 'led_status' option name 'STATUS' option interval '50' option sysfs 'db120:green:status' option default '0' option

[OpenWrt-Devel] [PATCH] ipq806x: add platform_pre_upgrade for sysupgrade

We're in process of cleaning nand_do_platform_check. Currently is leaves a special mark in /tmp/sysupgrade-nand-path triggering some diffent code path in nand_upgrade_stage1. This can be a bit confusing. The plan is to have the check function only check the image and nothing else. Then platform

Re: [OpenWrt-Devel] [PATCH] ipq806x: add platform_pre_upgrade for sysupgrade

On 15/09/2015 14:18, Rafał Miłecki wrote: > We're in process of cleaning nand_do_platform_check. Currently is leaves > a special mark in /tmp/sysupgrade-nand-path triggering some diffent code > path in nand_upgrade_stage1. This can be a bit confusing. > > The plan is to have the check function

[OpenWrt-Devel] [PATCH] include: download.mk: If checkouts fail, attempt default download method

This will allow a more robust download system, especially in cases when building an older release where a source checkout system is gone. Signed-off-by: Pushpal Sidhu --- include/download.mk | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

Re: [OpenWrt-Devel] [PATCH 0/9] Support for three PowerCloud Systems devices

On 02/09/2015 12:08, Daniel Dickinson wrote: > The following patch series adds support for three PowerCloud devices. > The patches have been reworked from the previous bunged up iteration > and have been tested on the actual devices which are currently in use. > > There is, however, one

Re: [OpenWrt-Devel] Project specific settings

> what kind of changes are we talking about ? just config file stuff or > big changes to how stuff is built and installed ? >From what I've seen so far, it is about half in the package Makefiles, so how >stuff is built and installed. The other half is shared between changes in the >code and

Re: [OpenWrt-Devel] [PATCH v2] ar71xx: Add UBNT airGateway Pro support

Hi On 21/08/2015 09:27, Matthew Reeve wrote: > This patch adds kernel and userspace support for the Ubiquiti Networks > airGateway Pro. > > v2: Modify file bases so that git apply will apply it. the change log should go below the tear line > Signed-off-by: Matthew Reeve > which should be

[OpenWrt-Devel] [PATCH] imx6: fix platform checking

Fix platform checking when configuring networks and when doing sysupgrade. Signed-off-by: Pushpal Sidhu --- target/linux/imx6/base-files/etc/uci-defaults/02_network | 12 ++-- target/linux/imx6/base-files/lib/upgrade/platform.sh | 4 ++-- 2 files changed, 8

[OpenWrt-Devel] [PATCH] uboot-envtools: Add Gateworks Ventana Support

Signed-off-by: Tim Harvey Signed-off-by: Pushpal Sidhu --- package/boot/uboot-envtools/files/imx6 | 11 +++ 1 file changed, 11 insertions(+) diff --git a/package/boot/uboot-envtools/files/imx6 b/package/boot/uboot-envtools/files/imx6 index

[OpenWrt-Devel] ralink: RX buffer length setting in ralink_soc_eth.c

Hi, I am currently searching for the reason that MT7621a doesn't want to receive 1526 byte large ethernet frames (1500 mtu, 14 eth hdr, 4 byte outer vlan hdr, 4 byte inner vlan hdr, 4 byte fcs). One thing I found during my search was the odd looking way the PDMA Rx descriptors were written.

Re: [OpenWrt-Devel] OpenWrt /etc/hotplug.d/button/00-wps

* John kerry [15.09.2015 13:44]: > Hi, > > I have added following condition but its not working: > > MYDEV='eth0' > > if [ "$ACTION" = "pressed" -a "$BUTTON" = "BUT_2" ] && { remove the 'if' > devstatus "$MYDEV" | grep '"up": true' && { > echo "255" > >

Re: [OpenWrt-Devel] i2c device not in /dev

2015-09-14 20:17 GMT+02:00 John Crispin : > > > On 14/09/2015 20:09, Daniel Golle wrote: >> On Mon, Sep 14, 2015 at 07:47:08PM +0200, John Crispin wrote: >>> On 14/09/2015 19:28, Baptiste Clenet wrote: Hi, I'm using a MT7628 chip and I try to implement an I2C

Re: [OpenWrt-Devel] OpenWRT www version banner a security risk

Mine vote for generally _not do anything_, Defaults are safe as pointed out here few times... We can not start to babysit users from themselves... We can guide, we can help and so on, but it's still end user responsibility when opening port(s) to WAN, or securing access in a big LAN/VPN/VLAN/etc