Reduce the possible range in Kconfig to the half of the possible range.
E.g. setting job to be run every 40minutes is not trivial and */40 will
not work. Instead it will run the job at minute 0, then 40, then again
at 0 (after 40min, then after 20min).

Signed-off-by: Adam Wujek <dev_public@wujek.eu>

And fix two typos in the script itself

Signed-off-by: Adam Wujek <dev_public@wujek.eu>

Signed-off-by: Adam Wujek <dev_public@wujek.eu>

To be reported by SNMP as SNMPv2-MIB::sysContact.0 and SNMPv2-MIB::sysLocation.0

Signed-off-by: Adam Wujek <dev_public@wujek.eu>

Signed-off-by: Adam Wujek <dev_public@wujek.eu>

Signed-off-by: Adam Wujek <dev_public@wujek.eu>

Don't start radiousvlan if CONFIG_RVLAN_DAEMON is not present in dot-config

Signed-off-by: Adam Wujek <dev_public@wujek.eu>

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

This simply sends SIGUSR1 to radiusvlan and sorts the output file.

Example:

wri2 (001bc5090845 <-> 001bc509007d): state configured, vlan 4094, pid 0, fd -1
wri3 (001bc5090846 <-> 00e04c1bfd8d): state configured, vlan 31, pid 0, fd -1
wri4 (000000000000 <-> ): state down, vlan 0, pid 0, fd -1
wri5 (000000000000 <-> ): state down, vlan 0, pid 0, fd -1
wri6 (000000000000 <-> ): state down, vlan 0, pid 0, fd -1
wri7 (000000000000 <-> ): state down, vlan 0, pid 0, fd -1
wri8 (000000000000 <-> ): state down, vlan 0, pid 0, fd -1
wri9 (000000000000 <-> ): state down, vlan 0, pid 0, fd -1
wri10 (000000000000 <-> ): state down, vlan 0, pid 0, fd -1
wri11 (000000000000 <-> ): state down, vlan 0, pid 0, fd -1
wri12 (000000000000 <-> ): state down, vlan 0, pid 0, fd -1
wri13 (000000000000 <-> ): state down, vlan 0, pid 0, fd -1
wri14 (000000000000 <-> ): state down, vlan 0, pid 0, fd -1
wri15 (000000000000 <-> ): state down, vlan 0, pid 0, fd -1
wri16 (000000000000 <-> ): state down, vlan 0, pid 0, fd -1
wri17 (000000000000 <-> ): state down, vlan 0, pid 0, fd -1
wri18 (000000000000 <-> ): state down, vlan 0, pid 0, fd -1

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

The full set of /etc/raddb/dictionary* is overkill, we only need
a few symbols from these three files, if we run radclient.

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

[Thanks a lot to Enkhbold Ochirsuren of GSI who traced back a strange
behaviour to the "printf" incompatibility].

This removes "printf -v <outputvar> <format> ..." which is only
available in bash.

These needless incompatible extensions to standard commands are a
source of endless headaches. New features must spit an error when
unavailable (i.e., bash people should add vprintf, not break printf,
imho)

In this case, my previous "fix" to this file was incomplete, because
I fixed a bashism but didn't see this other one.

Also, this changes the shebang to call sh (which is already done by rcS:
only the interactive execution now uses sh instead of bash).

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

In sh, string comparison for equality is "=", not "==". Bash accepts
either operator but suggests to use "=" for posix conformance.
Our /bin/sh is currently busybox, which accepts "==" like bash, but
if you use ash or dash it fails:

   $ CONFIG_FOO=y
   $ if [ "$CONFIG_FOO" = "y" ]; then echo ok; fi
   ok
   $ if [ "$CONFIG_FOO" == "y" ]; then echo ok; fi
   dash: 3: [: y: unexpected operator

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

There is a monit-related problem in commit 9bc9dd16

.

The commit renames /etc/init.d/lldpd.sh into /etc/init.d/lldpd.bash
whle adding a single stanza. Try "git diff e61eb08 9ebc5e2" to
see the difference.

But monit still uses the old name. Instead of changing monit
(a two-liner, but adds noise because of .bash), this renames back
the file to .sh and removes the needless bashism in the new stanza.

Please note that calling stuff ".bash" makes no sense (suffixes
make no sense most of the time!). The only thing rcS does is checking
if the name is "*.sh", to just read it in the current shell instead
of executing. So anything not ".sh" is executed, we don't need to
special case .bash, .py or whatever.

Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

RX LLDP frames worked without any change.

Signed-off-by: Michal Wasiak <michal.wasiak@gmail.com>

Signed-off-by: Kinga Wujek <dev_public@wujek.eu>

Signed-off-by: Kinga Wujek <dev_public@wujek.eu>

Maciej Lipinski authored 4 years ago and Grzegorz Daniluk committed 4 years ago

Some deamons/etc that log messages to syslog do not specify facility.level
in their messages. The logger is configured to parse the message looking
for facility.level (option: --prio-prefix). If the message does not include
If no facility.priority is specified, the logger will use the one specified
after -p, this is now provided. For example, PPSi does not specify
facility.priority in messages (hopefully, this will change), without
"-p daemon.info", it was reported as user.info. If user wishes to,
he/she can override. This is the default config

This reverts commit 9c8412e3.

S59leap_seconds_file_update is already there to call the script at boot
time.

Setting the options to force dot-config/IP over DHCP can
be dangerous. Until now, the switch would wait endlessly
in an infinite loop.

This commit introduces a way to escape the loop. This can
be done by connecting to the back UART and pressing any
key.

- New script to generate the VLAN kconfig
- Allows raw configuration for vlan ports
- New key for PTP VID

As monit process is started after other processes, it does not take into
account  the 'unmonitor' messages sent from start scripts (ldap.sh,
...). This generates error messages at startup.

To avoid that, the configuration of monit is set now dynamically in the
apply_dotconfig script. All disabled processes are then removed from the
configuration to avoid errors due to process start order.
Also the first monitoring cycle is postponed by 30s at startup.

If dot-config is read remotly using DHCP for the URL, the host name in
the URL is not well substitute.
The fix forces the update of "hostname" when the script
dhcp_get_filename.sh is called.

When the configuration indicates that the network is  forced to use the
DHCP service for its setup (CONFIG_ETH0_DHCP=y), the script waits
forever the availability of the DHCP service.

In the other cases, the behavior remains unchanged.

When the dot-config file is read at startup using the DHCP service to
get the server IP address, the script waits forever the availability of
DHCP service in the following case :
- CONFIG_DOTCONF_SOURCE_FORCE_DHCP=y AND CONFIG_ETH0_DHCP=y

CONFIG_ETH0_DHCP: Set to indicate that the network is forced to use DHCP
for its setup.

In the other cases, the behavior stay unchanged.

- ARB_GM correspond to clock class 13.
- Interface changed with assembly_ppsi_conf.sh :
   - The clock class number is always defined in dot-config.
assembly_ppsi_conf.sh uses it instead of the timing mode.
   - The PTP options (accuracy, variance, timeSource) can be overwritten
and KConfig proposes always the default ones depending of the timing
mode.