Skip to content

libremesh/network-profiles

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

network-profiles

Check out the full documentation on https://libremesh.org/development-network_profiles.html

Set of profiles for the networks using LibreMesh used by the firmware builder.

  • Each community profile goes into a directory named as the community.
  • Inside a community profile directory goes the devices profile, also split in directories
  • The files available into community/device/root/ will be copied to the output firmware binary

The expected files to be into this repository are:

  • Customized /etc/config/lime-community
  • Set of scripts to configure/fix/add small specific stuff on the system in /etc/uci-defaults/
  • SSH public keys from the community administrators in /etc/dropbear/authorized_keys
  • Any other stuff you need to customize your own community network firmware

A special file named Makefile have to be placed in the device directory community/device/Makefile, see this file as an example. This file can also be used to include a list of extra packages which will be included in the firmware.

Hacking (imagebuilder)

Supported hacks:

  • _hacks/pkg_configs: Define a list of configs to be modified in PKG_CONFIGS.
  • _hacks/pkg_conflicts: Define a list of packages to be removed in PKG_CONFLICTS.

Warn: Usable safely with imagebuilder-docker. Warn: To use it with asu, the server must support this hack.
Currently the asu server https://sysupgrade.antennine.org supports it:

  • do not returning errors if the main build was killed after the second build completes
  • prepending packages that starts with 'profile-' at the beginning of the packages list (to use it with the firmware-selector)
  • checking the manifest from a file printed in BIN_DIR/manifest instead from STDOUT

To use the defined PKG_CONFIGS or PKG_CONFLICTS include the preinst defined in _hacks/index.mk that will trigger a new build with the defined modifications, like in the example below:

include $(TOPDIR)/rules.mk

PROFILE_DESCRIPTION:=Generic libremesh metapackage
PKG_CONFIGS:=\
	CONFIG_CLEAN_IPKG=y
PKG_CONFLICTS:=\
	-dnsmasq \
	-odhcpd-ipv6only
PROFILE_DEPENDS:=\
	+profile-libremesh-suggested-packages

include ../../_hacks/index.mk
include ../../profile.mk

# call BuildPackage - OpenWrt buildroot signature

About

Set of profiles for the networks using LibreMesh

Topics

Resources

Stars

Watchers

Forks

Contributors 23