Switch issues and CI to GitHub

2022-01-07 Thread Paul Spooren
Hi all, Back at the Hamburg meeting in 2019 and a succeeding vote we decided to migrate over to a self-hosted GitLab instance. Some years passed and nothing really happened so I’d like to give this another go. None of the OpenWrt project members is willing to setup and maintain a GitLab instan

Re: Switch issues and CI to GitHub

2022-01-07 Thread Sam Kuper
On Fri, Jan 07, 2022 at 10:34:34AM +0100, Paul Spooren wrote: > Instead of maintaining flyspray and the server, I’d like to export all > flyspray issues, migrate them to GitHub and open GitHub issues for > openwrt/openwrt to the public. Please don't do this. GitHub has substantial accessibility a

Re: Switch issues and CI to GitHub

2022-01-07 Thread Daniel Golle
On Fri, Jan 07, 2022 at 12:07:38PM +, Sam Kuper wrote: > On Fri, Jan 07, 2022 at 10:34:34AM +0100, Paul Spooren wrote: > > Instead of maintaining flyspray and the server, I’d like to export all > > flyspray issues, migrate them to GitHub and open GitHub issues for > > openwrt/openwrt to the pub

Re: Switch issues and CI to GitHub

2022-01-07 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 --- On 07/01/2022 12:07, Sam Kuper wr

Re: IP-PBX users?

2022-01-07 Thread Torsten Duwe
On Wed, 5 Jan 2022 17:09:19 -0700 Philip Prindeville wrote: > Anyone have documentation on getting started? > Or strong arguments to use Freeswitch over Asterisk or vice versa? My personal impression is that the mature Asterisk is good at combining POTS with VoIP, with very limited support for v

[firewall3 PATCH] firewall3: support async table init in 5.15+ kernel

2022-01-07 Thread Ansuel Smith
With 5.15+ tables are init in an async way. Firewall3 use the proc entry ip_tables_names to check if a table exist. With this new implemenation, the proc entry can contain wrong data in the case where a table is present but never used/init and firewall3 would uncorrectly think that the table is not

Re: [firewall3 PATCH] firewall3: support async table init in 5.15+ kernel

2022-01-07 Thread Rui Salvaterra
Hi, Ansuel, On Fri, 7 Jan 2022 at 17:26, Ansuel Smith wrote: > > With 5.15+ tables are init in an async way. Firewall3 use the proc entry > ip_tables_names to check if a table exist. With this new implemenation, > the proc entry can contain wrong data in the case where a table is > present but ne

[PATCH] hostapd: fallback to psk when generating r0kh/r1kh

2022-01-07 Thread Eneas U de Queiroz
The 80211r r0kh and r1kh defaults are generated from the md5sum of "$mobility_domain/$auth_secret". auth_secret is only set when using EAP authentication, but the default key is used for SAE/PSK as well. In this case, auth_secret is empty, and the default value of the key can be computed from th

Re: Switch issues and CI to GitHub

2022-01-07 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 --- Indeed, so +1 Paul > Op 7 jan. 20

Re: Switch issues and CI to GitHub

2022-01-07 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 --- Indeed, so +1 Paul > Op 7 jan. 20

Re: Switch issues and CI to GitHub

2022-01-07 Thread Rosen Penev
On Fri, Jan 7, 2022 at 1:38 AM Paul Spooren wrote: > > Hi all, > > Back at the Hamburg meeting in 2019 and a succeeding vote we decided to > migrate over to a self-hosted GitLab instance. Some years passed and nothing > really happened so I’d like to give this another go. > > None of the OpenWrt