Just the module and no default sysctl conf file is provided
Ref: https://forum.openwrt.org/t/20-xx-tcp-hybla/83076
Signed-off-by: Yousong Zhou
---
package/kernel/linux/modules/netsupport.mk | 20
1 file changed, 20 insertions(+)
diff --git a/package/kernel/linux/modules/net
On 12/22/20 20:27, Rafaël Carré wrote:
Hello,
I forgot two things:
- I did not sign-off either Linux or OpenWRT patch. Will do that next time.
- I have many segfaults in userspace unless I build gcc with PIE:
Advanced configuration options (for developers) -->
Toolchain Options -->
Build exec
Upstream switched to building with CMake. Adjust accordingly.
Reapplied patch as upstream changed the file format.
Added HOST_BUILD_PARALLEL for faster compilation.
Added cmake tool dependency.
Adjusted dependent tools to use NOCACHE as they are needed to build
ccache.
Signed-off-by: Rosen Pen
Upstream switched to building with CMake. Adjust accordingly.
Reapplied patch as upstream changed the file format.
Added HOST_BUILD_PARALLEL for faster compilation.
Added cmake tool dependency.
Adjusted dependent tools to use NOCACHE as they are needed to build
ccache.
Signed-off-by: Rosen Pen
CPU: Atheros AR9342 rev 3 SoC
RAM: 64 MB DDR2
Flash: 16 MB NOR SPI
WLAN 2.4GHz: Atheros AR9342 v3 (ath9k)
WLAN 5.0GHz: QCA988X
Ports: 1x GbE
Flashing procedure is identical to other ubnt devices.
https://openwrt.org/toh/ubiquiti/common
Flashing through factory firmwa
Heads up that there’s a major change to the PR:
https://github.com/openwrt/packages/pull/14240
It adds support for “cname”, “domain”, “mxhost”, and “srvhost” config sections.
Thanks to Bjorn for pointing me at how to use nsupdate to do this.
Calling out run-time requirements on “named” and “ns
Hello,
Here is my current work in progress to support the Linksys WAP300N router.
See https://openwrt.org/toh/linksys/wap300n for some info.
This is based on the RT6855A SoC.
Current status:
- serial works
- ethernet works (didn't test 1G yet, only 100MB), with a couple small
changes in the cus
Hi,
OpenWrt 19.07 on mt7621 can sometimes crash under load. It does not
trigger often so it might go unnoticed, but there are multiple reports of
this issue and I also experienced it on a device.
Here is an example crash log:
https://bugs.openwrt.org/index.php?getfile=1116
Somebody managed t
Hi
And thank you for report. I do care. I am going to investigate it. Feel free to
revert it as I most probably won't be addressing it on Christmas but I am going
to
submit it again with fix or just fix once I found out what happened.
With regards
Karel
Excerpts from Petr Štetiar's message of
In that case, check router side, client can support it most likely.
Try different release or factory firmware
On 22/12/2020, Henrique de Moraes Holschuh wrote:
> On 21/12/2020 17:13, Tom Psyborg wrote:
>> In case your client doesn't support mfp, you should configure the
>> setting on router to op
A few devices in ath79 and ramips use mtd-concat to concatenate
individual partitions into a bigger "firmware" or "ubi" partition.
However, the original partitions are still present and visible,
and one can write to them directly although this might break the
actual virtual, concatenated partition
On 21/12/2020 17:13, Tom Psyborg wrote:
In case your client doesn't support mfp, you should configure the
setting on router to optional instead of required so non-mfp client
can fallback to basic connection type.
I took my time to answer to test it again just in case, but as soon as I
set it t
Sander Vanheule [2020-12-22 13:22:37]:
> I was actually made aware that my approach is not recommended, so I'm
> just going to retract this patch.
ok, then please remove the patches from patchwork ASAP, otherwise it's waste
of time, thanks
___
openwrt
Hi,
On Tue, 2020-12-22 at 12:21 +0100, Petr Štetiar wrote:
>
> does not apply anymore, so you should rebase and resend.
I was actually made aware that my approach is not recommended, so I'm
just going to retract this patch.
As described in commit 0c0bb6299 [1], the bootloader on these devices
h
Hi,
> -Original Message-
> From: openwrt-devel [mailto:openwrt-devel-boun...@lists.openwrt.org]
> On Behalf Of Petr Štetiar
> Sent: Dienstag, 22. Dezember 2020 10:47
> To: openwrt-devel@lists.openwrt.org
> Cc: Petr Štetiar
> Subject: [PATCH] build: replace which with Bash command built-in
This reverts commit e401a2a42e6d7c892e1cf7d765fa5ec9b2db3fb3 as at least
two users had reported breakage on their devices.
References:
https://lists.infradead.org/pipermail/openwrt-devel/2020-December/032837.html
References:
https://github.com/openwrt/openwrt/commit/e401a2a42e6d7c892e1cf7d765fa5
Magnus Kroken [2020-12-18 00:30:42]:
Hi Magnus,
thank you for the bug report and sorry for the breakage.
> Commit e401a2a42e6d7c892e1cf7d765fa5ec9b2db3fb3 causes my Turris Omnia
> CZ11NIC13 to no longer boot. Compiling with EARLY_PRINTK does not show
> anything of interest:
>
> ## Executing sc
Reuben Dowle [2020-07-16 00:10:43]:
Hi,
> This occurs because netifd can incorrectly indicate carrier down on an
> interface through devstatus after issuing a carrier up hotplug event.
then it seems like this should be fixed in netifd.
> This patch ignores carrier status for bridge interfaces,
Sander Vanheule [2020-09-27 15:59:33]:
Hi,
> Now that firmware partitions starting with an ELF kernel loader can be
> split automatically, move the TP-Link ar9344-based CPE and WBS devices
> from an OKLI loader to a plain kernel loader.
>
> This reduces the size of the device images a bit (2kB
Maksym Kovalchuck [2020-11-04 15:40:04]:
Please add proper commit description, see openwrt.org/submitting-patches for
details
> Signed-off-by: Maksym Kovalchuck
> ---
> defaults.c | 54 ++
> options.h | 14 +++---
> 2 files changed,
Rosen Penev [2020-12-22 02:21:15]:
> It's not on the installed device. It's under InstallDev.
>
> find staging_dir/target-mips_*/root-*/ -xtype l
>
> for more.
$ find staging_dir/target-x86*/root-*/ -xtype l
staging_dir/target-x86_64_musl/root-x86/etc/localtime
staging_dir/target-x86_64_mus
On Tue, 22 Dec 2020 at 17:51, Petr Štetiar wrote:
>
> `which` utility is not shipped by default for example on recent Arch
> Linux and then any steps relying on its presence fails, like for example
> following Python3 prereq build check:
>
> $ python3 --version
> Python 3.9.1
>
> $ make
> /bin
On Tue, Dec 22, 2020 at 2:18 AM Petr Štetiar wrote:
>
> Rosen Penev [2020-12-19 19:11:48]:
>
> Hi,
>
> > Fixes dead symlink under InstallDev.
>
> where is that dead symlink?
It's not on the installed device. It's under InstallDev.
find staging_dir/target-mips_*/root-*/ -xtype l
for more.
>
> ro
Rosen Penev [2020-12-19 19:11:48]:
Hi,
> Fixes dead symlink under InstallDev.
where is that dead symlink?
root@OpenWrt:/# ls -al /etc/ssl/cert.pem
lrwxrwxrwx1 root root34 Dec 21 16:53 /etc/ssl/cert.pem ->
/etc/ssl/certs/ca-certificates.crt
root@OpenWrt:/# ls -al /etc/ssl/
On Tue, Dec 22, 2020 at 1:50 AM Petr Štetiar wrote:
>
> `which` utility is not shipped by default for example on recent Arch
> Linux and then any steps relying on its presence fails, like for example
> following Python3 prereq build check:
Funny. I have a different error on my barebones Manjaro VM
`which` utility is not shipped by default for example on recent Arch
Linux and then any steps relying on its presence fails, like for example
following Python3 prereq build check:
$ python3 --version
Python 3.9.1
$ make
/bin/sh: line 1: which: command not found
/bin/sh: line 1: which: comman
26 matches
Mail list logo
