inline
On 2024-05-10 19:48, g...@eigenlab.org wrote:
> From: Gioacchino Mazzurco
>
> Add support for hostapd Access Point Micro Peering
>
> Signed-off-by: Gioacchino Mazzurco
> ---
> .../wifi-scripts/files/lib/netifd/hostapd.sh | 16 +-
> package/network/services/hostapd/Makefile | 2
Any further comments or reviews for this to go in?
On 2024-04-09 05:04, Paul Donald wrote:
> From: Paul Donald
>
> applies to odhcpd master HEAD d8118f6e76e5519881f9a37137c3a06b3cb60fd2
>
> Before:
> ==
> ICMPv6 Option (Prefix information : fd51:1c2a:8909::/64)
> Type: Prefix information
On 2024-04-25 22:12, Linus Walleij wrote:
> These patches have been cooking for some time, let's
> get them moving.
>
> The idea is to merge this base so we have base support
> for the target and then try to work out remaining issues
> such as the LED handling.
>
> To:
>
> Signed-off-by: Linus
commit 33ec3d52cea628df91eb0eb1701e16172c1e - HEAD
Problems.
the first error was the absence of
/home/user/openwrt/staging_dir/target-mips_24kc_musl/usr/include/libubox/udebug.h
Had to manually download udebug.h from the libubox repo...?
Next error - (c)make cannot seem to find
On 2024-04-16 16:41, Etienne Champetier wrote:
> Le mar. 16 avr. 2024 à 10:34, Paul D a écrit :
>>
>> On 2024-03-27 23:56, Etienne Champetier wrote:
>>>
>>> As this is a legal issue, should we get SFC opinion first ?
>>>
>>> Etienne
>>>
On 2024-03-27 23:56, Etienne Champetier wrote:
>
> As this is a legal issue, should we get SFC opinion first ?
>
> Etienne
>
Is this happening?
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
>> 6. Adjust "ipaddr" (access point) and "serverip" (TFTP server) addresses
Might be an idea to explicitly document these IPs so that dedicated users can
already set their gear to those IPs and just smash enter
___
openwrt-devel mailing list
On 2024-04-11 10:52, Bjørn Mork wrote:
> Ivan Ivanov writes:
>
>>> SOC: MediaTek MT7981B , Wi-Fi: MediaTek MT7976C
>>
>> Are these Mediateks capable of working without any binary blobs, at
>> least in theory?
>
> A simple question back to you: Could you please list the wifi chips you
> know of
> It's not beautiful, but it works:
>
> xargs -a blacklist.txt -I {} sh -c 'find package \( -name "$1" -prune \) -o
> -type f -print' sh {}
>
>
I take that back - no it doesn't :/
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
On 2024-04-10 16:45, Philip Prindeville wrote:
>
>
>> On Apr 9, 2024, at 6:03 PM, Paul D wrote:
>>
>> On 2024-04-09 23:30, Philip Prindeville via openwrt-devel wrote:
>>> I'm trying to modify a script generates a list of filenames one per
>>> line,
On 2024-03-27 23:56, Etienne Champetier wrote:
>
>
> (On my phone, Gmail mobile only sends html emails, sorry for that)
>
> As this is a legal issue, should we get SFC opinion first ?
>
> Etienne
>
When can we know the result of such an opinion?
On 2024-04-09 23:30, Philip Prindeville via openwrt-devel wrote:
> I'm trying to modify a script generates a list of filenames one per
> line, but should be filtered against a blacklist of file globs.
>
> Something like:
>
> % find dir -print | grep -v -f blacklist
I got this. When I run it
On 2024-04-06 12:05, Jonas Gorski wrote:
> Hi,
You're right on all counts. I separated out the value clamping and config
values to another patch-set.
Thanks for your sharp eyes.
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
On 2024-04-05 03:34, Daniel Golle wrote:
> On Fri, Apr 05, 2024 at 02:53:03AM +0200, Paul Donald wrote:
>> From: Paul Donald
>>
>> refactor and fix limit prefix preferred_lt to valid_lt in accordance with
>> RFC4861
>
> All changes look good and I generally agree. Thank you!
>
Good. Thank
On 2024-04-04 17:02, Stijn Tintel wrote:
> On 4/04/2024 18:00, Paul D wrote:
>> On 2024-04-04 16:28, st...@linux-ipv6.be wrote:
>>
>>> -netgear,gs110tpp-v1)
>>> - ucidef_set_poe 130 "$(filter_port_list "$lan_list" "lan9 lan10")&quo
On 2024-04-04 16:28, st...@linux-ipv6.be wrote:
> -netgear,gs110tpp-v1)
> - ucidef_set_poe 130 "$(filter_port_list "$lan_list" "lan9 lan10")"
> - ;;
If adding a device, surely these remove lines should not be there?
___
openwrt-devel mailing
On 2024-04-04 12:00, John Crispin wrote:
> Hi,
>
>
> http://mirror2.openwrt.org/OpenWrtOne_top.png
Looks nice. Is that silkscreened PD1 - 5V or PD - 15V? I guess it's not
critical since PD auto-negotiates, but avoiding ambiguity is good.
Were the chip numbers modified in the photos after?
On 2024-04-03 01:15, Jo-Philipp Wich wrote:
> Hi,
>
> What's the purpose of this isolated comment? Either we're shipping version >=
> v1.0.15 so this code is guaranteed to work or we don't, in which case the
> code should not be there. We're not putting such comments next to all other
> option
Thanks for the insight, Jo. Inline:
On 2024-04-03 01:12, Jo-Philipp Wich wrote:
> Hi,
>
>> For interface type parameters, the man page documents patterns:
>> ```
>> *,!eth*,!!eth1
>>
>> uses all interfaces, except interfaces starting with "eth",
>> but including "eth1".
>> ```
>
> at some
On 2024-04-02 23:00, Elliott Mitchell wrote:
> Second, appears the ${parameter:offset:length} may not be POSIX. I
> dislike this, but do not object since OpenWRT's shell is built with this
> functionality enabled.
UUOC! Ha. Yes, there are a few non POSIXy things in openwrt ash. A number of
(On my phone, Gmail mobile only sends html emails, sorry for that)
As this is a legal issue, should we get SFC opinion first ?
Since you deem it a legal issue, yes, get their opinion.
___
openwrt-devel mailing list
When running uci from the command line, it parses files in
/etc/config
If other 'config' type files exist in this path, uci emits:
uci: Entry not found
to stderr for each non-uci type encountered. This can be confusing.
Additionally, for every line printed to stderr in this process, it
Recommend avoiding -a and -o params.
Use instead e.g.
[ -n "$GUID" ] || [ "$KERNELPARTTYPE" = "6" ] || [ "$KERNELPARTTYPE" = "c" ]
https://www.shellcheck.net/wiki/SC2166
On 2024-03-28 18:00, Tomasz Maciej Nowak wrote:
From: Tomasz Maciej Nowak
Some old or proprietary bootloader recognize
lets make a vote
So... what's necessary for a vote to start?
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Christian and I have read on IRC people that got offended by my profile pic
People will take offence at *anything*. Thus, 'take' and not 'give'.
It's a *them* problem, not a *you* problem.
___
openwrt-devel mailing list
My 2 cent on the problem of permitting nick is that if we accept that,
some funny guy might use nickname like "ExtraHardCockSucker"
and we wouldn't have anything to say about it and have to accept
it if the contribution is correct.
Using Real name prevents that (on 99% of the case)
Examples of
a) It's a policy change and not a code change.
Policy changes require a vote
Then take a(nother) vote.
https://lists.openwrt.org/pipermail/openwrt-devel/2024-January/042063.html
b) Just because the kernel changed their interpretation of DCO
requirements doesn't mean this automatically
We have quorum/consensus on this issue. Is it too much to ask that
everyone now follow it, or at least have this token 'vote'?
Triggered by the yggdrasil additions of recent.
https://github.com/openwrt/packages/pull/23072
Paul S amended the policy (in packages[1] and openwrt[2] repos) with
Judging by the recent PRs bumping platforms to 6.6, it seems 6.6 is the
goal.
https://github.com/openwrt/openwrt/pulls
On 2024-03-19 04:27, abnoeh wrote:
May I ask what was the result of this vote was?
2024-02-03 오후 9:06에 Hauke Mehrtens 이(가) 쓴 글:
Hi,
I track the status of the Linux kernel
Maybe needs Rafał Miłecki approval?
===
diff --git a/package/system/procd/files/procd.sh
b/package/system/procd/files/procd.sh
index 8ee25f4f08b47..9d936bb7e9778 100644
--- a/package/system/procd/files/procd.sh
+++ b/package/system/procd/files/procd.sh
@@ -601,7 +601,7 @@
Maybe others have raised this idea. I won't address potential security
issues at the abstract phase (firewalling necessary), but...
How about a node which spins up a live openwrt system with the latest
luci master with the various PRs that come in? So contributors can see
the effect of
Elliott,
You raise some important points, and also mention some *solutions* which
is commendable.
1) all work is done voluntarily
2) time is limited
3) understanding is lacking
4) courage is lacking
Or... success has many fathers, but failure is an orphan.
Speaking from personal experience
On 2024-03-02 19:50, Jo-Philipp Wich wrote:
Hi.
You need a double backslash to escape the backslash itself.
"/usr/bin/find -L /dev -maxdepth 3 -type c -name lp\\[0-9\\]": ["exec"]
~ Jo
No go. Still 403.
Pretty sure I've tried all workable permutations in the js and JSON of
escaping.
No voting rights, but +1 for his contributions and help esp on XG6846
and bcm/marvell stuff.
On 2024-03-02 16:01, Christian Marangi (Ansuel) wrote:
From: Petr Štetiar
Hi,
Linus is renowned in the FOSS community primarily for his exceptional
contributions to the Linux kernel, where he
Can this be fixed or is lib micro box the limitation?
See jows commit for the current apex of permission strings:
https://git.openwrt.org/?p=project/rpcd.git;a=commitdiff;h=aaa08366e6384d9933a405d1218b03c1b167f9e5
In https://github.com/openwrt/luci/pull/6907 I encountered a permissions
].running"
returns simply: true
This is working when script execution takes some time.
For some scripts that take very less time (for e.g, a single instruction such as "uci set
.."), we are not able to detect the transition of "running" flag to false from true
as the
The last PR that you merged included some fatal copy/paste errors.
At least the first PR below fixes them
https://github.com/openwrt/openwrt/pull/14583
https://github.com/openwrt/openwrt/pull/14584
I have some other fixes pending but those depend on these PRs.
/P
On 2024-02-23 15:49, Thomas Richard wrote:
In GPT there is no reason to limit the active partition number to 4.
This limitation is only for MBR, as it corresponds to the maximum number
of primary partitions.
Signed-off-by: Thomas Richard
Agreed.
On 2024-02-26 19:39, John Crispin wrote:
Hi Rafał,
Is there any update / schedule you could share?
I have been meaning to send an update for a few days. Thanks for
reminding me.
I'm really looking forward to this device.
yeah, me too ;)
Lots of stuff has been happening. There was a short
What tar standard are you aiming to adhere to?
On 2024-02-26 15:14, Rafał Miłecki wrote:
From: Jo-Philipp Wich
This allows building uncompressed tar archives from shell scripts (and
compressing them later if needed)
Signed-off-by: Rafał Miłecki
---
On 2024-02-23 13:43, Ravi Paluri (QUIC) wrote:
Can you let us know, is there a way to get a notification when the "running" key value moves to
"false" from "true"?
OR is there any ubus API to which we can register a callback, which will then
be invoked when the execution is complete?
Not
On 2024-02-17 22:55, e9hack wrote:
Hi,
I face a problem with hotplug calls. To execute hotplug calls, procd
checks given environment variables. If a variable is empty, it is
simply not set by procd. If such a variable is already set by the
shell, the called hotplug script gets a wrong value.
On 2024-02-15 15:42, Rafał Miłecki wrote:
On 14.02.2024 21:50, Paul D wrote:
Would services not do better to be tracked within uci and its config
files in /etc/config?
Well, it's a part of a mess we have in our init/config code. It was only
last week that Jo was discussing it with Ansuel
I recommend avoiding Docker (hub) entirely if possible.
GHCR has been great in my experience. Integrates nicely with GH actions.
On 2024-02-15 13:37, Paul Spooren wrote:
On Feb 15, 2024, at 00:12, Paul D wrote:
https://github.com/openwrt/packages/actions/runs/7908507874/job/21587828762
https://github.com/openwrt/packages/actions/runs/7908507874/job/21587828762?pr=23415
for various platforms
errors:
#4 [internal] load metadata for
docker.io/openwrt/rootfs:i386_pentium-mmx-openwrt-23.05
#4 ERROR: no match for platform in manifest
(Not directly commenting on this change set)
Would services not do better to be tracked within uci and its config
files in /etc/config?
Or do changes to those files there risk triggering other procd actions
to the services they dictate?
On 2024-02-14 16:05, Rafał Miłecki wrote:
From:
On 2024-02-13 00:23, Hartmut Birr wrote:
Hi,
I let /etc/init.d/network log some more things by changing:
--- network.rom 2024-02-12 20:46:51.0 +0100
+++ network 2024-02-12 23:18:07.0 +0100
@@ -16,8 +16,10 @@ start_service() {
init_switch
FAO Rafał
A great to have mdns addition within procd.sh:
https://github.com/openwrt/openwrt/pull/10715
A necessary bug fix:
https://github.com/openwrt/openwrt/pull/14597
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://github.com/openwrt/luci/pull/6347
approved?
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
On 2024-02-03 13:06, Hauke Mehrtens wrote:
Hi,
I track the status of the Linux kernel 6.1 migration in this github
issue: https://github.com/openwrt/openwrt/issues/14546
There are still many targets on kernel 5.15 without testing support for
kernel 6.1 in OpenWrt master. I assume that we
Who reviews what goes on in this repo?
https://github.com/openwrt/odhcpd
It needs some reviewer love.
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
+1
On 2024-01-30 19:15, Christian Marangi (Ansuel) wrote:
Robert is active in OpenWrt since 2017 and with some recent stats, he
has more than 310 commits merged in OpenWrt.
He also have uncounted Reviewed-by tag on various PR and merged commits
and generally helps in everything related to
Is this what we tested on 6846? Or this is what you've been cooking? :)
I'm almost certain it's the latter.
On 2024-01-30 23:33, Linus Walleij wrote:
This adds a kernel module package for the Marvell
MV88E6XXX DSA switch and a separate module package for
the DSA tagger since it can in theory
The simple past tense of offset is... offset :)
Suggested: Split also after offset uImage
BTW: was this what I tested in your factory and sysimages for the XG6846?
If so can you roll a fresh one with this patch? Then I can give you a
more recent Tested-By:
On 2024-01-23 23:17, Linus
Trying to add the almost mandatory +kmod-usb-printer to p910nd package
Since just about every known configuration still mandates that the user
install kmod-usb-printer.
https://github.com/openwrt/packages/pull/23094
Is there a smarter way to add this depends? I don't yet understand how
So, the power budget is a global option. Do we ever envisage that parts
of this budget can be concretely assigned to specific ports or more
abstract ?
e.g.
config port
option name 'lan8'
option id '1'
option enable '1'
A kickstarter is a good way to forecast demand.
You've captured the imagination of the geek community.
Not aware of peripheral issues or complexities in doing a kickstarter,
though I agree with forecasting demand. "Geeks" are good at commenting
on stuff, and intellectualizing a new
https://lists.mindrot.org/pipermail/openssh-unix-announce/2024-January/000156.html
OpenSSH dropping DSA
2024/06 disabled
2025/01 code removal
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
Please take a look at the PRs here:
https://github.com/openwrt/odhcpd/pulls
They need some attention :)
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
On 2024-01-08 16:03, Paul Spooren wrote:
Hi Paul,
PKG_MAINTAINER:=Joe Bloggs
PKG_MAINTAINER_HANDLE:=github: @joe; https://forum.openwrt.org/u/joe/
Plan B
co-opt existing PKG_MAINTAINER field, but perhaps it's possible?
e.g:
PKG_MAINTAINER:=Joe Bloggs , github: @Joe
I think for that you
6GHz seems a starting point nowadays, although I get by with 5GHz.
If the BPi can be extended with add-on cards for exactly this area,
that's a great starting point also.
Ideally sub $100 for any product.
* Packages with cases+PSU are a must for broader acceptance, and to
prevent fatigue
Plan A
Proposal for e.g. PKG_MAINTAINER_HANDLE which uniquely identifies the
user's github @ handle (or forum?) to ease identifying and tagging the
user (for review purposes) on github, given the general trend to discuss
changes in these locations.
Such variable to go into Makefiles:
Could I get some reviews please?
https://github.com/openwrt/openwrt/pull/14269
https://github.com/openwrt/openwrt/pull/14179
There are some other PRs for dnsmasq which are interesting (around ~20),
but they seem to need some more work.
___
Anything useful here which could go in a PR or two on github?
I've added multihome to luci:
a5ed5976f4cf70a36863e69da8c055f855545f87
The --local param seems to be in there already.
On 2023-12-18 17:30, e9hack wrote:
Am 18.12.2023 um 16:22 schrieb Paul D:
How does pppoe-wan get its IP
How does pppoe-wan get its IP?
You may not be able to do much about that, but you can hint which IPv6
an interface gets using the assignment length, hint and prefix settings.
I don't use openvpn, but perhaps it has something like this? I guess it
would try to pick a source IP with the
How does pppoe-wan get its IP?
You may not be able to do much about that, but you can hint which IPv6
an interface gets using the assignment length, hint and prefix settings.
I don't use openvpn, but perhaps it has something like this? I guess it
would try to pick a source IP with the
On 2023-12-09 23:47, Philip Prindeville wrote:
Hi all,
I'm working on a drop-in for Kea that will parse existing ISC-DHCP
configurations in UCI and crank out the derivative JSON config files for Kea,
but I have a couple of PR's that are necessary to making this happen that have
been pending
Worth mentioning this new UEFI bootloader vuln which was unembargo'd today.
https://binarly.io/posts/The_Far_Reaching_Consequences_of_LogoFAIL/
Might affect a few devices out there, upon which OpenWRT runs.
___
openwrt-devel mailing list
On 2023-11-18 20:42, Philip Prindeville wrote:
Hi all,
I'm trying to figure out what best practices are for shell libraries, as I'm
working on changes to a pretty significant library which I envision being
leveraged in a lot of places.
My questions are these:
* should a good library do
Hi, maybe some housekeeping process is nececssary, but I got this
immediately after I did the usually recommended checkout procedures, and
have been even after a git pull, every time I run make.
Do these packages need bumping to another libpcre version?
===
WARNING: Makefile
What is the proven way forward here?
I've found some delicious kernel panics while running 6.1 on broadcom H/W.
But IIRC, kernel isn't interested in bugs unless you've tested on the
latest versions which are not readily available to owrt.
___
While I second the urgency of this, I venture the question of how one
might otherwise catch these things, but for sharp eyes. There is an
attention deficit with respect to the volume of patches and PRs that
come in.
On 2023-10-15 19:41, Bjørn Mork wrote:
A typo snuck in with the addition of
Pretty sure not. I'm receptive to ZFS and have used it in a few
projects. Openwrt tends to focus on (devices with) smaller flash drives.
Other FS better suited to such env.
No ZFS is in available software packages today, in any case.
On 2023-08-06 00:53, Philip Prindeville wrote:
> Has
Given that they both cover similar ground, I think this is a good idea.
I am a user of both, on various platforms/OSes, although on owrt, I use
dnsmasq almost exclusively for its broader functionality which also
covers DHCP.
On 2023-07-27 00:26, Philip Prindeville wrote:
I'm the
For those executing this at the command line, how does one 'repeat'?
-v 1 -v 2, or -v1 -v2 or -v123 or -v 1,2,3?
I had to think for a bit since it wasn't immediately obvious.
Perhaps a hint string with "(repeatable eg -v 1 -v 2)"?
On 2023-07-22 14:40, Legale Legale wrote:
From
On 2023-07-22 07:43, Randy Dunlap wrote:
Fix grammar and punctuation in the vlynq Kconfig file.
Fixes: 55e331cf7ebe ("drivers: add support for the TI VLYNQ bus")
Signed-off-by: Randy Dunlap
Cc: Florian Fainelli
Cc: openwrt-devel@lists.openwrt.org
Cc: Andrew Morton
---
drivers/vlynq/Kconfig
Please review/merge
On 2023-07-14 21:51, Rosen Penev wrote:
On Fri, Jul 14, 2023 at 8:12 AM Shiji Yang wrote:
From: Shiji Yang
Due to circuit issue or silicon defect, sometimes the WiFi switch button
of the Archer C7 v2 can be accidentally triggered multiple times in one
second. This will
On 2023-04-25 16:12, Jan Hoffmann wrote:
On 2023-01-30 at 23:40, Jan Hoffmann wrote:
Some VRX518 modems fail to initialize properly with the error message
"dc_ep_clk_on failed". As a result, the DSL data path doesn't work.
This hack, which is based on code from the FRITZ!Box 7530 GPL archive,
On 2023-02-08 11:44, Robert Marko wrote:
On Sun, 5 Feb 2023 at 01:10, Jan Hoffmann wrote:
Am 02.02.23 um 11:54 schrieb Robert Marko:
On Tue, 31 Jan 2023 at 23:52, Jan Hoffmann wrote:
Hi Robert,
On 2023-01-30 at 00:08, Robert Marko wrote:
Shouldn't it be possible for the modem driver
Signed-off-by: Paul Dee
---
root/usr/share/ucode/fw4.uc | 64 -
1 file changed, 63 insertions(+), 1 deletion(-)
diff --git a/root/usr/share/ucode/fw4.uc b/root/usr/share/ucode/fw4.uc
index 5dce90d..96f2780 100644
--- a/root/usr/share/ucode/fw4.uc
+++
Any takers?
ping jo wich?
On 2023-01-07 17:00, Paul D wrote:
comment is documented as a string in the man page.
Ref: https://github.com/openwrt/luci/pull/6187#issuecomment-1374506633
Signed-off-by: Paul Dee
---
root/usr/share/ucode/fw4.uc | 2 +-
1 file changed, 1 insertion(+), 1
comment is documented as a string in the man page.
Ref: https://github.com/openwrt/luci/pull/6187#issuecomment-1374506633
Signed-off-by: Paul Dee
---
root/usr/share/ucode/fw4.uc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/root/usr/share/ucode/fw4.uc
On 2022-02-21 22:38, Rich Brown wrote:
There is a new RFC on the OpenWrt forum proposing "Automatic LAN Subnet
Reassignment"
https://forum.openwrt.org/t/rfc-automatic-lan-subnet-reassignment-upon-conflict-with-wan/120938
The RFC responds to the advice given at last week's OpenWrt-Adm meeting
Sounds like the intended efforts for DSA bringup for 21.x and beyond
have been fruitful.
:)
On 2021-12-22 08:45, Kristian Evensen wrote:
Hi,
On Tue, Dec 21, 2021 at 6:34 PM Kristian Evensen
wrote:
Since the only change between my sets of tests is the software,
something has clearly
I generalize, but this is a problem which affects a few devices in the
DSA bring-up.
Some platforms require some tinkering and tweaking, and perhaps input
from the chip-set manufacturer (or information from a datasheet of the
chip-set) if things are to improve.
DSA brings advantages and is
Never mind - they appear to be more sporadic, and perhaps also require a
network restart.
Time_Zone appears in Probe Response frames only.
On 2021-12-07 04:06, Paul D wrote:
I tried enabling the wifi settings for 2.4 and 5Ghz.:
== time_advertisement ==
Result: OK. Time appears in beacon
Sorry - seems like it's already there :)
On 2021-12-07 16:29, Paul D wrote:
Could this also be picked to 21.02 branch, please?
https://github.com/openwrt/openwrt/commit/85ce590705072be78c3ef7dc6b64e3b1facc892b
___
openwrt-devel mailing list
Could this also be picked to 21.02 branch, please?
https://github.com/openwrt/openwrt/commit/85ce590705072be78c3ef7dc6b64e3b1facc892b
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
I tried enabling the wifi settings for 2.4 and 5Ghz.:
== time_advertisement ==
Result: OK. Time appears in beacon frames. e.g.
Tag: Time Advertisement
Tag Number: Time Advertisement (69)
Tag length: 17
Timing capabilities: UTC time at which the TSF timer is 0 (2)
Time Value:
Could this be picked to 21.02 branch, please?
https://github.com/openwrt/openwrt/commit/e309b57619b9c073b9b8857858d9456183f27d7d
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
On 2021-12-06 14:33, Paul Spooren wrote:
On 6. Dec 2021, at 13:37, Paul D wrote:
Could coreutils in rust be interesting for this project? (memory safety, at
least at a later date)
I think long term rust routers would be of interest, did you already do some
rather research? From a first
They use MIT license, however.
https://github.com/uutils/coreutils
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
Could coreutils in rust be interesting for this project? (memory safety,
at least at a later date)
They use MIT license, however.
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
C7v2 here. 21.02
eth0: 73
eth1: 72 (br-lan)
wlan0: 71 (11n+ac, 5GHz)
wlan1: 72 (11bgn, 2.4GHz)
Works fine as is.
On 2021-11-15 21:04, e9hack wrote:
Hi,
I'm using two tp-link routers. Both are using the same mac address for
one eth and one wlan interface:
archer c7-v2:
uboot
only at IPv6 layer the PMTU is reduced. possibly something similar
occuring at IPv6. Is it possible something unusual is happening in 6in4
or lower?
On 2021-11-04 23:04, Nathan Lutchansky wrote:
On 11/4/21 11:52 AM, Paul D wrote:
Having a bit of IPv6 6in4 problem. I set a static MTU to 1480
Clarification: I ping6 the next ipv6 hop after my 6in4 tunnel, to rule
out PMTU being at fault.
On 2021-11-04 16:52, Paul D wrote:
Having a bit of IPv6 6in4 problem. I set a static MTU to 1480 locally
and remotely (HE tunnel).
___
openwrt-devel
Having a bit of IPv6 6in4 problem. I set a static MTU to 1480 locally
and remotely (HE tunnel).
As I interpret the RFC [1] as referenced by overarching RFC [2], it notes:
> When using the static tunnel MTU, the Don't Fragment bit MUST NOT be
> set in the encapsulating IPv4 header. As a
If I use js e.g. :
o = ss.option(form.TextValue, 'blah', _('blah'), _('blah.'));
o.optional = true;
o.monospace = true;
And add either:
o.width = "500px";
or:
o.width = "60ch";
I do not get the desired effect. Is this normal?
Here (
The below is a fairly prescient analysis of the situation, and a good
approach, Rui. I think openwrt will be fine staying put on iptables,
until bpfilter matures. I think I have about 20 individual rules on my
FW. Having the capability is nice, but most home users probably don't
have or need
Wise words from the experienced!
If making a yearly release is unattainable, isn't making point releases
more achievable? Even if it's adding a single commit, point releases
send a signal to the outside world that the project is still active, and
e.g. that security is in focus. Any point
1 - 100 of 109 matches
Mail list logo
