![]() Streaming application for Linux-UVC compatible webcamsĬonfiguration files for multiple WAN routes ![]() Web server options (Busybox httpd, deprecated) Uses iptables layer7-, ipp2p- and recent-modules to block p2p/filesharing trafficĪnother idle-daemon for attached hard drives Wireless settings and wifi network definitionĪd-Hoc Configuration Protocol (AHCP) server and forwarder configurationĮ-MailRelay: simple SMTP server and proxy with POP support. Switch, interface and route configuration: Basics, IPv4, IPv6, Routes, Rules, WAN, Aliases, Switches, VLAN, IPv4/IPv6 transitioning, Tunneling NAT, packet filter, port forwarding, etc. In this case, remember that you have to login again using SSH as the device is now accessible at its new IP address!ĭnsmasq and odhcpd settings: DNS, DHCP, DHCPv6 To do this, using any text editor, such as vi, change the line This implies that solely (re)starting the executable directly, without calling the appropriate init.d script, would not behave as expected as it would not yet result in the incorporation of configuration updates into the program's standard configuration file(s).Īs an example of modifying the UCI configuration, suppose you want to change the device's IP address from the default 192.168.1.1 to 192.168.2.1. Many programs are made compatible with UCI by simply making their init.d script first update their standard program-specific configuration files, based on the updated UCI configuration in /etc/config, and then restarting the executable. Upon changing a UCI configuration file, whether through a text editor or the command line, the services or executables that are affected must be (re)started (or, in some cases, simply reloaded) by an init.d call, such that the updated UCI configuration is applied to them. UCI configuration files are also modifiable through various programming APIs (like Shell, Lua and C), which is also how web interfaces like LuCI make changes to the UCI files. You can edit the configuration files with a text editor or modify them with the command line utility program uci. OpenWrt's central configuration is split into several files located in the /etc/config/ directory.Įach file relates roughly to the part of the system it configures. Note that, for most third party programs, you should consult the program's own documentation. ![]() There are ways to disable UCI in case you want to adjust settings in the original configuration file not available through UCI, in rver you can see how to disable UCI for samba, for example.įor those non-UCI compatible programs, there is a convenient list of some non-UCI configuration files you may want to tend to. In addition, the application's configuration file is often stored in RAM instead of in flash, because it does not need to be stored in non-volatile memory and it is rewritten after every change, based on the UCI file. Thus, when starting a daemon with such a UCI-compatible initialization script, you should be aware that the program's original configuration file gets overwritten.įor example, in the case of Samba/CIFS, the file /etc/samba/smb.conf is overwritten with UCI settings from the UCI configuration file /etc/config/samba when running /etc/init.d/samba start. This is done upon running the initialization scripts in /etc/init.d/. Many packages in the OpenWrt repository have been made compatible with the UCI system.Īpplications are made UCI-compatible by simply writing the original configuration file (which is read by the program) according to the chosen settings in the corresponding UCI file. It is the main configuration user interface for the most important system settings including the main network interface configuration, wireless settings, logging functionality and remote access configuration. ![]() UCI is the successor to the NVRAM-based configuration found in the White Russian series of OpenWrt. The abbreviation UCI stands for Unified Configuration Interface, and is a system to centralize the configuration of OpenWrt services. See also: UCI defaults, Network scripting
0 Comments
Leave a Reply. |