[OpenWrt-Devel] Can't build OCF kernel files with 2.6.38 and x86 target

I'm building trunk with 2.6.38 enabled, but ocf is failing to build: ... CC [M] crypto/ocf/crypto.o crypto/ocf/crypto.c:67:26: fatal error: linux/config.h: No such file or directory compilation terminated. make[6]: *** [crypto/ocf/crypto.o] Error 1 make[5]: *** [crypto/ocf] Error 2 make[4]:

[OpenWrt-Devel] coreutils-uptime not working?

Has coreutils-uptime ever worked? I recently tried turning it on: root@OpenWrt:~# uptime uptime: couldn't get boot time: No such file or directory root@OpenWrt:~# root@OpenWrt:~# who root@OpenWrt:~# users root@OpenWrt:~# And evidently who and users are also broken, since root on the console

[OpenWrt-Devel] [PATCH 1/1] cs5535 driver no longer in drivers/char/ as of 2.6.38

The Geos target (and probably others, like net5501) need to grab the new cs5535 gpio driver. Signed-off-by: Philip Prindeville phil...@redfish-solutions.com --- Index: target/linux/x86/geos/target.mk === --- target/linux/x86/geos

[OpenWrt-Devel] [PATCH 1/3] solos-pci: Don't display pseudo-header when dumping packet contents

The 8 bytes of struct pkt_hdr immediately before a AAL5 frame should not be included as part of the packet contents hex dump. Signed-off-by: Philip Prindeville phil...@redfish-solutions.com --- --- a/drivers/atm/solos-pci.c.orig 2011-03-19 12:19:06.0 -0600 +++ b/drivers/atm/solos

[OpenWrt-Devel] [PATCH 2/3] solos-pci: Don't duplicate atm common code

net/atm/common.c already includes the same function as atm_dev_release_vccs(); don't duplicate it. Signed-off-by: Philip Prindeville phil...@redfish-solutions.com --- --- linux-2.6.37/drivers/atm/solos-pci.c.orig 2011-03-20 01:42:22.0 -0600 +++ linux-2.6.37/drivers/atm/solos-pci.c

[OpenWrt-Devel] [PATCH 2/3] solos-pci: Don't delete PVCs on carrier transitions

Don't delete the PVC set up by br2684ctl for nasX when carrier flaps. Signed-off-by: Philip Prindeville phil...@redfish-solutions.com --- --- a/drivers/atm/solos-pci.c.orig 2011-03-20 15:27:40.0 -0600 +++ b/drivers/atm/solos-pci.c 2011-03-20 16:32:11.0 -0600 @@ -382,8

[OpenWrt-Devel] x86 platform issues

Hi. I use a lot of x86 platforms, and I'm seeing some issues: (1) there are missing symbols for the 2.6.38 x86 images; (2) squashfs seems to fail when booting something about LZMA; (3) I couldn't find documentation about either upgrading a running system to a newer binary, or how to keep

Re: [OpenWrt-Devel] [PROPOSAL] growing OpenWrt devel team

I'm not sure that qualifies as a sure-fire method. I picked up a few packages and updated them, but still didn't hear back about my request for commit rights or ownership of x86-platform stuff. I agree with one of the other responders that it would be nice to have a more ordered and

[OpenWrt-Devel] [PATCH 1/1] geos: support cpu MSR register and flashrom for coreboot upgrades

The early versions of the platform shipped with coreboot 3.0, which had some issues rebooting correctly the first time. Allow the user to upgrade his BIOS from Linux. Signed-of-by: Philip Prindeville phil...@redfish-solutions.com Index: target/linux/x86/geos/target.mk

[OpenWrt-Devel] [PATCH 1/1] flashrom version bump to 0.9.3 and fix dependency

Bump flashrom to current version, and reflect that it uses dmidecode as a helper. Signed-off-by: Philip Prindeville phil...@redfish-solutions.com Index: feeds/packages/utils/flashrom/Makefile === --- feeds/packages/utils

[OpenWrt-Devel] Bounty: simplify extracting/restoring kernel .config

Hi. I’m working on a project where I need to be able to force certain kernel configuration parameters from a script, to automate building tailored kernels for performance testing, certification, etc. I love the way that I can use “scripts/diffconfig.sh” to save the deltas into a file… update

Re: [OpenWrt-Devel] Using kdump... persistent logs, etc.

https://github.com/lede-project/source/blob/master/target/linux/generic/patches-4.9/930-crashlog.patch > > > Best Regards, > Syrone Wong > > > On Thu, Feb 23, 2017 at 10:05 AM, Philip Prindeville > <philipp_s...@redfish-solutions.com> wrote: >> Hi, >> >

[OpenWrt-Devel] Using kdump... persistent logs, etc.

Hi, Has anyone managed to use kdump with OpenWRT/LEDE? I have a box which periodically panics, and since /var is a link to /tmp/ there are no persistent logs. Which reminds me: is it safe to configure a third partition on my CF card, format it as ext3, and mount that as /var/log in

Re: [OpenWrt-Devel] [LEDE-DEV] Makefile question

> On Feb 12, 2017, at 10:04 PM, Yousong Zhou <yszhou4t...@gmail.com> wrote: > > On 13 February 2017 at 11:23, Philip Prindeville > <philipp_s...@redfish-solutions.com> wrote: >> >>> On Feb 11, 2017, at 8:29 PM, David Lang <da...@lang.hm> wrote: >

[OpenWrt-Devel] Observing procd progress

One thing I was wondering about was, on a headless system, but that does have an LCD display, is maybe capturing the progress of procd as it runs and displaying it on that LCD. Looking at /var/log/messages, I see: 2017-02-12T05:49:52+00:00 Powercode kernel:4.660666] procd: - early -

Re: [OpenWrt-Devel] [LEDE-DEV] Observing procd progress

> On Feb 14, 2017, at 2:45 AM, Petr Štetiar <yn...@true.cz> wrote: > > Philip Prindeville <philipp_s...@redfish-solutions.com> [2017-02-12 12:57:19]: > > Hi, > >> One thing I was wondering about was, on a headless system, but that does >> have an LC

Re: [OpenWrt-Devel] [LEDE-DEV] Makefile question

> On Feb 13, 2017, at 11:25 PM, Yousong Zhou <yszhou4t...@gmail.com> wrote: > > On 14 February 2017 at 10:51, Philip Prindeville > <philipp_s...@redfish-solutions.com> wrote: >> >> Hi Yousong, >> >> I’ve been working on both OpenWRT and LEDE and

[OpenWrt-Devel] PHP at build time

Hi. I’m working on a project (some GUI interfaces and a back end for generating traffic shaping using netfilter/tc) written in PHP7. It uses PHP’s “composer”. I could install composer (it’s only ever run once on a released project) on the target machine, and run it on first boot. But that

[OpenWrt-Devel] Race condition in openssh build?

I did a “make dirclean” and then “make -j12” and I end up seeing the following (it’s reproducible): ... make[3] -C feeds/packages/utils/bash compile make[3] -C feeds/packages/utils/bc compile make[3] -C feeds/packages/net/bmon compile make[3] -C package/network/utils/iptables compile

Re: [OpenWrt-Devel] [LEDE-DEV] Bug in ipkg?

> On Jan 2, 2017, at 10:08 PM, Philip Prindeville > <philipp_s...@redfish-solutions.com> wrote: > > Okay, resolved…. I needed to change the Package/perl-cgi/install macro in > the Makefile to invoke perlmod/Install/NoStrip instead of perlmod/Install. > Sigh. >

[OpenWrt-Devel] [PATCH oldpackage/eventlog oldpackage/syslog-ng3] version bump to latest

update-syslog-eventlog.patch Description: Binary data ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel

[OpenWrt-Devel] Scripting builds... how to?

Hi. I wanted to be able to script building images completely. I understand how to do: cp ../my-saved-config .config make defconfig make oldconfig to generate the .config file in a completely scripted way, by seeding it with the minimum set of relevant parameters (the deltas) per the steps

[OpenWrt-Devel] Bug in ipkg?

I just saw something bizarre. I had a Perl module (CGI v4.35) which contained the following: my $appease_cpants_kwalitee = q/ use strict; use warnings; #/; which is just a quoted string containing the lines that some sanity checking code expects to see (albeit as actual code, and not embedded

Re: [OpenWrt-Devel] [LEDE-DEV] Bug in ipkg?

> On Jan 2, 2017, at 9:32 PM, Philip Prindeville > <philipp_s...@redfish-solutions.com> wrote: > > I just saw something bizarre. > > I had a Perl module (CGI v4.35) which contained the following: > > my $appease_cpants_kwalitee = q/ > use strict; > us

Re: [OpenWrt-Devel] [LEDE-DEV] Bug in ipkg?

> On Jan 2, 2017, at 9:59 PM, Philip Prindeville > <philipp_s...@redfish-solutions.com> wrote: > > >> On Jan 2, 2017, at 9:32 PM, Philip Prindeville >> <philipp_s...@redfish-solutions.com> wrote: >> >> I just saw something bizarre. >&g

[OpenWrt-Devel] Problem building modules out-of-tree (kbuild) for x86

Hi. I’m trying to add the Intel e1000e, igb, and ixgbe drivers that are on Source Forge. A snapshot of my work is here: https://github.com/pprindeville/packages/tree/sf-ether When I build this as “make -j1 V=s” using a mostly unmodified x86_64 generic configuration, I get: make[3]:

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

On Dec 21, 2016, at 10:13 PM, Russell Senior wrote: >> "Florian" == Florian Fainelli writes: > >>> However, I also agree with Dave, Alberto and Stefan that a name >>> change may be a really smart way to communicate the fresh start of >>>

Re: [OpenWrt-Devel] Any interest in adding runit to OpenWRT?

> On Dec 25, 2016, at 1:01 PM, Denys Vlasenko wrote: > > In my humble opinion, for distros which can't use systemd because > of the size, or won't use systemd because they don't like it, > a good contender is daemontools or one of its clones. > It is especially suited

Re: [OpenWrt-Devel] Problem building modules out-of-tree (kbuild) for x86

> On Dec 19, 2016, at 1:25 AM, Alexandru Ardelean <ardeleana...@gmail.com> > wrote: > > On Mon, Dec 19, 2016 at 1:41 AM, Philip Prindeville > <philipp_s...@redfish-solutions.com> wrote: >> Hi. >> >> I’m trying to add the Intel e1000e, igb, a

Re: [OpenWrt-Devel] [LEDE-DEV] Using kdump... persistent logs, etc.

at 10:27 AM, Philip Prindeville > <philipp_s...@redfish-solutions.com> wrote: > > Thanks for that. > > >> On Feb 22, 2017, at 11:44 PM, Syrone Wong <wong.syr...@gmail.com> wrote: >> >> According to LEDE's source code: >> >> con

Re: [OpenWrt-Devel] [LEDE-DEV] Using kdump... persistent logs, etc.

|| powerpc || sparc || TARGET_uml || i386 || x86_64) > > x86_64 is disabled by default. You may want to enable it yourself. I > don't know why. > > > Best Regards, > Syrone Wong > > > On Fri, Mar 3, 2017 at 2:31 PM, Philip Prindeville > <philipp_s...@redfis

[OpenWrt-Devel] glibc finally fixes /etc/resolv.conf handling

For everyone who has ever wondered why they need to stop and restart long running services when they move from one network to another (as is common for laptops using Wifi that are roaming around), this can be quite vexing. The reason was that /etc/resolv.conf would get rewritten by DHCP when

Re: [OpenWrt-Devel] [LEDE-DEV] openwrt and lede - remerge proposal

> On May 8, 2017, at 7:29 AM, David Woodhouse wrote: > > On Mon, 2017-05-08 at 15:19 +0200, John Crispin wrote: >> >> *) mailing list >> - ask david to add the openwrt-adm and openwrt lists >> - announce the switch to the infradead serves, asking people to >> unsubscribe

Re: [OpenWrt-Devel] [LEDE-DEV] openwrt and lede - remerge proposal

> On May 8, 2017, at 7:19 AM, John Crispin wrote: > > Hi, > > Felix, Imre and myself had 2 calls last week lasting several hours and > discussed the following proposal of conditions for a remerge that we would > like to propose and have people vote on. > > *) branding > -

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

Can we add “Powered by LEDE” in little tiny letters underneath? ;-) > On May 29, 2017, at 4:11 AM, Jamie Stuart wrote: > > Hi, > First of all, I’m glad to hear the process of remerging LEDE with OpenWrt is > moving forward. > For what it’s worth, if prefer the LEDE name

Re: [OpenWrt-Devel] [LEDE-DEV] glibc finally fixes /etc/resolv.conf handling

to afflict clients (especially roaming WiFi clients) being an LEDE router than LEDE itself. -Philip > On Jul 3, 2017, at 2:04 PM, Philip Prindeville > <philipp_s...@redfish-solutions.com> wrote: > > For everyone who has ever wondered why they need to stop and restart long >

Re: [OpenWrt-Devel] [LEDE-DEV] [PATCH v2] merge: add OpenWrt branding

Hi all, Does it seem to anyone else that we’re making this more complicated than it needs to be? If one of the goals we’re going for from here on out is “equality”, then a basic litmus test to be applied to any action might be “does this get us closer to a level playing field, or further

Re: [OpenWrt-Devel] [LEDE-DEV] [PATCH 1/9] hwmon-coretemp: add thermal monitor for Core/Core2/Atom

> On Oct 22, 2017, at 11:57 PM, Felix Fietkau <n...@nbd.name> wrote: > > On 2017-10-23 05:50, Yousong Zhou wrote: >> On 23 October 2017 at 04:21, Zoltan HERPAI <wigy...@uid0.hu> wrote: >>> From: Philip Prindeville <phil...@redfish-solutions.com> >&g

Re: [OpenWrt-Devel] Merged: x86: fix bios mkimage during efi image generation

The original work is about a year old now, I think. What do we still need to make it into master? Also, how did the target/host Makefile issue for sfdisk end up being resolved? Thanks, -Philip > On Mar 14, 2018, at 12:18 PM, Jo-Philipp Wich wrote: > > Merged into my staging tree at >

[OpenWrt-Devel] Testing packages (and images) under KVM/Qemu

Hi all, Does anyone have a baseline KVM machine description (i.e. an domain.xml file) for testing x86_64 images? I’ve spotted a bug in Busybox that requires some debugging to root-cause it, but I don’t want to do this on an actual production router for obvious reasons and I’m a little short

Re: [OpenWrt-Devel] Testing packages (and images) under KVM/Qemu

Inline > On Jun 13, 2018, at 2:19 PM, Alberto Bursi wrote: > > > > On 13/06/2018 22:08, Philip Prindeville wrote: >> Hi all, >> >> Does anyone have a baseline KVM machine description (i.e. an domain.xml >> file) for testing x86_64 images? >> &

Re: [OpenWrt-Devel] [PATCH v2 1/4] openssl: Upgrade to 1.1.0h

Inline… but generally, please spellcheck yourself. > On May 30, 2018, at 8:35 PM, Eneas U de Queiroz via openwrt-devel > wrote: > > From: Eneas U de Queiroz > Subject: [PATCH v2 1/4] openssl: Upgrade to 1.1.0h > Date: May 30, 2018 at 8:18:34 PM MDT > To: openwrt-devel@lists.openwrt.org > Cc:

Re: [OpenWrt-Devel] [PATCH v2 1/4] openssl: Upgrade to 1.1.0h

Inline > On Jun 4, 2018, at 10:27 AM, Eneas Ulir de Queiroz > wrote: > > Sorry about the typos and spacing changes. This should have never happened. > Thank you for pointing them out. I have corrected them in the PR I've opened > on github. Since I'm new to the mailing list and don't

Re: [OpenWrt-Devel] Customizing openssh password login, preprovisioned root passwords, etc.

> On Jun 24, 2018, at 12:42 PM, Eric Luehrsen wrote: > > On 06/22/2018 12:43 AM, Philip Prindeville wrote: >> Hi all, >> A while back I proposed some PR’s to allow baking in root passwords >> (configurable, so it wouldn’t have to be some lame constant password)

Re: [OpenWrt-Devel] [PATCH packages] php7: add package dependency on zoneinfo-core

LGTM Sent from my iPhone > On Jun 24, 2018, at 2:19 AM, Rafał Miłecki wrote: > > From: Rafał Miłecki > > Having "select PACKAGE_zoneinfo-core" wasn't enough for builds without > php7-cli=y or php7-cgi=y. It didn't result in installing zoneinfo-core > when using "opkg install" (during runtime

Re: [OpenWrt-Devel] [PATCH] firewall3: make reject types selectable by user

> On Jul 3, 2018, at 3:22 PM, Alin Năstac wrote: > > On Tue, Jul 3, 2018 at 6:39 PM Philip Prindeville > wrote: >> >> Aren’t all inbound SYNs unsolicited by definition? Is there a danger of >> reflection attacks? > > Not all inbound SYNs are unsolicited.

[OpenWrt-Devel] Fwd: Issues porting 5.28.0 to Openwrt

in the community has an idea that’s not occurred to me? Thanks. > Begin forwarded message: > > From: Philip Prindeville > Subject: Re: Issues porting 5.28.0 to Openwrt > Date: July 1, 2018 at 10:07:09 PM MDT > To: Karl Williamson > Cc: perl5-port...@perl.org > > >

Re: [OpenWrt-Devel] [LEDE-DEV] [PATCH] base-files: quote values when evaluating uevent

LGTM Been using it here for a few days. > On Feb 1, 2018, at 5:57 PM, Daniel Golle wrote: > > When sourcing /sys/class/block/*/uevent values have to be quoted as > they may contain spaces (e.g. in PARTNAME). > Fix this by pre-processing with sed before sourcing. > >

Re: [OpenWrt-Devel] [LEDE-DEV] [PATCH 0/5] x86: add support for microcode update

> On Jan 18, 2018, at 2:15 PM, Hauke Mehrtens wrote: > > On 01/18/2018 01:51 PM, Nick Lowe wrote: >> Does an update to the Kernel, 4.9.77 and 4.14.14 need to be made to >> properly address this? There are fixes to mitigate Spectre. > > We even need a patch for GCC which will

Re: [OpenWrt-Devel] GSoC 2018 - we are in!

Well, before I write out a formal proposal… What about storing Openwrt configs natively in YANG and then synthesizing appropriate config files out of that for various subsystems (Ssh, network, firewall, DHCP, etc)? We would probably need bi-directional conversion from YANG to UCI, etc. so that

Re: [OpenWrt-Devel] GSoC 2018 - we are in!

> On Feb 13, 2018, at 11:12 AM, Anton Ivanov <anton.iva...@cambridgegreys.com> > wrote: > > > > On 02/13/18 17:31, Philip Prindeville wrote: >> Well, before I write out a formal proposal… What about storing Openwrt >> configs natively in YANG and then s

Re: [OpenWrt-Devel] [LEDE-DEV] [PATCH v1 1/1] openssh: disable passwords for openssh server

> On Feb 11, 2018, at 3:54 AM, Yousong Zhou <yszhou4t...@gmail.com> wrote: > > On 9 February 2018 at 08:28, Philip Prindeville > <phil...@redfish-solutions.com> wrote: >> From: Philip Prindeville <phil...@redfish-solutions.com> >> >> Allowing pas

Re: [OpenWrt-Devel] [LEDE-DEV] [PATCH v1 1/1] openssh: disable passwords for openssh server

> On Feb 13, 2018, at 9:14 PM, Michelle Sullivan wrote: > > [snip] > Personally - my thoughts > > There should be an option to enable passwords (default off...) > A warning should be placed on the checkbox to inform the user it is not a > good idea to enable them. >

Re: [OpenWrt-Devel] [LEDE-DEV] [PATCH v1 1/1] openssh: disable passwords for openssh server

> On Feb 14, 2018, at 1:06 AM, Yousong Zhou <yszhou4t...@gmail.com> wrote: > > On 14 February 2018 at 11:53, Philip Prindeville > <philipp_s...@redfish-solutions.com> wrote: >> >>> On Feb 11, 2018, at 3:54 AM, Yousong Zhou <yszhou4t...@gmail.com>

Re: [OpenWrt-Devel] [LEDE-DEV] [PATCH v1 1/1] openssh: disable passwords for openssh server

> On Feb 14, 2018, at 1:25 AM, Stijn Segers wrote: > > Yousong Zhou schreef op 14 februari 2018 09:06:11 CET: >> >> No, it's just complicating things up. When people really cares about >> the default settings' security, the will override the

Re: [OpenWrt-Devel] [LEDE-DEV] [PATCH v1 1/1] openssh: disable passwords for openssh server

> On Feb 14, 2018, at 3:00 PM, Magnus Kroken wrote: > > On 14.02.2018 22.13, Michelle Sullivan wrote: >> FWIW, I had misunderstood the intent of the original comments... OpenSSH >> server vs Dropbear - if someone is using OpenSSH server they already >> went in with advanced

Re: [OpenWrt-Devel] [PATCH v3 6/7] uclient-utils: Handle memory allocation failure for url file name

LGTM > On Feb 20, 2018, at 3:26 AM, Tobias Schramm wrote: > > Add null pointer check to allocation of url filename > > Signed-off-by: Tobias Schramm > --- > uclient-utils.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git

Re: [OpenWrt-Devel] [PATCH v2 6/7] uclient-utils: Handle memory allocation failure for url file name

> On Feb 18, 2018, at 5:46 AM, Tobias Schramm wrote: > > Add null pointer check to allocation of url filename > > Signed-off-by: Tobias Schramm > --- > uclient-utils.c | 9 +++-- > 1 file changed, 7 insertions(+), 2 deletions(-) > > diff --git

Re: [OpenWrt-Devel] 18.03/4

> On Feb 16, 2018, at 5:46 AM, John Crispin wrote: > > Hi, > > whats on the critical todo list for the upcoming release ? i still have a few > minor things that I'll be adding shortly, apart from that I am currently not > aware of any huge problems. the release will be a

[OpenWrt-Devel] Customizing openssh password login, preprovisioned root passwords, etc.

Hi all, A while back I proposed some PR’s to allow baking in root passwords (configurable, so it wouldn’t have to be some lame constant password) as well as turning off password login for OpenSSH server. The maintainers of base-files and openssh didn’t like either. So I’m proposing a virtual

Re: [OpenWrt-Devel] [PATCH] base-files: execute package prerm script in a subshell

LGTM > On Aug 23, 2018, at 6:21 PM, Luis Araneda wrote: > > This fixes a problem that's causing an early return of > default_prerm() when the package prerm script has an > exit statement at the end, which is implemented as > "exit 0" by most of the packages that use prerm > > With the new

[OpenWrt-Devel] libtirpc broken Makefile?

I just ran: % scripts/feeds update -i packages % rm -rf tmp/ % make defconfig oldconfig % grep libtirpc .config % grep "Package: libtirpc” tmp/.packageinfo % ls tmp/info/.packageinfo-feeds_packages_libtirpc ls: cannot access 'tmp/info/.packageinfo-feeds_packages_libtirpc': No such file or

[OpenWrt-Devel] IETF #102 Montreal

Hi, If anyone else is at the IETF #102 in Montreal this week, especially the ANRW (Advanced Networking Research Workshop) and you want to stop by and say hello, I’m around. Today I’m wearing a gray T-shirt and sporting a beard… Linkedin has a picture of me posted a couple of days ago at the

[OpenWrt-Devel] Minimum UCI to change macaddr of wlan0

I have some boards that came from the factory with the wrong MAC address burned into wlan0. What’s the minimum UCI required to associate a new MAC with them regardless of what configurations they might appear in (i.e. in the be: “option ifname ‘eth0 wlan0’” etc). Thanks. -Philip

Re: [OpenWrt-Devel] [PATCH] firewall3: make reject types selectable by user

Aren’t all inbound SYNs unsolicited by definition? Is there a danger of reflection attacks? Sent from my iPhone > On Jul 2, 2018, at 9:29 AM, Alin Nastac wrote: > > From: Alin Nastac > > RFC 6092 recommends in section 3.3.1 that an IPv6 CPE must respond to > unsolicited inbound SYNs with

Re: [OpenWrt-Devel] [LEDE-DEV] 18.03/4

> On Mar 4, 2018, at 6:26 PM, Alif M. Ahmad wrote: > > On Fri, Feb 16, 2018 at 01:46:31PM +0100, John Crispin wrote: >> Hi, >> >> whats on the critical todo list for the upcoming release ? i still have >> a few minor things that I'll be adding shortly, apart from that I

Re: [OpenWrt-Devel] 18.03/4

> On Feb 16, 2018, at 1:32 PM, Philip Prindeville > <philipp_s...@redfish-solutions.com> wrote: > > > >> On Feb 16, 2018, at 5:46 AM, John Crispin <j...@phrozen.org> wrote: >> >> Hi, >> >> whats on the critical todo list for t

Re: [OpenWrt-Devel] [PATCH v2 4/4] base-files: add sysupgrade -k to save list of pkgs

Inline > On Apr 4, 2018, at 5:28 PM, Luiz Angelo Daros de Luca > wrote: > > When '-k' is used, sysupgrade inserts into backup a new file > /etc/sysupgrade.installed which contains pkgname and > origin (rom, overlay, unknown). > > It's maily used to reinstall all extra

Re: [OpenWrt-Devel] [PATCH v2 4/4] base-files: add sysupgrade -k to save list of pkgs

Inline > On Apr 4, 2018, at 5:28 PM, Luiz Angelo Daros de Luca > wrote: > > When '-k' is used, sysupgrade inserts into backup a new file > /etc/sysupgrade.installed which contains pkgname and > origin (rom, overlay, unknown). > > It's maily used to reinstall all extra

Re: [OpenWrt-Devel] [PATCH] x86: Add APU3 reference to x86 board.d

Looks okay to me. Are the cases stenciled with the port #’s? Last PC Engines board I had (a Alix 2D3) the firmware would detect the ports in the opposite order (PCI enumerator) than the markings on the case. > On Mar 15, 2018, at 6:30 AM, Kristian Evensen >

Re: [OpenWrt-Devel] [PATCH] fstools: mount ntfs with ntfs-3g utility if it exists

Comments inline > On Sep 29, 2018, at 9:04 PM, Rosy Song wrote: > > From: Rosy Song > Subject: [OpenWrt-Devel] [PATCH] fstools: mount ntfs with ntfs-3g utility if > it exists > > This patch can mount ntfs with fuseblk fs type and make the deivces to be > mounted writable. > > --- a/block.c

Re: [OpenWrt-Devel] [PATCH] kernel: tolerate using UBI/UBIFS on MLC flash (FS#1830)

Can you drop the CAPS on words (not acronyms) and the _markup_? Sent from my iPhone > On Oct 18, 2018, at 6:28 AM, Koen Vandeputte > wrote: > > starting from upstream commit 577b4eb23811 ("ubi: Reject MLC NAND") > it is not allowed to use UBI and UBIFS on a MLC flavoured NAND flash chip. [1]

Re: [OpenWrt-Devel] Use binutils 2.31.1 by default

> On Aug 27, 2018, at 4:41 AM, Daniel Engberg > wrote: > > As per request, > > https://github.com/openwrt/openwrt/pull/1297 > > Longer tests with > https://lists.openwrt.org/pipermail/openwrt-devel/2018-July/013394.html > without issues > > Not subscribed so please cc > > Best regards,

Re: [OpenWrt-Devel] [PATCH v3] kernel: revert bad module stripping patch

Some hardware (it’s rare but not unheard of) can only be reset by unloading and reloading the module that controls it. Otherwise, you have to reboot the box. If you build all of your drivers in, then rebooting is all you have. My firewall has been up for 3 years. I update it with opkg,

Re: [OpenWrt-Devel] [PATCH v3 3/6] x86: add packages files to image bootfs

Inline > On Oct 31, 2018, at 11:02 AM, Tomasz Maciej Nowak wrote: > > Add files to bootfs image from selected as built-in packages, which want > to install files to targets boot file system. > > Signed-off-by: Tomasz Maciej Nowak > --- > target/linux/x86/image/Makefile | 2 ++ > 1 file

Re: [OpenWrt-Devel] [PATCH, V2] fstools: mount ntfs with ntfs-3g utility if it exist

I’m not seeing where “mount.ntfs-3g” is being set as the program to use... and should the test for the presence and modes of the program be generic? i.e. regardless of what type of FS or which program you use to mount it, you’ll want to test for its presence. So these are really two

[OpenWrt-Devel] Tarpit support in firewall

Jo-Philipp, Felix, et al: I’ve added the following to my /etc/firewall.user but I was thinking it might be useful for others, and worth integrating into the firewall. It’s currently implemented in Shell, but should be trivial in C. The relevant config (/etc/config/firewall) looks like: config

[OpenWrt-Devel] Quick question about firewall patch

I’m looking at: https://git.openwrt.org/?p=project/firewall3.git;a=commitdiff;h=c03e20d7f594058ff223f30cf34de1b5e8210b8d;hp=b59934331c4b9271ceb5e30b793a552618299d39 and wondering, why not just do: v4->s_addr = htonl(~(UINT_MAX >> bits)); For instance, with bits == 14, we get: UINT_MAX >>

Re: [OpenWrt-Devel] [PATCH, V2] fstools: mount ntfs with ntfs-3g utility if it exist

> On Oct 1, 2018, at 10:22 AM, Jérôme Benoit wrote: > > Signed PGP part > Le 01/10/2018 à 06:21, Philip Prindeville a écrit : >> I’m not seeing where “mount.ntfs-3g” is being set as the program to use... > > I think this patch is just plain wrong. > A correct one

Re: [OpenWrt-Devel] [PATCH, V2] fstools: mount ntfs with ntfs-3g utility if it exist

> On Oct 1, 2018, at 10:22 AM, Jérôme Benoit wrote: > > Signed PGP part > Le 01/10/2018 à 06:21, Philip Prindeville a écrit : >> I’m not seeing where “mount.ntfs-3g” is being set as the program to use... > > I think this patch is just plain wrong. > A correct one

Re: [OpenWrt-Devel] [PATCH] base-files: add network_get_metric() to /lib/functions/network.sh

LGTM Sent from my iPhone > On Sep 24, 2018, at 6:20 AM, Florian Eckert wrote: > > Signed-off-by: Florian Eckert > --- > package/base-files/files/lib/functions/network.sh | 5 + > 1 file changed, 5 insertions(+) > > diff --git a/package/base-files/files/lib/functions/network.sh >

Re: [OpenWrt-Devel] OpenWrt 19.01 plans

> On Sep 22, 2018, at 4:42 PM, Hauke Mehrtens wrote: > > Signed PGP part > Hi, > > We talked about plans for the next OpenWrt releases in this mail thread: > http://lists.infradead.org/pipermail/openwrt-adm/2018-July/000849.html > This mail is more or less a summary of the conclusions, this

Re: [OpenWrt-Devel] [RFC 4/6] x86: geode: shrink amount of default packages

Why is the hwclock being dropped everywhere? And who says the geos2, net5501, or alix2 are obsolete? I have some running right here… > On Jan 13, 2019, at 2:49 PM, Tomasz Maciej Nowak wrote: > > Drop excesive amount of default packages, instead, rely on packages > specified in device

Re: [OpenWrt-Devel] [RFC 4/6] x86: geode: shrink amount of default packages

Inline > On Jan 15, 2019, at 12:40 AM, Tomasz Maciej Nowak wrote: > > Hi Philip > > W dniu 14.01.2019 o 21:10, Philip Prindeville pisze: > >> Why is the hwclock being dropped everywhere? > > It's provided by busybox and installed by default, also greping for it

[OpenWrt-Devel] Rebasing "Generate EFI grub images for x86 platforms" (resend)

Hi all. I was trying to rebase my branch to upstream/master recently, but I couldn’t because this commit conflicted: commit 9e3edeb55a2f85ecf6233a5780e495ea1755c998 Author: DUPONCHEEL Sébastien Date: Tue Apr 11 12:46:44 2017 +0200 Generate EFI grub images for x86 platforms

Re: [OpenWrt-Devel] [Request] Build x86_64 with EFI Images for ext4 combined

Yup, amen to that, but it seems to be something that’s for whatever reason is not quick to happen… > On Aug 22, 2018, at 1:17 AM, Joel Wirāmu Pauling wrote: > > Currently the Auto-generated x86/64 images are all msdos > partition/boot layouts. Which means they are a PITA to run on >

Re: [OpenWrt-Devel] Issues with 4.19 and nft_reject_ipv4.ko after rebasing/updating

> On Jun 30, 2019, at 9:54 PM, Philip Prindeville > wrote: > > > >> On Jun 30, 2019, at 6:13 PM, Philip Prindeville >> wrote: >> >> I’m seeing the following failure after rebasing to master and 4.19: >> >> make[3]: Entering directory '/

[OpenWrt-Devel] Issues with 4.19 and nft_reject_ipv4.ko after rebasing/updating

I’m seeing the following failure after rebasing to master and 4.19: make[3]: Entering directory '/home/philipp/lede/package/kernel/linux' mkdir -p /home/philipp/lede/staging_dir/target-x86_64_musl/root-x86/stamp SHELL= flock /home/philipp/lede/tmp/.root-copy.flock -c 'cp -fpR

Re: [OpenWrt-Devel] Issues with 4.19 and nft_reject_ipv4.ko after rebasing/updating

> On Jun 30, 2019, at 6:13 PM, Philip Prindeville > wrote: > > I’m seeing the following failure after rebasing to master and 4.19: > > make[3]: Entering directory '/home/philipp/lede/package/kernel/linux' > mkdir -p /home/philipp/lede/staging_dir/target-x86_64_musl/root

Re: [OpenWrt-Devel] Problems w/ "make defconfig oldconfig" after rebasing

> On Jun 30, 2019, at 1:03 PM, Kevin Darbyshire-Bryant > wrote: > > >> On 30 Jun 2019, at 19:27, Philip Prindeville >> wrote: >> >> [snip] >> >> Anyone have an idea of what’s going on? > > There were some tweaks to how config in

[OpenWrt-Devel] Problems w/ "make defconfig oldconfig" after rebasing

I’ve been busy with other things, and just had a chance to try to get caught up with OpenWRT and my tickets, etc. I rebased openwrt and packages, then did “make defconfig oldconfig” but I’m seeing: WARNING: Makefile 'package/feeds/packages/zabbix/Makefile' has a dependency on

Re: [OpenWrt-Devel] Can build x86_64 because of ntf_reject_ipv4.ko missing

> On Apr 20, 2020, at 1:18 AM, Petr Štetiar wrote: > > Philip Prindeville [2020-04-19 > 21:47:19]: > > Hi, > >> I just rebased to openwrt master today, and tried to rebuild from scratch >> but I’m getting: > > So perhaps something related to y

[OpenWrt-Devel] Missing default CONFIG_ symbols for 5.4?

I’m trying to build x86/64 on master, and I’m getting the following prompts: Verify kernel signature during kexec_file_load() syscall (KEXEC_SIG) [N/y/?] (NEW) Netfilter nf_tables support (NF_TABLES) [M/n/y/?] m Netfilter nf_tables set infrastructure (NF_TABLES_SET) [M/n/?] m Netfilter

Re: [OpenWrt-Devel] Can't build x86_64 because of ntf_reject_ipv4.ko missing

> On Apr 20, 2020, at 1:18 AM, Petr Štetiar wrote: > > Philip Prindeville [2020-04-19 21:47:19]: > > Hi, > >> I just rebased to openwrt master today, and tried to rebuild from scratch >> but I’m getting: > > So perhaps something related to your

[OpenWrt-Devel] Can build x86_64 because of ntf_reject_ipv4.ko missing

Hi all, I just rebased to openwrt master today, and tried to rebuild from scratch but I’m getting: make[3]: Entering directory '/home/philipp/lede/package/kernel/linux' mkdir -p /home/philipp/lede/staging_dir/target-x86_64_musl/root-x86/stamp SHELL= flock

Re: [OpenWrt-Devel] Can build x86_64 because of ntf_reject_ipv4.ko missing

Sigh. *Can’t* build. > On Apr 19, 2020, at 9:47 PM, Philip Prindeville > wrote: > > Hi all, > > I just rebased to openwrt master today, and tried to rebuild from scratch but > I’m getting: > > make[3]: Entering directory '/home/philipp/lede/package/kernel/linu

Re: [OpenWrt-Devel] Can't build x86_64 because of ntf_reject_ipv4.ko missing

> On Apr 20, 2020, at 10:58 PM, Hannu Nyman wrote: > > [snip] > > Regarding IPv6 NAT, you stumbled into a kernel 5.4 issue originally reported > in > http://lists.infradead.org/pipermail/openwrt-devel/2020-February/021929.html > > Bug report:

Re: [OpenWrt-Devel] [PATCH v2 11/14] package/base-files: caldata: allow setting target file

Agreed, especially if you’re using “set -e” for debugging… > On Apr 20, 2020, at 8:09 AM, m...@adrianschmutzler.de wrote: > > Acked-by: Adrian Schmutzler > > I personally prefer > [ -n "$var" ] || do something > to > [ -z "$var" ] && do something > but that's pure matter of taste again. > >

Re: [OpenWrt-Devel] [PATCH] kernel: add gpio-it87

-5.4 b/target/linux/x86/64/config-5.4 > index 899668f77e..2a58983957 100644 > --- a/target/linux/x86/64/config-5.4 > +++ b/target/linux/x86/64/config-5.4 > @@ -199,7 +199,7 @@ CONFIG_GPIOLIB=y > CONFIG_GPIOLIB_IRQCHIP=y > CON

[OpenWrt-Devel] Routes disappearing when ip "ip link set down ethX" and bring it up again

Hi all, I noticed that if eth5 is my “wan” interface and I do: # ip link set down dev eth5 make some firewall changes, then do: # ip link set up dev eth5 then my routes don’t get repopulated. I thought that procd installed triggers so that if an interface flaps, then a helper would run (in

<    1   2   3   4   5   6   7   8   9   >