I liked the idea of including whois.
I think it should be one of those things that gets enabled if we’re not doing a
super-skinny-build.
And if I’m at a remote location and OpenWRT isn’t coming up enough for me to
run “whois” on a laptop behind it, then having it on OpenWRT itself makes it
tha
Hi guys,
Thank you for your feedback.
I was surprised how fast this was rejected and I thought that there is
going to be some vote or discussion about it. My bad.
I noticed that on OpenWrt forum, there are some requests like this [1]
to have whois present on their routers. We can be thinking abou
On 2020-11-18 06:54, Oldřich Jedlička wrote:
> út 17. 11. 2020 v 23:00 odesílatel Sebastian Kemper
> napsal:
>>
>> Commit 5d76065 moved the creation of the symvers directory to
>> include/kernel-build.mk. This is fine when building from scratch. But
>> when unpacking an SDK the directory doesn't
út 17. 11. 2020 v 23:00 odesílatel Sebastian Kemper
napsal:
>
> Commit 5d76065 moved the creation of the symvers directory to
> include/kernel-build.mk. This is fine when building from scratch. But
> when unpacking an SDK the directory doesn't exist and because the kernel
> won't be built (again)
On Wed Nov 11, 2020 at 1:53 PM HST, Rui Salvaterra wrote:
> Drop our local sstrip copy and use the current ELFKickers upstream
> version.
> Patch the original makefile in order to avoid building elftoc, since it
> fails
> with musl's elf.h. This is fine, since we only need sstrip anyway.
> Finally,
On Tue Nov 17, 2020 at 11:59 AM HST, Sebastian Kemper wrote:
> Commit 5d76065 moved the creation of the symvers directory to
> include/kernel-build.mk. This is fine when building from scratch. But
> when unpacking an SDK the directory doesn't exist and because the kernel
> won't be built (again) th
Hi Georgi,
> 2. WRT3200ACM has two Ethernet interfaces. Isn’t it more efficient to have
> dedicated interfaces for LAN and WAN compared to the DSA model which uses
> only one of them, and creates multiple interfaces using VLANs?
You only have to worry about that if you have (upload + download) >
On Tue, Nov 17, 2020 at 2:15 PM Georgi Valkov wrote:
>
> Dear DENG Qingfang,
>
> Can you please take a moment to discuss the switch from mvsw61xx swconfig
> driver to DSA?
> While I like the simplicity of having lan1 lan2 lan3 lan4 wan interfaces for
> each port, there are a few important issues
Hi,
> I assume this will land in kernel 5.11.
>
> At a minimum, it needs to be backported.
I already backported it, see commit 24410595e91c.
But there is no uci configuration available yet, you have to use `tc' in
command line.
Refer to
https://github.com/Mellanox/mlxsw/wiki/Port-Mirroring#u
On Tue, Nov 17, 2020 at 2:15 PM Georgi Valkov wrote:
>
> Dear DENG Qingfang,
>
> Can you please take a moment to discuss the switch from mvsw61xx swconfig
> driver to DSA?
> While I like the simplicity of having lan1 lan2 lan3 lan4 wan interfaces for
> each port, there are a few important issues
On Tue, Nov 17, 2020 at 3:16 PM Georgi Valkov wrote:
>
> Dear OpenWRT team,
>
> I just updated my laptop to macOS 11 Big Sur. Presently only the perl hostpkg
> package fails during the build. Once I get past perl, everything else
> compiles correctly. Below is a patch, workaround, and details fr
Dear OpenWRT team,
I just updated my laptop to macOS 11 Big Sur. Presently only the perl hostpkg
package fails during the build. Once I get past perl, everything else compiles
correctly. Below is a patch, workaround, and details from my research. My
target is Marvell EBU Armada, Linksys WRT3200
Paul Spooren wrote at Tue Nov 17 16:53:29 EST 2020:
> Could you please provide an example when that fails? E.g. what package
> makes the SDK copy things there?
Pretty much all kernel related packages, like I already disgnosed a few days
ago in
http://lists.openwrt.org/pipermail/openwrt-devel/20
Dear DENG Qingfang,
Can you please take a moment to discuss the switch from mvsw61xx swconfig
driver to DSA?
While I like the simplicity of having lan1 lan2 lan3 lan4 wan interfaces for
each port, there are a few important issues that remain to be addressed:
1. Since the new DSA does not support
On Tue, Nov 17, 2020 at 11:53:29AM -1000, Paul Spooren wrote:
> On Tue Nov 17, 2020 at 11:36 AM HST, Sebastian Kemper wrote:
> > Commit 5d76065 moved the creation of the symvers directory to
> > include/kernel-build.mk. This is fine when building from scratch. But
> > when unpacking an SDK the dire
Commit 5d76065 moved the creation of the symvers directory to
include/kernel-build.mk. This is fine when building from scratch. But
when unpacking an SDK the directory doesn't exist and because the kernel
won't be built (again) this directory will not be created by the build
system, causing build f
On Tue Nov 17, 2020 at 11:36 AM HST, Sebastian Kemper wrote:
> Commit 5d76065 moved the creation of the symvers directory to
> include/kernel-build.mk. This is fine when building from scratch. But
> when unpacking an SDK the directory doesn't exist and because the kernel
> won't be built (again) th
Commit 5d76065 moved the creation of the symvers directory to
include/kernel-build.mk. This is fine when building from scratch. But
when unpacking an SDK the directory doesn't exist and because the kernel
won't be built (again) this directory will not be created by the build
system, causing build f
Hi,
> It appears most of the major distros (Debian/Ubuntu, Fedora, Arch,
> Solaris) have moved to merge the contents of /{bin,sbin,lib}/ into
> /usr/{bin,sbin,lib}/, with top-level symbolic links added for
> compatibility.
Sounds good to me, do you have an estimate how much work this is?
> There
On Mon Nov 16, 2020 at 9:14 PM HST, Petr Štetiar wrote:
> Josef Schlehofer [2020-11-17 02:07:09]:
>
> Hi,
>
> > Whois can identify who owns a domain and how to get reach owner. Providing
> > this tool in OpenWrt someone does not need to use websites for everything.
>
> I don't think, that this to
Hi,
It appears most of the major distros (Debian/Ubuntu, Fedora, Arch,
Solaris) have moved to merge the contents of /{bin,sbin,lib}/ into
/usr/{bin,sbin,lib}/, with top-level symbolic links added for
compatibility.
There is a wiki page on freedesktop.org[1] that goes into the
reasoning, and LWN[2
Hi,
> -Original Message-
> From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org]
> On Behalf Of Filip Moc
> Sent: Dienstag, 17. November 2020 12:33
> To: openwrt-devel@lists.openwrt.org
> Subject: [PATCH v1 3/4] generic: add DTR quirk patch for MR400 LTE
>
> This is require
Hi,
> -Original Message-
> From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org]
> On Behalf Of Filip Moc
> Sent: Dienstag, 17. November 2020 12:33
> To: openwrt-devel@lists.openwrt.org
> Subject: [PATCH v1 2/4] uqmi: set device-operating-mode to online
>
> This is required
Hi,
> -Original Message-
> From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org]
> On Behalf Of Filip Moc
> Sent: Dienstag, 17. November 2020 12:34
> To: openwrt-devel@lists.openwrt.org
> Subject: [PATCH v1 4/4] ramips: add support for TP-Link MR6400 v4
>
> You can flash vi
You can flash via tftp recovery:
- serve tftp-recovery image as /tp_recovery.bin on 192.168.0.225/24
- connect to any ethernet port
- power on the device while holding the reset button
- wait at least 8 seconds before releasing reset button
Flashing via OEM web interface does not work.
LTE mo
This is required for LTE module MR400 (in TL-MR6400 v4).
Otherwise LTE module won't register to GSM network.
Signed-off-by: Filip Moc
---
package/network/utils/uqmi/files/lib/netifd/proto/qmi.sh | 3 +++
1 file changed, 3 insertions(+)
diff --git a/package/network/utils/uqmi/files/lib/netifd/pr
This is required for LTE module MR400 in TL-MR6400 v4.
Signed-off-by: Filip Moc
---
Notes:
Perhaps it would be better to go upstream with this?
...usb-qmi_wwan-Set-DTR-quirk-for-MR400.patch | 28 +++
1 file changed, 28 insertions(+)
create mode 100644
target/linux/generic
There already was an option for autoconfiguring IPv4 from QMI but this
was removed by commit 3b9b963e6e08 ("uqmi: always use DHCP for IPv4").
DHCP does not work on MR400 LTE module (in TL-MR6400 v4) so let's readd
support for IPv4 autoconf from QMI but this time allow to configure this
for IPv4 an
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 software.--- Begin Message ---
Op 14 nov. 2020, om 12:14 heeft Jo
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 software.--- Begin Message ---
There already was an option for au
30 matches
Mail list logo
