Re: Wifi bug

2021-09-26 Thread Henrique de Moraes Holschuh
On 24/09/2021 17:04, e9hack wrote: In the past (a few days ago), it was possible to disable or shut-down wifi by introduce the command 'wifi down'. This doesn't work currently. After some seconds, wifi is start again. What version of openwrt, please? And if you could be more specific than "a

Re: Wifi bug

2021-09-26 Thread Hannu Nyman
e9hack kirjoitti 26.9.2021 klo 10.02: Am 24.09.2021 um 22:04 schrieb e9hack: In the past (a few days ago), it was possible to disable or shut-down wifi by introduce the command 'wifi down'. This doesn't work currently. After some seconds, wifi is start again. It may be related to a page fault

Re: Wifi bug

2021-09-26 Thread e9hack
Am 26.09.2021 um 12:54 schrieb Hannu Nyman: e9hack kirjoitti 26.9.2021 klo 10.02: Am 24.09.2021 um 22:04 schrieb e9hack: In the past (a few days ago), it was possible to disable or shut-down wifi by introduce the command 'wifi down'. This doesn't work currently. After some seconds, wifi is st

Re: Wifi bug

2021-09-26 Thread Hannu Nyman
pd: wlan0: interface state ENABLED->DISABLED Do you see a page fault from netifd in the log? If it does crash, it is restarted by procd. This does restart the network stack. I do not see any crash in the logs. But I do see netifd PID first disappearing from the proccess list and the

Re: Wifi bug

2021-09-26 Thread Henrique de Moraes Holschuh
On 26/09/2021 06:28, Henrique de Moraes Holschuh wrote: On 24/09/2021 17:04, e9hack wrote: In the past (a few days ago), it was possible to disable or shut-down wifi by introduce the command 'wifi down'. This doesn't work currently. After some seconds, wifi is start again. What version of ope

Re: Wifi bug

2021-09-27 Thread Felix Fietkau
Hi, On 2021-09-26 14:48, e9hack wrote: > Do you see a page fault from netifd in the log? If it does crash, it is > restarted by procd. This does restart the network stack. If I start netifd > with strace, I got this lines immediately before the page fault: > > unlink("/tmp/resolv.conf.d/reso

Re: Wifi bug

2021-09-27 Thread e9hack
Am 27.09.2021 um 12:59 schrieb Felix Fietkau: Hi, On 2021-09-26 14:48, e9hack wrote: Do you see a page fault from netifd in the log? If it does crash, it is restarted by procd. This does restart the network stack. If I start netifd with strace, I got this lines immediately before the page f

Re: Wifi bug

2021-09-27 Thread Felix Fietkau
On 2021-09-27 13:33, e9hack wrote: > Am 27.09.2021 um 12:59 schrieb Felix Fietkau: >> >> Hi, >> >> >> On 2021-09-26 14:48, e9hack wrote: >>> Do you see a page fault from netifd in the log? If it does crash, it is >>> restarted by procd. This does restart the network stack. If I start netifd >>

Re: Wifi bug

2021-09-27 Thread e9hack
Am 27.09.2021 um 14:01 schrieb Felix Fietkau: Normally it should be active by default. Is CONFIG_KERNEL_ELF_CORE set in your .config? It was not activated, but the output from gdb looks not so helpful: hb@vbox-linux6:~/src/openwrt/LEDE/archer-C7-ath79-5.10.x-dsa/build_dir/target-mips_74kc_musl

Re: Wifi bug

2021-09-27 Thread Hannu Nyman
e9hack kirjoitti 27.9.2021 klo 16.39: Am 27.09.2021 um 14:01 schrieb Felix Fietkau: Normally it should be active by default. Is CONFIG_KERNEL_ELF_CORE set in your .config? It was not activated, but the output from gdb looks not so helpful: hb@vbox-linux6:~/src/openwrt/LEDE/archer-C7-ath79-5.1

Re: Wifi bug

2021-09-27 Thread Hannu Nyman
Felix Fietkau kirjoitti 27.9.2021 klo 13.59: On a crash, it should drop a .core file to /tmp. Please copy that to your build host and use ./scripts/remote-gdb to obtain a backtrace from it. I'd like to know, which line of code in netifd it crashes on, so I can fix it. So far the bug has not shown

Re: Wifi bug

2021-09-27 Thread Felix Fietkau
On 2021-09-27 17:45, Hannu Nyman wrote: > Felix Fietkau kirjoitti 27.9.2021 klo 13.59: >> On a crash, it should drop a .core file to /tmp. Please copy that to >> your build host and use ./scripts/remote-gdb to obtain a backtrace from >> it. I'd like to know, which line of code in netifd it crashes

Re: Wifi bug

2021-09-27 Thread Hannu Nyman
Felix Fietkau kirjoitti 27.9.2021 klo 19.17: On 2021-09-27 17:45, Hannu Nyman wrote: Felix Fietkau kirjoitti 27.9.2021 klo 13.59: On a crash, it should drop a .core file to /tmp. Please copy that to your build host and use ./scripts/remote-gdb to obtain a backtrace from it. I'd like to know, wh

Re: Wifi bug

2021-09-27 Thread Felix Fietkau
On 2021-09-27 18:30, Hannu Nyman wrote: > Felix Fietkau kirjoitti 27.9.2021 klo 19.17: >> On 2021-09-27 17:45, Hannu Nyman wrote: >>> Felix Fietkau kirjoitti 27.9.2021 klo 13.59: On a crash, it should drop a .core file to /tmp. Please copy that to your build host and use ./scripts/remot

Re: Wifi bug

2021-09-27 Thread e9hack
Am 27.09.2021 um 19:02 schrieb Felix Fietkau: Fix pushed, thanks for testing. - Felix It fixes my issue too. In bonding_enable_port() and bridge_enable_member() is in the middle a 'return -1'. In all error cases before and afterwards is located a 'goto ...' to revert some things. Is 'retu

Re: Wifi bug

2021-09-27 Thread Felix Fietkau
On 2021-09-27 19:59, e9hack wrote: > Am 27.09.2021 um 19:02 schrieb Felix Fietkau: >> >> Fix pushed, thanks for testing. >> >> - Felix >> > > It fixes my issue too. > > In bonding_enable_port() and bridge_enable_member() is in the middle > a 'return -1'. In all error cases before and afterwa

Re: LUCI behaviour

2021-10-22 Thread Karl Palsson
Paul D wrote: > > 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 ( > htt

Re: dnsmasq issue

2021-12-05 Thread e9hack
Hi, the scripts are executed. I did a mistake with path names for the logging files. But the issue with executing dnsmasq twice is still open. Regards, Hartmut Am 05.12.2021 um 12:13 schrieb e9hack+dnsmasq: Hi, I did configure a user script by adding: option dhcpscript '/etc/dnsmasq-test.s

Re: dnsmasq issue

2021-12-05 Thread Daniel Golle
On Sun, Dec 05, 2021 at 12:13:16PM +0100, e9hack+dnsmasq wrote: > > Hi, > > I did configure a user script by adding: > > option dhcpscript '/etc/dnsmasq-test.sh' > > The script and the main-script are never executed. I did add a line to both > scripts, which shall log to /var/run/dnsmaq/test-{

Re: dnsmasq issue

2021-12-05 Thread Daniel Golle
On Sun, Dec 05, 2021 at 01:26:18PM +0100, e9hack wrote: > Hi, > > the scripts are executed. I did a mistake with path names for the logging > files. > > But the issue with executing dnsmasq twice is still open. Do I understand correctly that you only observe this only in case of procd-ujail bei

Re: dnsmasq issue

2021-12-05 Thread Jo-Philipp Wich
Hi, > Or does this phenomenon also happen if running without ujail? afair it also happens without ujail. Whenever handler scripts are enabled, dnsmasq will spawn a secondary helper process. This was also the reason why /etc/hotplug.d/*/ support is only conditionally enabled if installed scripts a

Re: Firewall question

2022-02-09 Thread Jo-Philipp Wich
Hello Hartmut, [...] > If I check the logs from apache2, I see from lan network only the gateway > or router ip and no client ip's. From guest network, I see every individual > client ip's. Yeah, for lan this is expected. The automatic NAT reflection consists of one DNAT rule to forward the curr

Re: Firewall question

2022-02-09 Thread e9hack
Hi Jo, I do not understand however how the guest routing works in your network currently... Guest network is wifi only with wan access, but without access to the lan network. It is used for cell phones only, which does synchronize data with nextcloud via a ddns name over the wan address. Thi

Re: [RFC] ApkWrt

2022-02-12 Thread Lucas Ramage
This is incredible work Paul! If I were running Alpine, would I be able to install an OpenWrt repository in /etc/apk/repositories and install OpenWrt packages? Would I be able to copy my APKBUILDS over from Alpine's aports repository and easily port them over to OpenWrt? I look forward to read

Re: [RFC] ApkWrt

2022-02-12 Thread Daniel Golle
On Sat, Feb 12, 2022 at 02:28:40PM +, Lucas Ramage wrote: > This is incredible work Paul! > > If I were running Alpine, would I be able to install an OpenWrt repository in > /etc/apk/repositories and install OpenWrt packages? At this point Alpine is still using APK version 2.2 while Paul's A

Re: [RFC] ApkWrt

2022-02-12 Thread Ariadne Conill
Hi, On Sat, 12 Feb 2022, Paul Spooren wrote: Hi all, For the last year or so[1] I’ve been working on replacing the package manager OPKG with APK (Alpine Package Keeper)[2]. Different from our OPKG fork is APK an actively developed project. OPKG is replaced entirely, both on device as well a

Re: [RFC] ApkWrt

2022-02-12 Thread Enrico Mioso
Hello! thanks for your interesting work! Out of curiosity - did you use extroot or some other mean to run the Alpine Linux Container? Thanks! Enrico On Sat, 12 Feb 2022, Paul Spooren wrote: Date: Sat, 12 Feb 2022 14:16:05 From: Paul Spooren To: openwrt-devel Cc: Ariadne Conill , Danie

Re: [RFC] ApkWrt

2022-02-12 Thread Daniel Golle
On Sat, Feb 12, 2022 at 10:32:09PM +0100, Enrico Mioso wrote: > Hello! > thanks for your interesting work! > > Out of curiosity - did you use extroot or some other mean to run the Alpine > Linux Container? APK3 has the ability to manage different storage layers, one of them being the normal root

Re: Drop CONFIG_IPV6 ?

2022-03-13 Thread Sergey Ryazanov
Hello Etienne, On Mon, Mar 14, 2022 at 2:36 AM Etienne Champetier wrote: > We currently have some circular dependencies caused by the usage of > PROVIDES and @IPV6 > https://github.com/openwrt/openwrt/issues/9407 > > One radical way to fix, suggested by Jow, is to completely remove > CONFIG_IPV6

Re: Drop CONFIG_IPV6 ?

2022-03-13 Thread Philip Prindeville
Yeah, I disable CONFIG_IPV6, since most American ISP's have started rolling out residential IPv6. My local pop & pop ILEC hasn't deployed it. There's not even an announced date for it on their roadmap. I suspect that if everyone had an IPv6 address, which would be both routable and non-dynami

Re: Drop CONFIG_IPV6 ?

2022-03-13 Thread Philip Prindeville
Er, *haven't started* > On Mar 13, 2022, at 9:54 PM, Philip Prindeville > wrote: > > Yeah, I disable CONFIG_IPV6, since most American ISP's have started rolling > out residential IPv6. My local pop & pop ILEC hasn't deployed it. There's > not even an announced date for it on their roadmap.

Re: Drop CONFIG_IPV6 ?

2022-03-13 Thread Fernando Frediani
How come, at the stage we are, one can be thinking of disabling IPv6 just because the ISP didn't deploy it yet ? How one can expect IPv6 to advance (and it has been going farily well), if routers at end user have IPv6 disabled ? What when the ISP finishes deployment and deliver IPv6 yo users ?

Re: Drop CONFIG_IPV6 ?

2022-03-13 Thread Reiner Karlsberg
Practically always I disable IPv6. First of all, to get rid of stuff, which might be "nice to have", but is not required "to do the job". The less code I have running, the smaller the probability to run into bugs. Second, it is a good method to reduce the requirements on flash, when having many

Re: Drop CONFIG_IPV6 ?

2022-03-14 Thread Robert Marko
Hi, I am not one of the core devs, but I don't see a point in disabling IPv6 in 2022. Since 21.02 4/32 MB devices aren't viable anymore, can somebody comment on whats the actual size reduction cause I don't see that helping to squeeze stuff like PHP, etc that somebody mentioned? Even if your ISP

Re: Drop CONFIG_IPV6 ?

2022-03-14 Thread Rui Salvaterra
Hi, Etienne, On Sun, 13 Mar 2022 at 23:33, Etienne Champetier wrote: > > We currently have some circular dependencies caused by the usage of > PROVIDES and @IPV6 > https://github.com/openwrt/openwrt/issues/9407 These don't seem unfixable. > One radical way to fix, suggested by Jow, is to comple

Re: Drop CONFIG_IPV6 ?

2022-03-14 Thread Jo-Philipp Wich
Hi, > Is anyone disabling CONFIG_IPV6 ? no. > Do people agree we can drop CONFIG_IPV6 ? yes. > Should we do this before we branch 22.x ? yes please. I am tired of sprinkling ifdefs, maintaining separate package build flavors, conditional dependency forests and runtime checks for IPv6 presence

Re: Drop CONFIG_IPV6 ?

2022-03-14 Thread Fernando Frediani
IPv6 is not a "nice to have" think. If you are using OpenWrt and consider IPv6 a nice to have thing you should do some reading and network understanding as it seems it lacks some very fundamental one to you. I see people often complaining they don't get IPv6 from their ISPs and what is the wa

Re: Drop CONFIG_IPV6 ?

2022-03-14 Thread Jonathan Lancett via openwrt-devel
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 --- Hi, Is anyone disabling CONFIG_I

Re: Drop CONFIG_IPV6 ?

2022-03-14 Thread Stijn Tintel
On 14/03/2022 01:31, Etienne Champetier wrote: > Hi All, > > We currently have some circular dependencies caused by the usage of > PROVIDES and @IPV6 > https://github.com/openwrt/openwrt/issues/9407 > > One radical way to fix, suggested by Jow, is to completely remove > CONFIG_IPV6 from OpenWrt. >

Re: ipsec broken

2020-12-28 Thread Alberto Bursi
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 w

Re: ipsec broken

2020-12-28 Thread Alberto Bursi
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.

Re: umdns bug

2021-04-10 Thread Daniel Golle
Hi Nick, On Sat, Apr 10, 2021 at 01:31:21PM +0200, Nick wrote: > There is an error in the current umds project: "UMDNS: does not start on > master with seccomp" > https://bugs.openwrt.org/index.php?do=details&task_id=3355 > > It is affecting several other projects that make use of umdns. > Is som

Re: umdns bug

2021-04-10 Thread Nick
Nice thanks for the fast reply! :) Bests, Nick On 4/10/21 6:39 PM, Daniel Golle wrote: Hi Nick, On Sat, Apr 10, 2021 at 01:31:21PM +0200, Nick wrote: There is an error in the current umds project: "UMDNS: does not start on master with seccomp" https://bugs.openwrt.org/index.php?do=details&tas

RE: Enabling Hotplug

2022-07-19 Thread Ravi Paluri (QUIC)
Can anyone please guide? The OpenWRT version we are using is 21.02.1 Thanks, Ravi -Original Message- From: openwrt-devel On Behalf Of Ravi Paluri (QUIC) Sent: Tuesday, July 19, 2022 12:27 PM To: openwrt-devel@lists.openwrt.org Subject: Enabling Hotplug WARNING: This email originated fro

Re: Enabling Hotplug

2022-07-20 Thread Alberto Bursi
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: DSA Terminology

2022-09-07 Thread Rich Brown
Hi jow, thanks for weighing in. I'm glad that I'm not unnecessarily confused - the naming *is* inconsistent. It sounds as if different "contexts" have varying definitions for the terms "interface", "network", "device", etc... (LuCi, /etc/config/network, the kernel.org article about DSA configura

Re: DSA Terminology

2022-09-09 Thread Rich Brown
Thanks for all this discussion. I have read everyone's notes carefully, but I feel as if I am falling farther and farther behind. I don't understand the distinctions between the terms that everyone is using. (The networking field is replete with synonyms for the same thing: "interface" (and de

Re: DSA Terminology

2022-09-10 Thread Arınç ÜNAL
On 10.09.2022 03:04, Rich Brown wrote: Thanks for all this discussion. I have read everyone's notes carefully, but I feel as if I am falling farther and farther behind. I don't understand the distinctions between the terms that everyone is using. (The networking field is replete with synonyms

Re: DSA Terminology

2022-09-10 Thread David Lang
On Sat, 10 Sep 2022, Arınç ÜNAL wrote: As a start, certain terms have cropped up multiple times in this discussion. Could I ask for definitions for the following terms? Here's my understanding. There is a difference between a physical device that passes bits and the logical interface that

Re: DSA Terminology

2022-09-10 Thread Rich Brown
I got the following definitions from Arınç, I am taking the liberty of opening this to the entire list, so we can refine these definitions together. I include some questions in-line to clarify the definitions. >>> As a start, certain terms have cropped up multiple times in this >>> discussion.

Re: DSA Terminology

2022-09-10 Thread Rich Brown
> On Sep 10, 2022, at 7:52 AM, David Lang wrote: > > There is a difference between a physical device that passes bits and the > logical interface that communicates with a network range. A given physical > devices can have multiple logical interfaces on them, and a logical interface > can use

Re: DSA Terminology

2022-09-10 Thread Arınç ÜNAL
On 10.09.2022 14:52, David Lang wrote: On Sat, 10 Sep 2022, Arınç ÜNAL wrote: As a start, certain terms have cropped up multiple times in this discussion. Could I ask for definitions for the following terms? Here's my understanding. There is a difference between a physical device that pas

Re: DSA Terminology

2022-09-10 Thread Arınç ÜNAL
On 10.09.2022 14:59, Rich Brown wrote: I got the following definitions from Arınç, I am taking the liberty of opening this to the entire list, so we can refine these definitions together. I include some questions in-line to clarify the definitions. As a start, certain terms have cropped up m

Re: DSA Terminology

2022-09-11 Thread Rich Brown
I think I see where I went wrong. I have updated the definitions in the DSA Terminology page to incorporate what I understand from this conversation. See: https://openwrt.org/docs/guide-user/network/dsa/dsa-mini-tutorial#terminology Is this getting closer to a set of good definitions? Thanks.

Re: DSA Terminology

2022-09-11 Thread Arınç ÜNAL
On 12.09.2022 00:28, Rich Brown wrote: I think I see where I went wrong. I have updated the definitions in the DSA Terminology page to incorporate what I understand from this conversation. See: https://openwrt.org/docs/guide-user/network/dsa/dsa-mini-tutorial#terminology Is this getting closer

Re: DSA Terminology

2022-09-12 Thread Rich Brown
Hello Arınç, Thank you for persisting in correcting my understanding. I appreciate the link to the dsa.rst document. I now realize that as you and jow have said, "DSA is simply a way to give each port of a switch its own name" so it can be configured. But if I'm reading it right, there's a cl

Re: DSA Terminology

2022-09-13 Thread Arınç ÜNAL
Hey Rich, On 13.09.2022 05:43, Rich Brown wrote: Hello Arınç, Thank you for persisting in correcting my understanding. I appreciate the link to the dsa.rst document. I now realize that as you and jow have said, "DSA is simply a way to give each port of a switch its own name" so it can be conf

Re: DSA Terminology

2022-09-13 Thread Val Kulkov
On Tue, 13 Sept 2022 at 04:09, Arınç ÜNAL wrote: > > On 13.09.2022 05:43, Rich Brown wrote: > ... > > > > > But if I'm reading it right, there's a clash between your definitions (say, > > in https://openwrt.org/playground/arinc9/network.interfaces) and the LuCI > > interface and the /etc/config/

Re: DSA Terminology

2022-09-13 Thread Jo-Philipp Wich
Hi, > IMHO changing, in /etc/config/network: > "config interface" -> "config network" > "config device" -> "config interface" > would eliminate this semantic inconsistency and bring the naming > convention more in line with what Rich referred to in his comments > above. This cannot be done in a s

Re: DSA Terminology

2022-09-13 Thread Arınç ÜNAL
On 13.09.2022 22:56, Jo-Philipp Wich wrote: Hi, IMHO changing, in /etc/config/network: "config interface" -> "config network" "config device" -> "config interface" would eliminate this semantic inconsistency and bring the naming convention more in line with what Rich referred to in his comments

Re: DSA Terminology

2022-09-13 Thread Bas Mevissen via openwrt-devel
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 --- On 2022-09-13 21:56, Jo-Philipp W

Re: DSA Terminology

2022-09-13 Thread Jo-Philipp Wich
Hi, >> Well, it would still be less confusing than the state we're currently in. >> Anyway, converting "config interface" to "config network" and "config >> device" to "config iface" is an option. I don't like `iface`, it is also easily confused with `interface` (which - as explained - still has

Re: DSA Terminology

2022-09-13 Thread Rich Brown
Let me rephrase to be sure if I understand correctly: > On Sep 13, 2022, at 3:56 PM, Jo-Philipp Wich wrote: > > > This cannot be done in a sane manner though as it would render future versions > entirely backwards incompatible. > > Renaming `config interface` to `config network` makes sense an

Re: DSA Terminology

2022-09-13 Thread Val Kulkov
Hi Rich, On Tue, 13 Sept 2022 at 21:42, Rich Brown wrote: > > Let me rephrase to be sure if I understand correctly: > > > On Sep 13, 2022, at 3:56 PM, Jo-Philipp Wich wrote: > > > > > > This cannot be done in a sane manner though as it would render future > > versions > > entirely backwards inc

Re: DSA Terminology

2022-09-13 Thread David Lang
On Tue, 13 Sep 2022, Rich Brown wrote: I am assuming that the code that processes /etc/config/network and /etc/config/wireless is the difficulty. It would be possible to change names on labels in the GUI, and to update the documentation with the new terms. But we need to be able to handle exis

Re: DSA Terminology

2022-09-19 Thread Paul Oranje via openwrt-devel
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 sep. 2022, om 03:39 heeft Ri

Re: DSA Terminology

2022-09-19 Thread Paul Oranje via openwrt-devel
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 sep. 2022, om 03:39 heeft Ri

Re: firewall4 question

2022-11-26 Thread Jo-Philipp Wich
Hi, try adding `option dest lan` to your block rule. Without any destination, it is treated as input rule, not a forwarding one. ~ Jo signature.asc Description: OpenPGP digital signature ___ openwrt-devel mailing list openwrt-devel@lists.openwrt.org

Re: firewall4 question

2022-11-26 Thread e9hack
Hi, I could solve the issue by my own. The "option dest lan" is missing in the blocking rule and the destination port must be 8443. Regards, Hartmut Am 26.11.2022 um 11:47 schrieb e9hack: Hi, I do redirect https traffic from wan to a specific ip address in lan with a different port: config

Re: backport mac80211

2022-12-13 Thread Felix Fietkau
On 12.12.22 15:24, e9hack wrote: Hi, backports-6.1-rc8 build fails for ath9k due to a missing dependency: Fixed, thanks. I added the dependency to kmod-ath9k-common instead, since that's the module that actually depends on kmod-random-core. - Felix ___

Re: DHCP leasetime

2023-02-27 Thread Eric via openwrt-devel
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 --- On Monday, February 27th, 2023 at

RE: DHCP leasetime

2023-02-28 Thread Ravi Paluri
' Thanks, Ravi -Original Message- From: Eric Sent: Monday, February 27, 2023 9:53 PM To: Ravi Paluri (QUIC) Cc: openwrt-devel@lists.openwrt.org Subject: Re: DHCP leasetime WARNING: This email originated from outside of Qualcomm. Please be wary of any links or attachments, and do not enabl

Re: OpenWrt @ Battlemesh

2023-03-08 Thread Arınç ÜNAL
On 8.03.2023 02:25, Hauke Mehrtens wrote: Hi, Wireless Battlemesh v15 is coming up in May 8-14. https://battlemesh.org/BattleMeshV15 Battlemesh will take place this year in Calafou, Vallbona d'Anoia, Barcelona. We were thinking to do a OpenWrt meeting in parallel or before/after Battlemesh. I

Re: Old hardware...

2023-04-28 Thread Bill Moffitt
I have three (3) old Ubiquiti UniFi indoor access points. Still supported in OpenWRT ath79, these are from 2015 or so. They're actually new in the box, purchased for a project that required OpenWRT; when Ubiquiti locked their bootloader they became unattractive and I set them aside. I have checked

Re: Matter integration

2023-07-27 Thread Dave Taht
So wonderful to see matter begin to matter! https://forum.openwrt.org/t/cerowrt-ii-would-anyone-care/110554 regrettably I am mostly retired from openwrt now and do not understand the workflow. On Thu, Jul 27, 2023 at 2:14 PM Karsten Sperling via openwrt-devel wrote: > > The sender domain has a

Re: Matter integration

2023-07-28 Thread Stijn Tintel
On 28/07/2023 00:11, Karsten Sperling via openwrt-devel wrote: Hello, Hi! I’m part of an effort by the Connectivity Standards Alliance to bring support for routers and access points into Matter. Matter is an open-source connectivity standard built to enable developers and device manufacture

Re: Matter integration

2023-07-29 Thread Lukas Zeller
Hi Karsten, I am very excited to see matter activity in the openwrt space! For the past year, I was working on a bridge app for my OpenWrt based SmartHome daemon p44mbrd [1]. To make it work, I already constributed a few things to matter itself, in particular the possibiity to make it use libev

Re: Matter integration

2023-07-30 Thread Karsten Sperling via openwrt-devel
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 --- Hi Stijn, Great to hear that inte

Re: Matter integration

2023-07-30 Thread Karsten Sperling via openwrt-devel
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 --- Hi Lukas, Exciting to see Matter

Re: Packaging ZFS

2023-08-06 Thread Paul D
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 anyone

Re: Packaging ZFS

2023-08-06 Thread Philip Prindeville
I don't know... I have a Xeon D-1548 based 1U Supermicro server with a 4TB NVMe stick that would make a decent file server/NAS... > On Aug 6, 2023, at 11:46 AM, Paul D wrote: > > Pretty sure not. I'm receptive to ZFS and have used it in a few projects. > Openwrt tends to focus on (devices wit

Re: Packaging ZFS

2023-08-07 Thread Alberto Bursi
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

2023-08-08 Thread Philip Prindeville
Thanks, Alberto. I'm wondering how much work making it cross-build packages is going to be... Digging into it now... > On Aug 7, 2023, at 3:23 AM, Alberto Bursi wrote: > > 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 exten

Re: Packaging ZFS

2023-08-08 Thread Luiz Angelo Daros de Luca
> Thanks, Alberto. I'm wondering how much work making it cross-build packages > is going to be... > > Digging into it now... > You should take a look at ksmbd package. It does compile an out-of-tree module. Maintaining a package like that might be challenging for a stable version. The kernel in

Re: Packaging ZFS

2023-08-09 Thread Philip Prindeville
> On Aug 8, 2023, at 3:14 PM, Luiz Angelo Daros de Luca > wrote: > >> Thanks, Alberto. I'm wondering how much work making it cross-build packages >> is going to be... >> >> Digging into it now... >> > > You should take a look at ksmbd package. It does compile an out-of-tree > module. >

Re: Packaging ZFS

2023-08-10 Thread Torbjörn Jansson
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 would make a decent file server/NAS... On Aug 6, 2023, at 11:46 AM, Paul D wrote: Pretty sure not. I'm receptive to ZFS and have used it in a few project

Re: Packaging ZFS

2023-08-10 Thread Philip Prindeville
> 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 would make a decent file server/NAS... >>> On Aug 6, 2023, at 11:46 AM, Paul D wrote: >>>

Re: Packaging ZFS

2023-08-10 Thread Thibaut
> 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 would make a dec

Re: Packaging ZFS

2023-08-10 Thread Torbjörn Jansson
On 2023-08-10 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

Re: Reserving USERID

2023-08-11 Thread Paul Spooren
Hi, > Is explicit better or not? And if it is better, how do I go about reserving > values that won't get stepped on? Who is our Numbers Czar, who is our IANA? I always used Gentoos numbers[1] whenever I added something. Since Clixon is not part of that list, maybe use something that’s not ye

Re: Reserving USERID

2023-08-11 Thread Philip Prindeville
> On Aug 11, 2023, at 10:11 AM, Paul Spooren wrote: > > Hi, > >> Is explicit better or not? And if it is better, how do I go about reserving >> values that won't get stepped on? Who is our Numbers Czar, who is our IANA? > > I always used Gentoos numbers[1] whenever I added something. Since

Re: Packaging ZFS

2023-08-15 Thread Alberto Bursi
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

Re: your mail

2020-08-02 Thread Daniel Golle
On Sun, Aug 02, 2020 at 07:49:40PM -0300, SAn 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 t

Re: your mail

2020-08-05 Thread Daniel Golle
ped > automatically by the mailing list software. > Date: Tue, 4 Aug 2020 20:35:26 -0300 > From: SAn > To: Daniel Golle , s@gmx.de > Cc: openwrt-devel@lists.openwrt.org > Subject: Re: your mail > > Hi Stefan and Daniel, > > On 8/2/20 8:19 PM, Daniel Golle wrot

Re: your mail

2020-08-05 Thread Daniel Golle
ped > automatically by the mailing list software. > Date: Wed, 5 Aug 2020 16:51:00 -0300 > From: SAn > To: Daniel Golle > Cc: s@gmx.de, openwrt-devel@lists.openwrt.org > Subject: Re: your mail > > Hi Daniel > > On 8/5/20 6:04 AM, Daniel Golle wrote: > >

Re: Changing Inittab

2020-08-14 Thread Alberto Bursi
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

2020-08-14 Thread Shalla Thakur
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 during build these changes get overridden. What

Re: Changing Inittab

2020-08-14 Thread Alberto Bursi
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 duri

Re: Changing Inittab

2020-08-14 Thread Shalla Thakur
On 14/08/20 6:20 pm, Alberto Bursi wrote: 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/fil

Re: system broken

2020-10-22 Thread Daniel Golle
On Thu, Oct 22, 2020 at 02:36:51PM +0600, Roman Kuzmitskii wrote: > yeah, i found that it is broken too. > i tested on few octeon boards and all of them fall in ‘high memory device’ > category. > > reverting commit brings back the working tree back. > > i would suggest to revert for now and do b

<    1   2   3   4   5   6   7   8   9   10   >