[System] You are an OpenWrt support assistant; use the following forum posts as background but remember they may be incomplete or outdated—if you’re unsure, flag the uncertainty and point the user to the official OpenWrt documentation.

[User]
Title: Help pre-select new OpenWrt One logo in the poll

You may already know that there's an upcoming hardware design named OpenWrt One, which is expected to be available in the near future. Naturally, this significant milestone calls for an appropriate logo
Logo variant A
Logo variant B
Logo variant C
Logo variant D
Logo variant E
I'm reaching out to request your participation in a preliminary vote over the next 3 days, where I'd like you to choose your preferred option from among 5 variants. Your selection will help me determine which variant to nominate in the official vote, as outlined in the project rules. Thanks for help!
Logo variant A
Logo variant B
Logo variant C
Logo variant D
Logo variant E
None of the above
49 voters
64 total votes

3

[Assistant]
Needs a caption:
"One firmware/device to rule them all"?

Although I like the "wedge shape" underneath the logo, I just voted "None of the above" for a couple reasons:
It violates our style guide for use of the logo. See https://github.com/openwrt/branding/blob/master/openwrt-styleguide.pdf All these variations seem to violate one of the "misuse" rules by adding elements to the logo. They also only have two arcs instead of the three arcs in the "o".
This is a "clever" use of (a variation of) the OpenWrt logo as the initial "O" of OpenWrt. But in our next 20 years, there will likely be an OpenWrt Two, Three, etc. I would prefer to choose the (unaltered) Logo with the word "one" (or "two" or "three"...) next to it. I would preserve the wedge underline shape, though, to indicate that it's all one mark.
Thanks for listening.

2 Replies
8

@ynezz
I cast my vote, but it honestly feels like splitting hairs, they are all good despite their minor differences, I would have added an option "All of the above". as well.
@richb-hanover-priv
Maybe in 10 years it will be OpenWrt One 2034 (for smaller form-factor) and OpenWrt TwO (for larger one).

2 Replies
1


[System] You are an OpenWrt support assistant; use the following forum posts as background but remember they may be incomplete or outdated—if you’re unsure, flag the uncertainty and point the user to the official OpenWrt documentation.

[User]
Title: PPPoE “unknown error (USER_REQUEST)”

Router: TP-Link TL-WR841N/ND v8
Kernel Version: 4.14.152
Build: latest master (18.06.5)
WAN interface (PPPoE) takes a lot of time to reconnect internet. Often gives me this error
daemon.info pppd[2767]: Plugin rp-pppoe.so loaded.
daemon.info pppd[2767]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.7
daemon.notice pppd[2767]: pppd 2.4.7 started by root, uid 0
daemon.warn pppd[2767]: Timeout waiting for PADO packets
daemon.err pppd[2767]: Unable to complete PPPoE Discovery
daemon.info pppd[2767]: Exit.
Sometimes luckily it connects other times it takes n number of times of re-connections.
Never happened this before on stock firmware or for any other routers.
More Info:
Switch "switch0" (AR934X built-in switch)===> only CPU (eth1) tagged default
Everything else is default.

Solved by AlanDias17 in post #20
Solved. Turns out current PPPoE module was creating multiple PPPoE connections after one another without properly terminating the previous session and my ISP doesn't allow multiple PPPoE connections simultaneously. Hence it was taking time until ISP server resets my session ID>to connect internet. …
3 Replies

[Assistant]
Please post the whole network configuration in preformated text </> rather than screenshots
uci show network

uci show network output:
network.loopback=interface
network.loopback.ifname='lo'
network.loopback.proto='static'
network.loopback.ipaddr='127.0.0.1'
network.loopback.netmask='255.0.0.0'
network.lan=interface
network.lan.type='bridge'
network.lan.ifname='eth1.1'
network.lan.proto='static'
network.lan.ipaddr='192.168.1.1'
network.lan.netmask='255.255.255.0'
network.wan=interface
network.wan.ifname='eth0'
network.wan.proto='pppoe'
network.wan.username=*********
network.wan.password=*********
network.@switch[0]=switch
network.@switch[0].name='switch0'
network.@switch[0].reset='1'
network.@switch[0].enable_vlan='1'
network.@switch_vlan[0]=switch_vlan
network.@switch_vlan[0].device='switch0'
network.@switch_vlan[0].vlan='1'
network.@switch_vlan[0].ports='1 2 3 4 0t'

AlanDias17:
daemon.warn pppd[2767]: Timeout waiting for PADO packets
There doesn't seem to be any response from the ppp server.
Make sure that the modem is synchronized. If this is not the issue, ask your provider if you must set any service name or access concentrator.

2


[System] You are an OpenWrt support assistant; use the following forum posts as background but remember they may be incomplete or outdated—if you’re unsure, flag the uncertainty and point the user to the official OpenWrt documentation.

[User]
Title: Access to right . com . cn

Hi guys,
I have a bricked phicomm k3 which i'm trying to revive and will require some spi soldering etc. I see there is a large community over right.com.cn , unfortunately can't get access. I'll need at least a file downloaded.
I see payments are required for registering and accessing content which is perfectly fine with me but couldn't figure Alipay (and not sure if i want my cc there). If someone has account there and can help me with grabbing some files I'm of course willing to wire the required cash via paypal. Or if you know a way i can register in other way than Alipay.
Thanks!

1

[Assistant]
Send the link to the post,I'll download it for you.

3 Replies
1

Thanks!
So far I'm after K3CFE217.zip from this https://www.right.com.cn/forum/thread-308276-1-1.html thread. There a lot of scrolling involved. Once my chips arrive I might need something else but that should get me rolling and is highly appreciated.

There you go.
https://drive.google.com/file/d/1NKVAt6frsP6iDXTM8bBr9s5qArbgvHwJ/view?usp=sharing
At the end of that article, the author noted that he could not flash on Windows10,instead he suggest using Windows XP.

1


[System] You are an OpenWrt support assistant; use the following forum posts as background but remember they may be incomplete or outdated—if you’re unsure, flag the uncertainty and point the user to the official OpenWrt documentation.

[User]
Title: OpenWrt as AD controller

Hello,
since OpenWRT supports samba - i have an idea. Can an OpenWRT act as domain controller ?
Inclusive updates to dnsmasq to cover the domain controller.
Is there a GUI to manage the domain ?
regards

[Assistant]
This looks like a bad idea.
Deploying and supporting a Samba AD DC on a home network is overkill.
And in case of a business/enterprise, it won't be reliable and secure enough.

You never want a MS master service as important as AD running as a compatoble/emulation service but as a native MS service. This service is way too important to run in emulation mode, if running for actual business needs. If its just to fool around, maybe.
However, it is very unwise to run such a service on an Internet facing computer/device, you should always hide behind the front line, in the event the front line is under attack, compromised or rendered disfunctionnal, the front line can be taken offline and the LAN is still functional, the AD being still on active duty fullfilling its job. Furthmore, Samba is a “prized” service for active attack on a front line device, far from secturity “best practice”.
I suggest you read this page on gardening you router :
Hardening your OpenWrt device
Notice at the end of page the 4 high-value targets, Samba being one of them.
Just a thought...

3 Replies

I replied to the topic, I meant to reply to you...


[System] You are an OpenWrt support assistant; use the following forum posts as background but remember they may be incomplete or outdated—if you’re unsure, flag the uncertainty and point the user to the official OpenWrt documentation.

[User]
Title: Wi-Fi EasyMesh

https://www.wi-fi.org/discover-wi-fi/wi-fi-easymesh
I think openwrt is a good platform to implement Wi-Fi EasyMesh.
What's your opinion?

Solved by bluewavenet in post #35
The very first post in this thread: I think the thread is done after five years. Time for it to be closed.
@psherman
@Pablomagno
, if you would care to share some code or point to your repository, you could open a new thread, then it can be discussed whether "openwrt is a good platform to implemen…
1 Reply
1

[Assistant]
As my opinion, 66 pages of spec, including the arguable security implications of enabling TR-069 (remote management of CPE by ISPs) and "push-button configuration" (WPS) don't have me terribly excited.
It potentially could be implemented by a combination of user-space programs and driver modifications to implement both the logic of the protocol, as well as the new message types.
My opinion is that this is a forward-looking draft specification primarily intended to guide in-chip implementation for the next generations of devices.

1 Reply
2

Well, it seems that prplMesh has brought the idea into reality.
There is even prplMesh-openwrt and prplwrt !
Has anyone got experience on these?

3

I somehow fail to understand how this is different from a “normal” 802.11s mesh, other than it uses a similar method like WPS to add extra mesh points.
Could someone explain that in 3 easy sentences?


[System] You are an OpenWrt support assistant; use the following forum posts as background but remember they may be incomplete or outdated—if you’re unsure, flag the uncertainty and point the user to the official OpenWrt documentation.

[User]
Title: I need help forming a class-action against AT&T (IPv6 rights)

I demand my /56
This class-action will be in two parts:
AT&T doesn't have an escalation process to take responsibility for their customer premise equipment. If at the end of the call to tech support regarding a bug in the behavior of their CPE, you are forwarded to their pay-per-incident support for which you pay $59.95 for them to forward you back to the same tech support call center.
The two CPE options for GPON fiber was the BGW210 and the current BGW320. Both contain broken behavior with the DHCPv6 server offered to the pass-thru third-party router. For any request of a prefix delegation length, a /64 is returned. As a /64 only represents a single address block, it is useless for subnetting. The best-practices recommendation is to offer a /56 (256 address blocks) for residential service.

3

[Assistant]
I'm wondering if we shouldn't write text for proposed legislation for ipv6 consumer rights. I note you're also in California. Perhaps that's a good starting direction or a parallel track.

3

Proposed legislation is a great idea. For me, that would be a visit to CA State Rep. Nancy Skinner's office. I've never done anything like this before. Exciting. At least their office could help me get in touch with the public utilities council for filing a complaint against AT&T

First volley served! I filed this with Nancy Skinner's office. I hope they get back in touch with me
"Consumer rights. The product sold by AT&T, network ISP services, is
deficient according to the IETF recommended practices for the assignment
of end-user prefixes. This "delegated prefix" is supposed to contain
256 blocks. AT&T is only giving me a single block which is restricting
my ability to configure my local area network"

1 Reply
3


[System] You are an OpenWrt support assistant; use the following forum posts as background but remember they may be incomplete or outdated—if you’re unsure, flag the uncertainty and point the user to the official OpenWrt documentation.

[User]
Title: Luci Gui improvement needed

Hello. First time posting here, I don't know if it's the right place. If it's not, I'm sorry.
I just wanted to share some feedback regarding my experience with LEDE so far.
This is a great community with a lot of information and many great people who are willing to help with any issues. After making the decision to go with LEDE instead of the others. I spent some time learning the many features that are available and how to use them. Some are easier than others. I realize that LEDE is a great project however if you're a complete noob, it's kinda hard to take advantage of the many features available. From my personal experience, I think Luci GUI if improve, would be a great help for us noobs. For example, VPN is one feature that's very popular, everyone is trying protect their privacy from ISP snooping. However the way to set it up is very confusing. The Luci interface is no help to configure vpn service and others like DNS encryption. I believe a lot of features of LEDE are being missed especially noobs because of confusing and lack of information from the User Interface. I don't know if there are any plans to add these features and improvements. I just thought I would share my experience so far.
Thanks!

1 Reply
2

[Assistant]
You are write, but it's finding some one who would like to work on it. I was on about this to a fue people the other day in regards to setting up USB drives on OpenWRT. It can be verry hard. The interface will not help you to understand what partitions you have on a drive or even if your filesystem has the rite driver or package installed. same gos for setting up things like ddns or dnscrypt.

1

OpenWrt/LEDE seems to be UCI driven, so I would not expect any improvements in LuCI anytime soon.

@tapper
I was trying to do this the other day I couldn't do it so I gave up on it. It's one of the reasons I wanted to share my feedback with the community.
@jwoods I do understand its mostly UCI driven, however a mentally that's just the way it is doesn't really welcome improvements. I hope (not expect) that one day Luci Gui will be improve better, because it would really help a lot of people.
Hopefully after the merger someone find it important to work on these improvements. It would be very helpful and people won't be starting new topics just to find help using the basic features of LEDE.
Thanks!

2 Replies
1


[System] You are an OpenWrt support assistant; use the following forum posts as background but remember they may be incomplete or outdated—if you’re unsure, flag the uncertainty and point the user to the official OpenWrt documentation.

[User]
Title: Help pre-select new OpenWrt project logo in the poll

This is continuation of Refresh project identity - new OpenWrt project logo topic, based on the received feedback.
Logo variant E
Logo variant F
Logo variant G
Logo variant H
Logo variants in black&white and inverse
This is for your overview only, how it's going to look in such cases, not for voting
So I would like to ask you for your vote in the following 3 days, helping me pre-select one variant out of 4, your favorite so to speak. I'm then going to propose winner of this pool in the official vote as defined in the project rules.
Logo variant E
Logo variant F
Logo variant G
Logo variant H
None of the above
118 voters
118 total votes

10

[Assistant]
Too bad the other colour combinations have gone out the window. I liked the greenish tints.

1

I've posted my vote. You should vote first, then click the triangle to see my reasoning.
Summary
Thanks!
PS If you want to do the twisty-triangle things, use [details=Summary] ... your text here... [/details] It's called a "disclosure triangle" in the GUI biz...

1

Is the voting closed already?
I find no way to vote... (instead I see the results)


[System] You are an OpenWrt support assistant; use the following forum posts as background but remember they may be incomplete or outdated—if you’re unsure, flag the uncertainty and point the user to the official OpenWrt documentation.

[User]
Title: FYI/A: Why Your Wi-Fi Router Doubles as an Apple AirTag

https://krebsonsecurity.com/2024/05/why-your-wi-fi-router-doubles-as-an-apple-airtag/
In late March 2024, Apple quietly updated its website to note that anyone can opt out of having the location of their wireless access points collected and shared by Apple — by appending “_nomap” to the end of the Wi-Fi access point’s name (SSID). Adding “_nomap” to your Wi-Fi network name also blocks Google from indexing its location.
.....
“You may not have Apple products, but if you have an access point and someone near you owns an Apple device, your BSSID will be in [Apple’s] database,” he said. “What’s important to note here is that every access point is being tracked, without opting in, whether they run an Apple device or not. Only after we disclosed this to Apple have they added the ability for people to opt out.”
OpenWRT's BSSID "randomly generating" MAC addresses in the advanced settings of the wireless network come to the rescue

2 Replies
2

[Assistant]
This is nothing new. This has been the case for at least a decade. Phones use a fusion of (at least) 3 systems to get precise location data: GPS, cellular tower triangulation, and wifi network proximity. Devices without GPS and cellular are also able to get reasonably good location data in many places by using the databases of wifi network proximity.
Since your wifi network is stationary, it doesn't really reveal anything interesting -- it's not like tracking your movements with an airtag -- not the same thing at all. Randomly generating wifi BSSIDs doesn't 'fix' the issue (especially because it's not really an issue). This is also not really an OpenWrt topic... the article talks about appending a string to the end of the SSID -- this can be done on any wifi device and doesn't require any special techniques.

2 Replies
3

Guess BSSID randomization is still good to have especially for those travel router owners as mentioned by the researchers:
https://www.cs.umd.edu/~dml/papers/wifi-surveillance-sp24.pdf
11. Conclusion
In this work, we demonstrated the large-scale privacy
threat presented by Apple’s WPS. A remote, unprivileged
adversary, possessing only the knowledge of which parts of
the MAC address space have been assigned by the IEEE, can
quickly build a corpus of hundreds of millions of geolocated
BSSIDs, spanning all seven continents and extending to even
the most remote corners of the Earth.
The ability to obtain this worldwide view of Wi-Fi
AP distribution is a privacy vulnerability. Because people
often move with their AP, querying a WPS for the same
BSSIDs over time reveals when routers—and by proxy their
owners—move. We demonstrated that this attack could be
applied to individual users, such as travel router owners,
as they move from location to location. We also showed
that WPSes could be used to find sensitive equipment, like
Starlink routers in Ukraine.
There are practical steps to take to limit this vulnerability. WPS operators can limit access to their APIs, governments can legislate that their citizen’s devices not be used
as geolocation landmarks, and users wary of tracking can
be sure to not use the same AP at multiple locations.
However, the most robust solution to this problem is to
implement the same privacy protections that were implemented in mobile devices in Wi-Fi APs. BSSID randomization at each boot, or when the device changes locations
prevents user tracking even in a world in which WPS
operators permit open access to their APIs.

1 Reply
1

dudez7:
In late March 2024, Apple quietly updated its website to note that anyone can opt out of having the location of their wireless access points collected and shared by Apple
Ahhhh....good news because about ~10 years my AP is using the SSID appendix "_nomap" ...and yes, I know: All the twenty APs around me don't ;- )
dudez7:
OpenWRT's BSSID "randomly generating" MAC addresses in the advanced settings of the wireless network come to the rescue
Wouldn't it be better to add "_nomap" to your SSIDs, or even better: Do both measures?
One question about randomly generated BSSIDs: How "good" aka randomly are the OpenWrt generated MACs?
psherman:
This is also not really an OpenWrt topic
...but it helps to spread the word about the Apple AND Google opt-out in a network and/or security and/or privacy interested multiplier "influencer" group

2 Replies
3


[System] You are an OpenWrt support assistant; use the following forum posts as background but remember they may be incomplete or outdated—if you’re unsure, flag the uncertainty and point the user to the official OpenWrt documentation.

[User]
Title: Why are there barely any tutorials?

OpenWRT, sadly, has almost no tutorials on how to set things up, the wiki is too technical, and it is very shunning for beginners. I've been trying to find a guide on how to install reboot scheduler, and all they ever talk about are CLI commands that I don't understand as I don't know networking. It's daunting to say the least. I understand those who know all of it and configure with ease, but it's sad to see newcomers or beginners shyed away by too much technicality or who only want to use LuCI. LuCI itself has no guide which explains what each checkbox does what, the options are just there and it is so difficult to find out what some of them even do.

4 Replies
3

[Assistant]
redsoviet:
how to install reboot scheduler
i'm glad you listed you ultimate goal... it's important to put some context...
redsoviet:
almost no tutorials on how to set things up
think alot of the time there are too many!
you have some valid points... and i think users similar to can be broadly categorized by;
I need simple ( common ) graphical features that are easy to understand
and
I want to do something specific, easily...
On point one, i'd agree with you.... easy ways to do common things and related documentation can be improved alot.
On point two... from what I see here... 77+% of "newcomers" are attempting to do something advanced/custom... which is why they probably chose / needed openwrt in the first place. It a bit of a catch-22....
There are some simple options for your intended result. I can see tho' how tracking the "best" one down might be overwhelming....
Why....
a) basic users rarely give the right constructive feedback in the right places to achieve change / in the right numbers / for the duration needed to instill change... ( maybe you can write a simplified wiki article when you find your solution? )
So i'm glad you posted your experience here... you never know.. doing so might lead to the very improvements you need.

3

redsoviet:
OpenWRT, sadly, has almost no tutorials on how to set things up, the wiki is too technical, and it is very shunning for beginners.
Just for reference, can you point to a "similar product" (open or closed router-oriented OS, or even a standalone router) with better documentation or more tutorials, please?
redsoviet:
I've been trying to find a guide on how to install reboot scheduler [...]
Scheduled reboots are a bad practice, or a last resort when everything else fails; I guess there is just a very few people doing scheduled reboots.
Again, can you point to a similar product with better documentation for scheduled reboots?
redsoviet:
[...] all they ever talk about are CLI commands that I don't understand as I don't know networking. [...] LuCI itself has no guide which explains what each checkbox does what, the options are just there and it is so difficult to find out what some of them even do.
Well, perhaps OpenWrt is not for you, just like a plane is not for people who cannot pilot a plane.
Is your complain about how to use / configure OpenWrt, or about networking in general?

2 Replies
4

redsoviet:
I've been trying to find a guide on how to install reboot scheduler, and all they ever talk about are CLI commands that I don't understand as I don't know networking.
OpenWrt Wiki – 3 Oct 15
Scheduling tasks with cron
Scheduling tasks with cron This article relies on the following: * Accessing web interface / command-line interface * Managing configs / packages / services / logs Introduction * OpenWrt can run scheduled tasks using cron service. * This...
You don't need networking knowledge for periodic reboot via cron.

2 Replies
7


[System] You are an OpenWrt support assistant; use the following forum posts as background but remember they may be incomplete or outdated—if you’re unsure, flag the uncertainty and point the user to the official OpenWrt documentation.

[User]
Title: How to delete account?

How to delete forum.openwrt.org account? I don't need it. Couldn't find button.

[Assistant]
Done, account anonymized (too old to be completely deleted) and suspended.

3 Replies

Same issues. I want to delete my account but I don't find the button.

Done, account anonymized (too old to be completely deleted) and suspended.

1 Reply


[System] You are an OpenWrt support assistant; use the following forum posts as background but remember they may be incomplete or outdated—if you’re unsure, flag the uncertainty and point the user to the official OpenWrt documentation.

[User]
Title: OpenWrt Homepage (Wiki) offline for unplanned maintenance

We’re currently investigating unusual activity on the OpenWrt Wiki server and decided to shut down the machine since we have reasons to suspect a security compromise.
We'll follow up with further details in this thread as soon as we have more information. Since we do have to review the integrity of our wiki backups, restoring the website might take a little while.

20

[Assistant]
Update:
After reviewing the situation we found no indication of any unauthorized access to the system.
Background:
During maintenance work to implement performance improvements for the table of hardware (ToH) views on the wiki, which are currently the primary reason for severe system load, we encountered a debug log containing username and passwords of login attempts in clear text.
What we initially believed to be a malicious modification of the DokuWiki PHP code turned out to be leftover debug code from an earlier wiki migration. We removed the offending debug functionality and purged the related log file. As a precaution, we're going to force a password reset for all users.
Note that the user database itself contains one-way password hashes and was not compromised, neither did we find an indication of any unauthorized access.

19


[System] You are an OpenWrt support assistant; use the following forum posts as background but remember they may be incomplete or outdated—if you’re unsure, flag the uncertainty and point the user to the official OpenWrt documentation.

[User]
Title: Move away from GitHub

GitHub being Microsoft-owned, is not the ideal great place for community projects such as OpenWRT.
We all know about Microsoft's historically combative stance against FOSS projects, and recently Github has been randomly shadow-banning accounts in other communities that I'm a member of.
Operating on Github is antithetical to the spirit of the OpenWRT community, and even the Software Freedom Conservancy (a prominent supporter of OpenWRT) has long advocated for Open Source projects to switch from Github: https://giveupgithub.org/
I can see that this has been discussed before, but no move was ever made in the end. Is there anything I can do right now to help facilitate a move to a more honest and open source system, like Codeberg perhaps?

1 Reply
4

[Assistant]
Github is mirror of https://git.openwrt.org/

2 Replies
1

Not any more, since a while back everything including all PR is run and administered in github.

That git.openwrt.org link doesn't seem useful for anything other than viewing the changelogs, though? It looks and feels like an internal tool designed for no one other than the creators. I don't see a way for me to clone a repo from there - where do I even find a .git link? Where do I create a PR, or report an issue?
On the OpenWRT website I also see Github as being the only place to report bugs:
Hoping for some clarity directly from one of the project leaders since this is potentially an impactful change we're discussing here.

2 Replies


[System] You are an OpenWrt support assistant; use the following forum posts as background but remember they may be incomplete or outdated—if you’re unsure, flag the uncertainty and point the user to the official OpenWrt documentation.

[User]
Title: Is Breed Bootloader “author” hackpascal a Mediatek dev?

While researching Breed and MT7621A bootloader options I came across the pseudonym hackpascal. After encountering github,com/hackpascal I associated the name Weijie Gao with the pseudonym.
Yesterday (Feb 2nd 2021) the following was committed in the header of a file on github using the hackpascal account:
From b7c230c5ab9009d6d9612294dbb1084f2070610b Mon Sep 17 00:00:00 2001
From: Weijie Gao <weijie.gao@mediatek,com>
Date: Tue, 2 Feb 2021 10:51:25 +0800
Subject: armv8: do not read ESR_EL3 in AArch32 state
So apparently BREED is from Mediatek. Why would they go to such extreme lengths to avoid associating BREED with Mediatek? Are there any security implications to worry about? At any level, personal, political, etc.? Mediatek posts the source code for lots of bootloaders publicly including the 1st and 2nd stages for the MT7621, and complete versions of Uboot for other chips. Why is BREED different?
I posted this here too:
https://forum.doozan.com/read.php?8,115324
more links from searching and others in ^^^ forum thread:
https://breed.hackpascal.net/
https://blog.hackpascal.net/
https://github.com/hackpascal
http://projects.dymacz.pl/?dir=u-boot_mod
https://github.com/pepe2k/u-boot_mod
https://forum.archive.openwrt.org/viewtopic.php?id=55180

Solved by 981213 in post #2
FYI Breed is his personal project done with his free time at college, and he probably has absolutely no interest to donate all his prior work to his employer. There's no assotiation between breed and mediatek simply because it's not a mediatek project at all.
1

[Assistant]
FYI Breed is his personal project done with his free time at college, and he probably has absolutely no interest to donate all his prior work to his employer. There's no assotiation between breed and mediatek simply because it's not a mediatek project at all.

1 Reply
Solution
8

BREED works on Qualcomm/Atheros platforms as well, there's no reason MediaTek would spend their time on competitors' platforms. Like 981213 points out it's just coincidence the author happens to work for MediaTek now.

981213:
Thanks for clarifying this. I understand your role as a dev/ the chain of trust within openWRT, and I mean no disrespect, but do you have a source for this information?
IMO perhaps Mediatek should pay Mr. Weijie Gao an agreeable sum for his efforts and open source this code. Mr. Weijie Gao seems well worth the investment. This is my first point of contact with Mediatek as an electronics hobbyist, and it shapes how I view their company and hardware. As someone from outside of Asia, IMO the entire toolchain for network related hardware should be transparent. I would much prefer the ability to read the source and compile it myself, both for the peace of mind and learning experience.
-Jake

2 Replies


[System] You are an OpenWrt support assistant; use the following forum posts as background but remember they may be incomplete or outdated—if you’re unsure, flag the uncertainty and point the user to the official OpenWrt documentation.

[User]
Title: We need to talk about why OpenWrt doesn’t support automatic updates, saving configurations across updates, NIHS, and the developer clique

Everyone knows that we can't deploy OpenWrt to a user who can't maintain it themselves, because OpenWrt can't update itself. This restricts to use of OpenWrt to a small clique of users measured in the thousands, rather than ANYONE, who are measured in billions.
Everyone knows that OpenWrt doesn't save packages across upgrades, so anyone who isn't already capable on managing a local IT department can't keep a complex system up to date and working across upgrades.
Everyone knows that OpenWrt development stagnated and some developers split off to start LEDE.
For the good of the project today and in the future, I want to encourage all the "hardcore nerds" to think of the bigger picture and the millions of people out there who need good networking hardware powered by good networking software like OpenWrt. When I see a member of the community write code to make the system work better for the everyday user (like https://github.com/openwrt/openwrt/pull/1310 and there are others), only to be shut down by project leaders because "it's complicated", I see the fate of too many open source projects: death by self-strangulation, the programmers not seeing and understanding the users they're programming for. It's not about the feature or the code, it's about the effort YOU put in to make the SYSTEM work for MORE people.
I get that you probably work on OpenWrt for your own satisfaction. But I encourage you to look long-term at a time when there is no OpenWrt because you didn't include the convenient features that make it possible for 10x or 100x or 100,000x more human beings to adopt OpenWrt into their homes and workplaces.

1 Reply
6

[Assistant]
It seemed to me that the suggestion was to introduce this as separate package, possibly wrapping sysupgrade, which is a sensible approach for yet unproven code in my opinion.
The code in the PR you linked added a lot of complexity and hard-coded assumptions (builtin certificates, scraping of HTML directory listings to discover versions, assumptions about future version and feed formats etc.).
This is - to some extent - necessary in order to have something working now but this is not the kind of code that should end up in the low level system upgrade program given that we do not even know how downloads, version formats packages etc. will be called ten years down the road. For sure the builtin PGP certs will be expired by then.
Being part of sysupgrade and thus, the 'base-files' package, will also prevent users of this functionality to upgrade this package in order to make it conform to the latest release requirements.
As a separate, installable, arch agnostic package, possibly even in the base repository, the linked PR will be a suitable interim solution for some use cases, but in the long run a lot of things have to be done to enable proper automatic updates, such as:
Long term release planning
Well known procedures and update notification mechanisms
Proper management of trust anchors and involved certificates
Release quality management

11

I think the psychology of the project's management is what I'm talking about rather than any given merge request. We can move mountains to migrate to a new kernel, but features that only "normal" people would use remain bridges too far for years. This is about time and energy dedicated to things that aren't for us. You don't need the things I'm talking about. The indefinite postponement of "consumer"-facing features is, I think, a toxic trend that naturally creeps into open source projects, and we want to avoid it by focusing on what the next million users of the project will need.

1 Reply
4

ibex-are-goats:
It's not about the feature or the code, it's about the effort YOU put in to make the SYSTEM work for MORE people.
I get that you probably work on OpenWrt for your own satisfaction.
Applause, applause.
Doing my first (Assembler-)code almost half a century ago, I feel qualified to remind here of an "ancient" coding principle: "Egoless programming". Which seems to be forgotten in the modern universe of Open Source.

3 Replies
5


[System] You are an OpenWrt support assistant; use the following forum posts as background but remember they may be incomplete or outdated—if you’re unsure, flag the uncertainty and point the user to the official OpenWrt documentation.

[User]
Title: Stickers with the new OpenWrt logo

Hello,
has anyone produced stickers with the new 2020 OpenWRT logo yet? I would like to get some to attach on the devices on which I use OpenWRT. Alternatively, does anyone know of an online service that can produce not too many stickers of good quality at a reasonable price?
Thank you.
Cheers,
Dan

2

[Assistant]
I may order some stickers on Sticker Mule . It would be nice to share an order to keep cost low. Please let me know if anyone is interested.

Hello,
I don't know about the others, but maybe someone would be able to prepare wallpapers with a new logotype, graphics for T-shirts maybe?

2 Replies
1

For T-Shirts see Official OpenWrt merchandise: T-shirt (phase 1/3, ideas)

2


[System] You are an OpenWrt support assistant; use the following forum posts as background but remember they may be incomplete or outdated—if you’re unsure, flag the uncertainty and point the user to the official OpenWrt documentation.

[User]
Title: Curious about LEDE web site statistics?

The LEDE web sites (main site, forum, and downloads) recently began to use the awstats log file analyzer to summarize and display the web traffic for those sites. See the stats at:
LEDE Web Site: https://wiki.lede-project.org/stats/
LEDE Forum: https://forum.openwrt.org/stats/
LEDE Downloads: http://downloads.lede-project.org/stats/
In addition the About page of this forum has brief statistics as well.

2

[Assistant]
This is great data!!!
I think in particular that we should look to see if it's possible to tune the data on the file downloads, or at least be able to funnel this data off line for better stats.
Specifically, as a "feature" in the form of a package may be located under different targets, there should be some way of aggregating the variations of the *.ipk across all targets or instruction sets. This will allow the devs to see what's most popular to the community, which should help prioritize development efforts.
Similar with the targets themselves. What are the most popular platforms, and what can be sunset.
Is it possible to increase the displayed characters in the first column "downloads". It appears to only show the first 70 or so characters, and some of these entries are much longer.
Do we know if these stats account for all download activity, meaning does this include wget and opkg install calls?
I also expect that this does NOT include mirror activity, which is unfortunate.

1 Reply

Updated original post to say
In addition the About page of this forum has brief statistics as well.

@RangerZ
You're right - these pages provide a wealth of data. They're created by the awstats web server log analysis package to summarize the raw server logs. Here are quick answers to your questions:
The log summary probably does include each wget and opkg install (they'd be shown in server logs)
But... This log analysis only provides suggestive (not definitive) information about what's going on.
They would not show traffic to mirror sites. That would be up to the individual mirrors to provide.
I'm not sure that it's necessary to have an automatic analysis of the popularity of platforms/packages. We're not going to "turn on a dime" and start/stop support for any platform. Reviewing the popularity every 3-6 months (or when it becomes too hard/expensive to support a platform) seems like a reasonable choice.
We can probably tune up the config's for awstats to exclude boring info. For example,
wiki stats shouldn't show hits from /lib/... nor referrers from lede-project.org
forum stats shouldn't show hits from /message-bus...
... etc.


[System] You are an OpenWrt support assistant; use the following forum posts as background but remember they may be incomplete or outdated—if you’re unsure, flag the uncertainty and point the user to the official OpenWrt documentation.

[User]
Title: Kong has Moved to OpenWrt - Is this True or Fake?

As you may have noticed I have not been able to follow dd-wrt development for a few weeks now.
Due to changes in life I don't have time anymore to continue compile/test/publish any custom builds anymore.It is simply to time consuming, especially since I moved to openwrt.
It's been a fun time, but now it is time to move on.
https://www.desipro.de/dd-wrt/Notice.txt
This is being posted around the forums like reddit but i'm unsure if it's just an excuse to spam the desipro website as it doesn't seem to have anything to do with Kong?

2

[Assistant]
The desipro site is used by kong.
FYI see the dd-wrt forum item here.
Kong has been testing his own "community" build for a while (see this dd-wrt forum item).

2

He could do with a new website design as it visually reminds me of one of those fake websites full of install.exe files for windows users.

I personally don't care what his site looks like as I'm just grateful his builds are available.

1


[System] You are an OpenWrt support assistant; use the following forum posts as background but remember they may be incomplete or outdated—if you’re unsure, flag the uncertainty and point the user to the official OpenWrt documentation.

[User]
Title: [solved] Openwrt.org server configuration | 403 forbidden

Hello there,
could anyone from the openwrt.org team check the (web-/file-)server configuration?
Personally my router got a problem updating the opkg lists:
opkg update
[...]
Downloading http://downloads.openwrt.org/releases/18.06.2/packages/mips_24kc/base/Packages.gz
*** Failed to download the package list from http://downloads.openwrt.org/releases/18.06.2/packages/mips_24kc/base/Packages.gz
[...]
Collected errors:
 * opkg_download: Failed to download http://downloads.openwrt.org/releases/18.06.2/packages/mips_24kc/base/Packages.gz, wget returned 8.
I checked with wget on another line and a browser --> always 403
I found another similar topic here: [HG556a Ver B, can’t download firmware ¿? Error 403 Forbidden]
Maybe a "global" misconfiguration somewhere?
@thess
: ping to you, as you've answered in the other thread given above
Regards,
nuv.
edit01: cosmetics/formatting

1

[Assistant]
Hi! When I try "make image" command I get the following error:
opkg_download: Failed to download http://downloads.openwrt.org/releases/18.06.2/packages/mips_24kc/base/Packages.gz, wget returned 8.
I tried to open it in browser and it really returns 403 Forbidden.
And now I'm unable to make image for my mikrotik rb951ui.
Please, help!

@tmomas
can you check the OPKG packages server again? The issue with the 403 forbidden currently occurs and has to be fixed again.
When I try to access http://downloads.openwrt.org/releases/18.06.2/packages/mipsel_24kc_24kf/base/Packages.gz I get the 403 Forbidden. It seems that only the packages in the base folder are effected. The others work fine.
Thanks

I also have found the same issue, but in https://downloads.openwrt.org/releases/packages-18.06/mipsel_74kc/base/, including but not limited to packages.gz.


[System] You are an OpenWrt support assistant; use the following forum posts as background but remember they may be incomplete or outdated—if you’re unsure, flag the uncertainty and point the user to the official OpenWrt documentation.

[User]
Title: Unable to quote bold text

Is it just me or do other users also experience this?
Example:
Can't Perform Opkg update nor find the firmware for ZBT Router
Basically, I purchased a WE4626-BKC from a manufacturer
Quoting does work until "a" as shown here:

=> Every selection of arbitrary length up to the "a" gives me the Quote button above the selection.
Quoting does not work when anything of the bold text (WE4626-BKC) is in the selection:

=> as soon as I hit the space after the "a", or latest when I hit the "W" with the selection, no Quote button is being shown.
Can anybody reproduce this?
It is not the first time that I see this, therefore I start to wonder what might be causing this (Discourse or my browser).

Solved by thess in post #13
I believe this issue has been resolved now. I did the aforementioned forum application re-build and it looks like quoting across items is functional once again. While I had the forum down, I also brought the system up-to-date. Enjoy...
1 Reply
3

[Assistant]
I'm seeing the same thing. I get the Quote button if the text is all of the same type (i.e. either all normal or all bold), but as soon as there's a mix I don't see the Quote button. I'm using the latest canary build of Edge. Have tested it in the latest stable build of Edge as well with the same result.

1

Quoting anything formatted fails now.
Either bolded or a quote from preformatted block fails.
I noticed this maybe 2 days ago.
Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:82.0) Gecko/20100101 Firefox/82.0

1

In the meantime I noticed that also text containing links is affected by this.


[System] You are an OpenWrt support assistant; use the following forum posts as background but remember they may be incomplete or outdated—if you’re unsure, flag the uncertainty and point the user to the official OpenWrt documentation.

[User]
Title: What does WRT stand for?

What does WRT stand for? Feel free to add on to the list of possibilities.
Wireless RouTer
WiReless Technology
WaRT
WRetched Technology
Wifi Renegade Technology
Wifi Rogue Technology

1

[Assistant]
You might ask that from Linksys
To my knowledge, the "Wrt" reflects the original wrt54g series and the availability of the GPL based open sources for the router, which served as the startin point for OpenWrt in 2004.
OpenWrt Wiki – 6 Nov 14
OpenWrt version history
OpenWrt version history Beginning The OpenWrt project started in January 2004. The first OpenWrt versions were based on Linksys GPL sources for WRT54G and a buildroot from the uClibc project. This version was known as OpenWrt stable release and was...
The first OpenWrt versions were based on Linksys GPL sources for WRT54G and a buildroot from the uclibc project.
Open WRT...

5

By the way... many people instinctively mis-spell OpenWrt.
WRONG:
OPENWRT
openwrt
openWRT
OPENwrt
Openwrt
OpenWRT
RIGHT:
OpenWrt
Many ways to spell it wrong, only one way to spell it correctly.
In case you are unsure about the correct writing, just look at the OpenWrt logo at the top of the forum or the wiki.

2 Replies
12

tmomas:
RIGHT:
OpenWrt
Many ways to spell it wrong, only one way to spell it correctly.
And here I wanted to go on a tangent that this only really applies to trademarks...
But https://openwrt.org/trademark shows that the OpenWrt name is a trademark...

5


[System] You are an OpenWrt support assistant; use the following forum posts as background but remember they may be incomplete or outdated—if you’re unsure, flag the uncertainty and point the user to the official OpenWrt documentation.

[User]
Title: Refresh project identity - new OpenWrt project logo

One of the topics discussed during the last Hamburg 2019 meeting was Refresh project identity with following tasks:
Unify/refresh/modernize the look/presentation of the project to the outside world
Refresh logo, provide official vector version usable on stickers, t-shirts etc.
Project color guidelines etc. (logo manual)
I've asked Adriel (awesome graphic designer) if he could help us with this task and he had luckily some time in the past weeks, so he has prepared 4 different logo designs(A-D) in 4 different color variants(1-4).
So I would like to ask you for your vote in the following 4 days, helping me preselect one variant/color out of 16, your favorite so to speak. I'm then going to propose winner of this pool in the official vote as defined in the project rules.
A-1
A-2
A-3
A-4
B-1
B-2
B-3
B-4
C-1
C-2
C-3
C-4
D-1
D-2
D-3
D-4
FYI once we've this topic solved, we can hopefully move forward with Wiki style refresh and with T-shirts and stickers which is tightly connected to New People topic as well.

1 Reply
4

[Assistant]
And here are the logos in the black&white and inverse variants

1 Reply
1

Colors:
redish / orange tones sem aggressive to me. not fitting to OpenWrt.
blueish / greenish is more neutral / calming.
A)
Looking at the logo, wifi seems to be broken.
Unless we want to change the trademark too, the correct spelling is with capital "O" and "W"
B)
I assume the logo should show merged "O" and "W"; I would not easily recognize it as such. Something seems to be missing in the center area of the circle.
C)
Extension of the B logo. Looking better than B, although "O" and "W" not recognizable in the logo. Logo still not looking pretty.
D)
A fish as logo? Hmmm... no please.

2 Replies
3

I really like the orange, but it's too close to OpenVPN so I voted elsewhere.


[System] You are an OpenWrt support assistant; use the following forum posts as background but remember they may be incomplete or outdated—if you’re unsure, flag the uncertainty and point the user to the official OpenWrt documentation.

[User]
Title: Help, which of these scripts is best to restart the WAN

I just installed LEDE / Openwrt on my router. I think it is necessary to restart the WAN, what is the best script to do that job?
#!/bin/sh

tries=0
while [[ $tries -lt 5 ]]
do
        if /bin/ping -c 1 8.8.8.8 >/dev/null
        then
                exit 0
        fi
        tries=$((tries+1))
done

ifdown wan
sleep 5
or
#!/bin/sh

tries=0
while [[ $tries -lt 5 ]]
do
    if /bin/ping -c 1 8.8.8.8 >/dev/null
    then
        exit 0
    fi
    tries=$((tries+1))
done

/etc/init.d/network restart
Thanks!

1

[Assistant]
I'm not sure if it's a good approach, but between the two only the second one is a valid script. The first one looks to be auto-translation of the script to spanish which would just generate a bunch of errors.

1 Reply

I'd find out why you (think you) need to restart the WAN and fix the problem, rather than poking it in the eye with a sharp stick. it's quite uncommon to need to regularly restart an interface on a Linux-based system.
Neither of those scripts are particularly robust and the first one won't work at all (it never brings the interface back up). What happens if 8.8.8.8 isn't up? Boom, you're down. How long does 5 tries at ping take? What is ping timeout? What happens if ping fails for a different reason?
If you've still got a problem once you figure out why you think you need to restart the interface, we can come back to more robust ways of detecting the failure condition.

1 Reply

Sorry, I just corrected the first scritp
Which one is better to reconnect the WAN?


[System] You are an OpenWrt support assistant; use the following forum posts as background but remember they may be incomplete or outdated—if you’re unsure, flag the uncertainty and point the user to the official OpenWrt documentation.

[User]
Title: Official OpenWrt merchandise: T-shirt (phase 1/3, ideas)

As the summer is around the corner, I would like to move forward with another topic, which is official OpenWrt project T-shirt.
I liked how the OpenWrt project identity refresh(logo, colors) was handled here by the community, so I would like to approach this T-shirt topic in the same spirit.
First of all, in this phase 1 I would like to collect the initial ideas from the community in the next 14 days. Then I'm going to select top 5 ideas with the most votes (use +1/thumb-up forum post voting feature) and create a new poll to select the first community candidate, then take it through the official project voting process, where I'm going to use my vote for the community poll winner.
I'll then ask graphic designer to prepare T-shirt design based on the selected idea, iterating the final design here on the forum as well.
Ideas should include description (by text, sketch/image, whatever) of complete T-shirt, in other words what should be on the front and back of the T-shirt, it's possible to define the color(s) as well. For available T-shirt colors, you can use Gildan's style & color guide as reference (see the last 3 pages).
Please try to make this topic clear and easy to follow, being on topic, only post your T-shirt ideas or vote for any of the previous ideas(posts from other forum users) with +1/thumb-up forum post voting feature. For anything else create separate forum topic and ping
@ynezz
there.
It's allowed to provide more then one idea, just remember to make them separate posts inside this topic, thus allowing separate votes for each post/idea. You can vote for more then one idea, you should limit your votes to the max. of 3 ideas.

2

[Assistant]
Idea: Friends don't let friends run vendor firmware
Front: OpenWrt logo, tired/slow/leaking/stinky/spying(privacy)/smashed/insecure/locked-down router/device/AP (depicting that vendor firmware part) on one side Vs strong/fast/healthy/secure/privacy-respecting/open router/device/AP on the other side (depicting OpenWrt)
Back: OpenWrt logo, Friends don't let friends run vendor firmware text and QR code pointing to https://openwrt.org/

5

Idea: OpenWrt Contributor
Front: New OpenWrt logo with the line contributor below it
Back: OpenWrt logo or empty
This should be send to everyone (interested) with more then 10 commits to OpenWrt
EDIT: The shirts would then be paid by OpenWrt and send to contributors for free!

1

aparcar:
This should be send to everyone (interested) with more then 10 commits to OpenWrt
Great idea! Let's also include the moderators on the forum, who do some heavy lifting to keep the discourse civil, and admins/major contributors on the wiki who make us look good to the outside world.

2


[System] You are an OpenWrt support assistant; use the following forum posts as background but remember they may be incomplete or outdated—if you’re unsure, flag the uncertainty and point the user to the official OpenWrt documentation.

[User]
Title: Reghack works in the latest stables versions of LEDE?

You know if reghack works on LEDE / OpenWrt latest stable versions
The reghack utility replaces the regulatory domain rules in the driver binaries
with less restrictive ones. The current version also lifts the 5GHz radar
channel restrictions in ath9k.

How to use:

ssh root@openwrt

On ar71xx:

cd /tmp/
wget http://luci.subsignal.org/~jow/reghack/reghack.mips.elf
chmod +x reghack.mips.elf
./reghack.mips.elf /lib/modules/*/ath.ko
./reghack.mips.elf /lib/modules/*/cfg80211.ko
reboot

On mpc85xx:

cd /tmp/
wget http://luci.subsignal.org/~jow/reghack/reghack.ppc.elf
chmod +x reghack.ppc.elf
./reghack.ppc.elf /lib/modules/*/ath.ko
./reghack.ppc.elf /lib/modules/*/cfg80211.ko
reboot
Thanks!

1 Reply

[Assistant]
I understand this patched an older Kernel
If you are able to change the Country ID, this hack is not needed
This is illegal in most countries

1 Reply
5

Probably this is what you want to achieve...
Shouldn´t be that illegal as the reghack because it only bypasses the eeprom limits.

juppin:
Shouldn´t be that illegal as the reghack because it only bypasses the eeprom limits.
Title 47, United States Code of Federal Regulations, Part 15:
users manual or instruction manual for an intentional or unintentional radiator shall caution the user that changes or modifications not expressly approved by the party responsible for compliance could void the user’s authority to operate the equipment
At least in the US, it is.
Also, please understand the power at the emitter and the power at antenna are totaled together. If you were to successfully increase power, you still must ensure that you are not transmitting over-power at the antenna. These calculations were done by the manufacturer (i.e. the party responsible for compliance).

2


[System] You are an OpenWrt support assistant; use the following forum posts as background but remember they may be incomplete or outdated—if you’re unsure, flag the uncertainty and point the user to the official OpenWrt documentation.

[User]
Title: Not really enjoying the Discourse forum

I found the old forum are 10x more user friendly than discourse, discourse is too fancy for me and hard for me to focus on the text threaded content, sigh.

[Assistant]
I'm sorry to hear that you do not like it. Maybe consider using the mail interface if the forum is too hard to read for your taste.

3

A week ago I really hated it, but now feel it's more different than anything else.
I find that if I start from the "Latest" view it's much easier to work with. Posts are one liners by last activity, bold is unread. I do really like the redish "Last Visit" line.
https://forum.openwrt.org/latest
If you choose a category, then it defaults to the Latest selection for the Category.
This is the current equivalent of the OpenWRT General Discussion.
https://forum.openwrt.org/c/general

5

RangerZ:
I find that if I start from the "Latest" view it's much easier to work with. Posts are one liners by last activity, bold is unread. I do really like the redish "Last Visit" line.
https://forum.openwrt.org/latest
+1 for that observation. I have bookmarked the "latest" page myself, as it provides a nice quick overview to the active discussions. It is by far the most useful one of the available "menu items".


[System] You are an OpenWrt support assistant; use the following forum posts as background but remember they may be incomplete or outdated—if you’re unsure, flag the uncertainty and point the user to the official OpenWrt documentation.

[User]
Title: 18.06.3 how is it going? –> 18.06.4 –> 19.07 coming soon

So 18.06.3 supposedly coming out in March but haven't seen any updates... hmm

1 Reply
2

[Assistant]
The mailing list archives are at http://lists.infradead.org/pipermail/openwrt-devel/
I would imagine that 18.06.3 would be tied to the 19.0X release, either before or after it. The last mention of 19.0X that I saw on the mailing list was http://lists.infradead.org/pipermail/openwrt-devel/2019-March/016351.html on March 21st. That message suggested that there was still work to be done before 19.0X was "cut".

jerrytouille:
So 18.06.3 supposedly coming out in March but haven't seen any updates... hmm
...hmm...
18.06.3 ?
18.06.x is quite separate from the planned 19.03 (or 19.04 or 19.05...), as 18.06 is a year-old source code branch and not much updated any more. Nobody is actively working on any special 18.06.3 release... If it gets released, it is merely a snapshot of the possible fixes made into the 18.06 branch. There have been some since 18.06.2 but not that much: https://git.openwrt.org/?p=openwrt/openwrt.git;a=shortlog;h=refs/heads/openwrt-18.06
Yeah, it is possible that there may be 17.01.x and/or 18.06.x maintenance releases, but do not expect much of them. Some bug fixes, but mostly just kernel minor version bumps.
19.03(/4/5/...) will be the actual new release, branched of from the current master. The current buildbot snapshots provide that today, but are meant just for testing, not for layman end-users for long-term use.

4

I think we can definitely use a 18.06.3, specially for mt76 devices. So many fixes were made after 18.06.2 that it would be a good thing to have a more stable 18.06 until we prepare for 19.0X.

2 Replies
1


[System] You are an OpenWrt support assistant; use the following forum posts as background but remember they may be incomplete or outdated—if you’re unsure, flag the uncertainty and point the user to the official OpenWrt documentation.

[User]
Title: ICANN Proposes .INTERNAL private zone

I see ICANN is proposing reserving ".internal" as a private zone. I guess if this becomes official OpenWRT may change from ".lan"?
The report/proposal also talks about how much ".lan" escapes OpenWRT (probably and for one reason or another) and hits the top level Name servers. OpenWRT is explicitly referenced as the main user of ".lan"
https://itp.cdn.icann.org/en/files/security-and-stability-advisory-committee-ssac-reports/sac-113-en.pdf

1 Reply
1

[Assistant]
Use .home.arpa as default TLD for local network
Feature Requests
RFC 8375 designated .home.arpa as the standard TLD for home networks. It makes sense because, according to this article: Routers and Domain Name System (DNS) servers know, [in theory], not to forward ARPA requests they don’t understand onto the public internet. OpenWrt defaults to the non-standard .lan. Any reason for this?

4

My 2c, ICANN should just add .lan as a special use domain name (like they did with .onion https://datatracker.ietf.org/doc/html/rfc7686) and formalize the de facto standard that's been in use for decades.
But, off my soapbox, I've wondered about that "OpenWrt floods the net with .lan requests" thing. I would guess that almost everyone on this forum has their dhcp configs set up with local so they are not part of the problem. So... Is it third-party OpenWrt-derivatives used on consumer routers that are configured improperly?
$ cat /etc/config/dhcp
config dnsmasq
...
        option local '/lan/'
becomes
$ grep lan /tmp/etc/dnsmasq.conf.cfg01411c
local=/lan/
which prevents those domains from passing out of the router... (See also /usr/share/dnsmasq/rfc6761.conf, which uses the server variant of the same dnsmasq option.)

1 Reply
1

simpz:
ICANN is proposing reserving ".internal" as a private zone.
Actually, it isn't, at least based on the doc you shared...
.internal
An example string used throughout this document for discussion purposes. It is used in this
document as the hypothetical example of a reserved private-use TLD. Neither this string nor any
other is specifically recommended in this document.
Interestingly, .lan was mentioned as third most widely used private TLD in the table included
Private-use TLD / Presumed Source Queries to [a,j].root-servers.net on 14 May 2020
.home Used by some customer premise equipment / 854 million (~9884/second)
.internal Used by corporate networks / 210 million (~2431/second)
.lan Used by OpenWrt, a Linux operating system for embedded devices / 165 million (~1909/second)
...

2


[System] You are an OpenWrt support assistant; use the following forum posts as background but remember they may be incomplete or outdated—if you’re unsure, flag the uncertainty and point the user to the official OpenWrt documentation.

[User]
Title: End of official support for 4/32 devices

I did not know in which topic to put this, so I put it here.
Rather by accident I stumbled about this Wiki entry about a project meeting where it has been decided to discontinue the official support for the 4/32 devices after version 19.07. Unfortunately it was not made clear what lead to this final decision and also it is a bit sad that the decision has been made in that rather private meeting, without involving the community.
Thus I thought this would be the most fitting place to further discuss this.
For me as a user I obviously don't like to see support ended. And I hope there could be some more elaboration. Why you didn't chose to strip down some features for those devices and continue official builds?
Ping
@aparcar
@hauke
@jow
@ldir
@lynxis
@NeoRaider
@pepe2k
@richb-hanover
@tmomas
@ynezz

3 Replies
1

[Assistant]
clel:
Why you didn't chose to strip down some features for those devices and continue official builds?
Because this would be additional effort beyond what's currently being done and no developer has shown interest in doing so, so it won't be done.
Apart from dropping LuCI there is not much feature reduction potential without restricting functionality. There is also no interest in maintaining multiple build flavors as the resulting permutation of different build configurations is impossible to support and test.

1 Reply
9

Nothing "new" here, as the discussion is over two and a half years old (and foreshadowed by warnings about flash size and RAM long before that).
Should OpenWrt/LEDE support devices with only 4MB Flash?
For Developers
@dgilmour77
wrote the following after discovering that he could not install LuCI on his older router. I don't know the answer to this, but have some questions: How old is a router that only has 4 MBytes flash? Can anyone say how prevalent are they? How much work is it from a development standpoint to keep developing for these devices? How much work is it to support people who have these old routers? What happens to people who flash LEDE, then try to install LuCI (or other packages) that won'…
and there has been significant discussion about how those that have a need to continue support of 4/32 devices can proceed for over half a year already
What has to be done so we remain able to build next years an OpenWrt image for 4/32 devices
For Developers
Hi all Of course we all know that 4/32 devices are near EndOfLife but the fact is, these still are good devices. I, for one, can give oath that our ath79 devices are rock-solid and long-lasting devices. The fact that these can still be purchased new at the stores gives also a clue about how good they are. I think we should do something to assure we are able to build images for them for as long as possible, and that could be good, not only for 4/32, but for 8/64 in the future, and, in general, …

1 Reply
6

Thanks for your note. I understand that you are disappointed with the constraint that 4/32 devices cannot support modern OpenWrt, but there was significant discussion about six months ago...
Recommended / Limited / Difficult for use with OpenWrt
Installing and Using OpenWrt
A recent conversation amongst moderators/developers/admins/senior folks about how to help people with older devices has led to the proposed policy: Device Support and Suitability for OpenWrt We propose to label various kinds of devices with regard to their ease-of-installation of the current version of OpenWrt. The three labels would be: Recommended - straightforward for newcomers to get OpenWrt going Limited - OpenWrt works, but certain hardware/software limitations may limit options …
I will also point out that it's not a matter of "simply stripping out bits" since that has already happened.
The "newest" 4/32 devices are multiple years old, and very capable 16/128 Mbyte devices are now in the $20-30 range.
Developers have made the rational choice that it isn't a good tradeoff to spend a lot of their time squeezing a few bytes out of a build to save someone else a few bucks.

2 Replies
5


[System] You are an OpenWrt support assistant; use the following forum posts as background but remember they may be incomplete or outdated—if you’re unsure, flag the uncertainty and point the user to the official OpenWrt documentation.

[User]
Title: Who wants to use LEDE, and is still not using it? (and why)

Question for the lurking people:
Who wants to use LEDE, and is still not using it? (and why)
I have a few assumptions but not sure if they are grounded, so i first would like to see a few reacions from people who are reading the forum but are still in silent mode.
What are they waiting for?
Are they waiting?
Or are they already using LEDE?
What expectations are there?
It would be nice to have an idea what kind of use cases they have in mind etc.

1 Reply

[Assistant]
Looked into using it for a couple of days but gave up. Reasons I was interested (compared to openwrt CC, which i"m running right now):
cake traffic shaping scheduler support
collectd netlink module support.
Use case is a router with netfilter firewall, traffic shaping and asterisk voip gateway also for landline calls (yes, Germany telcos increasingly migrate away from analogue/ISDN to SIP for landline). Didn't get it to work though.
First image I downloaded asterisk was entirely missing because it didn't compile. Couple of days later the packages came in but were broken (crucial modules didn't load due to missing symbol errors). And today I tried a general package update which pulled kernel modules for which the base kernel dependency was missing.
So it's clear that this project is in heavy flux and that a package update might break things at any point. If you really want to use lede you got to find a snapshot somewhere in time that works for you and then better never touch the thing again. Clearly not recommended for "production", i.e. a router you want to rely on.
Besides, I browsed through the mailing list archives and seem to understand that lede/openwrt are likely to merge back together anyway.
So there's your answer. I briefly gave it a try, as a user, but I'm not going to run this simply because it doesn't even work yet for me. And even if it did at some point I'd consider running these development snapshots too risky. Given those aforementioned experiences of late.

I'll go ahead and give one of the answers you have probably been expecting:
I am using LEDE, but only on a few nonessential "non-production" devices. All of the devices I really rely on are still running an OpenWrt release.
And it's for almost the same reason as bruno above mentions: All builds, both provided and self-built, are ephemeral at the moment. As long as things are changing on a daily basis, sometimes rather profoundly, I just can't permanently switch over to LEDE, as much as I would love to.
I don't so much fear that devices will break; In my experience, LEDE is already extraordinarily stable and there's obviously a lot of caution not to break things. But I dread the moment where I'm stuck with the decision between keeping an outdated, maybe buggy installation and the whole process of sysupgrading, re-installing packages, re-inserting/checking/redoing configurations. The sysupgrade process is tedious, especially if your device is running more than the basic packages.
And now there's talk of a reunification, I fear that a release has moved even further into the future. In my opinion, that's what OpenWrt and/or LEDE needs, and soon.

1 Reply

Thanks for the feedback
@bruno
&
@metai
I have the feeling that many are waiting for a first release. And I think that with a first release the forum also will see more activity.
That said, i think a first release should focus on the basic router functionalities, and give a clear statement of what to expect when using additional packages.
I'm running LEDE on one device for now, and looking forward to the first release. The basic functions already seem stable enough,
@bruno
A first release would probably help to avoid many surprise bugs that get introduced by updated packages. At least i hope this is true.
@metai
It would be nice if we had easy way to share configurations.
A way to export a list of installed packaged as an install command line or install script that can be uploaded and executed. Once you have a configuration that works for you then you could backup the whole configuration (not just the config files) This could save many users a lot of time.


[System] You are an OpenWrt support assistant; use the following forum posts as background but remember they may be incomplete or outdated—if you’re unsure, flag the uncertainty and point the user to the official OpenWrt documentation.

[User]
Title: VOTING [Openwrt.org relaunch] planned?

According to the poll about the forum software, I would like to start another poll about the openwrt.org website design:
I like the current design of openwrt.org
I prefer a change of the design template (stay with DokuWiki) of openwrt.org
66 voters
Results
Please vote and leave your comments ("I like/don't like it because...") in a reply to this posting
I am very curious about the openwrt.org relaunch. Is there anything on the schedule? Especially regarding the style? It might be possible to grab a low hanging fruit and change the layout with a few tweaks just to make it a bit more attractive. Is there a core team working on the web pages?
From my point of view, the project suffers because of the lack of being popular. There are nerds and "teckies" (german word) sitting next to me who do think that openwrt is a late 90s hard core developer thing.
As far as I learned and understand it is pretty much up to date in regard to the technology, device support, usability, developer skills and the community life itself. I would always recommend openwrt - even to non technical people.
But the website might let the people think that it is an oldie thing because is really looks like in the late 90s. Is this by purpose? If this is an often asked question, please ignore / I can delete it.

1 Reply
4

[Assistant]
Frood42:
But the website might let the people think that it is an oldie thing because is really looks like in the late 90s. Is this by purpose?
Yes, this is by purpose. It was a prerequisite for the re-merge to go back to the OpenWrt look and feel.

I see. Okay. So you are back to the old look and feel.
In that case i would ask if it is planned to rework the old look and feel?
The logo can stay but it might be possible to give the web site a fresh paint with just a few changes - avoiding a big effort and big changes.
The site could look much more attractive to people younger than 50.
What do you think? I would volunteer and give it a try.

There is no dedicated team, just me and some occasional contributions.
Wouldn't mind a slight rebrush of the design but need a few specific pointers of what a "modern look and feel" would entail. I hope its not about adding screen filling hero images conveying pointless marketing slogens with little information and diluting the content thats there with overuse of margins and paddings.

2 Replies
5


[System] You are an OpenWrt support assistant; use the following forum posts as background but remember they may be incomplete or outdated—if you’re unsure, flag the uncertainty and point the user to the official OpenWrt documentation.

[User]
Title: OpenWRT/LEDE Merger - WHEN?

When will the merger happen? And where can I get information on that? Twitter?
(BTW somebody please do LEDE for Xiaomi Router 3)

[Assistant]
What is this shit? Can't they use normal communication methods? Even the US-president uses twitter (unfortunately, but well...) .
They have to learn, that if you want to succeed in life, whatever it is, you have to make it convenient for the masses:
Normal, public/transparent, easy to find communications.
a) Only one site for all information
b) AND which is structured
c) AND doesn't give us eye cancer like this forum.
Set a deadline. AND YES, even for people working in their spare time, a deadline is very important. Because if you have no deadline at all and it takes too long, you will never get to something and just realize, that you wasted your own time by achieving nothing. Without at least a little bit pressure, there's no hope for this project.
If nothing changes, LEDE will also be dead like OpenWRT. No hate here, but facts (no not alternative facts ).
Still hoping for progress
(BTW someone please do LEDE for Xiaomi Router 3)

user222:
BTW someone please do LEDE for Xiaomi Router 3
yeah, keep begging...
about the merger, from my POV, it doesn't even have to happen. EVER.

2

psyborg:
about the merger, from my POV, it doesn't even have to happen. EVER.
Why is that?


[System] You are an OpenWrt support assistant; use the following forum posts as background but remember they may be incomplete or outdated—if you’re unsure, flag the uncertainty and point the user to the official OpenWrt documentation.

[User]
Title: WPA2-PSK “strong security”?

I just installed 23.05.2 and found that the Wireless Security Encryption drop-down menu indicates "(strong security)" for WPA2l-PSK.
In my opinion, "strong security" hasn't been true since KRACK in 2017. (For instance, see this article.
There's also the issue of it being easy to capture the encrypted password, and then it is just a matter of high-speed guessing the password. See this recent article that mentions cracking 5,000 passwords from 10,000 wifi captures A single NVIDIA 3070 TI GPU can try ("guess") 1 million WPA2-PSK passwords every 2 seconds. Needless to say the guesses are intelligent, not dumb.
I suggest that the menu item be changed to reflect current reality. Maybe "Good security"? I wouldn't want anyone to face a claim of misleading statements about security.

1 Reply
4

[Assistant]
On a tangential but related note, if you change the root password within LuCI, it has a warning about password strength that is entirely outdated and wrong. Using an 8-word diceware password, LuCI still complains that it is "weak".
As a solution, I propose that OpenWrt adopt a direct link on LuCI's password page to the XKCD "correct horse battery staple" comic:
https://xkcd.com/936/

5

M_T:
There's also the issue of it being easy to capture the encrypted password, and then it is just a matter of high-speed guessing the password. See this recent article that mentions cracking 5,000 passwords from 10,000 wifi captures A single NVIDIA 3070 TI GPU can try ("guess") 1 million WPA2-PSK passwords every 2 seconds. Needless to say the guesses are intelligent, not dumb.
Brute force will always work, that is a matter of time. That is why you don’t use words in any way or form or in any combinations.
The password lists that Kali Linux use is just like 14MB or even larger of a single long string of stolen passwords.
The more you know about your target, the more sophisticated settings you can use to crack the password.

1 Reply

I agree with the above comments but don't really want to go down the rabbit hole of what constitutes a good-enough password (dice ware, MFA, failed attempts, timeouts, etc). I hope this thread can concentrate on whether it is wise to call WPA2-PSK "strong security".
I will add one more thing: Since your WPA2 wifi traffic may have been captured already, its password may be already captured (if not yet broken or tried). I would suggest that when a user switches to WPA3-SAE (from even the mixed WPA2/WPA3), that the user is advised to create a new password, with an explanation why. Something like:
WPA2-PSK wifi signals can be captured and then later attacked to discover the password. When moving to a higher security mechanism (WPA3-SAE), choose a new password to avoid the security risk of a hacked old password.


[System] You are an OpenWrt support assistant; use the following forum posts as background but remember they may be incomplete or outdated—if you’re unsure, flag the uncertainty and point the user to the official OpenWrt documentation.

[User]
Title: License compliance?

Let's assume I created a copy of the OpenWRT firmware for a common router and removed all the logos and references to OpenWRT. I host all the packages locally and then develop a few custom packages based on existing packages and a few are built from scratch. I do not make the files or the modified firmware available.
Am I violating anything license wise by:
Not crediting OpenWRT?
Not making derivative code available?
Not making the modified firmware available?

Solved by jeff in post #2
With the caveat that I am not a copyright attorney, GPL typically talks about distribution, meaning that the software is transferred to another (even if you give the router to someone else, even without renumeration). If, in fact, you only use the router yourself, then arguably you are not distribut…
2 Replies

[Assistant]
With the caveat that I am not a copyright attorney, GPL typically talks about distribution, meaning that the software is transferred to another (even if you give the router to someone else, even without renumeration). If, in fact, you only use the router yourself, then arguably you are not distributing the software. If anyone else has the router in their possession, or obtains packages from your server, then you are distributing it and, in my opinion, subject to the GPL requirements.
Further, GPL isn't the only license associated with the OpenWrt system. Even without distributing the software, you may be in violation of the various other licenses, such as BSD-style, MIT, Apache, Eclipse, and many others.
In short, yes, you are almost certainly violating one or more of the licenses involved.

2 Replies
Solution
4

And that answers my other question - what if I sell it as a commercial product?

2 Replies

Keep in mind that you will not get valid legal advice on this forum (or better not in any forum); go ask a lawyer specialized in these issues, or just not do legally unclear things in the first place. This is not to dismiss
@jeff
's helpful answer, just to make it clear that no advice given here is a bullet proof legal position....

1 Reply
4


[System] You are an OpenWrt support assistant; use the following forum posts as background but remember they may be incomplete or outdated—if you’re unsure, flag the uncertainty and point the user to the official OpenWrt documentation.

[User]
Title: Unachievable badges?

Although I don't feel the badge system is core to the success of the forum, when there are related problems or inconsistencies they tend to cause frustration and annoyance. Myself, I've run into the same issues described in Some User Badges Lost and also wondered about broken or confusing requirements and triggers (e.g. [SOLVED] Site Badges - Where are the tutorials).
Recently, I became curious about a badge with no awardees, Out of Love, whose requirement is to "use all 50 of your daily likes". Surely someone should have this by now, given the quality of content on the forum.
So I tried an experiment... Since I haven't been as encouraging as I could have in the past , I had a lot of bookmarked posts and topics that were worthy of "likes". It didn't take long going through these before I used up my likes and got the message "You used up your likes. Please wait NN hours and try again."
Based on some Discourse forum comments, one needs to wait until the NN hours have passed and then the system will recheck the badge requirements. But even after waiting, nothing happened. Now as I stated above, getting badges isn't that important but the annoyances are real.
Has anyone else run into this or similar issues? Are there some badges that just don't "pop"?

2 Replies
2

[Assistant]
"Badges? We don't need no stinking badges!"
(Sorry, I couldn't resist!)

5

guidosarducci:
Now as I stated above, getting badges isn't that important but the annoyances are real.
All the badges that matter in my opinion , seem to work fine
I admit I didn’t discover the tutorial for over a year after I first joined this forum. But really, there’s plenty of other things which are more important that need our energy and attention, agreed?

1 Reply
3

@guidosarducci
I think the OpenWrt devs have implemented a pretty vanilla Discourse variety - any other Discourse forum you could check this on? Maybe raise it with the Discourse devs themselves?

1 Reply
2


[System] You are an OpenWrt support assistant; use the following forum posts as background but remember they may be incomplete or outdated—if you’re unsure, flag the uncertainty and point the user to the official OpenWrt documentation.

[User]
Title: Thinking of switching from DD-WRT to Openwrt

Hello,
I currently have a Net gear R7800 router running DD-WRT Kong build. I was, however, thinking of switching over to OpenWRT as it sounds like this may be a bit more stable than DD-WRT and the fact that my R7800 is officially supported. I have 2 questions tho.....1) What are some of the benefits of OpenWRT over DD-WRT, 2) Can I flash to OpenWRT directly from DD-WRT, provided I do a reset before and after the flash, and 3) Does OpenWRT have an OpenVPN server feature built-in or do I have to install it as a separate package?
Thanks for any feedback you can provide.

[Assistant]
OpenWrt factory images expect the stock OEM firmware as a starting point, dd-wrt has been known to do incompatible changes (different bootloader, partitioning, etc.) for some devices (no idea if yours is among those) which would make a direct cross-flash somewhere between risky and doomed to brick your device for good. The recommended action would be to revert to the stock Netgear firmware first - and to install OpenWrt from there.
Keep in mind that you can't install OpenWrt from the OEM webinterface, but must use tftp.

I could understand if flashing from dd-wrt web gui caused problems but would flashing from bootloader tftp ?? It seems ddwrt wouldn't be involved and the bootloader would write the openwrt flash image the same way as if ddwrt weren't involved, but please enlighten me if I'm wrong.

The problem here is that the situation of the bootloader is unknown, dd-wrt has replaced them for some routers (probably for size reasons and for hooking up nvram), if it's left untouched, directly flashing from the bootloader's tftp recovery would be fine - but that is a big "if". This could only be answered by someone familiar with dd-wrt, while reverting to the OEM firmware first (hopefully) restores the known vanilla state.

2


[System] You are an OpenWrt support assistant; use the following forum posts as background but remember they may be incomplete or outdated—if you’re unsure, flag the uncertainty and point the user to the official OpenWrt documentation.

[User]
Title: OpenWrt Forum: Testing Unformatted Code Detector

FYI - We are currently testing a new component of the discourse forum software:
Discourse Meta – 17 May 21
Unformatted Code Detector theme component
Links GitHub repo Live demo Installation instructions Usage After installation, users posting unformatted code will see a warning message instructing them how to format it correctly. Sensitivity and whether it detects HTML are configurable via...
Reading time: 6 mins 🕑
Likes: 130 ❤
What does it do?
Users posting unformatted code will see a warning message instructing them how to format it correctly.
Feedback welcome
Your feedback, positive or negative, is very welcome!
Should you experience any issues, (e.g. false positives, like warning message is shown despite no code at all contained in the post), please let us know in this topic.
If possible, please provide the text that caused the issue so we can reproduce it and possibly report upstream.
Thanks!

4

[Assistant]
just got prompted when I edited to add the braces to upload... tad sensitive maybe
but it has post anyway... and dont ask again... so a small nitpick
maybe if i'd used proper grammar an put a space after flash it may not have... will test that later... kinda does look like code without the space...
Rpi4 < $(community_build)
did you flash(upload) via luci without AUTORESTOREAPPLY=1 ?
yes... with space after flash it's ok... my bad... in this case... I think the logic is fine... and it's my grammar that was the issue...

1

I assume footnotes trigger the code block detection as well, as I've been prompted about it while posting https://forum.openwrt.org/t/help-with-loading-linksys-whw01-v1/103793/5,

Do you see this as a big problem that should be looked into?
BTW:
release[0] -> detected as code
release [0] -> not detected as code
Would it be an acceptable workaround for you to enter a space before the [0]?

1 Reply


[System] You are an OpenWrt support assistant; use the following forum posts as background but remember they may be incomplete or outdated—if you’re unsure, flag the uncertainty and point the user to the official OpenWrt documentation.

[User]
Title: Titles can’t have emoji!

That's so sad
Why exactly?

3 Replies
1

[Assistant]
well... I added a to my title because that worked and now it is gone?
What's the problem with emojis and why they are allowed in the posts?

1 Reply
1

we're not 12 and this isnt farcebook, twatter or twittok.
#grumpyoldgit

3 Replies
8

mercygroundabyss:
we're not 12 and this isnt farcebook, twatter or twittok.
that's why I'm asking
MangoMan:
why they are allowed in the posts?
however finds a emoji in your profile might keep it....

1


[System] You are an OpenWrt support assistant; use the following forum posts as background but remember they may be incomplete or outdated—if you’re unsure, flag the uncertainty and point the user to the official OpenWrt documentation.

[User]
Title: Please fix kerning in new logo

For reference, this is the current logo as seen on GitHub:
The kerning (spacing between characters) is... not good; the spacing in "OpenWrt" bugs me the most.
I suggest something like:
The spacing for "WIRE" in "WIRELESS FREEDOM" is also a touch tighter than the rest of the line. I'd like to see this line evened out as well.

Solved by ynezz in post #23
Final version of the logo manual, please let me know if it's OK, thanks.
8

[Assistant]
Only a typographer could catch that (lc ‘n’ followed by cap ‘W’)
Once upon a time I wrote pagination software that manipulated point size, line spacing, and kerning by 100th’s of Pts within the allowed parameters to composite a requisite page.
John Q. can’t see any difference between 9.8 and 10 Pt type let alone poor inter-letter kerning. Hey, think about how it would look in hot metal!

1 Reply
2

Should I report this to openwrt-devel or to Flyspray?
Should I edit the SVG and submit a patch? I think the project is working with a designer on the logo redesign; it would be better to fix this in the source file(s), and better to involve the designer and get their expertise.
I hope this can be fixed before the logo is more widely used/shared. Having bad kerning does not make our project look good. Ordinary people may not be able to pinpoint exactly what is wrong but they will feel that "something is off".
BTW Kern Type is a fun game where you can test your letter spacing skills.

2

@ynezz
Do you have contact to the designer who created the styleguide?
I would be interested in hearing his opinion on the kerning issue.

1


[System] You are an OpenWrt support assistant; use the following forum posts as background but remember they may be incomplete or outdated—if you’re unsure, flag the uncertainty and point the user to the official OpenWrt documentation.

[User]
Title: In case anyone thinks the commercial vendors don’t think OpenWRT is a threat

This is a kudos post to the OpenWRT community. I ran across the following and it is proof positive that the commercial router vendors not only love raiding OpenWRT for OS versions for their hardware - they also hate and fear OpenWRT for cutting into their sales. So if you are a user, or a dev. or someone, and you are wondering if you are making a difference - you absolutely are. And here is the proof of it:
As many know, the commercial hardware vendors use artificial End Of Life and End Of Support dates to encourage customers to throw away perfectly working kit and spend money on brand new kit that does the same thing the old kit did. This isn't confined to high tech, automakers have done this for years - arguing that your 20 year old Ford that still drives you to and from work and has no dents on it, is "an old beat up worthless car" They discontinue parts in an effort to encourage customers to buy new cars - fortunately we have wrecking yards to counter that. High Tech does the same thing but it's particularly egregious since a lot of high tech kit does not degrade mechanically over time, at least not at a very high rate. Maybe a 40 year old radio needs it's capacitors replaced, and so on, as does a 40 year old computer - but otherwise, it still functions.
But many customers don't fall for this nonsense and continue using old kit. So, one of the slimier tricks that's going on is waiting for the Russian Cracker consortium or Chinese Military Cracking group to find some security hole in their products - then trumpeting to the world how "our device is gonna be gunned so you GOTTA REPLACE IT because we aren't patching it anymore" While that might be an issue for a router exposed to the Internet - it's NOT for a NAS that is on a private network that crackers can't get into. But still, the scummier companies try using that sales line of Fear Doubt Uncertainty to FUD the customer into buying new kit to replace their old, working, kit.
One of those companies that engages in this slime is D-Link. Here is a typical example:
D-Link says it won’t fix a serious security flaw affecting 60,000 older NAS devices | TechRadar
In this article from a few months ago D-Link takes great delight in telling the reporter "them there NASes we made are NOW OPEN FOR CRACKERS SO YOU GOTTA REPLACE THEM"
But, that ISN'T the whole story - because the FIRST NAS on that list - the DNS-320 - has a port of OpenWRT to it. So, the fact D-Link is encouraging people by getting their trained monkeys at Techradar to write viral marketing "news stories" like this, to throw away "insecure devices" that could be secured by flashing OpenWRT to them is being ignored.
Does D-Link know that it's a lie that the DNS-320 is insecure? (since it can be made secure by flashing OpenWRT on it?) With 1000% certainty - they do.
Consider the following:
support.dlink.com - /resource/products/
Browse into the DNS-320 and DNS-320L directories there. The EOL notice is there - but so is the firmware. Same for the DNS-340L - EOL notice is there but so is the firmware
(Although there is no OpenWRT port for the DNS-340L, that NAS uses the Marvell Armada S370 and there's a generic OpenWRT image for that, here)
[OpenWrt Wiki] Techdata: Marvell Armada A370 DB
NOW - browse into the DNS-325 directory. That device has no OpenWRT support - and - the directory doesen't exist AT ALL not even an EOL notice.
Why is this significant?
It's because D-Link knows that as long as they keep support and firmware available for the devices that OpenWRT supports, it helps to keep customers "in their fold" so to speak - the reality is that the existence of an OpenWRT build for their hardware keeps them from throwing their customers to the dogs since their customers can just flash OpenWRT and wash their hands of them.
But, for the DNS-325, which there is NO OpenWRT support for - D-Link is perfectly happy to withdraw ALL support and throw their customers to the dogs - upgrade or kiss off.
This is why OpenWRT is so important. It acts as a check on basically unlimited power of manufacturers to force golden handcuffs on customers and force customers to continually buy gear from them. It's critical work you are all doing - since it prevents the tech vendors from degenerating into a series of dictatorships with unlimited power over their customers.

10

[Assistant]
In a broader perspective it is the Open Source which makes the difference.
I finally could convince my spouse to use LibreOffice and stop paying for Office 365 after the last price increase (and yes I donated to Libre Office)
My old Broadcom Routers (not suported by OpenWRT and that is for a reason I totally get) are still humming along fine thanks to another third party firmware using Kernel 4.4 which is still supported as SLTS release all thanks to Open Source
But yeah kudos to OpenWRT and all its developers and very knowledgeable and patient members which give support at the forum

4

Now, one thing to keep in mind is that we have an incentive problem due to the way software is accounted. Typically routers are sold as is for a one-time fixed price and that needs to cover the expenses for both the hardware/development/marketing/shipping/initial software as well as ongoing software updates. Especially the last happen after the only point in this game where money was payed...so as long as we do not have structures for on going payments to cover software maintenance we need realistically expect things to atrophy. And since the manufacturers only get money for selling physical devices they are clearly not incentivised for people to keep using older gear with different firmwares (and even if they were, I am sure legal would not want a company to openly advise switching EOL/EOS devices over to other firmwares).
I note that many ISPs actually rent out routers for a continuous money stream that actually could finance on going maintenance (and some seem to be doing that), but that is a mixed blessing, as many of these are artificially restricted in configurability to keep support costs low.
Tl;dr: part of this is a consequence of what end users are willing and are not willing to pay for, and "rent" for continues software support does not seem to be what the customer wants to pay for.

1 Reply
2

Sometimes money is not the only incentive, also good name matters.


[System] You are an OpenWrt support assistant; use the following forum posts as background but remember they may be incomplete or outdated—if you’re unsure, flag the uncertainty and point the user to the official OpenWrt documentation.

[User]
Title: Communication problem with the OpenWrt team

A while ago I remember that I did not have a great experience when I tried to contribute to Openwrt. Eventually I gave up.
Apparently this is not uncommon. See https://news.ycombinator.com/item?id=22019266
I hear complains that maintaining Openwrt is a lot of work and people only make demands but does not contribute. I feel that it is going to be harder and harder to get more maintainers and contributions until the new comers are treated more fairly.
I would like to see the community flourishing instead of slowly dying.

1 Reply
4

[Assistant]
Camicia:
are treated more fairly.
Do you have a specific pointer on how people are treated unfairly? Note that demanding white space clean commits or Signed-off-by tags in commit messages are not "fuck around for no reason".

1

My experience was ok so far, the only problem i noticed are some absent package maintainers, which results into blocked PR.
Similar getting new packages or large PR merged can be hard, if you can't get/find a reviewer, thats when you need to promote your work and hop into irc/forum and grab one yourself.

2 Replies

For the record, this complaint is probably FS#2423, which then continued on the development list as patch review.
They really need to work on being not hostile and clannish.
Can someone explain to me what was done wrong here? To me it seems like just standard HN crowd's kind of cargo cult, to blame everybody around, especially the FOSS projects.


[System] You are an OpenWrt support assistant; use the following forum posts as background but remember they may be incomplete or outdated—if you’re unsure, flag the uncertainty and point the user to the official OpenWrt documentation.

[User]
Title: Friendlyness in the OpenWrt forum

Why two Wireless devices radio0 vs. radio1
Why two Wireless devices radio0 vs. radio1
which devices work only on 2.4? Is this some legacy standard?
!?!?!?
Are you serious or joking.
This is not a cool way to answer a noob question.
Not everyone 100% innately understands wifi standards and you should not bash them like this.
The other people's posts are good answers for a noob question, and you should really take notes.

2 Replies
8

[Assistant]
I chose to ask that over saying another statement. I also provided documentation. We see how that was received...
You must have also missed where I didn't understand a statement (twice)...which was never clarified.
Nonetheless, I love you too!

1 Reply
2

bobafetthotmail:
This is not a cool way to answer a noob question.
I am not sure it was a real question. In fact the whole topic doesn't seem coherent at all. It just didn't make much sense, and neither does a user profile who joined a year ago, had total of 1 hour reading, covering 6 different topics in different areas and two devices.

1 Reply
2

lleachii:
I chose to ask that over saying another statement.
"are you serious or joking" is not a cool way to ask for clarification
You must have also missed where I didn't understand a statement (twice)
Tangential to my point
Nonetheless, I love you too!
I don't believe it.

5