Skip to content
Snippets Groups Projects
Select Git revision
  • experimental default protected
  • nrb/airmax-test
  • v2023.2.4-ffs
  • nrb/ar9344-reset-sequence
  • autinerd/experimental-openwrt-24.10
  • v2023.2.3-ffs
  • v2023.2.2-ffs
  • v2023.2-ffs
  • v2023.1-ffs
  • v2022.1.4-ffs
  • feature/addMikrotikwAP
  • v2022.1.3-ffs
  • v2021.1.2-ffs
  • v2022.1.1-ffs
  • master protected
  • v2021.1.1-ffs
  • nrb/gluon-master-cpe510
  • v2021.1-ffs
  • v2020.2.3-ffs
  • nrbffs/fastd-remove-delay
  • experimental-2025-05-18
  • experimental-2025-05-18-base
  • experimental-2025-05-15
  • experimental-2025-05-15-base
  • experimental-2025-05-13
  • experimental-2025-05-13-base
  • experimental-2025-05-08
  • experimental-2025-05-08-base
  • experimental-2025-05-05
  • experimental-2025-05-05-base
  • experimental-2025-05-02
  • experimental-2025-05-02-base
  • experimental-2025-05-01
  • experimental-2025-05-01-base
  • experimental-2025-04-29
  • experimental-2025-04-29-base
  • experimental-2025-04-27
  • experimental-2025-04-27-base
  • experimental-2025-04-26
  • experimental-2025-04-26-base
40 results

check_site.lua

Blame
    • Matthias Schiffer's avatar
      4b8251c9
      gluon-core: initialize interfaces role configuration · 4b8251c9
      Matthias Schiffer authored
      The new configuration generates sections iface_single/lan/wan in
      /etc/config/gluon. These sections usually refer to a sysconfig-controlled
      interface list, but adding custom sections with verbatim interfaces names
      is also possible.
      
      Each interface section contains a list of roles. The supported roles are
      'client', 'uplink' and 'mesh'. Multiple roles can be configured on the
      same interface (for example the old 'mesh_on_wan' setting would become
      'uplink'+'mesh').
      
      'client' is subsumed by any other role configured on the same interface
      ('client'+'mesh' is equivalent to 'mesh'). This property is important, as
      it allows the Wired Mesh settings in gluon-web-network to simply add and
      remove the mesh role without having to care what other roles are set -
      so in the default setup, this would switch between 'client' and
      'client'+'mesh' for the LAN interface.
      
      By default, the WAN interface has role 'uplink' and the LAN interface
      'client'; if only a single interface exists, the roles from the WAN
      interface are used by default. The default for each of the three
      interfaces (WAN/LAN/single) can be changed separated in site.conf,
      superseding the old mesh_on_wan, mesh_on_lan and single_as_lan settings.
      gluon-core: initialize interfaces role configuration
      Matthias Schiffer authored
      The new configuration generates sections iface_single/lan/wan in
      /etc/config/gluon. These sections usually refer to a sysconfig-controlled
      interface list, but adding custom sections with verbatim interfaces names
      is also possible.
      
      Each interface section contains a list of roles. The supported roles are
      'client', 'uplink' and 'mesh'. Multiple roles can be configured on the
      same interface (for example the old 'mesh_on_wan' setting would become
      'uplink'+'mesh').
      
      'client' is subsumed by any other role configured on the same interface
      ('client'+'mesh' is equivalent to 'mesh'). This property is important, as
      it allows the Wired Mesh settings in gluon-web-network to simply add and
      remove the mesh role without having to care what other roles are set -
      so in the default setup, this would switch between 'client' and
      'client'+'mesh' for the LAN interface.
      
      By default, the WAN interface has role 'uplink' and the LAN interface
      'client'; if only a single interface exists, the roles from the WAN
      interface are used by default. The default for each of the three
      interfaces (WAN/LAN/single) can be changed separated in site.conf,
      superseding the old mesh_on_wan, mesh_on_lan and single_as_lan settings.