+1 - I endorse installing LuCI in snapshot builds.
- A significant fraction of people will wind up installing LuCI anyway.
- It's a FAQ on the forum. "I just installed a snapshot build, but there's no
web GUI." (This even bites me from time to time...)
- LuCI poses less of a space concern (in
Thank you Felix for the careful review.
> On Feb 5, 2024, at 3:28 PM, Felix Baumann via openwrt-devel
> wrote:
>
> I would do an estimate if I could. I don't think it's possible to do one
> without building images. Especially since OpenWrt will grow a bit as well
> till any release is done.
> On Feb 5, 2024, at 5:35 AM, Zoltan HERPAI wrote:
>
>
> One thing I fully agree with Hauke is that we should pick one (and only one)
> kernel for the next release, whenever that is. If we need to drop targets to
> achieve it (no maintainer stepping up or lack of storage on the devices), so
+1 Thanks
> On Jan 30, 2024, at 1:15 PM, Christian Marangi (Ansuel)
> wrote:
>
> Robert is active in OpenWrt since 2017 and with some recent stats, he
> has more than 310 commits merged in OpenWrt.
> He also have uncounted Reviewed-by tag on various PR and merged commits
> and generally
> On Jan 18, 2024, at 12:11 PM, Dave Taht wrote:
>
> OpenWrt One could use a logo...
Could we get the designer of the current OpenWrt logo/wordmark to augment it
with the word "One"?
See:
Thanks Arınç for opening this discussion about improving the development
process. I would like to expand the discussion to include what, if any, changes
we'd like to make in the user experience for OpenWrt.
The first one I would propose is "Automatic renumbering of LAN in case of
conflict with
RT=55
> boot() {
>
> lanip=$(uci get network.lan.ipaddr)
>
> grep -q "myrouter.local/$lanip" /etc/config/dhcp
> if [ $? -eq 1 ] ; then
> # add a redirect myrouter.local to our IP
>uci add_list dhcp.@dnsmasq[0].address="/myrouter.local/$lanip"
&
Let me rephrase to be sure if I understand correctly:
> On Sep 13, 2022, at 3:56 PM, Jo-Philipp Wich wrote:
>
>
> This cannot be done in a sane manner though as it would render future versions
> entirely backwards incompatible.
>
> Renaming `config interface` to `config network` makes sense
s discussion. Thanks again.
> On Sep 11, 2022, at 6:45 PM, Arınç ÜNAL wrote:
>
> On 12.09.2022 00:28, Rich Brown wrote:
>> I think I see where I went wrong. I have updated the definitions in the DSA
>> Terminology page to incorporate what I understand from this conversation.
&g
.
Rich
> On Sep 10, 2022, at 9:47 AM, Arınç ÜNAL wrote:
>
> On 10.09.2022 14:59, Rich Brown wrote:
>> I got the following definitions from Arınç, I am taking the liberty of
>> opening this to the entire list, so we can refine these definitions
>> together. I inc
why I'm striving to find solid definitions for the base terms, so we can
build on them and use them to create comprehensible documentation. Thanks, all.
Rich Brown
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
I got the following definitions from Arınç, I am taking the liberty of opening
this to the entire list, so we can refine these definitions together. I include
some questions in-line to clarify the definitions.
>>> As a start, certain terms have cropped up multiple times in this
>>>
Thanks for all this discussion. I have read everyone's notes carefully, but I
feel as if I am falling farther and farther behind.
I don't understand the distinctions between the terms that everyone is using.
(The networking field is replete with synonyms for the same thing: "interface"
(and
Hi jow, thanks for weighing in. I'm glad that I'm not unnecessarily confused -
the naming *is* inconsistent. It sounds as if different "contexts" have varying
definitions for the terms "interface", "network", "device", etc... (LuCi,
/etc/config/network, the kernel.org article about DSA
> On Sep 6, 2022, at 5:33 PM, Florian Fainelli wrote:
>
>> I don't see much content to document DSA. All DSA does is creating a network
>> interface for each switch port. What I think should be properly documented
>> is the Bridge VLAN filtering feature. I have made some efforts to do that
Hello Arınç (and the rest of the list),
It's good to hear from you again.
> On Sep 4, 2022, at 5:32 PM, Arınç ÜNAL wrote:
>
> I don't see much content to document DSA. All DSA does is creating a network
> interface for each switch port. What I think should
> be properly documented is the
Folks,
The DSA Mini-tutorial on the Wiki
(https://openwrt.org/docs/guide-user/network/dsa/dsa-mini-tutorial) is still
marked as a "Work In Progress"
I should know - I wrote this up as we were getting ready to ship 21.02, and I
thought that we should have something about DSA on the wiki. But I
> On Aug 12, 2022, at 5:12 PM, Florian Fainelli wrote:
>
>> As an idea, I understand this, it would basically be an "LTS" OpenWrt
>> release that
>> would receive security-only updates.
>> However, we had a long discussion on the IRC today and the resources are
>> spread
>> rather thin even
Bjørn,
Thanks for these comments.
> On Mar 23, 2022, at 8:34 AM, Bjørn Mork wrote:
>
> There is no need to read anything from a file or device. You can just
> serve the same memory buffer in a loop.
That might satisfy Paul Spooren's concern.
> I did a quick look at the document and it seems
Hi Paul,
> The spec wants a 8GB file which seems a bit much for common home routers. We
> could look into reading from /dev/zero since the body content isn’t relevant
> but still the device is likely slower at offering the content than your
> laptop can chew. A dedicated device could be
The Apple "RPM Tool" is great for measuring network responsiveness.
High numbers from the tool (measured in round-trips per minute - or "RPM") show
your network is responsive, even when it's heavily loaded with traffic. This
also implies you have low "bufferbloat" - which is good.
There are
There is a new RFC on the OpenWrt forum proposing "Automatic LAN Subnet
Reassignment"
https://forum.openwrt.org/t/rfc-automatic-lan-subnet-reassignment-upon-conflict-with-wan/120938
The RFC responds to the advice given at last week's OpenWrt-Adm meeting
/head' branch that needs to be
> picked and normalized and made stable (if that's how I might summarize making
> all the platforms behave consistently)? I would be fine without regular
> yearly releases. nightlies are available etc.
>
>
>
> On 2021-10-06 07:58, Rafał Miłecki wro
> On Oct 6, 2021, at 1:58 AM, Rafał Miłecki wrote:
>
> On 30.09.2021 03:34, Rich Brown wrote:
>> My desire would be to name our next release "22.03", with a target release
>> date in March 2022. And we should name the following release "22.09" with a
> On Oct 5, 2021, at 10:24 AM, Paul D wrote:
>
> Write this up into an FAQ/howto on openwrt.org (this is, after all, the OWRT
> way)
Yes, it's always more powerful (and useful) to tell people what TO do, instead
of what NOT to do.
I contribute very occasionally, and by trial and error, I
(I'm cc'ing both openwrt-devel and openwrt-adm since both will be involved in
the decision)
> On Sep 29, 2021, at 4:28 PM, Hauke Mehrtens wrote:
>
> The OpenWrt 21.02 release is done and we should plan the next release.
> We already talked about this in the last meeting, see
>
Hauke: My thanks also for writing up those note.
My desire would be to name our next release "22.03", with a target release date
in March 2022. And we should name the following release "22.09" with a release
date in September. And so on - every six months (or whatever interval we
believe
Hi Arınç
> On Sep 17, 2021, at 3:17 AM, Arınç ÜNAL wrote:
>
> The current naming used on LuCI/UCI is inaccurate and confusing. The
> “interfaces” under Network → Interfaces actually represent networks. The
> actual interfaces are called “device”.
I agree that the terminology is confusing. I
On Aug 29, 2021, at 6:31 AM, Hannu Nyman wrote:
>
> Hauke Mehrtens wrote at Sun Aug 29 02:53:47 PDT 2021:
>
> We have now reverted back to the old "let's wait long for branching and then
> wait even longer for the actual release".
>
> The reality is the same than earlier: almost all devs and
All,
> On Aug 10, 2021, at 1:10 PM, Hauke Mehrtens wrote:
>
> ... For 21.02 we should work on the DSA documentation which Rafal and Rich
> already did and continue like it is now...
Maybe I'm worrying needlessly, but I want to say I'm concerned about those DSA
pages on the wiki.
They may
Congratulations on RC4. I'm getting excited.
The release notes (below) have some steps for upgrading to 21.02. Is there any
information in
https://openwrt.org/docs/guide-user/network/dsa/upgrading-to-2102 that should
be incorporated there?
Thanks.
> On Aug 4, 2021, at 3:38 PM, Hauke
team could come together to get this
information together before we release 21.02. Thanks.
Rich
> On Jul 17, 2021, at 5:04 PM, Rich Brown wrote:
>
> Hauke and all,
>
> Thanks for the hard work to corral all those outstanding bug reports.
>
> As we move forwa
As I learn more about DSA, I want to make two requests to help out people who
support OpenWrt on the forums.
For the next several years, a question of the form, "I just upgraded my router
from X to Y, and the networking stopped working...", will mean we have to
figure out if this could be a
Hi Arınç
> On Jul 20, 2021, at 12:23 AM, Arınç ÜNAL wrote:
>
> I believe I could try to make one, I have a pretty good understanding
> of swconfig and DSA configuration. If someone can help me out with
> writing the script, I believe we can pull it off as a team effort.
I am in need of
I have updated the DSA Mini-tutorial in the playground:
https://openwrt.org/playground/richb/dsa-mini-tutorial
I finished the first section ("Bridging all LAN ports"), and I am going to stop
editing now, because:
1) I need someone else to look at the overall format of the document
2) I made
>> 1) I created a new "Upgrading to OpenWrt 21.02.0" page at:
>> https://openwrt.org/playground/richb/to2102 I distilled the announcement
>> page (https://openwrt.org/releases/21.02/notes-21.02.0) to make this
>> checklist for people that won't read that entire page.
>> Did I get the new
Hauke and all,
Thanks for the hard work to corral all those outstanding bug reports.
As we move forward, I want to be sure the documentation side is as good as the
software... I have these comments/questions:
1) I created a new "Upgrading to OpenWrt 21.02.0" page at:
I respectfully ask the participants in this conversation to take it off-line
from the OpenWrt Developer list. Thank you.
Rich Brown
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt
> On Sep 21, 2020, at 8:02 PM, Jacek Milewicz wrote:
>
>
>
> On 22/09/2020 00:06, Ansuel Smith wrote:
>>>
>>>
>>> On 19/09/2020 15:06, Paul Oranje wrote:
See below, regards,
Paul
> Op 15 sep. 2020, om 21:56 heeft jacekow...@jacekowski.org het volgende
>
Besides the "project management" concerns expressed in my earlier note, I also
share Karl Palsson's worries...
> On Sep 1, 2020, at 9:04 AM, Karl Palsson wrote:
>
> With this change, the very first thing users see is a browser
> warning telling the user very very very bad things about what
>
Forgive me for chiming in now, for I have not been following the discussion
closely.
Is this change (specifically, using these certs for "ordinary operation" of
OpenWrt) being considered for the 20.0x release? Would it delay the RC1 release
in any way?
If so, I believe we should move it off
I'm cc'ing the OpenWrt-Adm list on this as well, because I smell a policy
decision looming. Some thoughts:
1) In my opinion, we should not aim for a third (Tiny/Small/Normal) build for
20.xx. We don't need any more hurdles to overcome before we ship an RC1 version.
2) I had not understood how
>> On Aug 1, 2020, at 10:05 AM, Paul Oranje wrote:
>>
>>> Actually, my solution implements the config "on device" as a uci parameter,
>>> so the "on device" version is actually not the version of the firmware
>>> installed, but of the config installed. Therefore, one may indeed go that
>>>
Thanks for all these good ideas. A summary of my thoughts:
- Use of JSON. Not really risky - there'll be JSON parsers for the foreseeable
future. And sticking in a version field makes it possible to evolve. My primary
concern is that we use a SINGLE straightforward format and create tooling
>> A first step could be to establish a *versions.json* file at the root of
>> downloads.openwrt.org! The file would allow to check if a device still runs
>> the latest release. JSON seems common enough and is well supported by LuCIs
>> JavaScript implementation and also via jshn.sh on a
In hopes of guiding this conversation toward the forum, I reposted Nishant
Sharma's comment there...
https://forum.openwrt.org/t/help-pre-select-new-openwrt-project-logo-in-the-poll/52674/9
> On Jan 15, 2020, at 12:00 AM, Nishant Sharma wrote:
>
> Hi Petr,
>
> On 14/01/20 4:57 PM, Petr
I saw an notice for an update to the OpenWrt wiki:
Announcement for 19.07-rc1: https://openwrt.org/releases/start
Release Notes: https://openwrt.org/releases/19.07/notes-19.07.0-rc1
Thanks to all who helped to move us off top-dead-center.
Rich
___
> On Aug 20, 2019, at 5:32 PM, Rosen Penev wrote:
>> Can anyone speak to whether OpenWrt builds use any/all of those techniques
>> called out to provide additional security? OpenWrt's modern kernel provides
>> a bunch of security. That may be good enough, even if builds don't use all
>> those
l provides a
bunch of security. That may be good enough, even if builds don't use all those
techniques. And if we have implemented them, we can further differentiate
ourselves from vendor firmware...Thanks.
Rich
> вт, 20 авг. 2019 г. в 18:34, Rich Brown :
>>
>> Hi Vincent,
>>
&g
interfaces.
>
> Regards,
>
> Vincent
>
>
> On 20.08.19 13:21, Rich Brown wrote:
>> Hi folks,
>>
>> You've probably seen the Slashdot article about (lack of) security gains in
>> router firmware.
>> https://yro.slashdot.org/story/19/08/16/20
Hi folks,
You've probably seen the Slashdot article about (lack of) security gains in
router firmware.
https://yro.slashdot.org/story/19/08/16/2050219/huge-survey-of-firmware-finds-no-security-gains-in-15-years
The original article on Security Ledger is at:
create an estimate and the desired software
modifications.
Best regards,
Rich Brown
> On Jul 17, 2019, at 9:13 PM, SkullFace wrote:
>
> Hi
>
>
> I would like to ask openwrt team to add some special features that i need.
>
> I will use crowd funding to collect the money!
&
I was about to recommend the Download Stats page at
https://downloads.openwrt.org/stats/ as a first cut...
> Would it be possible to get some download stats for release/snapshot images,
> so we can get some rough numbers about popularity of devices in the wild?
BUT... that page doesn't seem to
check next? Thanks.
Rich Brown
Hanover, NH USA
Date: Thu, 24 May 2012 13:06:25 +0200
From: Jo-Philipp Wich x...@subsignal.org
To: OpenWrt Development List openwrt-devel@lists.openwrt.org
Subject: Re: [OpenWrt-Devel] Not quite getting IPv6 tunnel to work
Message-ID: 4fbe1631.4040
/
CeroWrt Wiki: http://www.bufferbloat.net/projects/cerowrt/wiki
CoDel article: http://queue.acm.org/detail.cfm?id=2209336
Best regards,
Rich Brown
Hanover, NH USA
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org
55 matches
Mail list logo
