System configuration

System

The system section contains settings that apply to the most basic operation of the system, such as the hostname, the time zone, and how and where to write logging information to. The default settings are:

config 'system'
	option 'hostname'	'lede'
	option 'timezone'	'UTC'

These options can be set in the system section:

Name	Type	Required	Default	Description
hostname	string	no	lede	The hostname for this system. Avoid points, even if they are within quotes. For example ' my.hostname ' will show only the ' my ' part
buffersize	integer	no	kernel specific	Size of the kernel message buffer.
conloglevel	integer	no	7	Number between 1-8. The maximum log level for kernel messages to be logged to the console. Only messages with a level lower than this will be printed to the console. Higher level messages have lower log level number. Highest level messages are ones with log level 0. If you want more verbous messages in console put conloglevel to 8 if you want less messages lower conloglevel to 4 or even less.
cronloglevel	integer	no	5	The minimul level for cron messages to be logged to syslog. 0 will print all debug messages, 8 will log command executions, and 9 or higher will only log error messages.
klogconloglevel	integer	no	7	The maximum log level for kernel messages to be logged to the console. Only messages with a level lower than this will be printed to the console. Identical to conloglevel and will override it.
log_buffer_size	integer	no	16	Size of the log buffer of the "new" procd based system log, that is output by the logread command. Tried 32 kB, more should be possible.
log_file	string	no	no log file	File to write log messages to (type file). The default is to not write a log in a file. The most often used location for a system log file is /var/log/messages.
log_ip	IP address	no	(none)	IP address of a syslog server to which the log messages should be sent in addition to the local destination.
log_port	integer	no	514	Port number of the remote syslog server specified with log_ip.
log_prefix	string	no	(none)	Adds a prefix to all log messages send over network.
log_proto	string	no	udp	Sets the protocol to use for the connection, either tcp or udp.
log_remote	bool	no	1	Enables remote logging.
log_size	integer	no	16	Size of the file or circular memory buffer in KiB.
log_trailer_null	bool	no	0	Use \0 instead of \n as trailer when using TCP.
log_type	string	no	circular	Either circular or file.
timezone	string	no	UTC	The time zone that date and time should be rendered in by default.
zonename	string	no	UTC	Only useful when using glibc and zoneinfo! (LIBC_USE_EGLIBC, PACKAGE_zoneinfo-) The time zone that date and time should be rendered in by default. Suppose you want to use Brussels' timezone, set this value to Europe/Brussels. Possible values can be found by running (cd /usr/share/zoneinfo; find )

Name

Type

Required

Default

Description

hostname

string

no

lede

The hostname for this system. Avoid points, even if they are within quotes. For example ' my.hostname ' will show only the ' my ' part

buffersize

integer

no

kernel specific

Size of the kernel message buffer.

conloglevel

integer

no

7

Number between 1-8. The maximum log level for kernel messages to be logged to the console. Only messages with a level lower than this will be printed to the console. Higher level messages have lower log level number. Highest level messages are ones with log level 0. If you want more verbous messages in console put conloglevel to 8 if you want less messages lower conloglevel to 4 or even less.

cronloglevel

integer

no

5

The minimul level for cron messages to be logged to syslog. 0 will print all debug messages, 8 will log command executions, and 9 or higher will only log error messages.

klogconloglevel

integer

no

7

The maximum log level for kernel messages to be logged to the console. Only messages with a level lower than this will be printed to the console. Identical to conloglevel and will override it.

log_buffer_size

integer

no

16

Size of the log buffer of the "new" procd based system log, that is output by the logread command. Tried 32 kB, more should be possible.

log_file

string

no

no log file

File to write log messages to (type file). The default is to not write a log in a file. The most often used location for a system log file is /var/log/messages.

log_ip

IP address

no

(none)

IP address of a syslog server to which the log messages should be sent in addition to the local destination.

log_port

integer

no

514

Port number of the remote syslog server specified with log_ip.

log_prefix

string

no

(none)

Adds a prefix to all log messages send over network.

log_proto

string

no

udp

Sets the protocol to use for the connection, either tcp or udp.

log_remote

bool

no

1

Enables remote logging.

log_size

integer

no

16

Size of the file or circular memory buffer in KiB.

log_trailer_null

bool

no

0

Use \0 instead of \n as trailer when using TCP.

log_type

string

no

circular

Either circular or file.

timezone

string

no

UTC

The time zone that date and time should be rendered in by default.

zonename

string

no

UTC

Only useful when using glibc and zoneinfo! (LIBC_USE_EGLIBC, PACKAGE_zoneinfo-*) The time zone that date and time should be rendered in by default. Suppose you want to use Brussels' timezone, set this value to Europe/Brussels. Possible values can be found by running (cd /usr/share/zoneinfo; find *)

Remote Time (ntp)

| | In /etc/config/system busybox-rdate (was invoked by scripts) has been replaced with busybox-nptd (can run as a daemon) to avoid race condition and also to use current NTP. The remote time is since configured in /etc/config/system and not in /etc/config/timeserver any longer.

WARNING: Old scripts first checked if a lease time server is defined for the interface in the network config.
WARNING: If not available or syncing fails, then it searches for time servers in the timeserver config that are either explicitly defined for that interface or via the global setting in the system config.

config 'timeserver' 'ntp'
	list 'server'     '0.openwrt.pool.ntp.org'
	list 'server'     '1.openwrt.pool.ntp.org'
	list 'server'     '2.openwrt.pool.ntp.org'
	list 'server'     '3.openwrt.pool.ntp.org'
	option enable_server 0

There are at least two valid option defined for the timeserver ntp section:

Name	Type	Required	Default	Description
server	list of hostnames	no	(none)	Defines the pool of NTP servers to poll the time from. If the list is empty, the builtin NTP daemon is not started.
enable_server	boolean	no	0	You can put busybox-ntpd in\\ client mode only: by defining at least one host to server and puting enable_server 0 \\ client & server mode: by putting enable_server to 1, (busybox-ntpd listens to UDP 123 by default),\\ server mode only: by not defining any servers in the config and just put enable_server 1 (ntpd will answer with the time of the router)

Name

Type

Required

Default

Description

server

list of hostnames

no

(none)

Defines the pool of NTP servers to poll the time from. If the list is empty, the builtin NTP daemon is not started.

enable_server

boolean

no

0

You can put busybox-ntpd in\\ client mode only: by defining at least one host to server and puting enable_server 0 \\ client & server mode: by putting enable_server to 1, (busybox-ntpd listens to UDP 123 by default),\\ server mode only: by not defining any servers in the config and just put enable_server 1 (ntpd will answer with the time of the router)

Leds

LEDs are represented by entries in the sys filesystem. You can check which LEDs are available in the /sys/class/leds directory. The name of an entry typically consists of the name of the hardware providing the LED (the router model), the color of the LED, and it’s designation (usually the label on the case). Some LEDs can show different colors. In this case, you will find one entry per color.

The LED can be controlled by various events in the system, which is selected by the trigger option. Depending on the trigger, additional options must be specified.

First of all, you need to know which triggers are available for a led, to do that simply look at the trigger file of that led. Example:

cat /sys/class/leds/**LED**/trigger
[none] timer default-on netdev morse usbdev

None

The LED is always in default state. Unlisted LED are default OFF, so this is only useful to declare a LED to be always ON.

Name	Type	Required	Default	Description
default	integer	no	0	LED state before trigger: 0 means OFF and 1 means ON
sysfs	string	yes	(none)	LED device name
trigger	string	yes	(none)	none

Name

Type

Required

Default

Description

default

integer

no

0

LED state before trigger: 0 means OFF and 1 means ON

sysfs

string

yes

(none)

LED device name

trigger

string

yes

(none)

none

Timer

The LED blinks with the configured on/off frequency.

opkg install kmod-ledtrig-timer

Name	Type	Required	Default	Description
default	integer	no	0	LED state before trigger: 0 means OFF and 1 means ON
delayoff	integer	yes	(none)	How long (in milliseconds) the LED should be off.
delayon	integer	yes	(none)	How long (in milliseconds) the LED should be on.
sysfs	string	yes	(none)	LED device name
trigger	string	yes	(none)	timer

Name

Type

Required

Default

Description

default

integer

no

0

LED state before trigger: 0 means OFF and 1 means ON

delayoff

integer

yes

(none)

How long (in milliseconds) the LED should be off.

delayon

integer

yes

(none)

How long (in milliseconds) the LED should be on.

sysfs

string

yes

(none)

LED device name

trigger

string

yes

(none)

timer

Default-on

The LED is ON. Deprecated, use default=1 trigger=none instead.

opkg install kmod-ledtrig-default-on

Name	Type	Required	Default	Description
default	integer	no	0	LED state before trigger: 0 means OFF and 1 means ON
sysfs	string	yes	(none)	LED device name
trigger	string	yes	(none)	default-on

Name

Type

Required

Default

Description

default

integer

no

0

LED state before trigger: 0 means OFF and 1 means ON

sysfs

string

yes

(none)

LED device name

trigger

string

yes

(none)

default-on

Heartbeat

The LED flashes to simulate actual heart beat thump-thump-pause. The frequency is in direct proportion to 1-minute average CPU load.

opkg install kmod-ledtrig-heartbeat

Name	Type	Required	Default	Description
default	integer	no	0	LED state before trigger: 0 means OFF and 1 means ON
sysfs	string	yes	(none)	LED device name
trigger	string	yes	(none)	heartbeat

Name

Type

Required

Default

Description

default

integer

no

0

LED state before trigger: 0 means OFF and 1 means ON

sysfs

string

yes

(none)

LED device name

trigger

string

yes

(none)

heartbeat

Flash Writes

The LED flashes as data is written to flash memory.

Name	Type	Required	Default	Description
default	integer	no	0	LED state before trigger: 0 means OFF and 1 means ON
sysfs	string	yes	(none)	LED device name
trigger	string	yes	(none)	nand-disk

Name

Type

Required

Default

Description

default

integer

no

0

LED state before trigger: 0 means OFF and 1 means ON

sysfs

string

yes

(none)

LED device name

trigger

string

yes

(none)

nand-disk

Network Activity

The LED flashes with link status and/or send and receive activity on the configured interface.

opkg install kmod-ledtrig-netdev

Name	Type	Required	Default	Description
default	integer	no	0	LED state before trigger: 0 means OFF and 1 means ON
dev	string	yes	(none)	Name of the network interface which status should be reflected
mode	string	yes	(none)	One or more of link, tx, or rx, seperated by spaces
sysfs	string	yes	(none)	LED device name
trigger	string	yes	(none)	netdev

Name

Type

Required

Default

Description

default

integer

no

0

LED state before trigger: 0 means OFF and 1 means ON

dev

string

yes

(none)

Name of the network interface which status should be reflected

mode

string

yes

(none)

One or more of link, tx, or rx, seperated by spaces

sysfs

string

yes

(none)

LED device name

trigger

string

yes

(none)

netdev

WiFi Activity

The LED flashes on events triggered in physical interface, rather than in software network interface. Besides phy triggers have more events, it also provides possibility of static LED setup in case you want to monitor your 2.4 GHz radio (phy0 usually) and 5 GHz radio (phy1 usually) separately. netdev can’t guarantee this distinguishing since wlan0 may be referring to 2.4 GHz or 5 GHz radio based on current network setup.

Name	Type	Required	Default	Description
default	integer	no	0	LED state before trigger: 0 means OFF and 1 means ON
sysfs	string	yes	(none)	LED device name
trigger	string	yes	(none)	phy0rx, phy0tx, phy0assoc, phy0radio or phy0tpt

Name

Type

Required

Default

Description

default

integer

no

0

LED state before trigger: 0 means OFF and 1 means ON

sysfs

string

yes

(none)

LED device name

trigger

string

yes

(none)

phy0rx, phy0tx, phy0assoc, phy0radio or phy0tpt

phy0rx - flashes on reception.
phy0tx - flashes on transmission.
phy0assoc - flashes on client association.
phy0radio - (WARNING: hard to say what this is supposed to do; this option did nothing on my tl-wr1043nd with Backfire 10.03.1, r29592 and Attitude Adjustment r32793)
phy0tpt - flashes slowly and steadily on network activity.in comparison to energetic flashes of tx and rx modes

USB Device

The LED turns ON if USB device is connected.

opkg install kmod-ledtrig-usbdev

Name	Type	Required	Default	Description
default	integer	no	0	LED state before trigger: 0 means OFF and 1 means ON
dev	string	yes	(none)	Name of USB device to monitor (in this example 1-1).
interval	integer	yes	(none)	Interval in ms when device is active.
sysfs	string	yes	(none)	LED device name
trigger	string	yes	(none)	usbdev

Name

Type

Required

Default

Description

default

integer

no

0

LED state before trigger: 0 means OFF and 1 means ON

dev

string

yes

(none)

Name of USB device to monitor (in this example 1-1).

interval

integer

yes

(none)

Interval in ms when device is active.

sysfs

string

yes

(none)

LED device name

trigger

string

yes

(none)

usbdev

To find out device name use logread to search for it or list /sys/bus/usb/devices (for this example, there would be /sys/bus/usb/devices/1-1 device).

Morse Code

The LED signals a message using Morse code.

Requires the kmod-ledtrig-morse package.

opkg install kmod-ledtrig-morse

Name	Type	Required	Default	Description
default	integer	no	0	LED state before trigger: 0 means OFF and 1 means ON
delay	integer	no	150	Dit length in milliseconds
dev	string	yes	(none)	Name of USB device to monitor (in this example 1-1).
message	string	no	(none)	The message to signal
sysfs	string	yes	(none)	LED device name
trigger	string	yes	(none)	morse

Name

Type

Required

Default

Description

default

integer

no

0

LED state before trigger: 0 means OFF and 1 means ON

delay

integer

no

150

Dit length in milliseconds

dev

string

yes

(none)

Name of USB device to monitor (in this example 1-1).

message

string

no

(none)

The message to signal

sysfs

string

yes

(none)

LED device name

trigger

string

yes

(none)

morse

GPIO

Allows LEDs to be controlled by gpio events.

opkg install kmod-ledtrig-gpio

Name	Type	Required	Default	Description
default	integer	no	0	LED state before trigger: 0 means OFF and 1 means ON

Name

Type

Required

Default

Description

default

integer

no

0

LED state before trigger: 0 means OFF and 1 means ON

Net filter

opkg install kmod-ledtrig-netfilter

Flash LED when a particular packets passing through your machine.

For example to create an LED trigger for incoming SSH traffic:

iptables -A INPUT -p tcp --dport 22 -j LED --led-trigger-id ssh --led-delay 1000

Then attach the new trigger to an LED on your system:

echo netfilter-ssh > /sys/class/leds/<ledname>/trigger

Name	Type	Required	Default	Description
default	integer	no	0	LED state before trigger: 0 means OFF and 1 means ON

Name

Type

Required

Default

Description

default

integer

no

0

LED state before trigger: 0 means OFF and 1 means ON