User Tools

Site Tools


meta:template_uci

Template UCI

The uci configuration file /etc/config/wireless is provided by the ??? package. This file is responsible for defining wireless devices and wireless networks. Note, that not all precompiled images contain the wireless functions. After installing the packages, reboot and proceed with the procedure documented in Regenerate Configuration.

or

The uci configuration file /etc/config/etherwake is provided by the etherwake package and defines hosts to wake when starting the /etc/init.d/etherwake init script. An alternative opkg-package is: wol.

or

The system configuration contains basic settings for the whole router. Larger subsystems such as the network configuration, the DHCP and DNS server, and similar, have their own configuration file. See dhcp, dropbear.

or

The timeserver config holds individual time servers and pools 1) that support the older time protocol for the rdate hotplug script.

FIXME Try to make the wiki entry as complete as possible. Especially the tables. If you do not know something or are uncertain, leave things blank or insert ???, so this is obvious! Somebody is going to insert the missing piece of the puzzle sooner or later. Of course, until the missing info is being inserted into the cloze text, the wiki entry will be quite useless. But somebody with the required knowledge and technical expertise may be too lazy to write the whole thing by himself. Cloze text could help here. Try to get missing info/background info in the forum, so your wiki page can be of help soon.

Sections

Below is an overview of the section types that may be defined in the firewall configuration. A minimal firewall configuration for a router usually consists of one defaults section, at least two zones (lan and wan) and one forwarding to allow traffic from lan to wan.

The config section type dnsmasq determines values and options relevant to the overall operation of dnsmasq and the DHCP options on all interfaces served. The following table lists all available options, their default value, as well as the corresponding dnsmasq command line option. See the dnsmasq man page for further details.

Section1

The section1 section declares …

FIXME This table should help get things done. So the types do not need to be exact, e.g. you could write ip address, mac address or port instead of integer.
Name Type Required Default Description
aname string yes (none) Specify all valid values! Look here internal link for related info.
bname boolean yes no Whether to start on boot up
cname list no (none) A list of stings/numbers separated by space, no commas
dname integer yes (none) Specify the available Bandwidth in Kilobite/sec (not Kebibit/sec)
ename integer yes (none) The TCP port on which to listen on (have a look at: List of TCP and UDP port numbers)
fname integer no (none) The maximum amount of space allocated to … in MiB (see Binary_prefix)
gname string yes (none) The interface to listen on
ename string no (none) ???

Section2

The section1 section declares …

Name Type Required Default Description
aname string yes (none) Bla bla bla

Examples

Sometimes it is far easier to extract the wanted information from some examples, rather then from reading the entire wiki. Even if the wiki is short. But you don't have to include examples.

Static Lease

Define a static lease for a host with the MAC address 00:a0:24:5a:33:69 and assign the IP address 192.168.1.230 and the hostname example-host to it.

config 'host'
	option 'name' 'example-host'
	option 'ip'   '192.168.1.230'
	option 'mac'  '00:a0:24:5a:33:69'

Custom Domain

Define a custom domain name and the corresponding PTR record - assigns the IP address 192.168.1.140 to the domain name typhoon and construct an appropriate reverse record 140.1.168.192.in-addr.arpa.

:!: Note that this currently only works for IPv4 addresses and that this functionality is not present in release prior to 8.09.2 .

config 'domain'
	option 'name' 'typhoon'
	option 'ip'   '192.168.1.140'

TFTP Boot

Direct BOOTP requests to the TFTP server at the IP address 192.168.1.2 and use /tftpboot/pxelinux.0 as boot file name.

config 'boot'
	option 'filename'      '/tftpboot/pxelinux.0'
	option 'serveraddress' '192.168.1.2'

Multiple DHCP options

Multiple DHCP options can be configured under a single dhcp_option object. In this case, option 66 (tftp-server) and option 150 (multiple tftp servers) were used for a Cisco Callmanager deployment.

config 'dhcp' 'lan'
        option 'interface' 'lan'
        option 'start' '62'
        option 'limit' '192'
        option 'leasetime' '600h'
        list 'dhcp_option' '66,172.16.60.64'
        list 'dhcp_option' '150,172.16.60.64'

Using plain dnsmasq.conf

It is possible to mix the traditional /etc/dnsmasq.conf configuration file with the options found in /etc/config/dhcp.

The dnsmasq.conf file does not exist by default but will be processed by dnsmasq on startup if it is present. Note that options in /etc/config/dhcp take precendence over dnsmasq.conf since they are translated to command line arguments.

Regenerate Configuration

To rebuild the configuration file, e.g. after installing a new wireless driver, remove the existing wireless configuration (if any) and use the wifi detect command with stdout redirected to the /etc/config/wireless file:

rm -f /etc/config/wireless wifi detect > /etc/config/wireless

This will populate your configuration file with some basic values, adequate for your hardware, you can base your wireless configuration on.

next_whatever

bla bla bla

Notes

If you have this and that problem, see Bug #7433.

If samba does not start, try adding your router's name and ip in /etc/hosts. (see also http://forum.openwrt.org/viewtopic.php?id=5401)

Consult the Forum for further https://forum.openwrt.org/viewtopic.php?pid=124669#p124669.

1) The selected pools have a lot of servers supporting the time protocol, but not all servers of a pool must support it. With the selected list complete sync failures are extremely rare.
meta/template_uci.txt · Last modified: 2011/02/24 03:16 (external edit)