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
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
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
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
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
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
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
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
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:
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
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
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";
+
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
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
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
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
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
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
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
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
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
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
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.
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
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
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
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,
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
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
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
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".
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
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
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
> 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 enable
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
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
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
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
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 ...
ther 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 Right
to Repair movement's goals
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
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
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,
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]
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
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
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
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.
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
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
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
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.
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
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
*
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
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
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
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
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
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
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
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.
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
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
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
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.
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
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
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
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"?
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
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
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
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
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
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
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
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.
It's
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
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
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
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
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
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
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
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
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
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
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 Specification [1
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
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
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
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?
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
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
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
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
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
1 - 100 of 189 matches
Mail list logo
