Steven Barth writes:
> NAK. The default configuration works well.
The default configuration does not work at all because the @wan syntax
does not work.
So no the default configuration does not work at ALL.
> If it does not please try to tell use why.
>
> You can set the reqprefix value if you
Jo-Philipp Wich writes:
> NACK to this patch, comments below.
>
>> -set network.lan.ip6assign='60'
>> +set network.lan.ip6assign='64'
>
> Cosmetical change, not needed. If less than a /60 is available, it will
> use less.
As far as I can tell the logic here is broken. What does it mean to
assig
Hi Rafał,
Thank you for your reply, but i have no idea about top post. If i do that
truly, i am sorry.
It will be appreciated, if you would like to tell me about how to avoid to
top post
Thanks again.
Jiapeng
2013/9/13 Rafał Miłecki
> 2013/9/12 Jiapeng Li :
> > I want to test bcm5357 openwrt
On Thu, Sep 12, 2013 at 05:55:33PM +0200, Yegor Yefremov wrote:
> Hi,
>
> Another useful feature is "The source directory override mechanism" as
> described here: http://free-electrons.com/blog/buildroot-2011-11/ Is
> it planned to integrate such a feature?
Just add the following line to your pac
Hi,
I want to develop my own package for OpenWRT. I'm a Buildroot user
though and AFAIK OpenWRT uses it heavily too. Buildroot provides a
very efficient CMake integration. It provides a toolchainfile.cmake,
that will be used to compile existing CMake based packages, but it can
be easily used to co
On 09/12/2013 07:39 AM, John Crispin wrote:
On 12/09/13 12:32, Bastian Bittorf wrote:
* Steffen Hoffmann [12.09.2013 12:29]:
Thank you for the translation, but 3 doesn't correlate with 'dutzende',
or you have another, undisclosed source for your information?
8-) i'am involved in this special
Changed two instances of "TL-MR3040" to "TL-MR3040-v1" and "TL-MR3040-v2",
respectively.
Signed-off-by: Mads Hansen
Index: trunk/target/linux/ar71xx/image/Makefile
===
--- trunk/target/linux/ar71xx/image/Makefile(revision 37950
* Gui Iribarren [12.09.2013 18:51]:
> in that case, you can even build a dumb cable (just pins on each
> side, no serial-to-usb circuit) and use it to connect two routers
> (i.e. one bricked, and one alive with package 'screen') , GND -> GND
> / TX -> RX / RX -> TX
i already thought about this an
Hi Zoltan,
do you have had already some time to look over this series?
Any objections or wishes that I could/should address?
Please let me know your opinion.
Thnx,
Michael
PS: The series is also avaiable at
https://github.com/mhei/openwrt/tree/mxs
Am Mittwoch, 28. August 2013, 13:08:21 schrieb
2013/9/12 Jiapeng Li :
> I want to test bcm5357 openwrt with my RT-N10U too. Which device should i
> choose to compile the OpenWrt, is there related patches need to use.
First of all, don't top post please.
I've no idea what are you asking for. You can compile OpenWrt *on*
almost any architectur
I want to test bcm5357 openwrt with my RT-N10U too. Which device should i
choose to compile the OpenWrt, is there related patches need to use.
Thank you
Jiapeng
2013/9/12 Rafał Miłecki
> Some example with Wireshark output visible too.
>
> ___
> open
Some example with Wireshark output visible too.
Wireshark running on notebook running "dhcpd-test eth0".
bgmac with debugging running on Linksys E900
What bgmac received doesn't really look like what was sent (registered by
Wireshark).
ff ff ff ff ff ff e8 11 32 cd e2 be 08 00 45 10
This patch adds support for building firmware images for the TP-Link TL-MR3040
v2. Tested and working on v2.1 hardware.
Signed-off-by: Mads Hansen
Index: trunk/target/linux/ar71xx/image/Makefile
===
--- trunk/target/linux/ar71xx/im
2013/9/12 Hauke Mehrtens :
> On 09/12/2013 01:23 PM, Rafał Miłecki wrote:
>> Network on BCM5357* devices isn't working since ever. It seems there
>> is some problem with bgmac I don't understand.
>>
>> First of all, when using interface without VLAN enabled and without
>> bridging it - no packets a
On 09/12/2013 01:23 PM, Rafał Miłecki wrote:
> Network on BCM5357* devices isn't working since ever. It seems there
> is some problem with bgmac I don't understand.
>
> First of all, when using interface without VLAN enabled and without
> bridging it - no packets appear. That can be easily workaro
Network on BCM5357* devices isn't working since ever. It seems there
is some problem with bgmac I don't understand.
First of all, when using interface without VLAN enabled and without
bridging it - no packets appear. That can be easily workarounded with
"ifconfig eth0 promisc". Then I can see pack
On 12/09/13 12:32, Bastian Bittorf wrote:
* Steffen Hoffmann [12.09.2013 12:29]:
Thank you for the translation, but 3 doesn't correlate with 'dutzende',
or you have another, undisclosed source for your information?
8-) i'am involved in this special case, so i know the real situation.
(somebod
* Steffen Hoffmann [12.09.2013 12:29]:
> Thank you for the translation, but 3 doesn't correlate with 'dutzende',
> or you have another, undisclosed source for your information?
8-) i'am involved in this special case, so i know the real situation.
(somebody tends to hype here) this is a very funny
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12.09.2013 09:34, Bastian Bittorf wrote:
> * Alina Friedrichsen [12.09.2013 09:14]:
>> Könnt ihr bitte einen Warnung im Wiki anbringen, dass der Router extrem
>> empfindlich gegenüber Lötwasser ist? Mir sind dutzende Router
>> abgeraucht, weil ich
NAK. The default configuration works well.
If it does not please try to tell use why.
You can set the reqprefix value if you like and if it makes your ISP
give you a better / bigger prefix.
The /60 on the interface does not interfere with RA or SLAAC, we still
only announce the first /64 out
NACK to this patch, comments below.
> -set network.lan.ip6assign='60'
> +set network.lan.ip6assign='64'
Cosmetical change, not needed. If less than a /60 is available, it will
use less.
> -set network.wan6='interface'
> -set network.wan6.ifname='@wan'
> +set network.wan6='alias'
> +set network.w
hello
are there any plans to update hostapd to current git?
it has ACS support,
IMHO ACS support should be enabled by default
best regads
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/
Στις Πεμ 12 Σεπτ 2013 09:34:34 Bastian Bittorf έγραψε:
> * Alina Friedrichsen [12.09.2013 09:14]:
> > Könnt ihr bitte einen Warnung im Wiki anbringen, dass der Router extrem
> > empfindlich gegenüber Lötwasser ist? Mir sind dutzende Router
> > abgeraucht, weil ich zu viel Lötwasser aufgetragen hab
On Thu, 12 Sep 2013 09:45:59 +0200, Joerg Dorchain wrote:
On Thu, Sep 12, 2013 at 08:55:29AM +0200, Alina Friedrichsen wrote:
Könnt ihr bitte einen Warnung im Wiki anbringen, dass der Router extrem
empfindlich gegenüber Lötwasser ist? Mir sind dutzende Router
abgeraucht, weil ich zu viel Lötwa
On Thu, Sep 12, 2013 at 08:55:29AM +0200, Alina Friedrichsen wrote:
> Könnt ihr bitte einen Warnung im Wiki anbringen, dass der Router extrem
> empfindlich gegenüber Lötwasser ist? Mir sind dutzende Router
> abgeraucht, weil ich zu viel Lötwasser aufgetragen habe. Nur ein ganz
> feiner Strich von u
On Mon, 26 Aug 2013 16:46:46 -0700
ebied...@xmission.com (Eric W. Biederman) wrote:
>
> By default generate the configuaration:
>
> config interface 'lan'
>option ifname 'eth0.1'
>option type 'bridge'
>option proto 'static'
>option ipaddr '192.168.1.1'
>op
* Alina Friedrichsen [12.09.2013 09:14]:
> Könnt ihr bitte einen Warnung im Wiki anbringen, dass der Router extrem
> empfindlich gegenüber Lötwasser ist? Mir sind dutzende Router
> abgeraucht, weil ich zu viel Lötwasser aufgetragen habe. Nur ein ganz
> feiner Strich von unten über die Pins. Bei me
manche sind eben nicht mit allen wassern gewaschen..
Am 12. September 2013 08:55 schrieb Alina Friedrichsen :
> Könnt ihr bitte einen Warnung im Wiki anbringen, dass der Router extrem
> empfindlich gegenüber Lötwasser ist? Mir sind dutzende Router
> abgeraucht, weil ich zu viel Lötwasser auf
28 matches
Mail list logo
