OpenWrt Forum Archive

Topic: OpenWrt Wiki – Maintenance

The content of this topic has been archived between 24 Apr 2018 and 2 May 2018. There are no obvious gaps in this topic, but there may still be some posts missing at the end.

danitool wrote:

What about images uploading?, as default the location is the same for  all images even when you upload from totally different articles. The directory is growing and the previews makes it annoying specially for people with low bandwiths, uploading an image is becoming slower and they are all mixed. They should be in different directories.

Done.

All media files are now in the :media namespace and sub-namespaces.
Upload of media files is only allowed to those namespaces. Attempting to upload to a different namespace will produce an error.

In addition to this, many media files have been renamed to something usefull, i.e. "tp-link_tl-mr3020_board-top.jpg" instead of "20120923125558.jpg".

Update as per today: 102 devices with missing confirmation.
Your confirmation of working OpenWrt on these devices is very welcome!

tmo26 wrote:

Confirmation missing, that OpenWrt is working on several devices

We currently have 72 devices in the Table of Hardware, that are showing promising signs of OpenWrt support like "changeset available" or even "firmware download link available". However, confirmation that OpenWrt is really working on these devices is still missing (-> no entry in columns "Supported Since Rel" and "Supported Current Rel").


How you can help to improve the data

Go to https://wiki.openwrt.org/toh/views/toh_admin_wip2 and check if you can deliver any of the below information:

  • What is unsupported (e.g. WLAN, ADSL, …)? → update "Unsupported" column

  • Do you own one of the devices shown below and can you confirm that it is working with OpenWrt version xyz? → update "Supported Since Rel", "Supported Current Rel column"

  • Is there an image available, but we don't know of it? → update "Firmware OpenWrt Install URL", "Firmware OpenWrt Upgrade URL" column

  • Is there a devicepage available, but we don't know of it? → update "Device Page" column


Editing the dataentries

To edit the dataentry of a device, click on the "View/Edit data" at the very end of the devices table row.
On the following page, clicking the LEFT edit button below the data will lead you to an editing form.

Do your changes, and before saving them, provide a short description of your change and possibly your datasource (e.g. "Supported current rel = 15.05, confirmed by own experience with this device and this OpenWrt version") in the summary field, which should be near the "Save/Preview/Cancel" buttons of the editor.

Your help in improving the OpenWrt wiki is greatly appreciated!
Have fun! ;-)

it would be very nice to have more fields in the table of hardware, showing wifi type, external antennas, USB, TTL, eth ports, gigabit/fastethernet, and so on with features that people might look for.

This is what I see: https://dl.dropboxusercontent.com/u/475 … 6%3A34.png

That table wastes a column with an index number I'm not sure what's for, could use A or D instead of Avaliable and Discontinued (or even do with a simple X in the field or the lack of such X in a Available column), Support Status should be a single column (currently split into "Unsupported", and two Supported Since for some reason, also links left expanded wasting space), it lacks a way to reach the router's page from that table.

I was talking about adding such fields to that table, since I don't see them currently.

As I see from each router's tech data here https://wiki.openwrt.org/toh/hwdata/7li … ks_px-4885 You do have that in the system. Why isn't it shown?

To make an example, I was talking about doing something like dd-wrt wiki's tables of hardware http://www.dd-wrt.com/wiki/index.php/Supported_Devices

Where you can see such data.

(Last edited by starshipeleven on 5 Mar 2016, 11:38)

starshipeleven wrote:

That table wastes a column with an index number I'm not sure what's for

For counting.


could use A or D instead of Avaliable and Discontinued (or even do with a simple X in the field or the lack of such X in a Available column)

We don't like abbreviations which need to be explained.


Support Status should be a single column (currently split into "Unsupported", and two Supported Since for some reason

Reason: Those are quite different information.
Supported since Rev -> contains the link to the revision with which support has been added
Supported since Rel -> contains first official supported release
Unsupported -> Contains information about what in detail is unsupported (e.g. ADSL modem)


also links left expanded wasting space

The links I see in your screenshot do not waste any space. It' something you don't see that wastes space. Scroll to the right.


it lacks a way to reach the router's page from that table.

Scroll to the right and you will find the desired link.

how I'm supposed to scroll to the right?

Where is the scrollbar? (you saw the screenshot right?)

(Last edited by starshipeleven on 5 Mar 2016, 13:06)

Reload the page, then you will see smile

NO.

Don't take it wrong.

But NO.

If I want to see hardware specs I need to scroll a screen to the right by using friggin keyboard arrows (slow clap for the web designer).
By the time I got to the hardware specs I have lost sight of the router name. If I need to look at things I need to order them and then remember how many records it goes down, scroll to the left a screen, and see the names.

Is that a readable table for you? Do you program only in assembler perhaps? Have you never ever seen a table in a website or paper or whatever? Have you seen the dd-wrt one?

For counting.

I don't see why I need to know what index number is a specific router in the table/database. Table maintainers do. What about making a "maintainer view"?

We don't like abbreviations which need to be explained.

Then use abbreviations that don't need to be explained. Like making "Available" column and setting a X for the available ones, nothing for the unavailable/unknown ones.

Reason: Those are quite different information.

Supported since Rev + Supported since Rel are redundant.
You either list the trunk rev if it isn't already supported by official release OR the release.

Still, leaving both link to trunk rev and release version in the same cell is fine too.

Because if it is supported by a official release the "Supported since Rev" becomes wasted space in the table, if one needs to compile old trunk versions can go fetch the very-less-used info from the specific router's page or something.

The links I see in your screenshot do not waste any space.

Yes they do, and for no good reason. leave a link icon and save the space occupied by the url.

It' something you don't see that wastes space. Scroll to the right.

Do you realize that to see the info I need you force me to scroll for at least a screen's worth for no reason?

That table has to be readable by humans, not by machines. Please keep in mind usual human limitations when designing it.

(Last edited by starshipeleven on 5 Mar 2016, 17:43)

Redundant columns: There is no redundant column in this table, since this table lists all available columns.
What are you searching for in detail? Maybe you don't need the biggest table we have, but only a subset of fields? Please list the fields that are of interest for you.

Column headings getting out of sight: Known issue -> https://github.com/splitbrain/dokuwiki- … issues/185
Feel free to improve the data plugin with this functionality.

Wasted space by links: Known issue -> Feel free to improve the data plugin with this functionality.

15.05.1 release seems to have invalidated quite many download links.
Apparently some devices have links that specify "latest" but the file name still contains the release reference 15.05.
Those links are now invalid as latest points to 15.05.1

Example:
https://forum.openwrt.org/viewtopic.php?id=64174
https://downloads.openwrt.org/latest/ar … actory.bin
https://wiki.openwrt.org/toh/tp-link/tl-mr3420
I am not sure if there is any mass-update way to fix those pages that have ...latest...15.05... links.

https://forum.openwrt.org/viewtopic.php … 10#p319210
https://forum.openwrt.org/viewtopic.php … 98#p318698

The wiki pages with the "plain old" direct links to 15.05 releases work (but point to old stuff).
And of course some pages have already been updated to point directly to .../chaos_calmer/15.05.1/...15.05.1...

What's better: Link to "latest" and get broken links with a new release (this could serve as a sign that the fw donload link needs to be updated), or use plain links w/o "latest", resulting in working but outdated links?

I tend to the latter one, w/o the "latest" in the url.
The "latest" was good at times where the release wasn't yet included in the fw name -> no need for updating the fw link at all, but leaving the user with files where nobody could tell what release it was.

Doing the necessary changes by batch update should be possible.

Personally I would prefer outdated but working link, i.e plain/direct link solution.
That is more helpful for novices, who can actually download something.
(The "latest" leads to broken links, which causes unnecessary discussions and bug tickets.)

Done.

Hi!

I've updated a bit the wiki page about the DGN3500 & DGN3500B.
Fact is I cannot understand how to filter results for datatables to show both the DGN3500 and DGN3500B; I tried to put an * to include all the results, but it doesn't work.
Could you explain me how to do so?

thanks

Hi all,

The OpenWrt wiki has just moved to a new server - waiting for the DNS updates. Please report any errors or slowness in the next few days.

Many thanks,
-w-

M3m3nt0 wrote:

I've updated a bit the wiki page about the DGN3500 & DGN3500B.
Fact is I cannot understand how to filter results for datatables to show both the DGN3500 and DGN3500B; I tried to put an * to include all the results, but it doesn't work.
Could you explain me how to do so?

Done, filters adjusted.

wigyori wrote:

Hi all,

The OpenWrt wiki has just moved to a new server - waiting for the DNS updates. Please report any errors or slowness in the next few days.

Many thanks,
-w-

Wouldn't that usually warrant:
a) a mail to dev ahead of time
b) with a short explanation what for
c) and an if all goes well editing is back by ...

For a) it's too late but b) and c) are still of interest.

PS: About mails to dev, what are you up to at https://github.com/openwrt/openwrt?

Hi,

info written on this page

https://wiki.openwrt.org/doc/howtobuild/single.package

seems to be outdated. Is it possible to update it?

I needed to compile a single package, found this page. It says in an example to run following cmd for compiling ncurses:

make package/ncurses/compile

First off, ncurses is not there. I have downloaded latest repo couple days ago. I wanted make some changes in aircrack-ng and recompile.

when I locate the package and run make like this I get an error:

cihan@cihan-N550JV:~/projects/openwrt/2503$ make build_dir/target-mips_34kc_musl-1.1.16/aircrack-ng-1.2-rc1/clean
make[1] build_dir/target-mips_34kc_musl-1.1.16/aircrack-ng-1.2-rc1/clean
make -r build_dir/target-mips_34kc_musl-1.1.16/aircrack-ng-1.2-rc1/clean: build failed. Please re-run make with -j1 V=s to see what's going on
/home/cihan/projects/openwrt/2503/include/toplevel.mk:192: recipe for target 'build_dir/target-mips_34kc_musl-1.1.16/aircrack-ng-1.2-rc1/clean' failed

make: *** [build_dir/target-mips_34kc_musl-1.1.16/aircrack-ng-1.2-rc1/clean] Error 1


I go to the dir of the package, do a 'make clean' there. objects files are gone. then I do 'make', then it starts compiling with gcc instead of cross-compiler.

ps: sorry if this is not the right thread

(Last edited by papates on 31 Mar 2017, 16:22)

The discussion might have continued from here.