Re: [OpenWrt-Devel] openwrt based router

On 26/09/19 11:25, sagar jain wrote: Can I sell openwrt based router ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel If you meancreate and sell new routers using OpenWrt as f

Re: [OpenWrt-Devel] [PATCH v2 2/2] ath79: Restore GL.iNet GL-AR300M-Lite first-boot connectivity

On 28/09/19 19:39, Jeff Kletsky wrote: From: Jeff Kletsky The relationship between GMAC0 and GMAC1 and the kernel devices eth0 and eth1 was reversed for many ath79 devices by commit 8dde11d521 ath79: dts: drop "simple-mfd" for gmacs in SoC dtsi The GL-AR300M-Lite is a single-port device, wit

Re: [OpenWrt-Devel] [PATCH 1/8] ncurses: add cygwin compatibility

On 08/10/19 12:14, Paul Oranje wrote: Hi, Op 8 okt. 2019, om 03:02 heeft Rosen Penev het volgende geschreven: From: Alexey Loukianov * Properly handle ".exe" suffix for cygwin. Signed-off-by: Alexey Loukianov (bumped PKG_RELEASE) Signed-off-by: Rosen Penev Two questions: Is there any

Re: [OpenWrt-Devel] OpenWrt 19.07 release schedule ?

On 11/10/19 12:59, Jo-Philipp Wich wrote: Hi Bjørn, Or: Start discussing the release blockers here and now. Thanks. 1) Blocker: LuCI master needs to be backported to 19.07 Time estimate: 2-3 weeks 2) Blocker: All relevant sub-components for WPA-3 + GUI support, such as hostapd, iwinfo etc. n

[OpenWrt-Devel] script hook for odhcpd

I'm adding hotplug.d support to all DHCP events. For now only dnsmasq triggers them, with openwrt/package/network/services/dnsmasq/files/dhcp-script.sh DHCP clients like udcpc and udcp6c are easy to add as the client calls a script hook with documented arguments and environment variables I can pa

Re: [OpenWrt-Devel] script hook for odhcpd

On 10/11/19 03:41, Hans Dedecker wrote: On Sat, Nov 9, 2019 at 2:43 AM Alberto Bursi wrote: I'm adding hotplug.d support to all DHCP events. For now only dnsmasq triggers them, with openwrt/package/network/services/dnsmasq/files/dhcp-script.sh DHCP clients like udcpc and udcp6c are ea

Re: [OpenWrt-Devel] Silence on the DEV list and what about 19.07 RC1 and 18.06.5

On 16/11/19 21:14, Paul Oranje wrote: l.s. Lately no new messages have arrived on the DEV list, which is further more remarkable since we have two releases and no word about these on the list. What is the matter ? (this mail message also poses as a test). Regards, Paul _

Re: [OpenWrt-Devel] [PATCH] wireless-regdb: Make it build with python2

On 18/11/19 08:42, Etienne Champetier wrote: Hi Hauke, Le dim. 17 nov. 2019 à 15:00, Hauke Mehrtens a écrit : This backports a patch to build it work with python2 in addition to python3. Why not make the scripts "/usr/bin/env python3" and require python 3 in 19.07 ? (I'm stuborn but I don't

Re: [OpenWrt-Devel] Running k3s on OpenWrt

On 28/11/19 22:02, Paul Spooren wrote: I know nothing about sunix, but the other three targets appear mostly space "indipendent". Sunxi target is basically a bunch of Raspberry Pi clones using different SoC. You usually have a SDcard to store the OS image. -Alberto _

Re: [OpenWrt-Devel] The meaning of Signed-off-by for netifd [Was: Re: [PATCH netifd] interface: warn if ip6hint is truncated]

On 03/12/19 15:59, Uwe Kleine-König wrote: Hello Hans, On 12/3/19 8:50 AM, Hans Dedecker wrote: On Fri, Nov 29, 2019 at 9:29 PM Uwe Kleine-König wrote: On 11/29/19 8:50 PM, Hans Dedecker wrote: On Wed, Nov 20, 2019 at 7:11 PM Uwe Kleine-König wrote: When for example a /60 is assigned t

Re: [OpenWrt-Devel] Requesting a custom firmware for a router

On 11/12/19 07:17, John Wick wrote: Kind request to upload the custom firmware for router model TP-LINK TD-W8951ND v5.0 if possible OpenWrt for that device is impossible. Device is using unsupported CPU (Ralink RT63365E) has 8MB RAM (which is less than half of the minimum required) and 2M

Re: [OpenWrt-Devel] Inquery

On 11/12/19 18:54, Daniel Golle wrote: On Wed, Dec 11, 2019 at 05:37:26PM +0100, WRT Burner wrote: On 11/12/2019 15:22, Daniel Golle wrote: And it's even needless to say that replying to a spam email in which ever way will always make it worse. +1. There is no constructive value in replyin

Re: [OpenWrt-Devel] [PATCH] kernel: ath10k-ct: provide a build variant for small RAM devices

On 15/12/19 14:09, Christian Lamparter wrote: But it seems that Ben had a change of heart in this regard. I don't know the details or why, But it makes sense because it would enable his company to save some money for the systems his company sells:

Re: [OpenWrt-Devel] [PATCH] kernel: ath10k-ct: provide a build variant for small RAM devices

On 16/12/19 21:04, Christian Lamparter wrote: Hello, On Mon, Dec 16, 2019 at 12:27 PM Alberto Bursi wrote: On 15/12/19 14:09, Christian Lamparter wrote: But it seems that Ben had a change of heart in this regard. I don't know the details or why, But it makes sense because it

Re: [OpenWrt-Devel] Problem with blockd starting after partitions mounting

On 29/12/19 15:35, Rafał Miłecki wrote: A year ago I introduced hotplug.d script meant to manage Samba shares in a clever way by: 1) Using "mount" hotplug.d event 2) Getting mount info from blockd Relevant commit ef1efa756e0d ("samba36: add package with hotplug.d script for auto sharing"): htt

Re: [OpenWrt-Devel] Preserving configs over sysupgrade on ath79/tiny broken for some boards (on 19.07 and master), possible solutions

On 31/12/19 16:29, Paul Fertser wrote: Hello David, On Tue, Dec 31, 2019 at 04:20:29PM +0100, David Bauer wrote: If no users speak up probably it's better to remove all the support code altogether to avoid wasting maintainers' time on it? The code is not really an issue, as there's not muc

Re: [OpenWrt-Devel] Preserving configs over sysupgrade on ath79/tiny broken for some boards (on 19.07 and master), possible solutions

On 01/01/20 15:02, Petr Štetiar wrote: Alberto Bursi [2020-01-01 03:30:34]: Hi, A LOT of OpenWrt userbase does not follow the mailing lists (or even know what a mailing list is), so if you want to have the full picture please visit the forum as well. users dont know/use mailing lists

Re: [OpenWrt-Devel] time for OJ 1.15 everyone?

On 06/01/20 13:58, edgar.sol...@web.de wrote: new year, new OJ. start of the year is OJ release time traditionally by now. are we in agreement? a snappy new NY to one and all ..ede ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org htt

Re: [OpenWrt-Devel] ToH dump missing HW version

On 10/01/20 21:40, Luiz Angelo Daros de Luca wrote: Hello, I was using https://openwrt.org/_media/toh_dump_tab_separated_csv.zip from https://openwrt.org/supported_devices and it is missing the hardware version. It is also missing the "unsupported features". Both are quite important for sel

Re: [OpenWrt-Devel] Releases [Was: Re: OpenWrt 20.X release plans]

On 20/01/20 10:01, Petr Štetiar wrote: Hauke Mehrtens [2020-01-19 18:17:10]: Hi, Does someone else other than jow know how to setup built bot for a new branch? Is this documented somewhere? It should be documented and at least 3 persons should be able (and willing) to do that. There is d

Re: [PATCH] build: prereq: drop support for Python 3.5

On 18/04/21 20:51, Etienne Champetier wrote: Le sam. 17 avr. 2021 à 17:47, Sven Roederer a écrit : Am Samstag, 17. April 2021, 16:45:01 CEST schrieb Sven Roederer: On my Ubuntu 16.04 based build-system I also have build-failures for meson using Python3.5. Correction: it's a 18.04 LTS ...

Re: Brokenness of the OpenWrt "packages" repo (was: Re: [PATCH] Revert "dbus: update to 1.13.18")

On 25/04/21 15:51, Bjørn Mork wrote: Rosen Penev writes: Why was this sent here? dbus is in the packages feed. Sorry, I assumed that was obvious. I'll explain There is a continous push to move packages from the OpenWrt core repo to the "packages" repo. This would have been fine if both t

Re: Brokenness of the OpenWrt "packages" repo

On 26/04/21 07:51, Bjørn Mork wrote: Etienne Champetier writes: Are you trying at the same time to complain about not run-tested updates and possibly having packages not up to date ? No. The package was fine before the version was changed. In fact, it was in much better shape before it w

Re: Brokenness of the OpenWrt "packages" repo

On 26/04/21 16:01, Daniel Golle wrote: On Mon, Apr 26, 2021 at 03:28:22PM +0200, Enrico Mioso wrote: ... I know you won't like this. But in the end, I guess D-Bus, glib2 and in the end all of MM dependencies will have to be incorporated in the core. A stac, of big big software, I know. But s

Re: Activate https server support in 21.02 by default

On 14/05/21 10:58, Petr Štetiar wrote: Fernando Frediani [2021-05-11 20:13:18]: Hi, I am no sure https support should still be something by default in the images as it's not something really essential to me it's like discussion about telnet versus SSH. (Puting aside, that one shouldn't be

Re: Activate https server support in 21.02 by default

> On 15/05/21 22:13, Fernando Frediani wrote: On 15/05/2021 16:59, Alberto Bursi wrote: I'm personally in the "encrypt all the things" camp. I fully support a switch to https only. But it should be a default, not a "let's add stuff people might want to ena

Re: Resize of ath79 / ZyXEL NBG6716 kernel partition

On 20/05/21 10:18, Andre Valentin wrote: Hi! The NBG6716 has recently been disabled because of size problems with the kernel partition. I'm thinking about extending it to 8MB, shouldn't be a problem. But I'm afraid users will brick their device when doing a sysupgrade to the new flash lay

Re: Flagship AX routers

On 26/05/21 10:56, Bjørn Mork wrote: Daniel Golle writes: When using as dual-band AP, also the Gigabit Ethernet of the E8450 can become a bottle-kneck, UniFi 6 LR got that Aquantina 2.5GBase-T PHY But there is no driver for that yet, right? And for those of us who aren't familiar with the

Re: openwrt developer / paid work

did you actually give them the result of the work before seeing payment or getting some form of legal contract? On 01/06/21 22:45, Philip Prindeville wrote: This was advertised as "paid work". I'm still waiting to be paid. On Apr 1, 2021, at 5:52 AM, Embedded Devel wrote: need someone t

Re: openwrt developer / paid work

oh no they had a "previous developer" that also fled the scene before completing the work. Gee I wonder why. On 02/06/21 05:41, Philip Prindeville wrote: On Jun 1, 2021, at 5:27 PM, Embedded Devel wrote: On 6/2/21 3:45 AM, Philip Prindeville wrote: This was advertised as "paid work". I

Re: Error compiling master on WSL2 Ubuntu 20.04

Re: Error compiling master on WSL2 Ubuntu 20.04

On 08/06/21 01:11, Bas Mevissen via openwrt-devel wrote: Thanks for the link. I wasn't aware of the existence of such a page. I don't really like the proposed solution. The problem is not the fact that they are Windows directories, but that they contain spaces. A better way would be to cal

Re: [PATCH] package/comgt: Handle bind/unbind events

On 19/06/21 01:44, Arjun AK wrote: On 08/05/21 5:38 am, Arjun AK wrote: On 06/01/21 9:03 pm, Arjun AK wrote: On 16/07/20 9:22 pm, Arjun AK wrote: This script was expecting only add/remove events which has not been the case since Kernel 4.12 (which added bind/unbind). Bind events were gettin

Re: [PATCH] package/comgt: Handle bind/unbind events

On 23/06/21 19:16, Arjun AK wrote: On 22/06/21 2:07 am, Alberto Bursi wrote: On 19/06/21 01:44, Arjun AK wrote: On 08/05/21 5:38 am, Arjun AK wrote: On 06/01/21 9:03 pm, Arjun AK wrote: On 16/07/20 9:22 pm, Arjun AK wrote: This script was expecting only add/remove events which has not

Re: [PATCH] comgt: Move to community packages repo

On 28/06/21 22:51, Lech Perczak wrote: W dniu 2021-06-28 o 21:55, Paul Spooren pisze: On 6/28/21 9:53 AM, John Crispin wrote: On 28.06.21 21:14, Paul Spooren wrote: I'm in favor of this too but if it's a core feature (i.e. SIM card support) we should provide the package by default to, not?

Re: Enabling Wi-Fi on First boot

On 06/07/21 09:12, Enrico Mioso wrote: On Mon, 5 Jul 2021, Paul Spooren wrote: Date: Tue, 6 Jul 2021 09:06:14 From: Paul Spooren To: Enrico Mioso , openwrt-devel@lists.openwrt.org Subject: Re: Enabling Wi-Fi on First boot On 7/5/21 8:45 PM, Enrico Mioso wrote: Hello all!! I would lik

Re: Enabling Wi-Fi on First boot

On 06/07/21 16:26, Henrique de Moraes Holschuh wrote: However, it is *not* a simple matter to just "enable wireless" at first boot in OpenWrt (due to a "default password" issue), except maybe in a home-and-enthusiast setting.  You cannot just do it for a device (or firmware) you're going to

Re: Enabling Wi-Fi on First boot

On 06/07/21 19:01, Henrique de Moraes Holschuh wrote: What would work is to reuse the vendor-provided password that is already in the label and somewhere in FLASH, if you could always know where it is in FLASH (you don't).  And some models don't have it. That's a lot of work to get a ver

Re: Enabling Wi-Fi on First boot

On 06/07/21 21:06, Enrico Mioso wrote: Hello all!! What I was thinking actually was an option I could enable at build-time (kinda preinit option), at my own risk, when building images. From a technical standpoint, will an uci default work in all cases? Thanks a lot for your ideas guys.

Re: Enabling Wi-Fi on First boot

On 06/07/21 22:57, Michael Richardson wrote: Alberto Bursi wrote: > "unique" per-device passwords like most vendors are doing are low security > and relatively easy to brute force once someone has disassembled the firmware > and learned the algorithm us

Re: Enabling Wi-Fi on First boot

On 08/07/21 09:39, Petr Štetiar wrote: Paul Spooren [2021-07-07 15:10:59]: Hi, Feel free to check this out, it's not ready yet but should give an idea: https://github.com/openwrt/openwrt/pull/4349 More sophisticated setups are not supported this is merely used to allow are not supported

Re: Enabling Wi-Fi on First boot

On 08/07/21 11:09, Paul Spooren wrote: I'd argue that it merely completes the OEM options. If that isn't a valid argument we should drop all of VERSIONOPTs since it can be all modified via /files. Adding it as a package would be imho better because it would allow people to use image build

Re: X86_64 : 8 CPU limitation on Vanilla release

On 09/07/21 10:03, Brice GIBOUDEAU via openwrt-devel wrote: Hello, I'm reaching out to you about a limitation on the X86_64 target. We use this version to operate large scale Wireguard VPNs on VMs and physical servers (DELL & HP). The actual limitation of 8 CPU is the only reason why we h

Re: OpenWrt 21.02 status

On 19/07/21 21:11, Luiz Angelo Daros de Luca wrote: This is not a migration script but a mitigation. A 21.02 image should detect during boot if the current network config was for swconfig in a system using DSA. It could happen during early boot stages, after FS are mounted, before services ar

Re: [PATCH] base-files: add option to make /var persistent

On 06/08/21 21:27, Stijn Tintel wrote: In OpenWrt, /var is symlinked to /tmp by default. This is done to reduce the amount of writes to the flash chip, which often don't have the greatest durability. As a result, things like DHCP or UPnP lease files, are not persistent across reboots. Since O

Re: [PATCH] base-files: add option to make /var persistent

On 07/08/21 02:46, Stijn Tintel wrote: On 7/08/2021 02:56, Alberto Bursi wrote: On 06/08/21 21:27, Stijn Tintel wrote: In OpenWrt, /var is symlinked to /tmp by default. This is done to reduce the amount of writes to the flash chip, which often don't have the greatest durability.

Re: [PATCH] base-files: add option to make /var persistent

On 07/08/21 10:40, Stijn Tintel wrote: On 7/08/2021 10:05, Alberto Bursi wrote: On 07/08/21 02:46, Stijn Tintel wrote: On 7/08/2021 02:56, Alberto Bursi wrote: On 06/08/21 21:27, Stijn Tintel wrote: In OpenWrt, /var is symlinked to /tmp by default. This is done to reduce the amount

Re: [PATCH 6/6] qoriq: add support for WatchGuard Firebox M300

On 22/08/21 01:15, Stijn Tintel wrote: This device is based on NXP's QorIQ T2081QDS board, with a quad-core dual-threaded 1.5 GHz ppc64 CPU and 4GB ECC RAM. The board has 5 A few questions about this device hardware: is there anything in uboot or Linux that shows or even hints at the fact t

Re: [PATCH 6/6] qoriq: add support for WatchGuard Firebox M300

On 22/08/21 13:06, Stijn Tintel wrote: The T1042 CPU in the M200 is e5500, as opposed to the e6500 in the M300. As Rui already explained, the T1042 does not support AltiVec, which musl expects for all PPC64 CPUs. I was able to boot Linux on it after patching the vector instructions out of the

Re: [PATCH 6/6] qoriq: add support for WatchGuard Firebox M300

On 22/08/21 14:51, Stijn Tintel wrote: On 22/08/2021 14:35, Adrian Schmutzler wrote: + + port@5 { + status = "disabled"; + + reg = "<5>"; + label = "cpu1"; +

Re: initramfs for ACPI tables on x86

On 30/09/21 15:04, Daniel Golle wrote: On Thu, Sep 30, 2021 at 02:49:57PM +0200, Florian Eckert wrote: Since the update of kernel from 5.4 to 5.10 in the openwrt master branch [1], I have problems with additional hardware on the I2C (SMBus) of my APU3. The Linux upstream removed the platform

Re: Release goals for 22.XX - procd-seccomp and procd-ujail

On 07/10/21 08:51, Paul Spooren wrote: On 9/29/21 10:28, Hauke Mehrtens wrote: Hi, The OpenWrt 21.02 release is done and we should plan the next release. We already talked about this in the last meeting, see https://openwrt.org/meetings/20210920 To monitor the current state I created thi

Re: Error in Common Ubiquiti Procedures for XM AirMax devices?

On 08/11/21 02:04, Joe Ayers wrote: Openwrt Github commit notes, Forum posts, and Documentation, refer to: "The mtd partitions layout for XM-type devices changed from AirOS v5.5 to AirOS v5.6. Before installing OpenWrt, downgrade first to AirOS 5.5." reference: https://openwrt.org/toh/ubiqui

Re: [RFC] Stop providing binary package updates for release builds?

On 12/12/21 20:42, Jo-Philipp Wich wrote: - The wiki actively discourages users from upgrading packages [1] - The overall sentiment in the forum is to instruct users to not/never upgrade packages [2] but to always upgrade to the next release, build from source [3] or use snapshots

Re: Support for Google Onhub devices

On 12/01/22 18:52, Brian Norris wrote: For the OnHub, you could leverage the same partition formatting (OnHub is also running a similar Chrome OS bootloader), but you'd have to bring up a different SoC (OnHub uses ipq8064, while Google WiFi is ipq4019). OnHub also doesn't have as easy of seria

Re: Seperating firmware-utils into seperate repo

On 14/03/22 01:56, Joseph Mullally wrote: Hi, firmware-utils was separated from openwrt.git into its own repository a few months ago: https://git.openwrt.org/?p=project/firmware-utils.git https://github.com/openwrt/openwrt/commit/8cc9a74a3f6bf363645efda6db417f8dadd3d844 If it's going to stay

Re: Enabling Hotplug

On 19/07/22 08:56, Ravi Paluri (QUIC) wrote: Hi all, We are trying to enable Hotplug functionality. We've our device node under "/dev/", which gets created at boot-up. SUBSYSTEM of this is "subsys". Hence, I created a folder named "subsys" under "/etc/hotplug.d/" and I added a script at

Re: [OpenWrt-Devel] [PATCH] base-files: diag: restore default trigger for 'boot' LED

On 04/02/20 13:32, Adrian Schmutzler wrote: Hi, -Original Message- From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org] On Behalf Of Piotr Dymacz Sent: Freitag, 31. Januar 2020 15:23 To: openwrt-devel@lists.openwrt.org Subject: [OpenWrt-Devel] [PATCH] base-files: diag:

Re: [OpenWrt-Devel] mptcp in openwrt

On 05/02/20 08:51, André Valentin wrote: Hi! mptcp is only for the devices intiating and terminating the connection. All routers in between (maybe OpenWRT) do not care about this. The only way you could use mptcp on a router is with a proxy service running on it, which will do the mptcp stuff

Re: [OpenWrt-Devel] Protecting a vulnerable host behind an OpenWRt device

On 05/02/20 05:35, Enrico Mioso wrote: the LTE module runs old software and probably won't get updated as frequently. I would need a way to let the OpenWRt device continue to talk to it, but stop anything from the outside doing so. I did my attempt with the firewall and they seemed to work

Re: [OpenWrt-Devel] [PATCH] kirkwood: convert DTS patches into plain DTS files

On 27/02/20 06:16, Raylynn Knight 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 automatically by the mailing list sof

Re: [OpenWrt-Devel] [RFC] x86: use multiple profiles

On 16/04/20 01:16, Joel Wirāmu Pauling wrote: Related; would be nice to have a supported atomic update method (rollforward/back) and/or adapt sysupgrade/opkg to cope with full sys-upgrade style opperation. Fedora CoreOS and OSTree may be a possible inspiration point. Either way I am getti

Re: [OpenWrt-Devel] Port labels for DSA targets/devices

On 20/04/20 22:33, m...@adrianschmutzler.de wrote: Hi Martin, As for ath79, while many people agree that there should be a migration script/mechanism, it's hard to finally get one (since designing it is a much bigger problem than it seems at first hand). I fully agree that doing a migrat

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

On 21/04/20 07:15, Philip Prindeville wrote: 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 infrastr

Re: [OpenWrt-Devel] Upgrading LEDE to 19.07

On 25/04/20 19:46, Luca Bertoncello wrote: Hi list! I'm not sure, I'm asking to right list, but I didn't found any other list about OpenWRT I can ask... So, I have a "TP-Link TL-WR1043ND v1" running OpenWRT 17.01.4. I'd like to update it to 19.07, but I read on https://openwrt.org/toh/hwdata

Re: [OpenWrt-Devel] Upgrading LEDE to 19.07

On 25/04/20 20:16, Luca Bertoncello wrote: Am 25.04.2020 um 20:12 schrieb Alberto Bursi: If I undestand correct, I can upgrade to 19.07, but it will be the last version I can get, is it right? The main issue is the warning about 32MB of RAM you see on the top of that page. I read it

Re: [OpenWrt-Devel] Upgrading LEDE to 19.07

On 25/04/20 20:30, Luca Bertoncello wrote: Am 25.04.2020 um 20:27 schrieb Alberto Bursi: Hi that's weird, that's 64MB. Maybe a V2 in an older box? What is the CPU? check cat /proc/cpuinfo The V1 has Atheros AR9103. root@OpenWrt:~# cat /proc/cpuinfo system type

Re: [OpenWrt-Devel] [ModemManager] How can I make ModemManager work right?

On 29/04/20 08:29, Jeonghum Joh wrote: Hello, Thanks to many people in this list, I was able to find ModemManager and I've tried applying it. Testing environment Target Model        : MediaTek MT7622 AC4300rfb1 board Firmware Version : LEDE Reboot 17.01-SNAPSHOT unknown / LuCI Ker

Re: [OpenWrt-Devel] FULL CONE NAT in OpenWrt

Just allowing inbound connections from any external host on well-known port ranges (like a game) is bad and should NOT be default. It's basically a DMZ or full range port forwarding for all devices in the LAN. Just set a DMZ or full-range port forwarding for your console(s), it's still unsaf

Re: [OpenWrt-Devel] add support for netgear R6020

On 30/05/20 13:37, Evan Jobling wrote: Hi, From 8a2cf974be374612e8ea32d2182226d542ebbcdf Mon Sep 17 00:00:00 2001 From: Evan Jobling Date: Sat, 30 May 2020 20:39:47 +1000 Subject: [PATCH] ramips: add support for netgear r6020 Signed-off-by: Evan Jobling --- You can send patches with

Re: [PATCHv2 3/4] scripts/clean-package.sh: remove useless cat

On 12/07/20 01:38, Paul Spooren wrote: Hi, On 11.07.20 08:45, Rosen Penev wrote: Found with shellcheck. Signed-off-by: Rosen Penev ---   v2: rebased   scripts/clean-package.sh | 4 ++--   1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/scripts/clean-package.sh b/scripts/clean-p

Re: [PATCH] urngd: Add support for read()ing entropy

On 13/07/20 12:59, Petr Štetiar wrote: Nathaniel Filardo [2020-07-13 10:00:46]: Hi, Someone should update https://openwrt.org/submitting-patches then, so that the very first thing of "Patch Checklist" isn't "Single commit ( multiple commits must first be squashed, as described here )". I of

Re: Restoring (old) config backups and

On 20/07/20 19:32, Henrique de Moraes Holschuh wrote: Any thoughts on this?  I am certainly to have overlooked a lot of stuff, especially if it is present only on master.  Also, handling of an uci-defaults "reset" (so that they'd run again) in non-initramfs/overlayfs based system is likely

Re: github private respositories

On 01/08/20 17:39, Himanshu Chauhan wrote: Hi, Is there a way to compile github private repositories as package in openwrt? All the package Makefiles that I have looked at use https/http to clone the repository. Private repositories would require authentication while cloning. Thanks Reg

Re: Policy on BUILD_PATENTED

On 10/08/20 13:58, Sam Kuper wrote: IIUC, you are suggesting the creation of a new package repository through which OpenWRT devs who are based in countries (e.g. EU countries) that don't uphold software patents could distribute patent-encumbered software. Users would then be able to decide w

Re: Policy on BUILD_PATENTED

On 11/08/20 12:42, Caleb James DeLisle wrote: On 11/08/2020 02:30, Mauro Mozzarelli wrote: On 10/08/2020 10:08, Adrian Schmutzler wrote: -Original Message- From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org] On Behalf Of Mauro Mozzarelli Sent: Montag, 10. August 202

Re: Changing Inittab

On 14/08/20 05:54, Shalla Thakur wrote: Hi, I am trying to change inittab to launch a different binary than /usr/libexec/login.sh. I changed package/base-files/files/etc/inittab for that. But it seems during build these changes get overridden. What is the correct way to achieve this? Tha

Re: Changing Inittab

On 14/08/20 14:46, Shalla Thakur wrote: On 14/08/20 6:08 pm, Alberto Bursi wrote: On 14/08/20 05:54, Shalla Thakur wrote: Hi, I am trying to change inittab to launch a different binary than /usr/libexec/login.sh. I changed package/base-files/files/etc/inittab for that. But it seems

Re: OpenWrt's 'procd' now speaks containers

On 07/08/20 21:47, Daniel Golle wrote: Dear community, in the past couple of months I've been working on implementing the Open Container Initiative Runtime Specification [1] in procd by extending the already existing support for slim containers ('ujail'). As a result, there is now a new CLI t

Re: Disabling br-lan

On 15/08/20 08:00, Shalla Thakur wrote: Hi, I see that with default configuration, openwrt always creates a bridge br-lan. I am running openwrt on virtualbox and am assigning only one interface to it. I don't want the bridge to be created by default. The interface should take IP configurat

Re: OpenWrt's 'procd' now speaks containers

On 15/08/20 12:24, Daniel Golle wrote: Hi Alberto, On Sat, Aug 15, 2020 at 10:51:27AM +0200, Alberto Bursi wrote: On 07/08/20 21:47, Daniel Golle wrote: Dear community, in the past couple of months I've been working on implementing the Open Container Initiative Runtime Specificati

Re:

On 23/08/20 05:06, Raylynn Knight via openwrt-devel wrote: 1. Should I add each device individually? Even if some of the devices are very closely related. yes, add one device for each commit because it's easier to review, although you should use common dts files for features that are the

Re: A proposal of https certificate assignment system for luci

On 05/10/20 18:38, Michael Richardson wrote: Fernando Frediani wrote: > I am not sure click though certificate warning is that much of a > security issue in this context neither OpenWrt should have certificates > issued by default if I understood it correctly. > Most peo

Re: A proposal of https certificate assignment system for luci

On 06/10/20 19:43, Michael Richardson wrote: Training users to click through those warnings is exactly what browser makers are trying to avoid, and browser makers have been trying to make the exception harder and harder to find. Many would like it removed. And, for good reason, because it

Re: A proposal of https certificate assignment system for luci

On 07/10/20 04:01, Daniel Golle wrote: Hi Alberto, Hi Michael, Hi everyone else, I don't understand how your argument is related to that pretty nice suggestion regarding a fairly complex and (unfortunately) relevant problem. It is relevant because it's asking how big of a problem it actuall

Re: A proposal of https certificate assignment system for luci

On 07/10/20 15:34, abnoeh wrote: However, I think you are assuming a RA/DHCP-based WAN connection. For PPPoE (which is still a thing in a lot of places, including developing world, where last mile is often wifi), this won't work that well. at the end entire reason we need certificate is we

Re: The status of intel ax200 support (iwlwifi)

On 13/10/20 16:36, Alexander Pyattaev wrote: Hello! I am trying to figure out if any version of openWRT can in principle support the Intel's AX200 chips. I am quite willing to build a kernel from source, but I have absolutely no idea whether I actually need to do so. Some info on the internet

Re: Objective of OpenWRT/x86?

On 01/05/23 06:40, Philip Prindeville wrote: On Apr 28, 2023, at 11:18 PM, Elliott Mitchell wrote: On Fri, Apr 28, 2023 at 12:04:15PM -0600, Philip Prindeville wrote: [snip] See above: the radios and antennae I can get as add-ons for a Xeon-D 1U pizza box or even an APU6 mPCIe slot

Re: Objective of OpenWRT/x86?

On 26/04/23 22:17, Elliott Mitchell wrote: Well, was a specific objective ever chosen for the x86 version of OpenWRT? I can state my goal/hope for OpenWRT/x86. The *WRT Linux distributions were so named for originally targeting the LinkSys WRT54G. This was a small AP, so one might expect bu

Re: Packaging ZFS

ZFS would be useful for any device with a few GB of RAM that has data drives (a NAS for example). I've used ZFS extensively on x86 systems with other Linux distros (Debian/Proxmox and OpenSUSE). I think ZFS support is a good thing. Booting from ZFS is probably not necessary for OpenWrt but zfs

Re: Packaging ZFS

On 10/08/23 22:36, Thibaut wrote: Le 10 août 2023 à 22:25, Philip Prindeville a écrit : On Aug 10, 2023, at 11:49 AM, Torbjörn Jansson wrote: On 2023-08-06 21:39, Philip Prindeville wrote: I don't know... I have a Xeon D-1548 based 1U Supermicro server with a 4TB NVMe stick that wo

<    1   2