[LEDE-DEV] Using stable wireless/kernel but trunk userspace/kernel

Hi all, I'm wondering if there is an easy way to use trunk userspace with the stable release's wireless (and if necessary the rest of the kernel). The reason I ask ask is that at this time my primary concern with doing dog-fooding with things I develop for LEDE is that I can end up with wireless

Re: [LEDE-DEV] Luci/Statistics problem

On Fri, 3 Mar 2017 09:08:02 +0100 e9hack wrote: > Hi, > > Lusi/Statistics doesn't work any more. For every page, I got an > error, for example: > https://my-box.lan/cgi-bin/luci/admin/statistics/graph/uptime? > > The browser shows this: > /usr/lib/lua/luci/dispatcher.lua:380:

[LEDE-DEV] Host staging changes breaking packages feed

Hi all, The recent host staging changes are causing breakage in the packages feed, advising packages folks of how to fix that is needed (or if a core fix is needed, doing that). Regards, Daniel ___ Lede-dev mailing list Lede-dev@lists.infradead.org

Re: [LEDE-DEV] netifd: "bridge: disable IGMP snooping by default"

On Sat, 21 Jan 2017 03:50:50 + Eric Luehrsen wrote: > Dave, > > May I quote you for pull requests to achieve "dnsmasq: make DHCPv6 > work in standalone dnsmasq installation": > https://github.com/lede-project/source/pull/704 >

Re: [LEDE-DEV] s/dnsmasq/unbound+odhcpd/

On Thu, 19 Jan 2017 21:34:45 +0100 Dan Lüdtke wrote: > Hi everyone, > > i built LEDE without dnsmasq but with odhcp instead. Mainly out of > curiosity and to test a recent PR by Eric Luehrsen regarding > unbound+odhcp. Sound interesting. Can it do multiple instances? > > C)

[LEDE-DEV] Fw: [openwrt/luci] BUG: DHCP Leases "infinite" time shows as "expired" not as "unlimited" in IPv4 (#963)

Hi Hans, In LuCI GitHub issue 963 (https://github.com/openwrt/luci/issues/963), a user discovered that LuCI incorrectly reports dnsmasq infinite leasetime as expired because the LuCI check is based on odhcpd's -1 for INFINITE_VALID, but dnsmasq uses 0 in the dhcp.leases file for infinite leases.

Re: [LEDE-DEV] Talks between OpenWrt and LEDE

On Wed, 21 Dec 2016 13:06:22 -0500 "Hauke Mehrtens" wrote: > We had multiple meetings to find a solution to solve the problems > between the OpenWrt and the LEDE project and to discuss a possible > merge. Everyone with commit access to LEDE and all OpenWrt core > developers

[LEDE-DEV] It seems I didn't see most list activity due to list issues

Hi, It seems my impression that there wasn't much getting discussed was because there was some sort of list issue that prevented me from getting incoming mails; I had whitelisted the LEDE lists with my email provider, so there was definitely something funky

Re: [LEDE-DEV] Apology; Communication

On Fri, 25 Nov 2016 21:27:50 +0100 Hartmut Knaack <knaac...@gmx.de> wrote: > Hi Daniel. > > Daniel Dickinson schrieb am 25.11.2016 um 01:26: > > > > To be clear, I think what I mean by lack of communication is that > > the community doesn't see: > >

[LEDE-DEV] Apology; Communication

I want to apologize for my last email. I have been in a rather negative state of mind lately due to medical issues, in addition to struggling to keep from being excessively annoying at other times. In any event, the perception of lack of transparency and such, has more to due with lack of

[LEDE-DEV] Apologies; reimplementing delay

Hi all, Sorry for my last couple of messages, I'm re-implementing my delay mechanism so that I don't mess things up again; I do want to help both OpenWrt and LEDE, not create another bad situation; maybe in a week or few the things I'm dealing with will be sorted enough to remove that. At this

[LEDE-DEV] Getting 'too many bounces' notification

Hi all, Ended up having some problems again and when I got back to my email I noticed that I was getting a lot of 'too many bounces' notifications even though I have whitelisted the mailing lists for LEDE. Any ideas? Also, I noticed in the git log there were issues with older kernel versions.

[LEDE-DEV] Firewall UCI has non-working 'utc_time 0'

Hi all, The firewall package advertises utc_time uci option for firewall rules and redirects, however, based in the iptables-extensions manpage, only UTC time is supported by the time extension. This matches my experience with attempting to use local timezone with firewall rules based on time

Re: [LEDE-DEV] [PATCH] base-files: sysfixtime: Allow system time in local timezones

On Wed, 19 Oct 2016 22:05:43 +0200 Petr Štetiar wrote: > Felix Fietkau [2016-10-19 21:44:06]: > > > I'd like to know why you need to use local time for the RTC, I think > > that's rather uncommon. > > You mean system time in local time, right? RTC should be in

[LEDE-DEV] Discussion of FHS and /srv vs /usr/var for packages feed

Hi all, Most of you are probably unaware of the following discussion https://github.com/openwrt/packages/pull/3059 in which, in the context of postfix specifically, but touching on what should be the policy for the packages feed in general, it is discussed what is considered a reasonable way to

[LEDE-DEV] Luci + Luci2 compat

Hi all, In the interests of making LuCI2 development feasible without losing all of LuCI in the process, I'm planning on looking to a luci-luci2 compat mechanism that would allow LuCI2 apps to be used from within the current LuCI framework, while preventing

[LEDE-DEV] Back from hospital; getting reintegrated

Hi all, I was in the hop for a while and while I've been out for about a month there has been a lot to take care of. I've also gotten a couple boughts of already this school season (from those in the family who are in school or work at school), so that hasn't

Re: [LEDE-DEV] [openwrt/packages] mail/postfix: Use more FHS compliant /srv for data (#3059)

On Sun, 2016-08-14 at 11:39 -0700, Michael Heimpold wrote: > Hi, > could you please elaborate, why do you think that /srv is a more FHS- > compliant choice? I agree, that /usr is really the wrong place to put > data there, but according to my understanding of the FHS, /srv is not > even better,

[LEDE-DEV] per-host leasetime odhcpd patch I sent some time back

Hi, Just wondering if I missed any questions or comments about the odhcpd per-host leasetime patch I sent some time ago?  I don't recall seeing anything and I wasn't following the list all that closely for a while for personal reasons. Should I update and send again? Regards, Daniel

[LEDE-DEV] Kind of back

Hi all, I'm doing better than I was although I still can't spend a whole lot of time on LEDE. My plan is to ditch the SDK/IB stuff I was working on since I realized that I don't really need it anymore (my reasons for doing it have gone away), and it's taking time away from other things. The

[LEDE-DEV] May be out of commission

Hi all, Things have gotten a little crazy around here and I've not been able spend time on LEDE, and there's indications that I may soon be permanently unable to assist (not by my choice). Maybe I'm just having issues, if I am things should be back on track soon and I'll be back because I'm

Re: [LEDE-DEV] Multi-Profile selection support

On Mon, 2016-05-23 at 13:38 +0200, Felix Fietkau wrote: > Hi Daniel et al. > > after a long delay, I finally got around to looking into multi profile > selection again. After reviewing your code and thinking about it some > more, I decided to go with a slightly different approach from the one >

[LEDE-DEV] Transparency and remaining OpenWrt developers

Hi, It seems to me that one of the biggest accusations levelled at the LEDE team is their split was not done in a transparent manner, and that they are not yet transparent enough. That sounds great and all as an argument, but it seems to me that from the looks of it the LEDE team is serious

Re: [LEDE-DEV] [PATCH] mac80211: respect user-set regulatory domain by default

On Thu, 2016-05-26 at 02:57 +0200, Alexander Couzens wrote: > On Wed, 25 May 2016 19:32:01 +0200 > Daniel Golle wrote: > > I really like this commit. > Can you set the country *explicit* to world in /etc/config/wireless > before appling this patch? > If the FCC hadn't

[LEDE-DEV] A question on procd interface_trigger vs raw_trifger

Hi, I've noticed that network_trigger has gone away and is replaced by interface_trigger, but have seen raw_trigger too, and am not clear on when one would use which. Can you clarify? Regard, Daniel ___ Lede-dev mailing list

[LEDE-DEV] Problem with serial console

Hi John, Something seems to have broken with serial console, at least on ar71xx, possibly because the login.sh stuff. If you don't have passwords required on the serial console and you exit the shell, the shell doesn't respawn and you end up with no serial access until you reboot. Regards,

[LEDE-DEV] Device profiles have broken ImageBuilder somewhat

Hi Felix, The recent changes to the device profile stuff has caused issues with ImageBuilder. In ar71xx, if one selects the Default profile during the core build, then even if you set make PROFILE=SOMEBOARD image, the ImageBuilder tries to build the image for every device instead of just the one

Re: [LEDE-DEV] [PATCH 2/4] v2: block.c: Add support for checking vfat filesystems

Hopefully before I crash tonight I will have something to report. I'm in the process of a build now. On 16-05-19 02:07 AM, John Crispin wrote: > > > On 18/05/2016 13:28, l...@daniel.thecshore.com wrote: >> From: Daniel Dickinson <l...@daniel.thecshore.com> >>

Re: [LEDE-DEV] [PATCH 2/4] v2: block.c: Add support for checking vfat filesystems

On 16-05-19 02:07 AM, John Crispin wrote: > > > On 18/05/2016 13:28, l...@daniel.thecshore.com wrote: >> From: Daniel Dickinson <l...@daniel.thecshore.com> >> >> v2: Fix mixup of dosfsck checking ext* and e2fsck checking vfat. >> >> vfat is a co

[LEDE-DEV] procd and self-daemonizing processes with no useful foreground option

Hi, Rather than patching every package that daemonizes itself but doesn't provide a useful (non-debug mode) option for foregrounding the process (or not option at all for foreground operation), would it possible to do as systemd has done and support both a directly supervised instance (i.e. what

[LEDE-DEV] A request not making IRC necessary to be part of the action

Hi, I'd really appreciate if we could actually use the mailing list for the main communications venue rather than shutting out people not in the European timezones, which is what happens if IRC is the main way to participate in the community. I have been told that to really be part of the

[LEDE-DEV] Funkiness with lede-staging / lede-source

Hi all, Was there some history rewriting or something lede-staging and/or lede-source transition. I have a number of branches I created against lede-staging that after some pull diverged, and which also have a divergent set of commits from lede-source, so I'm wondering if something non-kosher

Re: [LEDE-DEV] Failed to execute /usr/libexec/login.sh

On 16-05-11 06:08 PM, Alexey Brodkin wrote: > Hi Daniel, > > > breaks something for my boards (in particular arc770-based boards). > I'm unable to activate console now. That's what I'm getting > every time I press ENTER: > ->8- > Failed to

Re: [LEDE-DEV] On the proposed Mantis and maximizing bug usefulness

Fundamentally I disagree with you unspoken premise that 'there is no such thing as a useless bug report'. I agree with the *reason* the developers proposed the bug reporting mechanism they dig, just not with mechanism itself, which is that there *are* bug reports that are not worth the time and

Re: [LEDE-DEV] On the proposed Mantis and maximizing bug usefulness

On 16-05-08 09:24 PM, Ben Greear wrote: > >> 1) I like the suggestion of one the of list members made of having >> something on the device that you clicked on and it prefilled as much as >> possible of the relevant information (like arch, model, etc) into the >> bug report (for example a luci

[LEDE-DEV] I really like the new output (bin) layout!

Hi, I just want to say kudos for the new output (bin) dir layout. Separating things that are target-specific from things can be shared among targets of the same arch is *awesome*! Regards, Daniel ___ Lede-dev mailing list Lede-dev@lists.infradead.org

Re: [LEDE-DEV] On the proposed Mantis and maximizing bug usefulness

One more note: if using prefilled forms (e.g. from openwrt_release) and the triagers notice that the report is from a third party source (e.g. a manufacturer who hasn't bothered to modified the URLs, etc), I'd suggest a boilerplate response that indicates what LEDE is and the fact it has no

Re: [LEDE-DEV] [PATCH] More OpenWrt -> LEDE renames

Also, as I mentioned in the preface (not sure if you saw), this patch was intended to point things out for whoever does the actual patch rather than as the patch that goes in. Feel free to make any changes you feel necessary. Regards, Daniel ___

Re: [LEDE-DEV] Proposal to sign all commits

On 16-05-06 08:28 PM, Kus wrote: > Daniel, I like what you said. I hinted something like that in the original > message. Er, sorry which part - I think you mean about fast-forward only and not the ideal world where everything is always tested no matter who it's from? Regards, Daniel > > I

Re: [LEDE-DEV] [RFC] A change to the way packages are built

On 16-05-05 04:16 AM, Michal Hrusecky wrote: > David Lang - 18:20 4.05.16 wrote: >> Debian has ... > > Just for the sake of discussion and inspiration, how openSUSE does it's > rolling > release. We have OBS, which is server software, connected to multiple > builders. [snip] Thank you David

[LEDE-DEV] Why technical elitism is contrary to stated goal of community

Hi all, I have noticed that some of the policies of this project are already veering towards a brand of technical elitism that I feel is completely contrary to the stated goal of having a stronger community. A strong community welcomes 'outsiders' and noobs and helps them find their place in the

Re: [LEDE-DEV] [OpenWrt-Devel] Introducing the LEDE project

Might I submit that my impression is that Kaloz (at least) holds infrastructure hostage to maintain control, and that the fundamental problem here is that OpenWrt is *not* democratic and ignores what people who were ones visibly working on openwrt want and overrides their wishes because he/they

Re: [RFC] A change to the way packages are built

On 16-05-05 01:57 PM, Jo-Philipp Wich wrote: > Hi Daniel, > >> Basically one builds a minimal SDK and does kind of like Debian where a >> git commit to a package kicks of a build of pristine environment which >> builds only the package and it's dependencies. > > I've set up a two-phase buildbot