Mirrors
/
aredn
mirror of https://github.com/aredn/aredn.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
aredn/files/etc/arednsysupgrade.conf

28 lines
854 B
Plaintext
Raw Normal View History

bugfix: We need to only pull a small selection of files over through sysupgrade instead of all config files. opkg config can cause issues on OS upgrade among others. ref AREDN->ticket:131
2015-07-09 10:25:00 -06:00
# This file contains a list of files to retain over a sysupgrade with "Keep Settings" in the GUI.
# This list will be used instead of the list normally used by sysupgrade.
/etc/config.mesh/_setup
/etc/config.mesh/_setup.dhcp.dmz
/etc/config.mesh/_setup.dhcp.nat
/etc/config.mesh/_setup.ports.dmz
/etc/config.mesh/_setup.ports.nat
/etc/config.mesh/_setup.services.dmz
/etc/config.mesh/_setup.services.nat
aredn: enhancement: Nat mode aliases Aliases in NAT mode allows the node admin to create alias names for hosts on the LAN and then use those for creating port forwarding rules. The aliases DO NOT effect the rest of the mesh network and are not propagated via OLSR. NAT Mode aliases are only usable on the local LAN where the IP addresses are known and routable only on the subnet. Since the NAT hides these IP addresses or the node masquerades, other mesh nodes and devices by definition only know about the node’s hostname. Thus aliases on the LAN in NAT mode are not propagated by OLSR across the mesh. You _CANNOT_ use an alias name in a service listing. You _will_ be able to set an alternate hostname for any host on the nodes' LAN however. A host named `CBY45-DELLLAPTOP` can also be known as `wxc-shack-laptop`. It may make remembering which host is which a bit easier. Since OLSR does not propagate the alias, the "Do Not Propagate" checkbox while in NAT Mode is hidden.
2020-10-07 17:20:59 -06:00
/etc/config.mesh/aliases.dmz
/etc/config.mesh/aliases.nat
bugfix: vtund was missing from arednsysupgrad.conf
2015-07-10 19:56:30 -06:00
/etc/config.mesh/vtun
Include tunnels by default (#302) * Include tunnels by default * Tunnels are always installed so no longer need this flag
2022-03-17 19:57:48 -06:00
/etc/config.mesh/network_tun
Add "Advanced config" page (#237) * initial commit * feature: advanced configuration page fixes #230 * add help page updates * added menu links to perlfunc.pm * add default value for serverpath * move "Reset to Firstboot" button from setup page to advancedconfig page * secure page minor ui changes * center the help icon * implement callback capabilities pre/post * hardening uci calls to prevent command injection attacks * moved settings to custom aredn uci file * resolve shellcheck warnings
2018-10-25 20:06:05 -06:00
/etc/config.mesh/aredn
A simple way to keep a user swconfig override across upgrades (#481)
2022-08-16 13:03:13 -06:00
/etc/aredn_include/swconfig.user
Optionally include static routes (and preserve them across upgrades)
2022-08-26 08:15:20 -06:00
/etc/aredn_include/static_routes
bugfix: We need to only pull a small selection of files over through sysupgrade instead of all config files. opkg config can cause issues on OS upgrade among others. ref AREDN->ticket:131
2015-07-09 10:25:00 -06:00
/etc/dropbear/dropbear_dss_host_key
/etc/dropbear/dropbear_rsa_host_key
bugfix: ssh keys not saving across sysupgrade
2015-11-16 13:44:52 -07:00
/etc/dropbear/authorized_keys
aredn: preserve custom firewall rules across sysupgrade groups with custom rules created in /etc/local/mesh-firewall for echolink, ampr.net, and other integrations with internet based appications can preserve rules across a firmware upgrade by locating the custom rules in this directory using a file named 59-custom-rules
2018-09-06 19:11:17 -06:00
/etc/local/mesh-firewall/59-custom-rules
bugfix: We need to only pull a small selection of files over through sysupgrade instead of all config files. opkg config can cause issues on OS upgrade among others. ref AREDN->ticket:131
2015-07-09 10:25:00 -06:00
/etc/firewall.user
/etc/group
/etc/hosts
/etc/local/services
/etc/local/uci/hsmmmesh
/etc/passwd
/etc/shadow