Newer
Older
Alessandro Rubini
committed
mainmenu "White Rabbit Switch configuration"
config BR2_CONFIGFILE
string "Configuration file for Buildroot"
default "wrs_release_br2_config"
help
The configuration file selects which packages are to be
included in the WRS filesystem and which are not. If
you pass a relative pathname, the build procedure will
look for it in wr-switch-sw/configs/buildroot, while
absolute pathnames are used unchanged.
If the string being passed doesn't refer to a file, the
scripts print a warning and use the default file. Incorrect
files lead to unpredicatable results.
config PPSI
bool "Use PPSi daemon"
menu "Local configuration"
config DOTCONF_URL
string "URL for a run-time replacement of dot-config"
help
The White Rabbit Switch is configured at run-time,
according to a dot-config .config file. The file
is the same .config you are defining now. If you
select an empty string, dot-config is not replaced
at run time. Otherwise, tftp://, ftp:// or http://
URLs are allowed. Names are allowed if you configured
a DNS server. The special strings IPADDR and MACADDR
are substituted before retrieving the file.
Example: "tftp//morgana/wrs-config-IPADDR"
config NTP_SERVER
string "IP address of local NTP server (empty for none)"
help
At boot time, the White Rabbit time is primed by querying
an NTP server, if any is there. Please write here the
IPV4 address (e.g.: "192.168.16.1"); an empty string
disables NTP-based priming.
config DNS_SERVER
string "static IP address of local DNS server (empty for none)"
help
Using names instead of IP addresses is sometimes handy. This
option allow to specify a static server name, that is stored
in /etc/resolv.conf, within the WRS image being built. If
the string is empty, /etc/resolv.conf is managed according
to buildroot defaults.
config DNS_DOMAIN
string "Default domain for DNS resolution"
help
If CONFIG_DNS_SERVER is being used, this option may be
useful as well.
config REMOTE_SYSLOG_SERVER
string "Send WRS syslog messages to this remote host"
help
This IP address or name, if not empty enables remote syslog
in the switch; all messages are sent to this specific host.
config REMOTE_SYSLOG_UDP
bool "Use UDP for syslog messages"
default y
help
Select UDP to send system logs. If not set, TCP is used.
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
config SNMP_TRAPSINK_ADDRESS
string "Static IP address or name where to send SNMPv1 traps"
help
If not empty, the address or name is ussed as "trapsink"
destination in the SNMP configuration file for the switch.
It empty, no v1 traps are generated. If both this and
the following TRAP2SINK_ADDRESS are set, snmpd sends two
traps (one per protocol version). Trapcommunity is "public"
(not configurable so far).
config SNMP_TRAP2SINK_ADDRESS
string "Static IP address or name where to send SNMPv2c traps"
help
If not empty, the address or name is ussed as "trap2sink"
destination in the SNMP configuration file for the switch.
It empty, no v2c traps are generated. Trapcommunity is "public"
(not configurable so far).
config SNMP_RO_COMMUNITY
string "Read-only community name for SNMP V1/V2 management"
default "public"
help
If not empty, the 'community' name is a sort of password,
that travels as clear text (we don't support encrypted SNMPv3
yet). The default is good for testing, but should be changed
for production. Please note, however, that the switch processes
SNMP only on the CPU Ethernet port (the copper "management" port).
config SNMP_RW_COMMUNITY
string "Read-write community name for SNMP V1/V2 management"
default "private"
help
If not empty, the 'community' name is a sort of password,
that travels as clear text (we don't support encrypted SNMPv3
yet). The default is good for testing, but should be changed
for production. Please note, however, that the switch processes
SNMP only on the CPU Ethernet port (the copper "management" port).
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
config WRS_LOG_HAL
string "Logging directions for the WR hal"
default "daemon.info"
help
The string can be a pathname (e.g. /dev/kmsg) or a <facility>.<level>
spefification like "daemon.debug". An empty strings is used
to represent no logging (like /dev/null). Please note that
unknown facility names will generate a runtime error on the switch.
config WRS_LOG_RTU
string "Logging directions for the RTU daemon"
default "daemon.info"
help
The string can be a pathname (e.g. /dev/kmsg) or a <facility>.<level>
spefification like "daemon.debug". An empty strings is used
to represent no logging (like /dev/null). Please note that
unknown facility names will generate a runtime error on the switch.
config WRS_LOG_PTP
string "Logging directions for the PTP server (ptpd or ppsi)"
default "daemon.info"
help
The string can be a pathname (e.g. /dev/kmsg) or a <facility>.<level>
spefification like "daemon.debug". An empty strings is used
to represent no logging (like /dev/null). Please note that
unknown facility names will generate a runtime error on the switch.
config KEEP_ROOTFS
bool "Keep generated filesystem and related script"
help
During development of build scripts, it may be useful
to keep the generated root filesystem as well as the
script used to create it. If selected, the build script
will report the actual file names at each build.
If unsusre, say N.
endmenu