Re: [LEDE-DEV] LEDE/OpenWrt firmware wizard

[Moritz Warning]

Hi Alberto,

I would parse this site https://lede-project.org/toh/views/toh_fwdownload once 
using node and generate the data needed.
This should be no issue in JavaScript, so there is no need to have a better 
formatted data.

Thanks,
Moritz

On 01/01/2018 07:35 PM, Alberto Bursi wrote:
> Would providing the text files which are the actual source of the wiki pages 
> help making this fully automated?
> 
> The source text file is already structured to be parsed by the wiki PHP 
> engine that generates the webpage.
> 
> This is an example (same page as linked):
> 
> = Dataentry =
>  dataentry techdata 
> Device Type_devicetype : WiFi Router # If 'other' -> 
> request new devicetype @wiki admin
> Brand  : BT # ===> Mandatory  <===
> Model  : Home Hub 5 # ===>  Mandatory 
>  <===
> Versions   : Type A # List versions comma 
> separated: v1, v1.1, v1.5, v2, v2.5
> FCCID_urls :  # link-scheme: 
> https://fcc.io/yourFCCid
> Availability_availability  : unknown 2017
> OWrt Supported Since Rev_hidden    : 
> https://dev.openwrt.org/changeset/46223 # 
> https://dev.openwrt.org/changeset/x
> OWrt Supported Since Rel_hidden    : ¿ # First official release 
> (i.e. not trunk)
> OWrt Supported Current Rel_hidden  : DD trunk # Current official 
> release (i.e. not trunk)
> OWrt Unsupported_hidden    :  # e.g. '5GHz wifi'; 
> Describe what is not supported
> 
> .
> 
> OEM Device Homepage URL_url    :  # yourbrand.com/yourdevice
> Firmware OEM Stock URL_url :  # 
> yourbrand.com/yourdevice/stockfirmware
> Firmware OWrt Install URL_hidden   :  # 
> downloads.openwrt.org/latest/...factory.bin; If more than 1 file for 
> install/upgrade -> link to download *folder* instead of image
> Firmware OWrt Upgrade URL_hidden   :  # 
> downloads.openwrt.org/latest/...sysupgrade.bin; If more than 1 file for 
> install/upgrade -> link to download *folder* instead of image
> Firmware LEDE Install URL_url  :  # 
> downloads.lede-project.org/releases//targets/...; If more than 1 
> file for install/upgrade -> link to download *folder* instead of image
> Firmware LEDE Upgrade URL_url  : 
> https://downloads.lede-project.org/releases/17.01.4/targets/lantiq/xrx200/lede-17.01.4-lantiq-xrx200-BTHOMEHUBV5A-squashfs-sysupgrade.bin
>  # downloads.lede-project.org/releases//targets/...; If more than 1 
> file for install/upgrade -> link to download *folder* instead of image
> 
> 
> 
> 
> I have a script running weekly in that server to update the package 
> lists/tables. It's easy to add a few lines that will make a zip file with all 
> these dataentry text files and then place it in the webserver folder so you 
> can retrieve it with wget.
> 
> I just need to ask tmomas on details (where I can place the zip file so it is 
> retrievable from the web) and also if he has any objections (as I'm not the 
> server owner/maintainer).
> 
> -Alberto
> 
> On 01/01/2018 06:09 PM, Moritz Warning wrote:
>> hi Hauke,
>>
>> somebody on the forum already pointed me there:
>>
>> https://forum.lede-project.org/t/firmware-wizard/9039/19
>> (example was also the same - coincidence? ;-))
>>
>> That particular site is easy to parse, but most are not (I click random 
>> entries).
>> Iirc, I already parsed the TOH table and added image names by hand when it 
>> was obvious.
>>
>> On 12/30/2017 02:13 PM, Hauke Mehrtens wrote:
>>>
>>> On 11/23/2017 06:44 AM, Moritz Warning wrote:
>>>> Hi,
>>>>
>>>> I've put online a firmware wizard for LEDE:
>>>>
>>>> http://mwarning.de/firmware-wizard/
>>>> (Sources: https://github.com/freifunk-bielefeld/firmware-wizard)
>>>>
>>>> Build with rather plain HTML5/CSS/JS. Merge requests are welcome.
>>>> Everything is still rough around the edges.
>>>>
>>>> It would be nice if downloads.lede-project.org would set 
>>>> "Access-Control-Allow-Origin: *",
>>>> since the code tries to scrape the download site. So far I use a 
>>>> pre-scraped file index as a workaround.
>>>> But that causes the file links to not work..
>>>>
>>>> Have fun,
>>>> mwarning
>>> Hi Moritz,
>>>
>>> I saw your presentation yester

Re: [LEDE-DEV] LEDE/OpenWrt firmware wizard

[Moritz Warning]

hi Hauke,

somebody on the forum already pointed me there:

https://forum.lede-project.org/t/firmware-wizard/9039/19
(example was also the same - coincidence? ;-))

That particular site is easy to parse, but most are not (I click random 
entries).
Iirc, I already parsed the TOH table and added image names by hand when it was 
obvious.

On 12/30/2017 02:13 PM, Hauke Mehrtens wrote:
> 
> 
> On 11/23/2017 06:44 AM, Moritz Warning wrote:
>> Hi,
>>
>> I've put online a firmware wizard for LEDE:
>>
>> http://mwarning.de/firmware-wizard/
>> (Sources: https://github.com/freifunk-bielefeld/firmware-wizard)
>>
>> Build with rather plain HTML5/CSS/JS. Merge requests are welcome.
>> Everything is still rough around the edges.
>>
>> It would be nice if downloads.lede-project.org would set 
>> "Access-Control-Allow-Origin: *",
>> since the code tries to scrape the download site. So far I use a pre-scraped 
>> file index as a workaround.
>> But that causes the file links to not work..
>>
>> Have fun,
>> mwarning
> 
> Hi Moritz,
> 
> I saw your presentation yesterday, but can not find you any more at
> 34C3. ;-)
Next time try DECT. :-)
> 
> You can probably get many meta data from the LEDE wiki which is now more
> restructured than the OpenWrt Wiki, see for example this page:
> https://lede-project.org/toh/hwdata/bt/bt_homehub_5_type_a
> 
> It probably makes more sens to use this as the central storage for board
> meta data, using the git has a pretty high entry barrier for external
> contributions.
> 
> Hauke
> 


___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] Uniform cryptography library

[Moritz Warning]

On 12/12/2017 06:48 PM, Matthias-Christian Ott wrote:
> On 2017-12-12 01:12, Moritz Warning wrote:
>> On 12/11/2017 07:10 PM, Matthias-Christian Ott wrote:
>> [..]
>>> Do you think it would be worth the effort to unify the cryptography
>>> libraries in LEDE?
>>
>> This sounds like a huge task.
> 
> It is and needs a conscious commitment and decision of the project. So I
> thought it is best to discuss it on the mailing list.
> 
>> Maybe you can extend a program so it supports a different crypto library 
>> that is also used in the LEDE/OpenWRT ecosystem.
> 
> That is the idea. LEDE would have a policy like, “If it is not
> impossible, packages need to use TLS library A and cryptography library
> B.” Package maintainers would adapt the package to these libraries. Then
> they would try to contribute the modifications to the upstream
> maintainer in hope that upstream maintainer would take over the
> maintenance of the modifications; otherwise, the package maintainer
> would have to maintain the modifications for LEDE.
> 

As for the default packages (dnsmasq, dropbear, uhttpd, ..), it is always 
desirable, if not even a policy, to use as much common libs as possible.
IMHO, policy changes won't help much. Just start contributing.

- mwarning

___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] Uniform cryptography library

[Moritz Warning]

On 12/11/2017 07:10 PM, Matthias-Christian Ott wrote:
[..]
> Do you think it would be worth the effort to unify the cryptography
> libraries in LEDE?

This sounds like a huge task.
Maybe you can extend a program so it supports a different crypto library that 
is also used in the LEDE/OpenWRT ecosystem.
That would sound like a good start to reduce library baggage.

just my2cents,
mwarning

___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

[LEDE-DEV] [PATCH] brcm47xx: remove versions from linksys-e1000 target

[Moritz Warning]

The target name does not need to included a revision
if all revisions are supported.
This target supports all revisions (v1, v2, v2.1).

Signed-off-by: Moritz Warning <moritzwarn...@web.de>
---
 target/linux/brcm47xx/image/Makefile | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/target/linux/brcm47xx/image/Makefile 
b/target/linux/brcm47xx/image/Makefile
index 8c681ac345..29bc08ecad 100644
--- a/target/linux/brcm47xx/image/Makefile
+++ b/target/linux/brcm47xx/image/Makefile
@@ -701,14 +701,14 @@ define Device/linksys-e900-v1
 endef
 TARGET_DEVICES += linksys-e900-v1
 
-define Device/linksys-e1000-v1-v2-v2.1
-  DEVICE_TITLE := Linksys E1000 v1 v2 v2.1
+define Device/linksys-e1000
+  DEVICE_TITLE := Linksys E1000
   DEVICE_PACKAGES := kmod-b43
   $(Device/linksys)
   DEVICE_ID := E100
   VERSION := 1.1.3
 endef
-TARGET_DEVICES += linksys-e1000-v1-v2-v2.1
+TARGET_DEVICES += linksys-e1000
 
 define Device/linksys-e1200-v1
   DEVICE_TITLE := Linksys E1200 v1
-- 
2.15.1


___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

[LEDE-DEV] [PATCH] brcm47xx: proper region code in image name

[Moritz Warning]

Replace 'north-america' by 'us' and remove 'other-regions' in image files for 
Netgear WGR614 v10.

Signed-off-by: Moritz Warning <moritzwarn...@web.de>
---
 target/linux/brcm47xx/image/Makefile | 18 +-
 1 file changed, 9 insertions(+), 9 deletions(-)

diff --git a/target/linux/brcm47xx/image/Makefile 
b/target/linux/brcm47xx/image/Makefile
index 8c681ac345..ccd6f4dc44 100644
--- a/target/linux/brcm47xx/image/Makefile
+++ b/target/linux/brcm47xx/image/Makefile
@@ -806,21 +806,21 @@ define Device/linksys-e4200-v1
 endef
 TARGET_DEVICES += linksys-e4200-v1
 
-define Device/netgear-wgr614-v10_north-america
+define Device/netgear-wgr614-v10-na
   DEVICE_TITLE := Netgear WGR614 v10 North America
   $(Device/netgear)
   NETGEAR_BOARD_ID := U12H139T01_NETGEAR
   NETGEAR_REGION := 2
 endef
-TARGET_DEVICES += netgear-wgr614-v10_north-america
+TARGET_DEVICES += netgear-wgr614-v10-na
 
-define Device/netgear-wgr614-v10_other-regions
-  DEVICE_TITLE := Netgear WGR614 v10 Other Regions
+define Device/netgear-wgr614-v10
+  DEVICE_TITLE := Netgear WGR614 v10
   $(Device/netgear)
   NETGEAR_BOARD_ID := U12H139T01_NETGEAR
   NETGEAR_REGION := 1
 endef
-TARGET_DEVICES += netgear-wgr614-v10_other-regions
+TARGET_DEVICES += netgear-wgr614-v10
 
 define Device/netgear-wn2500rp-v1
   DEVICE_TITLE := Netgear WN2500RP v1
@@ -910,23 +910,23 @@ define Device/netgear-wnr2000v2
 endef
 TARGET_DEVICES += netgear-wnr2000v2
 
-define Device/netgear-wnr3500l-v1-north-america
+define Device/netgear-wnr3500l-v1-na
   DEVICE_TITLE := Netgear WNR3500L v1 North America
   DEVICE_PACKAGES := kmod-b43 $(USB2_PACKAGES)
   $(Device/netgear)
   NETGEAR_BOARD_ID := U12H136T99_NETGEAR
   NETGEAR_REGION := 2
 endef
-TARGET_DEVICES += netgear-wnr3500l-v1-north-america
+TARGET_DEVICES += netgear-wnr3500l-v1-na
 
-define Device/netgear-wnr3500l-v1-other-regions
+define Device/netgear-wnr3500l-v1
   DEVICE_TITLE := Netgear WNR3500L v1 Other Regions
   DEVICE_PACKAGES := kmod-b43 $(USB2_PACKAGES)
   $(Device/netgear)
   NETGEAR_BOARD_ID := U12H136T99_NETGEAR
   NETGEAR_REGION := 1
 endef
-TARGET_DEVICES += netgear-wnr3500l-v1-other-regions
+TARGET_DEVICES += netgear-wnr3500l-v1
 
 define Device/netgear-wnr3500l-v2
   DEVICE_TITLE := Netgear WNR3500L v2
-- 
2.15.1


___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] fixing of image file names

[Moritz Warning]

I have forked the lede source code started to add some fixes.
The commits need to be cleaned up, tested, etc..

If somebody has some fixes, ideas, please let me know:

https://github.com/mwarning/source

- mwarning

On 11/28/2017 07:05 PM, Moritz Warning wrote:
> Hi,
> 
> I noticed that there are some image file names that do not follow the 
> "common" name scheme.
> Is it ok to change it? I would like to submit a patch.
> 
> Some examples:
> - all lower case image names
>   - lede-ipq806x-EA8500-squashfs-sysupgrade.tar => 
> lede-ipq806x-ea8500-squashfs-sysupgrade.tar
> - revision between -
>   - lede-mvebu-linksys-wrt1900acv2-squashfs-sysupgrade.bin => 
> lede-mvebu-linksys-wrt1900ac-v2-squashfs-sysupgrade.bin
> - region specific images with region identifiers (us, eu, il, ...)
>  - lede-ramips-rt305x-wnce2001-squashfs-factory-northamerica.bin => 
> lede-ramips-rt305x-wnce2001-us-squashfs-factory.bin
> - separate images for each version
>   - lede-brcm47xx-mips74k-linksys-e1000-v1-v2-v2.1-squashfs.bin => 
> lede-brcm47xx-mips74k-linksys-e1000-v1-squashfs.bin, ...
> 
> best wishes and unicorns,
> mwarning
> 
> ___
> Lede-dev mailing list
> Lede-dev@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/lede-dev
> 


___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] fixing of image file names

[Moritz Warning]

Ok,

looks like I should make a patch. :P

On 11/28/2017 07:24 PM, Daniel Golle wrote:
> Hi Moritz,
> 
> thanks for stepping forward and adressing this issue.
> It'd be good to include the two assertions added to your list beelow.
> 
> On Tue, Nov 28, 2017 at 07:05:23PM +0100, Moritz Warning wrote:
>> Hi,
>>
>> I noticed that there are some image file names that do not follow the 
>> "common" name scheme.
>> Is it ok to change it? I would like to submit a patch.
>>
>> Some examples:
>> - all lower case image names
>>   - lede-ipq806x-EA8500-squashfs-sysupgrade.tar => 
>> lede-ipq806x-ea8500-squashfs-sysupgrade.tar
>> - revision between -
>>   - lede-mvebu-linksys-wrt1900acv2-squashfs-sysupgrade.bin => 
>> lede-mvebu-linksys-wrt1900ac-v2-squashfs-sysupgrade.bin
>> - region specific images with region identifiers (us, eu, il, ...)
>>  - lede-ramips-rt305x-wnce2001-squashfs-factory-northamerica.bin => 
>> lede-ramips-rt305x-wnce2001-us-squashfs-factory.bin
>> - separate images for each version
>>   - lede-brcm47xx-mips74k-linksys-e1000-v1-v2-v2.1-squashfs.bin => 
>> lede-brcm47xx-mips74k-linksys-e1000-v1-squashfs.bin, ...
> 
>  - board_name (in target userspace) == profile (in imagebuilder) == DTS name
What is the target userspace and what does DTS mean?

> 
>  - image_filename == 
> ${distro}-${target}-${subtarget}-${board_name}-${fstype}-${imgtype}
> 
> that would make identifying sysupgrade images much more straight
> forward (and hence automatizable).
> 
> See also
> https://github.com/aparcar/attendedsysupgrade-server/issues/80
> 
> 
> Cheers
> 
> 
> Daniel
> 


___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

[LEDE-DEV] fixing of image file names

[Moritz Warning]

Hi,

I noticed that there are some image file names that do not follow the "common" 
name scheme.
Is it ok to change it? I would like to submit a patch.

Some examples:
- all lower case image names
  - lede-ipq806x-EA8500-squashfs-sysupgrade.tar => 
lede-ipq806x-ea8500-squashfs-sysupgrade.tar
- revision between -
  - lede-mvebu-linksys-wrt1900acv2-squashfs-sysupgrade.bin => 
lede-mvebu-linksys-wrt1900ac-v2-squashfs-sysupgrade.bin
- region specific images with region identifiers (us, eu, il, ...)
 - lede-ramips-rt305x-wnce2001-squashfs-factory-northamerica.bin => 
lede-ramips-rt305x-wnce2001-us-squashfs-factory.bin
- separate images for each version
  - lede-brcm47xx-mips74k-linksys-e1000-v1-v2-v2.1-squashfs.bin => 
lede-brcm47xx-mips74k-linksys-e1000-v1-squashfs.bin, ...

best wishes and unicorns,
mwarning

___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

[LEDE-DEV] LEDE/OpenWrt firmware wizard

[Moritz Warning]

Hi,

I've put online a firmware wizard for LEDE:

http://mwarning.de/firmware-wizard/
(Sources: https://github.com/freifunk-bielefeld/firmware-wizard)

Build with rather plain HTML5/CSS/JS. Merge requests are welcome.
Everything is still rough around the edges.

It would be nice if downloads.lede-project.org would set 
"Access-Control-Allow-Origin: *",
since the code tries to scrape the download site. So far I use a pre-scraped 
file index as a workaround.
But that causes the file links to not work..

Have fun,
mwarning

___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

[LEDE-DEV] LEDE/OpenWrt firmware wizard

[Moritz Warning]

Hi,

I've put online a firmware wizard for LEDE:

http://mwarning.de/firmware-wizard/
(Sources: https://github.com/freifunk-bielefeld/firmware-wizard)

Build with rather plain HTML5/CSS/ES6. Merge requests are welcome.
Everything is still rough around the edges.

It would be nice if downloads.lede-project.org would set 
"Access-Control-Allow-Origin: *",
since the code tries to scrape the download site. So far I use a pre-scraped 
file index as a workaround.
That causes the file links to not work..

Have fun,
mwarning

___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] [OpenWrt-Devel] Remerge logo ideas

[Moritz Warning]

Looks nice.

random idea, merge antenna with O of OpenWrt?

On 05/29/2017 01:10 PM, Jamie Stuart wrote:

See another iteration, with:

- correct capitalisation
- antenna to the side (will not work with lowercase ’n’)
- open sans typeface (open source)
- mockups of website header
- accent colours

http://i.imgur.com/ZKtcFXo.png



On 29 May 2017, at 13:52, John Crispin  wrote:



On 29/05/17 12:11, Jamie Stuart wrote:

Hi,
First of all, I’m glad to hear the process of remerging LEDE with OpenWrt is 
moving forward.
For what it’s worth, if prefer the LEDE name (it’s friendlier - ‘leddy’ - and 
not tied to the name of an old router!)

However, it seems the consensus is that the OpenWrt name should remain. I 
thought that maybe we should take this opportunity to at least give the project 
an updated look?
Maybe a new logo? I’m personally not one for mascots, so I had a quick go at a 
few simple text-based designs:

http://i.imgur.com/9zyXSYR.png

What are you thoughts?

Jamie, onebillion


Hi,

the correct spelling is OpenWrt with a capital O and W. could you add that to 
the proposal aswell please ? ideally with and without the antenna feature

   John

___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev





___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev




___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Re: [LEDE-DEV] nodogsplash v1.0.1 or 2.0.0

[Moritz Warning]

1.0.1 ist the current stable.
2.0.0 has not been released yet.

On 03/17/2017 10:33 PM, Nick Dennis wrote:
> Does anyone know if there is reason for the nodogsplash feed to be 
> downloading version 1.0.1? Could it be updated to download the current 
> version 2.0.0?
> 
> Thanks
> 
> 
> ___
> Lede-dev mailing list
> Lede-dev@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/lede-dev




signature.asc
Description: OpenPGP digital signature
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

[LEDE-DEV] Dedicated firmware images for several models missing

[Moritz Warning]

Hi,

Some devices are missing dedicated image files.
It confuses the hell out of me every time. ;-)

For example, the "bullet-m" image is for the m2 and m5 models and seem to be 
for the non existing
nanostation-loco-m2 / nanostation-loco-m5 / rocket-m2 / rocket-m5 / 
picostation-m2 images as well.

Would it be a good idea to create dedicated images? Is there are ticket already?

- mwarning



signature.asc
Description: OpenPGP digital signature
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

[LEDE-DEV] Image Wizard for LEDE?

[Moritz Warning]

Hi,

would the LEDE Community be interested in a firmware wizard like this one?

https://firmware.darmstadt.freifunk.net/

Sources: https://github.com/freifunk-darmstadt/gluon-firmware-wizard

It would take some time to add matchers for most of the images.
The current problem is that it is quite hard to find the correct image.
Current image names can be rather confusing for the ordinary user.

- mwarning



signature.asc
Description: OpenPGP digital signature
___
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev