Re: [OpenWrt-Devel] dnscrypt-proxy package missing in snapshot

[Maciej Soltysiak]

Hi,

It doesn't look like there are any takers for this task.
Can anyone guide me to a 101 tutorial on making a brand new package?
dnscrypt-proxy 2 is completely different from its predecessor. There are
sources, as well as pre-build binaries for 20+ architectures.
go is required to build.

I'd very much appreciate for helping do this,
Maciej

On Sun, Feb 18, 2018 at 12:24 AM, Maciej Soltysiak 
wrote:

> On my MIPS32 (WNDR3800) system, I noticed the C binary was <100k.
> The GO binary is 6.5MB, I ran upx on it and it went down to 1.5M.
> It incurs about 1s of delay for unpacking, but it works.
>
> I don't know much about packaging this around the uci scripting, etc, but
> I hope this helps the maintainer a bit.
>
> Best regards,
> Maciej
>
> On Sat, Feb 17, 2018 at 11:40 PM, Maciej Soltysiak 
> wrote:
>
>> The OpenWrt Makefile aims to get dnscrypt-proxy 1.9.5 from a mirror at
>> https://github.com/dyne/dnscrypt-proxy
>>
>> However, the upstream (Frank Denis) recently released a 2.0 which is
>> significantly different.
>> It's now written in go, instead of C and it support the new version of
>> the protocol (v2).
>>
>> If we're going to get this package fixed we should see if we can get the
>> new one to run.
>> Probably should come from upstream at: https://github.com/jedisct1/dn
>> scrypt-proxy
>>
>> Best regards,
>> Maciej
>>
>> On Mon, May 1, 2017 at 12:48 PM, Alexandru Ardelean <
>> ardeleana...@gmail.com> wrote:
>>
>>> On Mon, May 1, 2017 at 12:04 PM, Mangesh Bhamre 
>>> wrote:
>>> >
>>> > Hello,
>>> >
>>> > Last time I reported this issue was for MT7620.  dnscrypt-proxy now
>>> failing for MT7621.
>>> >
>>> > http://buildbot.openwrt.org:8010/broken_packages/ramips.mt76
>>> 21/dnscrypt-proxy/compile.txt
>>> >
>>> > I am not sure what was the fix made. Likely was related to SSL cert
>>> check. Can anyone please look at this and fix it same way as MT7620 ?
>>> >
>>> > Regards,
>>> > Mangesh
>>> >
>>> > --
>>> > Regards,
>>> >
>>> > Mangesh Bhamre
>>> > Co-founder & CTO | Open Netware
>>> > +91-8879735272 | LinkedIn
>>> >
>>> >
>>> > On Mon, Feb 13, 2017 at 9:33 PM, Ralph Sennhauser <
>>> ralph.sennhau...@gmail.com> wrote:
>>> >>
>>> >> On Mon, 13 Feb 2017 21:03:07 +0530
>>> >> Mangesh Bhamre  wrote:
>>> >>
>>> >> > Hi Alex,
>>> >> >
>>> >> > Looking at build log -
>>> >> > http://buildbot.openwrt.org:8010/broken_packages/ramips.mt76
>>> 20/dnscrypt-proxy/compile.txt
>>> >> >
>>> >> > Tar ball is available on download.dnscrypt.org . Build download
>>> fails
>>> >> > for some SSL issue.
>>> >>
>>> >> The site has HSTS enabled. Might that be the issue?
>>> >>
>>> >> Maybe just updating PKG_SOURCE_URL to use https might be all that
>>> >> is needed. There was another user having issues with a redirect and
>>> >> samba. I think he was using Ubuntu.
>>> >>
>>> >> Ralph
>>> >>
>>> >> >
>>> >> > Also, tar ball is missing on mirror2.openwrt.org and
>>> >> > downloads.openwrt.org/sources
>>> >> >
>>> >> > Not sure, how mirror2 or download.openwrt.org gets updated.  Any
>>> help
>>> >> > in getting is appreciated.
>>> >> >
>>> >> > Regards,
>>> >> > Mangesh
>>> >> >
>>> >> >
>>> >
>>> >
>>>
>>> Looks like the package wasn't found on OpenWrt mirrors.
>>> Maybe some intermittent failure.
>>>
>>> You could try to setup your own cache/mirror [for packages/tarballs]
>>> and point your build to use that as primary, and only then fallback to
>>> OpenWrt's official repos.
>>> ___
>>> openwrt-devel mailing list
>>> openwrt-devel@lists.openwrt.org
>>> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
>>>
>>
>>
>
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] kernel version status

[Maciej Soltysiak]

On Mon, Feb 19, 2018 at 3:41 PM, John Crispin  wrote:
> please dont top post.
Apologies! Thank you for the kind reminder.

> ath79 is the same as ar71xx but uses dts files instead of mach files
Right, does that mean there might be an ath79 target, which is not
ready yet, or am I confusing things?

> John
Maciej
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] kernel version status

[Maciej Soltysiak]

Hi John,

As a user of an ar71xx (WNDR3800) on OpenWrt, I'd like to ask if your
desire is that ar71xx never gets bumped up to anything higher than 4.9 or
it's just not 4.14 because of some specific reasons related to 4.14?

IOW, shall I be looking for a replacement because I'll stay on 4.9 forever?

Best regards,
Maciej

On Mon, Feb 19, 2018 at 7:41 AM, John Crispin  wrote:

>
>
> On 18/02/18 22:43, Hauke Mehrtens wrote:
>
>> The next OpenWrt release will use kernel 4.9 and kernel 4.14 depending
>> on the target. All targets that are *not* on either kernel 4.9 or 4.14
>> will not be included in the next release.
>>
>> I did some overview of the kernel version some months ago here:
>> http://lists.infradead.org/pipermail/lede-dev/2017-October/009446.html
>>
>> Here is the current situation as of today:
>>
>> The following targets are on kernel 4.14 and are fine:
>> * apm821xx
>> * archs38
>> * armvirt
>> * cns3xxx
>> * malta
>> * mediatek
>> * octeon
>> * octeontx
>> * sunxi
>> * x86
>>
>> The following targets are on kernel 4.9 and are fine:
>> * ar71xx
>> * ar7
>> * arc770
>> * at91
>> There are some patches for kernel 4.14 on the mailing list
>> waiting for response from author
>> * ath25
>> * bcm53xx
>> patches for 4.14 are available in master
>> * brcm2708
>> * brcm47xx
>> * brcm63xx
>> patches for 4.14 are available in master
>> * imx6
>> There are some patches for kernel 4.14 on the mailing list
>> which is being worked on
>> * ipq806x
>> * ixp4xx
>> * kirkwood
>> * lantiq
>> patches for 4.14 are in Mathias Kresin's staging tree.
>> * layerscape
>> * mpc85xx
>> * mvebu
>> patches for 4.14 are available in master
>> I would like to get this to kernel 4.14 by default soon.
>> * mxs
>> * omap
>> * orion
>> * pistachio
>> * ramips
>> patches for 4.14 are available in master
>> * rb532
>> * uml
>>
>> The following targets are on kernel 4.4 and will probably not be
>> included in the next release:
>> * gemini
>> * oxnas
>> * zynq
>>
>> The following targets are on kernel 3.18 and will probably not be
>> included in the next release:
>> * adm5120
>> * adm8668
>> * au1000
>> * mcs814x
>> I have patches which port this target to 4.4 in my tree, but
>> nobody tested them.
>> https://git.lede-project.org/?p=lede/hauke/staging.git;a=sho
>> rtlog;h=refs/heads/kernel-4.4
>> * ppc40x
>> * ppc44x
>> * xburst
>> I have patches which port this target to 4.4 in my tree, but
>> nobody tested them
>> https://git.lede-project.org/?p=lede/hauke/staging.git;a=sho
>> rtlog;h=refs/heads/kernel-4.4
>>
>> This target is on kernel 4.1 (WTF):
>> * omap24xx
>>
>> All the targets which are not on kernel 4.9 or 4.14 will probably not be
>> included in the next release, I also haven't seen any activity for any
>> of them to get support for more recent kernel versions, if you need them
>> please take care now.
>>
>> Hauke
>>
>
> Hi Hauke,
>
> I planned to make that list today, thanks for taking care of it !. I would
> like to see ar71xx and ramips stay on v4.9, regardless of there being
> patches for v4.14. I would also like to see ar71xx never being bumped to
> v4.14, I spent a few days last week revamping my old ath79 port and would
> like to see a hard cut, moving QCA mips target to OF only post release.
>
> John
>
> ___
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
>
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] dnscrypt-proxy package missing in snapshot

[Maciej Soltysiak]

On my MIPS32 (WNDR3800) system, I noticed the C binary was <100k.
The GO binary is 6.5MB, I ran upx on it and it went down to 1.5M.
It incurs about 1s of delay for unpacking, but it works.

I don't know much about packaging this around the uci scripting, etc, but I
hope this helps the maintainer a bit.

Best regards,
Maciej

On Sat, Feb 17, 2018 at 11:40 PM, Maciej Soltysiak <mac...@soltysiak.com>
wrote:

> The OpenWrt Makefile aims to get dnscrypt-proxy 1.9.5 from a mirror at
> https://github.com/dyne/dnscrypt-proxy
>
> However, the upstream (Frank Denis) recently released a 2.0 which is
> significantly different.
> It's now written in go, instead of C and it support the new version of the
> protocol (v2).
>
> If we're going to get this package fixed we should see if we can get the
> new one to run.
> Probably should come from upstream at: https://github.com/jedisct1/
> dnscrypt-proxy
>
> Best regards,
> Maciej
>
> On Mon, May 1, 2017 at 12:48 PM, Alexandru Ardelean <
> ardeleana...@gmail.com> wrote:
>
>> On Mon, May 1, 2017 at 12:04 PM, Mangesh Bhamre <mang...@opennetware.com>
>> wrote:
>> >
>> > Hello,
>> >
>> > Last time I reported this issue was for MT7620.  dnscrypt-proxy now
>> failing for MT7621.
>> >
>> > http://buildbot.openwrt.org:8010/broken_packages/ramips.mt76
>> 21/dnscrypt-proxy/compile.txt
>> >
>> > I am not sure what was the fix made. Likely was related to SSL cert
>> check. Can anyone please look at this and fix it same way as MT7620 ?
>> >
>> > Regards,
>> > Mangesh
>> >
>> > --
>> > Regards,
>> >
>> > Mangesh Bhamre
>> > Co-founder & CTO | Open Netware
>> > +91-8879735272 | LinkedIn
>> >
>> >
>> > On Mon, Feb 13, 2017 at 9:33 PM, Ralph Sennhauser <
>> ralph.sennhau...@gmail.com> wrote:
>> >>
>> >> On Mon, 13 Feb 2017 21:03:07 +0530
>> >> Mangesh Bhamre <mang...@opennetware.com> wrote:
>> >>
>> >> > Hi Alex,
>> >> >
>> >> > Looking at build log -
>> >> > http://buildbot.openwrt.org:8010/broken_packages/ramips.mt76
>> 20/dnscrypt-proxy/compile.txt
>> >> >
>> >> > Tar ball is available on download.dnscrypt.org . Build download
>> fails
>> >> > for some SSL issue.
>> >>
>> >> The site has HSTS enabled. Might that be the issue?
>> >>
>> >> Maybe just updating PKG_SOURCE_URL to use https might be all that
>> >> is needed. There was another user having issues with a redirect and
>> >> samba. I think he was using Ubuntu.
>> >>
>> >> Ralph
>> >>
>> >> >
>> >> > Also, tar ball is missing on mirror2.openwrt.org and
>> >> > downloads.openwrt.org/sources
>> >> >
>> >> > Not sure, how mirror2 or download.openwrt.org gets updated.  Any
>> help
>> >> > in getting is appreciated.
>> >> >
>> >> > Regards,
>> >> > Mangesh
>> >> >
>> >> >
>> >
>> >
>>
>> Looks like the package wasn't found on OpenWrt mirrors.
>> Maybe some intermittent failure.
>>
>> You could try to setup your own cache/mirror [for packages/tarballs]
>> and point your build to use that as primary, and only then fallback to
>> OpenWrt's official repos.
>> ___
>> openwrt-devel mailing list
>> openwrt-devel@lists.openwrt.org
>> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
>>
>
>
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] dnscrypt-proxy package missing in snapshot

[Maciej Soltysiak]

The OpenWrt Makefile aims to get dnscrypt-proxy 1.9.5 from a mirror at
https://github.com/dyne/dnscrypt-proxy

However, the upstream (Frank Denis) recently released a 2.0 which is
significantly different.
It's now written in go, instead of C and it support the new version of the
protocol (v2).

If we're going to get this package fixed we should see if we can get the
new one to run.
Probably should come from upstream at:
https://github.com/jedisct1/dnscrypt-proxy

Best regards,
Maciej

On Mon, May 1, 2017 at 12:48 PM, Alexandru Ardelean 
wrote:

> On Mon, May 1, 2017 at 12:04 PM, Mangesh Bhamre 
> wrote:
> >
> > Hello,
> >
> > Last time I reported this issue was for MT7620.  dnscrypt-proxy now
> failing for MT7621.
> >
> > http://buildbot.openwrt.org:8010/broken_packages/ramips.
> mt7621/dnscrypt-proxy/compile.txt
> >
> > I am not sure what was the fix made. Likely was related to SSL cert
> check. Can anyone please look at this and fix it same way as MT7620 ?
> >
> > Regards,
> > Mangesh
> >
> > --
> > Regards,
> >
> > Mangesh Bhamre
> > Co-founder & CTO | Open Netware
> > +91-8879735272 | LinkedIn
> >
> >
> > On Mon, Feb 13, 2017 at 9:33 PM, Ralph Sennhauser <
> ralph.sennhau...@gmail.com> wrote:
> >>
> >> On Mon, 13 Feb 2017 21:03:07 +0530
> >> Mangesh Bhamre  wrote:
> >>
> >> > Hi Alex,
> >> >
> >> > Looking at build log -
> >> > http://buildbot.openwrt.org:8010/broken_packages/ramips.
> mt7620/dnscrypt-proxy/compile.txt
> >> >
> >> > Tar ball is available on download.dnscrypt.org . Build download fails
> >> > for some SSL issue.
> >>
> >> The site has HSTS enabled. Might that be the issue?
> >>
> >> Maybe just updating PKG_SOURCE_URL to use https might be all that
> >> is needed. There was another user having issues with a redirect and
> >> samba. I think he was using Ubuntu.
> >>
> >> Ralph
> >>
> >> >
> >> > Also, tar ball is missing on mirror2.openwrt.org and
> >> > downloads.openwrt.org/sources
> >> >
> >> > Not sure, how mirror2 or download.openwrt.org gets updated.  Any help
> >> > in getting is appreciated.
> >> >
> >> > Regards,
> >> > Mangesh
> >> >
> >> >
> >
> >
>
> Looks like the package wasn't found on OpenWrt mirrors.
> Maybe some intermittent failure.
>
> You could try to setup your own cache/mirror [for packages/tarballs]
> and point your build to use that as primary, and only then fallback to
> OpenWrt's official repos.
> ___
> openwrt-devel mailing list
> openwrt-devel@lists.openwrt.org
> https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
>
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] Tried LEDE with SQM today

[Maciej Soltysiak]

Hi,

I gave LEDE a whirl on WNDR3800 on a 100 Mb DSL line.
Without SQM, speedtest.net gave around 90 Mbit/s of download and 3,6 upload.
I installed sqm-scripts and the luci app and enabled SQM on eth1, set
ingress and egress shaping to 90% of speedtest.net results, enabled
fq_codel and simple.qos

Now when on to dslreports bufferbloat tests and got about 42 Mbit/s. Great
bufferbloat result but ingress seems to perform at just above 50% of
ingress threshold (42 / 90% * 90).

I don't think I've seen that drastic effect when I was on cero and then on
openwrt.
Anything obvious I'm doing wrong?

Also, funny thing, there's a sqm-scripts-extra with cake and also the
packages seem to contain the right kernel modules, but there's not cake
queueing disciple in the luci UI. I found in /var/run/sqm/available_qdiscs
empty files which correspond to the dropdown in luci: codel, fq_codel, pie,
sfq. Could it be that it's just missing an empty file for cake or is that
something more deep?

Best regards,
Maciej
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] Upgrade from CC RC2 to RC3

[Maciej Soltysiak]

On Tue, Jul 21, 2015 at 7:22 AM, John Crispin blo...@openwrt.org wrote:



 On 20/07/2015 22:38, Felix Fietkau wrote:
  On 2015-07-20 18:49, Maciej Soltysiak wrote:
  Hi guys,
 
  Would s/rc2/rc3/ on the opkg.conf lead to a clean upgrade or is it
  better to reflash?
  Upgrading via opkg doesn't work. You need to reflash.
 
  - Felix
  ___
  openwrt-devel mailing list
  openwrt-devel@lists.openwrt.org
  https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
 

 what felix meant to say is that after a sysupgrade you need to restore
 opkg.conf from /rom or apply the regex you posted

Thanks,
Maciej
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] Upgrade from CC RC2 to RC3

[Maciej Soltysiak]

Hi guys,

Would s/rc2/rc3/ on the opkg.conf lead to a clean upgrade or is it better
to reflash?

Best regards,
Maciej
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] config for WNDR3800

[Maciej Soltysiak]

Hi,

I was planning to try and build openwrt on my box. Is there an official
.config file that's used when building the snapshots?

I'm looking for .config for Netgear WNDR3800.

Best regards,
Maciej
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] config for WNDR3800

[Maciej Soltysiak]

On Wed, Jul 1, 2015 at 5:57 PM, Jonathan Bennett jbscienc...@gmail.com
wrote:

 Instead of using a premade .config, you'll want to use make menuconfig.
 Under Target profile, you'll find the netgear WNDR3800.

 Right, I just wanted to start off with the same set of packages built in
as the trunk images.

Thanks,
Maciej
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] config for WNDR3800

[Maciej Soltysiak]

On Wed, Jul 1, 2015 at 5:56 PM, Lars la...@systemli.org wrote:

 hey,

 this is the dotconfig used for the snapshots:
 https://downloads.openwrt.org/snapshots/trunk/ar71xx/generic/config

 you only have to select the target, otherwise it'll build images for all
 ar71xx targets.

Why didn't I see it, thanks! :)

 lars

Maciej
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] uhttpd - bugs vs oficial repo

[Maciej Soltysiak]

Hi,

== A bit of background first ==
My TV fetches an XML from samsung.com every 2 seconds or so.
I used to trick the TV to get the file from a local server instead.

When I tried hosting the file on openwrt (I'm on trunk) the TV fails to
handle the HTTP response given by uhttpd. nginx, lighthttpd serve it just
fine. Yes, TV firmware is not robust, but the bugs are in uhttpd

== Issue ==
Fildder reports the response given by uhttpd violates HTTP in these ways:
1) Content-Length response header MUST NOT be present when
Transfer-Encoding is used (RFC2616 Section 4.4)
2) Content-Length mismatch: Response Header indicated 2.400 bytes, but
server sent 2412 bytes.

== Question ==
I'd like to see if I can fix the bug, but I don't know where is the
official repo for uhttp. Does anyone know?

Best regards,
Maciej Soltysiak
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] uhttpd - bugs vs oficial repo

[Maciej Soltysiak]

Hi Yousong, Martin,

On Sat, May 30, 2015 at 3:16 PM, Yousong Zhou yszhou4t...@gmail.com wrote:

 Not sure about the above issues reported.  As for the repos' URL, you
 can find them at http://nbd.name/gitweb.cgi

  - It's uhttpd on OpenWrt AA release and before.
  - It's uhttpd2 on OpenWrt BB and later.

 yousong

Thank you both. I manged to fix that issue in uhttpd2's git and pass a
preliminary test.
Now to see if this fixes it for the TV.

Best regards,
Maciej
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] is anybody working on supporting Linksys WRT1900ac ?

[Maciej Soltysiak]

On Thu, Jan 16, 2014 at 4:32 AM, Aaron Z aar...@pls-net.org wrote:
 Perhaps marketing is watching this thread? It now reads:
 Open Source is a vehicle for other communities, such as DD-WRT, Open WRT, 
 and Tomato, to create their own custom versions of open source firmware for 
 the product. OpenWRT developers will be provided hardware and SDKs/APIs to 
 begin creating custom firmware for the WRT1900AC.
Optimistic read of this suggests that they will release some kind of
patches to adopt in various projects?

 An OpenWRT custom firmware for WRT1900AC is planned to be available for 
 download online at availability in the spring 2014.
So OpenWRT will be the custom firmware? Will they then ship something
of their own? Based on what? OpenWRT?

Best regards,
Maciej
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] Netgear R6300 - 802.11ac device

[Maciej Soltysiak]

Hiya,

Netgear has recently released a 802.11ac device dubbed R6300 with 128 MB
Flash and 128 MB RAM.

The network processor is Broadcom’s BCM4706. For the 2.4GHz radio it uses
the BCM4331 w/ SiGE brand power amps. For the 5GHz radio it uses the
BCM4360 chip with Skyworks SE5003L power amps.

Anybody knows if this is as open as WNDR3800 to allow openwrt and ... open
the pandora's box with new and exciting issues with gigabit wireless? ;-)

Please CC, I'm not on the list.

Regards,
Maciej Soltysiak
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel

Re: [OpenWrt-Devel] Netgear R6300 - 802.11ac device

[Maciej Soltysiak]

On Tue, Jul 3, 2012 at 4:24 PM, Rafał Miłecki zaj...@gmail.com wrote:

 2012/7/3 Maciej Soltysiak mac...@soltysiak.com:
  Netgear has recently released a 802.11ac device dubbed R6300 with 128 MB
  Flash and 128 MB RAM.

 I guess my work on creating images for WNDR4500 will help here. I'm on
 vacations right now, will be back to development in next week.

Didn't know WNDR4500 was feasible. I heard it's not 100% open source
firmware at present and thus are not usable:
I'm basically quoting Dave Taht from Cerowrt project:
http://www.bufferbloat.net/issues/355

  The network processor is Broadcom’s BCM4706. For the 2.4GHz radio it uses
  the BCM4331 w/ SiGE brand power amps. For the 5GHz radio it uses the BCM4360
  chip with Skyworks SE5003L power amps.

 We don't have driver for flash yet. BCM4331 is poorly supported by
 b43, no brcmsmac support, Broadcom doesn't respond on questions on
 that.
 BCM4360 is even worse I guess.
Right. What is your broadcom contact?

Regards,
Maciej
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel