Re: 20.xx: postponse LuCI HTTPS per default

On 20/11/20 14:22, Fernando Frediani wrote: I don't see having HTTPS by default in LuCI as something good or even necessary ? It's actually an unnecessary complication that could always be optional. One of the main reasons is that in many and probably most cases of a new deployed OpenWrt r

Re: 20.xx: state of the DSA

On 20/11/20 01:36, Paul Spooren wrote: Hi all, DSA (Distributed Switch Architecture)[0] is a main feature of 20.xx and one of the last blockers for a branch. The goal states[1] support where possible, not necessarily every target. This mail thread should be used to get an overview of the mis

Re: 20.xx: postponse LuCI HTTPS per default

On 20/11/20 16:31, Fernando Frediani wrote: Yes, exactly it is only an issue when someone have to access the web interface via wifi. In a home environment that is a small issue. Not sure how it is a small issue when wifi is the main method used to connect to a router and the Internet in a h

Re: 20.xx: postponse LuCI HTTPS per default

On 20/11/20 16:52, W. Michael Petullo wrote: I think making use of self-signed certificates in production is a bad idea because (1) it reinforces poor practices, namely electing to trust a self-signed certificate and (2) it does not authenticate the server/router, a critical piece of the TLS s

Re: 20.xx: postponse LuCI HTTPS per default

On 20/11/20 17:17, Fernando Frediani wrote: Hi Alberto On 20/11/2020 13:09, Alberto Bursi wrote: The only thing I can accept as a valid complaint against https by default is the increased minimum space requirements, everything else I really don't understand nor agree with.

Re: 20.xx: postponse LuCI HTTPS per default

On 20/11/20 17:39, Fernando Frediani wrote: Hi. I don't really see having HTTPS by default as something that make such a difference for most common users nor as a major security issue in the context it is used at the cost it puts, which may seems not too much but I always think of the very mi

Re: 20.xx: postponse LuCI HTTPS per default

On 20/11/20 17:47, W. Michael Petullo wrote: I think making use of self-signed certificates in production is a bad idea because (1) it reinforces poor practices, namely electing to trust a self-signed certificate and (2) it does not authenticate the server/router, a critical piece of the TLS s

Re: 20.xx: postponse LuCI HTTPS per default

On 20/11/20 18:35, Adrian Schmutzler wrote: Hi, -Original Message- From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org] On Behalf Of Alberto Bursi Sent: Freitag, 20. November 2020 17:32 To: openwrt-devel@lists.openwrt.org Subject: Re: 20.xx: postponse LuCI HTTPS per

Re: 20.xx: postponse LuCI HTTPS per default

On 20/11/20 19:22, W. Michael Petullo wrote: I think making use of self-signed certificates in production is a bad idea because (1) it reinforces poor practices, namely electing to trust a self-signed certificate and (2) it does not authenticate the server/router, a critical piece of the TLS s

Re: 20.xx: postponse LuCI HTTPS per default

On 20/11/20 20:23, Paul Spooren wrote: On Fri Nov 20, 2020 at 7:35 AM HST, Adrian Schmutzler wrote: Hi, -Original Message- From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org] On Behalf Of Alberto Bursi Sent: Freitag, 20. November 2020 17:32 To: openwrt-devel

Re: running custom commands during sysupgrade -

On 22/11/20 18:07, Hannu Nyman wrote: Adrian Schmutzler wrote at Fri Oct 16 19:15:38 EDT 2020: > Fortunately, and I don't fully understand why, we were able to drive this to effectively zero by simply running > echo 3 > /proc/sys/vm/drop_caches > directly before sysupgrade. Out of a few h

Re: 20.xx: postponse LuCI HTTPS per default

On 26/11/20 06:57, suchan wrote: 2020-11-21 오전 12:31에 Fernando Frediani 이(가) 쓴 글: Yes, exactly it is only an issue when someone have to access the web interface via wifi. In a home environment that is a small issue. In a more corporate environment there are two options: 1) access is done via

Re: [RFC] remove x86 qemu images

On 06/12/20 10:06, Paul Spooren wrote: Hi, openwrt.git includes an old version of QEMU (0.14 vs 5.1.0 in packages.git) only to convert x86 images to vdi and vmdk. Is there anyone actively using the vanilla x86 QEMU images from the upstream servers or can can we remove that "feature"? Thi

Re: ramips: Strange boot failures on TP-Link RE200v1

On 08/12/20 00:12, Andreas Böhler wrote: Hey, I added TP-Link RE200v1 device support a few months ago. Currently, the snapshot builds are broken - they started to break about 4 weeks ago. The system does not even boot, the last output on serial is "Starting kernel ..." from U-Boot. The initram

Re: ramips: Strange boot failures on TP-Link RE200v1

On 08/12/20 19:42, Andreas Böhler wrote: On 08/12/2020 00:53, Alberto Bursi wrote: On 08/12/20 00:12, Andreas Böhler wrote: I added TP-Link RE200v1 device support a few months ago. Currently, the snapshot builds are broken - they started to break about 4 weeks ago. The system does not even

Re: ipsec broken

On 27/12/20 16:49, Mao Mei wrote: It seems that ipsec has been broken for a long time. see https://forum.openwrt.org/t/ipsec-has-been-broken-for-a-while/81120 log on mt7621: 12[CFG] selected proposal: ESP:AES_CBC_128/HMAC_SHA1_96/NO_EXT_SEQ 12[KNL] got SPI cecfbd68 12[KNL] adding SAD entry w

Re: ipsec broken

On 28/12/20 11:43, Mao Mei wrote: that package is maintained in the community feeds, please open an issue https://github.com/openwrt/packages/issues and use "@stintel" in the maintainer field to ping the maintainer Thanks for reply, but I think it's not strongswan issue, but a kernel issue.

Re: [PATCH v2] x86/patches-5.4: enable DCDE for x86(-64)

On 05/01/21 01:09, Rui Salvaterra wrote: Port and adapt Nick Piggin's original patch [1]. This enables dead code and data elimination at linking time (gc-sections) on x86(-64). openwrt-x86-64-generic-kernel.bin size, with my config: Before: 3138048 bytes After: 2937344 bytes In other words

Re: [PATCH] base-files: sysupgrade: store status of system-services

On 09/01/21 12:56, Reiner Karlsberg wrote: Am 09.01.2021 um 13:28 schrieb Stijn Segers: > Currently all services get enabled during image creation. This can cause > issues after upgrade with services explicitly disabled by the user. > With this created list sourced by a simple uci-defaults

Re: [PATCH] base-files: sysupgrade: store status of system-services

On 09/01/21 12:28, Stijn Segers wrote: Hi, Op zondag 3 januari 2021 om 23u14 schreef Sven Roederer : When saving the list of installed pkgs, also store the status of the system services. The list is created in the etc/backup folder also and formated as: /etc/init.d/ {enable|disable} This w

Re: [PATCH] base-files: sysupgrade: store status of system-services

On 10/01/21 08:26, Reiner Karlsberg wrote: Am 10.01.2021 um 03:32 schrieb Alberto Bursi: > > > On 09/01/21 12:56, Reiner Karlsberg wrote: >> Am 09.01.2021 um 13:28 schrieb Stijn Segers: >> >>  > Currently all services get enabled during image creation.

Re: [PATCH] base-files: sysupgrade: store status of system-services

On 10/01/21 22:50, Stijn Segers wrote: Hi Sven, Op zondag 10 januari 2021 om 22u28 schreef Sven Roederer : Am Samstag, 9. Januar 2021, 12:28:31 CET schrieb Stijn Segers:  > @@ -228,6 +229,7 @@ do_save_conffiles() {  >  > if [ "$SAVE_INSTALLED_PKGS" -eq 1 ]; then  > echo "${INSTALLED_PACKAGE

Re: [PATCH] base-files: sysupgrade: store status of system-services

On 10/01/21 22:40, Sven Roederer wrote: Am Sonntag, 10. Januar 2021, 09:47:27 CET schrieb Andre Heider: Same. I would personally like this as default sysupgrade procedure, as that's what makes most sense imho. If I have disabled a service it makes sense that after a firmware upgrade it remain

Re:

On 09/01/21 03:54, Gagan Sidhu via openwrt-devel wrote: The sender domain has a DMARC Reject/Quarantine policy which disallows sending mailing list messages using the original "From" header. To mitigate this problem, the original message has been wrapped hi, using the latest stuff from you

Re: SELinux status report and call to action

On 12/01/21 18:27, Dominick Grift wrote: - My question to the reader is: why haven't you enabled SELinux yet on your test builds at least? Or maybe you have but you havent given any feedback. Why is that? Thanks, Lack of documentation. Selinux is not an easy topic eve

Re: [PATCH 1/2] owipcalc: remove package

I think you are ovverreacting a bit, package feeds are still part of OpenWrt project and jow has commit access there as well. Anyobody that needs that tool can still take it from there. Actually moving it to Packages allows other downstream projects like Entware-ng (that is using OpenWrt Package

Re: Job board support on openwrt.org?

On 22/01/21 19:23, Philip Prindeville wrote: Hi, Is anyone interested in adding a page to the openwrt.org site about developers willing to do commercial work? It could be as simple as: * name * email address * mobile (if wanted) * packages/platforms/architectures you maintain or have compe

Re: OpenWrt 19.07.6 service release

On 22/01/21 19:53, Philip Prindeville wrote: As an alternative to dnsmasq, master now has isc-dhcp (v4 only) and Bind integration, so that's getting close to the essential functionality that dnsmasq provides. I stopped using dnsmasq about 8 years ago because it has several minor violations

Re: Job board support on openwrt.org?

On 22/01/21 20:03, Daniel Golle wrote: Hi Philip, On Fri, Jan 22, 2021 at 11:23:42AM -0700, Philip Prindeville wrote: Hi, Is anyone interested in adding a page to the openwrt.org site about developers willing to do commercial work? It could be as simple as: * name * email address * mobil

Re: Job board support on openwrt.org?

On 23/01/21 09:49, Paul Spooren wrote: On Sa, Jan 23, 2021 at 07:25, Alberto Bursi wrote: On 22/01/21 20:03, Daniel Golle wrote: Hi Philip, On Fri, Jan 22, 2021 at 11:23:42AM -0700, Philip Prindeville wrote: Hi, Is anyone interested in adding a page to the openwrt.org site about

Re: Compile and install OBS Studio in openwrt.

On 09/02/21 11:45, Hongyi Zhao wrote: Hi, Is it possible for me to compile and install OBS Studio in openwrt, so that I can use it as a media server? Any hints will be highly appreciated. Regards OBS Studio is an application to record or stream your own screen, not a media server. Mayb

Re: [PATCH v2] openpgm: Add Pragmatic General Multicast library

On 09/02/21 04:20, Ye Holmes wrote: openpgm: Add Pragmatic General Multicast library Signed-off-by: Ye Holmes --- Sorry for the late reply; I found the messages in the "Junk" section from my thunderbird email client, my bad, :) On Sun, 7 Feb 2021 21:31:45 +, Paul Spooren wrote: Can't t

Re: Compile and install OBS Studio in openwrt.

On 09/02/21 16:41, Tom Psyborg wrote: On 09/02/2021, Alberto Bursi wrote: On 09/02/21 11:45, Hongyi Zhao wrote: Hi, Is it possible for me to compile and install OBS Studio in openwrt, so that I can use it as a media server? Any hints will be highly appreciated. Regards OBS Studio

Re: [PATCH] x86/64: Add CONFIG_DEVMEM=y for targets/x86/64

On 09/02/21 17:46, Supriya Mane wrote: Setting 'CONFIG_DEVMEM=y' provides access to /dev/mem. Fixes "cannot access '/dev/mem' : No such file or directory" Signed-off-by: Supriya Mane --- target/linux/x86/64/config-5.4 | 1 + 1 file changed, 1 insertion(+) diff --git a/target/linux/x86/64

Re: OpenWrt 21.02 planning

On 11/02/21 23:57, Hauke Mehrtens wrote: Hi, Any objections to this plan? Hauke could someone merge the PR that adds support to Amazon T3 instances in x86-64 target? all feedback was addressed and it was also tested. It would be nice to get it into next stable. https://github.com/openwrt

Re: Host dependencies and checking them

On 20/02/21 23:52, Bas Mevissen wrote: Hi all, When starting a clean build (21.02 branch) on a clean Fedora 33 machine, I ran into the small issue of tools/autoconf failing to build. This was due to perl-File-Compare missing. I apparently missed that prerequisite. After installing said pa

Re: Curiosity about FRITZ!BOX 7530 porting

On 25/02/21 20:06, Enrico Mioso wrote: Hello all!! I have some curiosity about FRITZ!BOX 7530 workings: 1 - Why does wi-fi seem to not work correctly when booting the device over initramfs when installing openwrt, but working fine when booting from flash? maybe the initramfs version is n

Re: Unnecessary extension of default packeges for x86 generic

On 01/03/21 11:40, Florian Eckert wrote: Hello, Is it really necessary that we keep expanding the default package here [1]? The problem is, for example, that I don't need the whole AWS stuff. But now the whole package gets installed. If this is the case, then we should also install the vmware

Re: Unnecessary extension of default packeges for x86 generic

On 02/03/21 08:27, Florian Eckert wrote: Hello Alberto, Thank you for the explanation. If that is so then we should also remove the vmware driver as a kmod package [1]. That makes no sense if this is then already in the kernel enabled [2]. Kind Regards Florian [1] https://github.com/ope

Re: [PATCH 0/4] import libcap from packages feed

On 12/03/21 11:01, Stijn Tintel wrote: On 12/03/2021 10:50, Petr Štetiar wrote: Stijn Tintel [2021-03-12 01:25:24]: Also, I don't agree that any optional package should be moved to the packages feed. The packages feed is a mess, often PR's are accepted without maintainer approval, sometim

compiling only packages that have patented functionality

I'm investigating about making an unofficial third party repository with OpenWrt (non-kmod) packages where patented functionality is enabled. For example ffmpeg from packages is missing some functionality in its "non-patented" form and most end users won't be able to just recompile from sources

crowdfunding to create Right to Repair laws in the USA

A few days ago, Louis Rossmann, a relatively famous person in the electronics repair community has started a fundraiser to get the Right to Repair movement's goals passed into law though a "direct ballot initiative" in the USA. It's a way to create a law that is bypassing politicians and askin

Re: crowdfunding to create Right to Repair laws in the USA

rom 2021 and it will go through further evolution steps. On 03/04/2021, 22:40, "openwrt-devel on behalf of Alberto Bursi" wrote: A few days ago, Louis Rossmann, a relatively famous person in the electronics repair community has started a fundraiser to get the Ri

Re: [OpenWrt-Devel] Feedback problem

On 27/02/19 15:04, Buddy wrote: Engineer:           I am installed openwrt firmware 18.06.2 in Linksys WRT1900AC .           Installed AdBlock,but could not to add more rule resource.           For blocked more ADs , changed hosts to a big one that over 150MB,so the changes is spend 60% Memory,

Re: [OpenWrt-Devel] Trunk tl wdr4900 v1 boot fails on bootloader CRC check

On 10/03/19 21:32, Sami Olmari via openwrt-devel wrote: Okay it wasn't https://github.com/openwrt/openwrt/commit/576c69938bb38c7edfa23f220eb30cb5c1d0a726 nor the immediately next one https://github.com/openwrt/openwrt/commit/0fbd3d23aadee0d95beef4f077a866dae7f4841a so it's still unclear what

Re: [OpenWrt-Devel] Trunk tl wdr4900 v1 boot fails on bootloader CRC check

On 10/03/19 22:33, Sami Olmari wrote: On Sun, Mar 10, 2019 at 4:20 PM Alberto Bursi mailto:bobafetthotm...@gmail.com>> wrote: On 10/03/19 21:32, Sami Olmari via openwrt-devel wrote: > Okay it wasn't > https://github.com/openw

Re: [OpenWrt-Devel] [PATCH] x86: disable kmod-drm-radeon and kmod-drm-amdgpu for geode

On 08/04/19 11:42, Petr Štetiar wrote: Tomasz Maciej Nowak [2019-04-07 18:35:01]: Hi, thanks for trying to unbreak currently failing Geode builds. Building images for geode has been failing because of missing dependencies: backlight.ko drm_kms_helper.ko fb.ko ttm.ko Being geode a speciffic

Re: [OpenWrt-Devel] mtd: sysupgrade: Is `mtd write` Correct for NAND-Based Devices?

On 09/04/19 20:44, Jeff Kletsky wrote: In going through code used by a port of an IPQ4019 device, I see that target/linux/ipq40xx/base-files/lib/upgrade/linksys.sh in platform_do_upgrade_linksys() writes the image using get_image "$1" | mtd write - $part_label This surprises me as I had t

Re: [OpenWrt-Devel] [PATCH] ar71xx: add support for GL.iNet GL-X1200

On 11/04/19 09:53, wellnw wrote: This patch adds supports for GL-X1200. Specification: - SOC: QCA9563 (775MHz) - Flash: 16 MiB (W25Q128FVSG) - RAM: 128 MiB DDR2 - Ethernet: 4x 1Gbps LAN + 1x 1Gbps WAN - Wireless: QCA9563(2.4GHz) and QCA9886(5GHz)

Re: [OpenWrt-Devel] RFC: add metadata to buildroot

On 14/05/19 16:49, Petr Štetiar wrote: [adding Thomas and Alberto to the Cc loop] Paul Spooren [2019-05-04 17:48:03]: Hi, from my point of view the current OpenWrt device documentation lacks some unity, meaning the table of hardware is partly incomplete or inconsistent. Also documentations

Re: [OpenWrt-Devel] Documentation in the tree? [Was: Re: [PATCH v3] gemini: Support sysupgrade on DIR-685]

On 21/05/19 11:13, Petr Štetiar wrote: Linus Walleij [2019-05-20 23:48:41]: [adding Alberto, Thomas and Javier to the Cc: loop] how you want the sysupgrade to work. it's just preferred to share as much common code as possible. Maybe we could open a documentation page for new devices, like

Re: [OpenWrt-Devel] [PATCH v3] gemini: Support sysupgrade on DIR-685

On 20/05/19 23:48, Linus Walleij wrote: On Mon, May 20, 2019 at 10:56 PM Petr Štetiar wrote: And merged[1] it into my staging tree, so please check it and let me know if it's ok with you or if you prefer to go with v4, thanks. Thanks man, sorry if I'm a bit confused around how you want the s

Re: [OpenWrt-Devel] Documentation in the tree? [Was: Re: [PATCH v3] gemini: Support sysupgrade on DIR-685]

On 21/05/19 12:11, Petr Štetiar wrote: Alberto Bursi [2019-05-21 11:37:31]: The only clear thing is that documentation does not write itself and that you can't rely on users to write developer documentation. You actually can enforce it somehow, as you either include/update documentati

Re: [OpenWrt-Devel] [PATCH v3] gemini: Support sysupgrade on DIR-685

On 21/05/19 13:10, Petr Štetiar wrote: Alberto Bursi [2019-05-21 11:44:37]: On 20/05/19 23:48, Linus Walleij wrote: On Mon, May 20, 2019 at 10:56 PM Petr Štetiar wrote: I can start while I still have it in fresh memory and you can chime in on how you want people to do generic checksum etc

Re: [OpenWrt-Devel] Netgear DM200 Boot Issue/Patch Availability?

Last attempt I saw was here https://github.com/openwrt/openwrt/pull/1770 but it was rejected. I have some experience with the bootloader used in this device, I can provide more complete instructions to do the uboot fix though. TTL/serial access seems to be easy (there is a header as you see

[OpenWrt-Devel] EFI images for x86

On Github there is a PR about adding EFI image generation to the x86 target, but it has not been picked by anyone for a while. This is an important feature, can anyone look into merging it https://github.com/openwrt/openwrt/pull/1968 -Alberto ___

Re: [OpenWrt-Devel] Netgear DM200 Boot Issue/Patch Availability?

the situation to me. I'll get hold of an Arduino and give this a shot. All the best, Chris On Tue, May 28, 2019 at 4:52 PM Alberto Bursi mailto:bobafetthotm...@gmail.com>> wrote: Last attempt I saw was here https://github.com/openwrt/openwrt/pull/1770 but it was re

Re: [OpenWrt-Devel] EFI images for x86

, I can test it on my Gigabit connection. On Sun, Jun 2, 2019 at 7:59 AM Alberto Bursi mailto:bobafetthotm...@gmail.com>> wrote: On Github there is a PR about adding EFI image generation I'm not sure about what you mean with "is built from LEDE". I built test images

Re: [OpenWrt-Devel] [PATCH 1/2] base-files: make USE_PROCD=1 default

On 02/08/19 18:18, Kevin 'ldir' Darbyshire-Bryant wrote: On 2 Aug 2019, at 16:00, Hannu Nyman wrote: Hauke Mehrtens kirjoitti 2.8.2019 klo 17.42: On 7/23/19 3:37 PM, Petr Štetiar wrote: Transition period for init script migration was long enough, let's make USE_PROCD=1 default now so there

Re: [OpenWrt-Devel] Has OpenWrt suport for Powerline devices

On 11/08/19 02:08, Joan Moreau via openwrt-devel wrote: >The Powerline system needs a "Lan name" in order to synchronize teh devices. >How this is translated in OpenWrt ? RE450 is not a powerline. Only supported device is *https://openwrt.org/toh/hwdata/tp-link/tp-link_tl-wpa8630* and it

Re: [OpenWrt-Devel] Did they check security of OpenWrt?

On 20/08/19 17:34, Rich Brown wrote: Hi Vincent, I don't know whether the article, or its underlying report from Cyber Independent Testing Lab - CITL, is a joke or not. (Although, I'll agree that any firmware using 18-year old kernels is on its face a security joke.) My questions were more

Re: [OpenWrt-Devel] Did they check security of OpenWrt?

On 20/08/19 23:19, Rich Brown wrote: Dmitry, On Aug 20, 2019, at 11:58 AM, Dmitry Tunin wrote: Rich, OpenWrt is a Linux distro. It has all security as any other one. All CVE are timely addressed. There is no need for special tests. Yes, but... Virtually all the other vendor's firmware are

Re: [OpenWrt-Devel] Did they check security of OpenWrt?

On 21/08/19 00:24, Rich Brown wrote: On Aug 20, 2019, at 5:32 PM, Rosen Penev > wrote: ... Issues are more nuanced than this though. These same people several months ago mentioned a serious ASLR weakness with MIPS. Patches went in the kernel for it. Does this mean th

Re: [OpenWrt-Devel] Arduino support no ttyUSB0 no ttyACM0 :((

On 31/07/2018 10:02, free...@tango.lu wrote: Hello List, I have got a new WRT 1200 AC running LEDE: https://downloads.openwrt.org/releases/17.01.4/targets/mvebu/generic/ Sadly noticed that the ttyUSB ttyACM support is missing. Is there an alternate kernel which has these? If someone precom

Re: [OpenWrt-Devel] [PATCH] base-files: make wifi report unknown command

On 06/08/2018 07:20, John Crispin wrote: On 03/08/18 18:18, Thibaut VARÈNE wrote: Avoid having /sbin/wifi silently ignore unknown keywords and execute "enable"; instead display the help message and exit with an error. Signed-off-by: Thibaut VARÈNE ---   package/base-files/files/sbin/wifi |

Re: [OpenWrt-Devel] Desire to add a documentation section

On 06/08/2018 22:07, Dave Turvene - Work wrote: Greetings - I cleaned up the documentation in https://openwrt.org/docs/guide-user/base-system/log.essentials as a prelude to adding a section on iptable logging rules.  The wiki source just has the following snippet: "pagequery>@:docs:guide-use

Re: [OpenWrt-Devel] Firewall Documentation

On 09/08/2018 16:55, Dave Turvene - Work wrote: On 06/08/2018 22:07, Dave Turvene - Work wrote: Greetings - I cleaned up the documentation in https://openwrt.org/docs/guide-user/base-system/log.essentials as a prelude to adding a section on iptable logging rules.  The wiki source just has t

Re: [OpenWrt-Devel] Firewall Documentation

On 10/08/2018 16:39, Dave Turvene - Work wrote: On 09/08/2018, Alberto Busi wrote: Yeah I saw that. Wiki maintainers are notified of each edit in the wiki. Looks good, follows wiki guidelines. I cannot say how good it actually is, as I don't know much about manual firewall usage. That said, m

Re: [OpenWrt-Devel] Use DHCP by default on single port devices

On 8/27/2018 12:37 PM, Daniel Engberg wrote: As per request, Fine as long as we fix mdns in some way? https://github.com/openwrt/openwrt/pull/1062 Not subscribed, so CC Best regards, Daniel Engberg ___ openwrt-devel mailing list openwrt-devel@lis

Re: [OpenWrt-Devel] watchdog against router crash freezes?

On 27/08/2018 18:52, Marcel Partap wrote: […] https://openwrt.org/docs/guide-developer/ubus/system has watchdog information Well, I was hoping for a watchdog daemon packaged in the repo to easily solve my issue.. I already set up a timer switch to cut electricity to both cable modem and ro

Re: [OpenWrt-Devel] Package Bzip2 download URL no longer valid

On 29/10/2018 08:58, Xabier Oneca -- xOneca wrote: Hello, Please, note that Bzip2 no longer sources available for download on bzip.org (there's a LWN thread about this: https://lwn.net/Articles/762264/), but OpenWrt still points to that server. The Bzip2 package was patched in buildroot: htt

Re: [OpenWrt-Devel] Custom cases for Netgear r7800?

On 02/11/18 21:20, Ben Greear wrote: This is a bit off topic, but I'm curious if anyone has developed or knows of someone selling customized cases for the Netgear r7800 (or similar AP with similar radios and 128+MB of storage and 512+MB of RAM). In particular, I'd like to get access to the s

Re: [OpenWrt-Devel] OpenWrt Roadmap

On 12/11/18 21:20, Luiz Angelo Daros de Luca wrote: Hello, There are a significant amount of devices out there that has 4/32 specs. Even brand new ones. If there is stability issues with newer OpenWrt versions on those devices, we should rethink LEDE EOL. Maintenance burden is directly relate

Re: [OpenWrt-Devel] OpenWrt Roadmap

On 12/11/18 21:57, Fernando Frediani wrote: Totally agree with Luiz. That was the idea behind this proposal and you managed to even easier words. Alberto, the tiny subtarget you mentioned doesn't really seem to run well or stably for 18.06 on many of these devices regardless the flash size,

Re: [OpenWrt-Devel] OpenWrt Roadmap

On 12/11/18 21:40, John Clark wrote: We are talking of embedded hardware, stuff that can be replaced with future-proof hardware (4+ years) for 20-30$ in most cases. I don't think it is worth the manpower required to have any real attempt at a LTS (i.e. backporting security fixes). I supp

[OpenWrt-Devel] Does anyone use kmod-trelay? Is it better than relayd?

It should be a "a trivial ethernet relay which allows pseudo-bridging ad-hoc or client mode devices over vlans to other host" according to the commit message https://github.com/openwrt/openwrt/commit/c3bba7f8c61ee98265bcffef8ee86e22aa89bbe9 and the description is --- trelay relays ethern

Re: [OpenWrt-Devel] [RFC] stop accepting 4/32M board patches

On 05/12/2018 15:08, Carlos Ferreira wrote: I still have a bunch of Old Foneras and some TP-Link 703N and TL-MR11U battery powered micro-routers. The foneras are kinda useless, but the TP-Links are somewhat usefull and I still use them with OpenWRT. What other inexpensive routers would you sug

Re: [OpenWrt-Devel] [PATCH] block: generate hotplug.d mount events

On 05/12/18 22:35, Rafał Miłecki wrote: From: Rafał Miłecki This is what was implemented in mountd and what some scripts used to use. It's a pretty generic solution for managing software that may use e.g. USB storage. Could you explain a bit more about what is this doing instead of just me

Re: [OpenWrt-Devel] [RFC] stop accepting 4/32M board patches

On 06/12/2018 23:51, Jo-Philipp Wich wrote: But even this may be not needed: For Tp-Link recently was released a mobile app Tether to control a router https://www.tp-link.com/us/tether/ This would imply both tying OpenWrt to a proprietary app and limiting its configuration to whatever settin

Re: [OpenWrt-Devel] [PATCH v2 6/7] ipq40xx: specify "firmware" partition format for GL.iNet GL-B1300

On 15/12/18 22:02, Christian Lamparter wrote: Specify firmware partition format by compatible string. Signed-off-by: Christian Lamparter --- .../files-4.14/arch/arm/boot/dts/qcom-ipq4029-gl-b1300.dts | 1 + 1 file changed, 1 insertion(+) diff --git a/target/linux/ipq40xx/files-4.14/

Re: [OpenWrt-Devel] [PATCH v2 6/7] ipq40xx: specify "firmware" partition format for GL.iNet GL-B1300

On 17/12/18 10:57, Petr Štetiar wrote: Alberto Bursi [2018-12-17 10:29:36]: Hi Alberto, firmware@18 { + compatible = "denx,fit"; label = "firmware"; reg = <0x18 0x1e8>

Re: [OpenWrt-Devel] [PATCH v2 6/7] ipq40xx: specify "firmware" partition format for GL.iNet GL-B1300

On 17/12/18 12:39, Christian Lamparter wrote: On Monday, December 17, 2018 10:31:51 AM CET Alberto Bursi wrote: On 15/12/18 22:02, Christian Lamparter wrote: Specify firmware partition format by compatible string. Signed-off-by: Christian Lamparter --- .../files-4.14/arch/arm/boot/dts

Re: [OpenWrt-Devel] [RFC] stop accepting 4/32M board patches

On 20/12/18 14:37, Tom Psyborg wrote: This is true. 32mb is misinterpretted as a limitation among several forum/wiki articles while storage space is being the only serious limitation. I have ar71xx running on 32M RAM device, basic configuration with luci-ssl and secondary wifi interface (ath9k_

Re: [OpenWrt-Devel] [RFC] stop accepting 4/32M board patches

On 20/12/18 20:46, James Feeney wrote: On 12/20/18 8:54 AM, Alberto Bursi wrote: So no, the 4/32 warning should stay and remain loud and clear so newbies won't be frustrated by low end devices. There also seems to be a presumption that a "newbie" is, or should be, running l

Re: [OpenWrt-Devel] [RFC] stop accepting 4/32M board patches

On 22/12/18 09:38, Dana Myers wrote: On 12/20/2018 7:54 AM, Alberto Bursi wrote: So no, the 4/32 warning should stay and remain loud and clear so newbies won't be frustrated by low end devices. Not sure what "newbie" means in this context. Though I suppose the warn

Re: [OpenWrt-Devel] lantiq: Netgear DM200 kernel too large

On 22/01/19 01:11, Thomas Nixon wrote: On 1/21/19, Bjørn Mork wrote: Paul Oranje writes: Op 20 jan. 2019, om 17:52 heeft Thomas Nixon het volgende geschreven: I could add a new subtarget like xrx200 but with small_flash enabled, but this seems a bit excessive for a single board. The DM200

Re: [OpenWrt-Devel] [PATCH] brcm2708: Tethering by default

On 19/05/2018 12:09, Christo Nedev wrote: Why? Pi Zero and Zero W have no LAN port! For W radio is disabled by default! Pi 3 b+ has no working WIFI! So it is handy to have tethering by defult and nightmer without! usb0 interface is used by USB-to-ethernet adapters or smartphone tethering

Re: [OpenWrt-Devel] [PATCH] brcm2708: Tethering by default

On 19/05/2018 17:38, Christo Nedev wrote: usb0 interface is used by USB-to-ethernet adapters or smartph one tethering , and they need drivers to work. Just adding the interface does not have any effect. Do you mean these drivers -> kmod-usb-net kmod-usb-net-cdc-ether kmod-usb-net-rndis?

Re: [OpenWrt-Devel] node.js

On 25/05/2018 15:39, Levente wrote: Hi all, There is a tutorial here: https://wiki.openwrt.org/doc/howto/nodejs on how to compile node.js into OpenWRT, but the that configuration item is missing from menuconfig. I checked the feed, and it is there in the build tree. There is a dependency f

Re: [OpenWrt-Devel] Moving the mailing lists

On 27/05/2018 03:56, Daniel F. Dickinson wrote: On 2018-05-26 05:17 AM, Bjørn Mork wrote: "Daniel F. Dickinson" writes: 1) How many people have their own mail server and can do *server-side* mail filtering You do not need your own mail server to do server-side filtering.  Any mail service

Re: [OpenWrt-Devel] FS#1567 reported: making openrwrt unusable (BT Home Hub 5) since between r6080 and r7050

On 28/05/2018 15:52, Mauro Mozzarelli wrote: Neither it is to post an arrogant reply which is the only type of reply I get usually from Jo-Philipp as this isn't the first time. You reap what you seed guys. Where you see arrogance in Jo-Philipp's mail? He is just stating facts, it's not e

Re: [OpenWrt-Devel] [PATCH] brcm2708: Update brcm2708-gpu-fw package

On 30/05/2018 06:36, John Crispin wrote: On 27/05/18 13:43, Christo Nedev wrote: Fix brcm2710 image boot issues. please describe the issues and how they are fixed.     John Signed-off-by: Christo Nedev --- Christo write something like: "Raspi 3 B and 3 B+ don't boot at all because t

Re: [OpenWrt-Devel] [PATCH] iproute2: update to 4.17.0

On 13/06/2018 09:00, Russell Senior wrote: Hans Dedecker writes: Hi, On Sun, Jun 10, 2018 at 11:54 PM Russell Senior wrote: Signed-off-by: Russell Senior --- I get the following compile issues if the rdma utility is enabled : I wonder if rdma is actually useful in openwrt. As far as I

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

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? 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 ro

Re: [OpenWrt-Devel] [PATCH] Add BlueZ Firmware package

On 20/06/2018 11:54, Matej Kupljen wrote: Hi all, the following patch adds a BlueZ Firmware support. It was tested on Raspberry PI Zero W board only, but I believe it should work also on other boards, since it is not board specific. Signed-off-by: Matej Kupljen --- Bluez package is in co

Re: [OpenWrt-Devel] openwrt-imagebuilder-18.06.0-rc1-ar71xx-generic.Linux-x86_64

On 26/06/2018 11:19, Mikael Bak wrote: Martin, Mathias, On 2018-06-25 16:04, Martin Tippmann wrote: On Mon, Jun 25, 2018 at 3:56 PM, Mikael Bak wrote: Build dependency: Please install GNU 'time' or BusyBox 'time' Prerequisite check failed. Use FORCE=1 to override. make[1]: *** [Makefile:

Re: [OpenWrt-Devel] [PATCH v2 1/2 netifd] system-linux: add 2.5 and 10G interface speed definitions

On 27/06/2018 23:14, j...@corp.connectbit.io wrote: From: Joe Holden Signed-off-by: Joe Holden --- system-linux.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/system-linux.c b/system-linux.c index 0127b01..1330ea1 100644 --- a/system-linux.c +++ b/system-linux.c @@ -1688,6 +1688

Re: [OpenWrt-Devel] Good suggestion for Openwrt router board with 2x mini pci-express

On 12/07/2018 16:27, David Johnson wrote: It seems its quite hard to find a board that is fully supported by openwrt that has 2x mini pci-express, 2x ethernet ports (WAN, LAN), > 64M flash I want to plug in ath10k supported 802.11ac mini pci-e radios Any thoughts suggestions Thanks David _

Re: [OpenWrt-Devel] Disclaimer for user documentation?

On 28/07/2018 13:59, Sebastian Kemper wrote: Hi all, I'm adding a page about FreeSWITCH to the OpenWrt user documentation. I would like to add a guide on setting up a configuration to use freeswitch with Ekiga, along the lines of a testing ground for people to use and play around with befo

Re: [OpenWrt-Devel] Disclaimer for user documentation?

On 29/07/2018 19:53, Sebastian Kemper wrote: On Sat, Jul 28, 2018 at 02:36:20PM +0200, Alberto Bursi wrote: In the meantime you can place any disclaimer you want in the warning box at the top of your article, and be covered by that. A good starting point is copy-pasting LineageOS's

  1   2   >