On 23/06/2014 20:22, Paul Blazejowski wrote:
Hello list,
Have found bug in the ubifs component when mounting images on
wndr3700v4/4300 routers. This happens in trunk builds after r41130
but does not happen before r41118.
Please take a look at bug https://dev.openwrt.org/ticket/16803 i
On 24 June 2014 01:17, Paul Sokolovsky pmis...@gmail.com wrote:
Intuitively, this would look like problem with bridging (eth0.0 -
br-lan works, but the other direction doesn't), but brctl looks as
usual:
root@OpenWrt:~# brctl show
bridge name bridge id STP enabled
Guys if you need a guinea pig for testing the WNDR4300's I am happy to assist.
Since introducing the sysupgrade features, upon a router reboot all settings
are restored to factory defaults.
Also, is this mail list a channel that reaches most or all developers?
Hello,
On Tue, 24 Jun 2014 10:32:31 +0200
Rafał Miłecki zaj...@gmail.com wrote:
On 24 June 2014 01:17, Paul Sokolovsky pmis...@gmail.com wrote:
Intuitively, this would look like problem with bridging (eth0.0 -
br-lan works, but the other direction doesn't), but brctl looks as
usual:
On 24/06/2014 10:55, Adam Kuklycz wrote:
Guys if you need a guinea pig for testing the WNDR4300’s I am happy
to assist. Since introducing the sysupgrade features, upon a
router reboot all settings are restored to factory defaults.
ok, i'll look into it today. i think daniel already pushed
On 24 June 2014 11:23, Paul Sokolovsky pmis...@gmail.com wrote:
config switch_vlan 'eth0_0'
option device 'eth0'
option vlan '0'
option ports '1 2 3 4 5'
config switch_vlan 'eth0_1'
option device 'eth0'
option vlan '1'
option ports '0 5'
Old OpenWrt releases were using network configs that are not valid
anymore. They specified tagging in a different way (or were not tagging
CPU at all), used VID 0 which is a reserved value.
Porting old configs would be tricky (changing VIDs, interfaces names,
ports tagging), so it's probably wiser
Netifd is crashing when when a network reload (ubus call network reload) is
handled during the parsing of the network config in the function
config_init_all (called from main) at startup.
As an ubus_invoke function call is issued when the interfaces are created; ubus
will also process the
On 2014-06-24 01:17, Paul Sokolovsky wrote:
Hello,
I upgraded my Asus WL-500g Deluxe from 10.03.1 to today's daily build
of trunk (BARRIER BREAKER (Bleeding Edge, r41302)) to test fix for
issue https://dev.openwrt.org/ticket/7552 .
After upgrade, all WiFi clients work ok. However, all
On 2014-06-23 23:39, Etienne CHAMPETIER wrote:
The idea is to gradually fix the packages
Signed-off-by: Etienne CHAMPETIER etienne.champet...@free.fr
---
package/libs/gettext-full/Makefile|1 +
package/network/utils/comgt/Makefile |1 +
Hello,
On Tue, 24 Jun 2014 12:08:04 +0200
Rafał Miłecki zaj...@gmail.com wrote:
On 24 June 2014 11:23, Paul Sokolovsky pmis...@gmail.com wrote:
config switch_vlan 'eth0_0'
option device 'eth0'
option vlan '0'
option ports '1 2 3 4 5'
config switch_vlan
Hi,
That commit was intended to fix a bug report by me. I also attached a patch
with my issue:
diff --git a/package/netifd/files/sbin/ifup b/package/netifd/files/sbin/ifup
index af3aaa8..15c0c8e 100755
--- a/package/netifd/files/sbin/ifup
+++ b/package/netifd/files/sbin/ifup
@@ -35,7 +35,7 @@
hi
- Mail original -
De: Felix Fietkau n...@openwrt.org
À: Etienne CHAMPETIER etienne.champet...@free.fr,
openwrt-devel@lists.openwrt.org
Envoyé: Mardi 24 Juin 2014 12:48:37
Objet: Re: [OpenWrt-Devel] [RFC 3/3] PKG_CHECK_FORMAT_SECURITY: disable the
check for the failing packages
On 2014-06-24 12:46, Hans Dedecker wrote:
Netifd is crashing when when a network reload (ubus call network reload) is
handled during the parsing of the network config in the function
config_init_all (called from main) at startup.
As an ubus_invoke function call is issued when the interfaces
Hi,
On 21/06/2014 17:10, xf...@credosemi.com wrote:
From: Xiongfei Guo xf...@credosemi.com
- Support set VLAN ID of each vlan. - Support untag feature. -
Replace register address with C MACRO. - There are 8 ports for
MT7530 actually.
Signed-off-by: Xiongfei Guo xf...@credosemi.com
on
Hi,
On 22/06/2014 22:20, Forest Crossman wrote:
diff --git a/target/linux/ar71xx/files/arch/mips/ath79/nvram.c
b/target/linux/ar71xx/files/arch/mips/ath79/nvram.c index
43911b8..41c3542 100644 ---
a/target/linux/ar71xx/files/arch/mips/ath79/nvram.c +++
hi,
I'm test it on Mercury MW305R with a modified dts file for RT-N14U. Maybe I
can give a dts patch for this board later.
Actually, MT7530 is the ethernet switch inside the MTK MT7620A/N. So you
can try it with any MT7620 based board.
Xiongfei Guo
Credo Semi.
On Tue, Jun 24, 2014 at 8:54 PM,
The MAC as it's stored the u-boot environment looks like
'ethaddr=XX:XX:XX:XX:XX:XX', so to get the other functions to parse
the MAC correctly, I had to get rid of the quotes before and after the
MAC. There might be a better way to do it, but this method didn't seem
too horrible. All this function
Hi,
Applied the ubus patch but netifd_reload is still called while
config_init_all is processing the config and thus leading to a crash
when netifd_reload is done
Added extra traces in netifd which confirms this :
un 24 16:00:44 OpenWrt daemon.notice netifd: config_init_all : Enter
Jun 24
Hi John,
yes i know my way around ;-) so please do share the patch so i can
test...
Thank you,
-paul
On Tue, 2014-06-24 at 09:36 +0200, John Crispin wrote:
On 23/06/2014 20:22, Paul Blazejowski wrote:
Hello list,
Have found bug in the ubifs component when mounting images on
On 24/06/2014 15:54, Xiongfei(Alex) GUO wrote:
hi,
I'm test it on Mercury MW305R with a modified dts file for
RT-N14U. Maybe I can give a dts patch for this board later.
Actually, MT7530 is the ethernet switch inside the MTK MT7620A/N.
So you can try it with any MT7620 based board.
it
Hi Hans,
thanks for testing. I uploaded a new patch (same URL), which uses a
uloop timer to defer processing of incoming invoke msgs.
Note that this changes the ubus context data structure and thus affects
everything that depends on ubus, so it's better to reflash after rebuilding.
- Felix
On
Old OpenWrt releases were using network configs that are not valid
anymore. They were specifying ports tagging in a different way (or were
not tagging CPU at all) and were using VID 0 which is a reserved value.
Modifying network configuration to apply all needed changes would be
pretty tricky.
Signed-off-by: Etienne CHAMPETIER etienne.champet...@free.fr
---
package/boot/rbcfg/src/main.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/package/boot/rbcfg/src/main.c b/package/boot/rbcfg/src/main.c
index 5614a6c..b7cf79f 100644
--- a/package/boot/rbcfg/src/main.c
The idea is to gradually fix the packages
Signed-off-by: Etienne CHAMPETIER etienne.champet...@free.fr
---
package/libs/gettext-full/Makefile|1 +
package/network/utils/comgt/Makefile |1 +
package/network/utils/iperf/Makefile |1 +
The idea is to get rid of
http://en.wikipedia.org/wiki/Uncontrolled_format_string
by using -Wformat -Werror=format-security by default
Signed-off-by: Etienne CHAMPETIER etienne.champet...@free.fr
---
include/package.mk |4
1 files changed, 4 insertions(+), 0 deletions(-)
diff --git
Hi,
thanks for the patch, i just tested it on the external switch and it
works there as well (but you already knew that i guess :-) ). i added
the patch to my local queue and will push later on today.
John
___
openwrt-devel mailing list
Hi,
On 23/06/2014 20:22, Paul Blazejowski wrote:
Hello list,
Have found bug in the ubifs component when mounting images on
wndr3700v4/4300 routers. This happens in trunk builds after r41130
but does not happen before r41118.
Please take a look at bug
John,
Yes i use the reset with pin and from there i tftp the original firmware
from netgear after that i go to the gui and upload the open-wrt image
because the router will not accept the wndr3700v4 image (there's a
cosmetic fix for that, i created a patch that someone from the forums
has sent
This is much appreciated, but what is really needed for upstream merge
is converting the target to device tree usage.
On Tue, 2014-06-10 at 04:29 +0400, Sergey Ryazanov wrote:
This series is an attempt to cleanup checkpatch generated warnings and errors
to make AR231x patches suitable for
2014-06-24 12:15 GMT-07:00 Daniel Gimpelevich
dan...@gimpelevich.san-francisco.ca.us:
This is much appreciated, but what is really needed for upstream merge
is converting the target to device tree usage.
Well, that is all debatable, Device Tree only makes sense if there are:
- new
Hi Sergey,
2014-06-09 17:29 GMT-07:00 Sergey Ryazanov ryazanov@gmail.com:
This series is an attempt to cleanup checkpatch generated warnings and errors
to make AR231x patches suitable for upstream merge.
You might want to take a look at the recent SPI-NOR framework that MTD
came up with,
On 06/24/2014 07:38 PM, Florian Fainelli wrote:
2014-06-24 12:15 GMT-07:00 Daniel Gimpelevich
dan...@gimpelevich.san-francisco.ca.us:
This is much appreciated, but what is really needed for upstream merge
is converting the target to device tree usage.
Well, that is all debatable, Device
Hi again,
thanks for the tftp fix, flushing just became so much faster and easier.
Tested trunk r41336 after your jffs2 fix and the image boots fine,
restored my configuration changes, rebooted the router and all changes
are saved now. I will post the working dmesg to the ticket at
sorry i meant https://dev.openwrt.org/ticket/16803 the previous one is
closed for good ;-)
On Tue, 2014-06-24 at 16:25 -0400, Paul Blazejowski wrote:
Hi again,
thanks for the tftp fix, flushing just became so much faster and easier.
Tested trunk r41336 after your jffs2 fix and the image
On Tue, 2014-06-24 at 12:38 -0700, Florian Fainelli wrote:
I think AR231x has none of those, it's an End of Life platform, the
code base has been mostly static and well know for a while, so I would
argue that Device Tree should not be made a requirement here as it
will just delay Sergey's
On 24/06/2014 22:25, Paul Blazejowski wrote:
Hi again,
thanks for the tftp fix, flushing just became so much faster and
easier.
Tested trunk r41336 after your jffs2 fix and the image boots fine,
restored my configuration changes, rebooted the router and all
changes are saved now. I
i get The uploaded image file does not contain a supported format. Make
sure that you choose the generic image format for your platform. from
web interface.
this is what i have:
-rw-r--r-- 1 diffie diffie 8919040 2014-06-24 15:58
bin/ar71xx/openwrt-ar71xx-nand-wndr3700v4-squashfs-sysupgrade.tar
2014-06-24 13:30 GMT-07:00 Daniel Gimpelevich
dan...@gimpelevich.san-francisco.ca.us:
On Tue, 2014-06-24 at 12:38 -0700, Florian Fainelli wrote:
I think AR231x has none of those, it's an End of Life platform, the
code base has been mostly static and well know for a while, so I would
argue that
On Tue, 2014-06-24 at 13:51 -0700, Florian Fainelli wrote:
For the watchdog driver, if we have access to a revision register we
can read at runtime, then we could use a separate platform driver name
(e.g: ar2315-wdt vs ar2317-wdt) that would lead to either two separate
drivers to get
patch for package feed ready to merge
https://github.com/openwrt/packages/pull/57
- Mail original -
De: Etienne CHAMPETIER etienne.champet...@free.fr
À: openwrt-devel@lists.openwrt.org
Cc: Etienne CHAMPETIER etienne.champet...@free.fr
Envoyé: Mardi 24 Juin 2014 18:12:47
Objet:
On 24/06/2014 22:43, Paul Blazejowski wrote:
i get The uploaded image file does not contain a supported format.
Make sure that you choose the generic image format for your
platform. from web interface.
this is what i have:
-rw-r--r-- 1 diffie diffie 8919040 2014-06-24 15:58
On Tue, 2014-06-24 at 23:15 +0200, John Crispin wrote:
On 24/06/2014 22:43, Paul Blazejowski wrote:
i get The uploaded image file does not contain a supported format.
Make sure that you choose the generic image format for your
platform. from web interface.
this is what i have:
2014-06-24 23:39 GMT+04:00 Florian Fainelli flor...@openwrt.org:
Hi Sergey,
2014-06-09 17:29 GMT-07:00 Sergey Ryazanov ryazanov@gmail.com:
This series is an attempt to cleanup checkpatch generated warnings and errors
to make AR231x patches suitable for upstream merge.
You might want to
2014-06-24 23:38 GMT+04:00 Florian Fainelli flor...@openwrt.org:
2014-06-24 12:15 GMT-07:00 Daniel Gimpelevich
dan...@gimpelevich.san-francisco.ca.us:
This is much appreciated, but what is really needed for upstream merge
is converting the target to device tree usage.
Well, that is all
2014-06-24 15:30 GMT-07:00 Sergey Ryazanov ryazanov@gmail.com:
2014-06-25 0:30 GMT+04:00 Daniel Gimpelevich
dan...@gimpelevich.san-francisco.ca.us:
plus the AR2317 watchdog operates completely differently from the
AR2315 one.
Hm, I am missed that. Thank you Daniel for your note.
What
On Tue, 2014-06-24 at 15:33 -0700, Florian Fainelli wrote:
I think, if the differences we have to abstract for are (hopefully)
limited to GPIOs and the watchdog driver differences, we can have a
small data-base in the kernel, nobdoy should hopefully yell at you for
doing that. If we are
So I recently decided to compile my own OpenWRT images, and I have a few
questions:
1. Is there a way to preset the default IP address? The default is 192.168.1.1
but I want to change it to something like 10.0.0.1, so that my compiled
firmware’s IP address would be that.
2. Is there a way to
Geez, it must be true that you should only sleep when you're dead...damn Aussie
time zones...
I'll test with latest trunk as well will confirm. But looks promising!
-Original Message-
From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org] On Behalf
Of Paul Blazejowski
On 25 June 2014 01:07, Jonas Liepuonius thinker...@gmail.com wrote:
1. Is there a way to preset the default IP address? The default is
192.168.1.1 but I want to change it to something like 10.0.0.1, so that my
compiled firmware's IP address would be that.
Yes.
2. Is there a way to
On 24/06/14 22:01, Damian Kaczkowski wrote:
On 25 June 2014 01:07, Jonas Liepuonius thinker...@gmail.com
mailto:thinker...@gmail.com wrote:
1. Is there a way to preset the default IP address? The default is
192.168.1.1 but I want to change it to something like 10.0.0.1, so
that
Hello,
On Jun 24, 2014 4:07 PM, Jonas Liepuonius thinker...@gmail.com wrote:
So I recently decided to compile my own OpenWRT images, and I have a few
questions:
1. Is there a way to preset the default IP address? The default is
192.168.1.1 but I want to change it to something like 10.0.0.1,
Adam,
what do you know? hehehe when one sleeps another fixes things ;-)
so far so good, my router has been up for few hours without problems...
there's still issue with the sysupgrade image that John is already aware
of ... and may have a fix for us to test ... one fix at a time they say.
glad
Hi all,
I've flashed my Netgear WNDR4300 with trunk r41336 and have run a series
of tests.
Everything looks great! I can restore backed up settings, I can
configure it from scratch too should I desire.
Sysupgrade works fine on my WNDR4300 via the web UI. Paul if you're
still having
Hi,
can someone with a 3700v4 run cat /tmp/sysinfo/* on a 3700 ?
the sysupgrade fails because the board id is not added yet in the
upgrade script. however i fail to figure out what id it gets from the
ar71xx.sh script
John
On 25/06/2014 06:27, Adam Kuklycz wrote:
Hi all,
I've
55 matches
Mail list logo
