Re: [OpenWrt-Devel] [PATCH] Use build suffix on build_dir paths

On 10/04/12 08:04, Tathagata Das wrote: > diff -Naur a/include/kernel.mk b/include/kernel.mk > --- a/include/kernel.mk 2012-04-05 13:10:50.0 +0530 > +++ b/include/kernel.mk 2012-04-06 16:09:18.0 +0530 > @@ -33,7 +33,7 @@ > PATCH_DIR ?= ./patches$(if $(wildcard > ./

[OpenWrt-Devel] [PATCH] Use build suffix on build_dir paths

Hi, This patch helps to use build suffix on build_dir paths if it is defined else use subtarget. Defining model names on build suffix helps in building one or more pre-defined configurations (.config) of same platform in same build path without doing a clean. This preserves each models target

[OpenWrt-Devel] [Patch v4] BCMA - Enable use of IRQ6

Changes since v3: Fixed two references to bcma_core_mips_irq in driver_pci_host.c Signed-off-by: Nathan Hintz --- /dev/null 2012-04-07 22:03:23.120698218 -0700 +++ target/linux/brcm47xx/patches-3.2/235-bcma-dont-expose-mips-irq.patch 2012-04-09 20:18:16.988877496 -0700 @@ -0,0 +1,95 @@

Re: [OpenWrt-Devel] [PATCH] firewall: default firewall rules tweak

2) - (l / 2)); // fix list of which name/vals are malloced } xml->flags&= ~EZXML_DUP; // clear strdup() flag return xml; -- next part -- An HTML attachment was scrubbed... URL:<http://lists.openwrt.org/pipermail/openwrt-devel/attachments

[OpenWrt-Devel] [PATCH] e2fsck status reaping fix

This patch corrects a status reaping issue in e2fsck.sh, with e2fsck piped against logger. Signed-off-by: Lukasz Golec-Biernat --- Index: e2fsck.sh === --- e2fsck.sh   (revision 31048) +++ e2fsck.sh   (working copy) @@ -5,6 +5,7 @@

Re: [OpenWrt-Devel] Lost connection to OpenWRT router

Hi, 09.04.2012 15:45, Jo-Philipp Wich: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 http://wiki.openwrt.org/doc/howto/generic.failsafe Alternatively, fresh "installation using the TFTP method" using reset button as described in http://wiki.openwrt.org/toh/netgear/wndr3700 should also work v

[OpenWrt-Devel] [PATCH] ezxml segfault while removing attribute with ezxml_set_attr

This patch fixes a potential segfault when removing an attribute with ezxml_set_attr. Complete description can be found here: http://sourceforge.net/tracker/?func=detail&aid=1653391&group_id=122291&atid=693016 Signed-off by: Robert Hazbun r...@icontrol.com ---

Re: [OpenWrt-Devel] [PATCH] zabbix 1.8.11 version bump

Please ignore this patch, i have discovered a severe memory leak in zabbix_agentd 1.8.11 that rapidly eat all memory available on the device! I now i am trying to enable ipv6 on 1.6 version I am checking if 1.6 is also affected by the memory leak I'll came up with a new version bump when they wil

Re: [OpenWrt-Devel] [PATCH] update kernel-version.mk

Hi Jim, On 4 April 2012 17:30, Jim Cromie wrote: > add 3.2.14, 3.3.1, restore entry for 3.2.13. > ISTM theres not a reason to drop 3.2.13, > I think some platforms are still using it. There are no platforms using 3.2.12; I had previously updated all of them to use 3.2.13 (and just now 3.2.14),

[OpenWrt-Devel] [PATCH] Upgrade nginx to 1.0.14

Upgrade nginx to 1.0.14. Changelog: http://nginx.org/en/CHANGES-1.0 This upgrade includes a fix for a major security vulnerability, CVE-2012-1180. Signed-off-by: Mark Mentovai --- Index: packages/net/nginx/Makefile === --- packag

Re: [OpenWrt-Devel] Lost connection to OpenWRT router

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 http://wiki.openwrt.org/doc/howto/generic.failsafe -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk+Cy+EACgkQdputYINPTPMQkwCfXuYbhT1uSzxZ8rKTdip2NoG/ IZ0An1

[OpenWrt-Devel] Lost connection to OpenWRT router

Dear all, I have a Netgear WNDR3700v2 with OpenWRT. The problem is that I created a custom boot script as explained here (http://wiki.openwrt.org/doc/techref/initscripts) and after rebooting I was not able to connect to the router. What the custom script contained was the following: ---

Re: [OpenWrt-Devel] [PATCH] firewall: default firewall rules tweak

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi. > 1. Following "deny by default" principle, change the default section > policy to DROP. The firewall package already add rules to allow all > lo traffic, there should be no impact to user. NACK. If at all it should be reject, not drop - to at le

[OpenWrt-Devel] [PATCH] firewall: default firewall rules tweak

This change try to harden the security of default firewall rules 1. Following "deny by default" principle, change the default section policy to DROP. The firewall package already add rules to allow all lo traffic, there should be no impact to user. 2. harden the allow dhcp renew rule, sour