Package name of mbedtls is not 'mbedtls' but 'libmbedtls'.

Signed-off-by: David Bauer <mail@david-bauer.net>

gluon-core: dont fail on unset interface role

gluon-status-page: html: improve accessibility

OpenWrt does not ship with WolfSSL anymore. Instead mbedTLS is shipped
by default.

We can remove the default removal of WolfSSL packages, as they are not
included by default anymore.

Signed-off-by: David Bauer <mail@david-bauer.net>

In case no interface role was selected for a given interface,
gluon-reconfigure currently fails with

Configuring: 021-interface-roles
/usr/bin/lua: /usr/lib/lua/gluon/util.lua:25: bad argument #1 to 'pairs' (table expected, got nil)
stack traceback:
	[C]: in function '?'
	/usr/lib/lua/simple-uci.lua:22: in function 'foreach'
	./021-interface-roles:47: in main chunk
	[C]: ?

Check we actually have a role set before accessing the table.

Signed-off-by: David Bauer <mail@david-bauer.net>

Signed-off-by: Linus Lüssing <linus.luessing@c0d3.blue>

google-lighthouse:
Warning: Consider avoiding viewport values that prevent users from resizing documents.

Rule ID: meta-viewport
Accessibility:
Ruleset: axe-core 4.4
User Impact: Critical
Guidelines: WCAG 2.1 Best Practice, WCAG 2.0 Best Practice

Bumps [docker/metadata-action](https://github.com/docker/metadata-action) from 879dcbb708d40f8b8679d4f7941b938a086e23a7 to 62339db73c56dd749060f65a6ebb93a6e056b755.
- [Release notes](https://github.com/docker/metadata-action/releases)
- [Commits](https://github.com/docker/metadata-action/compare/879dcbb708d40f8b8679d4f7941b938a086e23a7...62339db73c56dd749060f65a6ebb93a6e056b755

)

---
updated-dependencies:
- dependency-name: docker/metadata-action
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

Bumps [docker/login-action](https://github.com/docker/login-action) from b4bedf8053341df3b5a9f9e0f2cf4e79e27360c6 to 1f401f745bf57e30b3a2800ad308a87d2ebdf14b.
- [Release notes](https://github.com/docker/login-action/releases)
- [Commits](https://github.com/docker/login-action/compare/b4bedf8053341df3b5a9f9e0f2cf4e79e27360c6...1f401f745bf57e30b3a2800ad308a87d2ebdf14b

)

---
updated-dependencies:
- dependency-name: docker/login-action
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

Bumps [korthout/backport-action](https://github.com/korthout/backport-action) from 1.4.0 to 2.0.0.
- [Release notes](https://github.com/korthout/backport-action/releases)
- [Commits](https://github.com/korthout/backport-action/compare/v1.4.0...v2.0.0

)

---
updated-dependencies:
- dependency-name: korthout/backport-action
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

Bumps [docker/build-push-action](https://github.com/docker/build-push-action) from 4c1b68d83ad20cc1a09620ca477d5bbbb5fa14d0 to fdf7f43ecf7c1a5c7afe936410233728a8c2d9c2.
- [Release notes](https://github.com/docker/build-push-action/releases)
- [Commits](https://github.com/docker/build-push-action/compare/4c1b68d83ad20cc1a09620ca477d5bbbb5fa14d0...fdf7f43ecf7c1a5c7afe936410233728a8c2d9c2

)

---
updated-dependencies:
- dependency-name: docker/build-push-action
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

Signed-off-by: David Bauer <mail@david-bauer.net>

gluon-radv-filterd: replace malloc with calloc

Rouven Czerwinski authored 1 year ago and Emantor committed 1 year ago

Allocation of the router structure for newly detected router
advertisements was done using malloc and selectively clearing some of
the structure fields. However the redirect boolean was never set to 0,
which means that during update_redirect, we would depend on the random
initialization value of the structure.

This means that sometimes ebtables-tiny wouldn't add the correct rules
for the advertised routes.

build: fix duplicate building of host-tools

ci: update branch-pattern matching

Upstream introduced two different methods for determining the state of a
package within the OpenWrt buildsystem. While both are based around the
md5 hash-function, one taks filename & mtime into account while the
other one uses the actual md5 hash of the file-content.

Ever wondered why Gluon suddenly took considerably longer to build?
The messy part is how the build-system chooses which method to use. This
is based around the AUTOREMOVE configuration. Gluon sets this variable
conditionally when built with GLUON_AUTOREMOVE set to 1.

Enter the Gluon build-system. It first compiles Lua, without the
AUTOREMOVE configuration passed to OpenWrt. This compiles the packages
with the old hash-method based around filename & mtime. Afterwards, it
builds with AUTOREMOVE enabled, changing the hash-function and
rebuilding all host-packages.

Fix this by setting AUTOREMOVE for both build-processes according to the
setting of GLUON_AUTOREMOVE.

Link: https://github.com/openwrt/openwrt/commit/53a08e37437972ba0a8fbf953a93a70a6b784ef4



Signed-off-by: David Bauer <mail@david-bauer.net>

Also known in Germany as Gigacube CAT20

It makes sense to run CI build-tests in case the CI itself is altered.

Signed-off-by: David Bauer <mail@david-bauer.net>

docs: fix typos, change letter case and remove whitespace characters

Add a workflow-dispatch trigger to the build-workflow to enable
triggering build-tests on branches not covered from the match
pattern.

Signed-off-by: David Bauer <mail@david-bauer.net>

In #2997 it was pointed out the current branch-trigger matches more
branches than the release-branches. Retrict the match-pattern to only
cover release-branches

Also only trigger builds on the next-branch and not branches prefixed
with this name.

Link: https://github.com/freifunk-gluon/gluon/pull/2997#issuecomment-1771076385



Signed-off-by: David Bauer <mail@david-bauer.net>

actions: improve docker image build-process

Prefer packages from Gluon feeds to upstream feeds

Also build the docker-container whan creating pull-requests. Keep the
pull-request triggered builds from pushing to the container registry.

Signed-off-by: David Bauer <mail@david-bauer.net>

We don't want OpenWrt packages to replace Gluon packages by accident;
the same logic applies to packages from site feeds.

This gives site feeds a higher precedence than gluon/packages, but that
is unlikely to cause any issues. Gluon base packages still have an even
higher precedence.

To avoid getting surprised again by a (possibly incompatible) OpenWrt
package replacing one of ours, move our own feed to the front, so it has
higher precedence than openwrt/{packages,routing}.

Only push the container to ghcr in case the repository is owned by the
freifunk-gluon organization.

THis avoids failing CI on forks.

Signed-off-by: David Bauer <mail@david-bauer.net>

lantiq-xrx200: mark target as broken

CI: Fix target filters, add CI check

modules: update gluon

Cherry-pick v2023.1.1 release notes to master

ce2e6ac1937a simple-tc: fix kmod dependencies

`make update-ci` is very fast, so we can run it unconditionally.

This reverts commit c418b7bb.

Our CI builds do not use the Docker image, so adding the Dockerfile to
the filter does not make sense. In addition, the entry was missing in
generate-target-filters.py, so it would have been removed when the
filters were regenerated.

modules: update to latest HEAD