Meeting 2023 01

Gluon Meetup 2023-01

15.02.2023 - 20:00 CEST - meet.ffmuc.net/gluon-meetup

Notes from Last Meetup: Meeting-2022-06

Attendees

• [ 👤 aiyion] (ffh)
• [ 👤 lemoer] (ffh)
• [ 👤 tomh]
• [ 👤 rotanid]
• [ 👤 mkg20001] (ffgraz)
• [ 👤 NeoRaider]
• [ 👤 stargieg] (ffberlin)

Topics

• [ 👤 lemoer] Reviewing the Roadmap.
• [ 👤 rotanid] 2022.1.x regressions
  • can we do better in the future? how?
  • looking into the specific bugs
  • (maybe also closed ones?)
  • https://github.com/freifunk-gluon/gluon/issues?q=is%3Aissue+is%3Aopen+label%3A%220.+type%3A+regression%22
• [ 👤 mkg20001] olsr2 pr is waiting for merge maybe discussing some open PRs? we did this in the past
• [ 👤 lemoer] How can we get forward with #2688 [Config-Mode UI for Interface Role Assignment (v2)]?
• [ 👤 NeoRaider] [#2778 gluon-setup-mode: allow network-triggered activation
• [ 👤 aiyion] short review of open PRs

Roadmap

• Roadmap was discussed and updated.

Regressions

List can be found here

Especially three regressions are new:

• #2692 [ipq40xx: issue with WiFi Mesh since v2022.1.x]
  • This issue was discussed.
  • Short term plan:
    • Use ath-10k mainline until the problem is resolved.
    • [ 👤 lemoer] will continue to bisect the issue.
    • [ 👤 blocktrron] is not here, but might have an oppinion here. We will open a PR for the change, and assign it to him.
  • Long term plan:
    • We want to use ath-10k-ct, since there is generally better support from bengeear than from QCA.
    • [ 👤 lemoer] will continue to bisect the issue.
• #2784
  • There seems to be a workaround, that is not directly a causality.
  • Short term plan:
    • Use the dirty hack CONFIG_AIO=y in targets/ath79-generic.
    • Somebody will create a PR for this.
  • Long term plan:
    • ? find dirty bug in openwrt ?
• #2779
  • Maybe get_wlan_mac() fails?
  • Maybe configure_mesh() is not run at all?
  • [ 👤 rotanid] will try to debug this issue (when he has time). Others are welcome to debug this aswell.

Question:

• Should we write a mail to warn communites about the regressions in this release?
  • Sounds like a good idea.
  • [ 👤 rotanid] will write this mail (if he has time). If he has no time till Friday evening, then [ 👤 tomh] will write this mail.

We plan to do a bugfix release 2022.1.3:

• This release should only contain the hotfixes.
• -> Link to Milestone.
• Issues will be removed from the milestone once the hotfix is merged. The issue itself will remain open until the problem is actually solved.

OLSR v2 is waiting for merge

• -> Link to the PR (#2535)
• It (only) meshes.
• Some upstream patches for openwrt/routing are pending: here and here.
• The PR has been reviewed by [ 👤 T_X] and [ 👤 Klaus_Dieter].
• This PR is a good first step.
• Let's merge it. [ 👤 Aiyion] will merge it tomorrow.

How can we get forward with #2688?

• Config-Mode UI for Interface Role Assignment (v2)?
• It needs a proper review.
• [ 👤 lemoer] reports that a coworker of [ 👤 T_X] wants to ask [ 👤 T_X] for a review. [ 👤 lemoer] will assign [ 👤 T_X].

gluon-setup-mode: allow network-triggered activation

• There is no other way to support the ZyXEL NWA55AXE.
  • The device has no reset button.
• There is no other modern outdoor device, that is currently purchasable.
• Implementation is:
  • During boot, the router looks for the reception of a magic packet. Then it boots to config mode.
• Original firmware handles this similar.
• Ideas to reduce the attack vector:
  • Trigger the config mode only an additional power cycle is after less than e.g. 3 min after boot.
  • Add a flag that the next reboot should not trigger the boot script "network-triggered activation". This could happen for scheduled reboots like an firmware upgrade done by the autoupdater.

Short Review of Open PRs

• A review day is scheduled: 22.02.2023, 8pm.
• Two issues that [ 👤 Aiyion] marked as controversial were discussed.