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-27
  • experimental-2025-05-27-base
  • 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
40 results

gluon-mesh-vpn-core

  • Clone with SSH
  • Clone with HTTPS
  • user avatar
    lemoer authored
    If a community uses different vpn providers, they typically
    assume the same MTU for the wan device underneath the VPN. As
    different VPN providers however have different overhead, the MTU
    of the VPN device differs for each provider. Therefore this
    commit makes the MTU of the VPN device provider specific.
    
    This has two advantages:
    1. The same site.conf can used to bake firmwares for different
       VPN providers (only by selecting a diferent vpn feature in the
       site.mk).
    2. We are coming closer to the option of integrating multiple VPN
       providers into one firmware.
    7c81897b
    History
    Name Last commit Last update
    ..