Generate dot1qPortVlanTable with a command:
mib2c -c mib2c.mfd.conf Q-BRIDGE-MIB::dot1qPortVlanTable
Signed-off-by: Michal Wasiak <michal.wasiak@gmail.com>

Generate dot1qVlanCurrentTable with a command:
mib2c -c mib2c.mfd.conf Q-BRIDGE-MIB::dot1qVlanCurrentTable
Signed-off-by: Michal Wasiak <michal.wasiak@gmail.com>

In the generated code MacAddress is mapped into ASN_OCTET_STR, which uses
a length as a first byte, then the content of MAC/string.
With this behaviour of ASN_OCTET_STR, the index was 1 byte longer than suppose
to be. Anyway, it is not needed to carry the length of MacAddress since it is
defined as fixed in the MIB.
Signed-off-by: Michal Wasiak <michal.wasiak@gmail.com>

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

Generate dot1qTpFdbTable with a command:
mib2c -c mib2c.mfd.conf Q-BRIDGE-MIB::dot1qTpFdbTable
Signed-off-by: Michal Wasiak <michal.wasiak@gmail.com>

Added functions were copied from rtu_stat
Signed-off-by: Michal Wasiak <michal.wasiak@gmail.com>

Remove the following OIDs, since such counters are not implemented in WRS.
--dot1dBasePortDelayExceededDiscards
--dot1dBasePortMtuExceededDiscards
Signed-off-by: Michal Wasiak <michal.wasiak@gmail.com>

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

Generate dot1dBasePortTable with a command:
mib2c -c mib2c.mfd.conf BRIDGE-MIB::dot1dBasePortTable

The data in this table is static, it does not need a cache.
Signed-off-by: Michal Wasiak <michal.wasiak@gmail.com>

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

In the generated code MacAddress is mapped into ASN_OCTET_STR, which uses
a length as a first byte, then the content of MAC/string.
With this behaviour of ASN_OCTET_STR, the index was 1 byte longer than suppose
to be. Anyway, it is not needed to carry the length of MacAddress since it is
defined as fixed in the MIB.
Signed-off-by: Michal Wasiak <michal.wasiak@gmail.com>

dot1dStaticTable with a command:
mib2c -c mib2c.mfd.conf BRIDGE-MIB::dot1dStaticTable
Signed-off-by: Michal Wasiak <michal.wasiak@gmail.com>

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

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

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

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

Only scalar objects in dot1dBase:
--dot1dBaseBridgeAddress
--dot1dBaseNumPorts
--dot1dBaseType
But without dot1dBasePortTable!

Generated with:
mib2c -c mib2c.scalar.conf BRIDGE-MIB::dot1dBase
Signed-off-by: Michal Wasiak <michal.wasiak@gmail.com>

dot1qFdbTable with a command:
mib2c -c mib2c.mfd.conf BRIDGE-MIB::dot1qFdbTable
Signed-off-by: Michal Wasiak <michal.wasiak@gmail.com>

dot1dTpFdbTable with a command:
mib2c -c mib2c.mfd.conf BRIDGE-MIB::dot1dTpFdbTable
Signed-off-by: Michal Wasiak <michal.wasiak@gmail.com>

Annoying warnings like:

In file included from ./include/libwr/hal_shmem.h:7:0,
                 from ./include/libwr/fan.h:3,
                 from ./include/libwr/switch_hw.h:6,
                 from pps_gen.c:17:
./include/libwr/generic_fsm.h: In function ‘fsm_consume_state’:
./include/libwr/generic_fsm.h:134:3: warning: implicit declaration of function ‘pr_info’ [-Wimplicit-function-declaration]
   pr_info("%s: Enter state %s\n", fsm->fsm_name, fsm_get_state_name(fsm));
   ^
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>

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

Fix the calculation of an offset in shmem when reopening shmem.
Signed-off-by: Adam Wujek <dev_public@wujek.eu>

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

add new OID: wrsStartCntRvlan
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>

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>

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>

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

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>