snmp_get_next works only when requesting oid is valid. Otherwise it fails to
find next entry.

Due to the above the snmpwalk works only when the walk is started from
the existing oid. Since snmp walk scans only oids in the current branch,
there was a need to create a special oid .1.3.

$ snmpwalk -On -c public -v 1 192.168.1.20 1.3
.1.3.6.1.2.1.1.5.0 = STRING: "wrc"
.1.3.6.1.2.1.25.1.1.0 = Timeticks: (792773) 2:12:07.73
.1.3.6.1.2.1.25.1.2.0 = Hex-STRING: 07 B2 00 01 05 00 00 00
.1.3.6.1.4.1.96.100.7.5.1.15.1 = Counter32: 445
.1.3.6.1.4.1.96.100.7.5.1.16.1 = INTEGER: 10
.1.3.6.1.4.1.96.100.7.5.1.17.1 = INTEGER: 174810
.1.3.6.1.4.1.96.100.7.5.1.18.1 = INTEGER: 191115
.1.3.6.1.4.1.96.100.7.5.1.19.1 = INTEGER: 157655
Timeout: No Response from 192.168.1.20

NOTE: Timeout message appears becasue there is no responce from node when
wrong packet is sent.
Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

Move SNMP just after syslog.
Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

--add defines of ASN types
--add 5 object from wrsPtpTable
Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

The "community" string is public. We have tree items only: the host
name, the date and uptime.

The code is designed to make it simple any addition. But we only have
snmpget support, not snmpwak (i.e. "get next" query).

This is run on an host build (CONFIG_HOST_PROCESS) where the time and
date are not related to the real world:

   # snmpget -v 1 -c public 192.168.16.1 .1.3.6.1.2.1.1.5.0
   SNMPv2-MIB::sysName.0 = STRING: wrc
   # snmpget -v 1 -c public 192.168.16.1 .1.3.6.1.2.1.25.1.2.0
   HOST-RESOURCES-MIB::hrSystemDate.0 = STRING: 1970-0-1,19:52:34.0
   # snmpget -v 1 -c public 192.168.16.1 .1.3.6.1.2.1.25.1.2.0
   HOST-RESOURCES-MIB::hrSystemDate.0 = STRING: 1970-0-1,19:53:2.0
   # snmpget -v 1 -c public 192.168.16.1 .1.3.6.1.2.1.25.1.1.0
   [...] hrSystemUptime.0 = Timeticks: (94193300) 10 days, 21:38:53.00
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

/var/lib/mibs/ietf/SNMPv2-TC

DateAndTime ::= TEXTUAL-CONVENTION
    DISPLAY-HINT "2d-1d-1d,1d:1d:1d.1d,1a1d:1d"
    STATUS       current
    DESCRIPTION
            "A date-time specification.

            field  octets  contents                  range
            -----  ------  --------                  -----
              1      1-2   year*                     0..65536
              2       3    month                     1..12
              3       4    day                       1..31
              4       5    hour                      0..23
              5       6    minutes                   0..59
              6       7    seconds                   0..60
                           (use 60 for leap-second)
              7       8    deci-seconds              0..9
              8       9    direction from UTC        '+' / '-'
              9      10    hours from UTC*           0..13
             10      11    minutes from UTC          0..59

            * Notes:
            - the value of year is in network-byte order
            - daylight saving time in New Zealand is +13

            For example, Tuesday May 26, 1992 at 1:30:15 PM EDT would be
            displayed as:

                             1992-5-26,13:30:15.0,-4:0

            Note that if only local time is known, then timezone
            information (fields 8-10) is not present."
    SYNTAX       OCTET STRING (SIZE (8 | 11))
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

Improve sfp handling
Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

To update an entry when SFP database is in the eeprom, particular entry
is searched then simply updated.
On the other hand, when SFP database is in the flash simple update is
not possible. First old database is copied to the memory, then updated in
memory. After, the erase of the entire flash block is performed. At the end
updated information is written into the flash.
Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

These stats will be used by SNMP.
Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

Use git config --get-all user.name as an build author, if not available use
user@hostname.
Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

Additionally use type checking
Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

It was neither used nor successfully updated (there was no erase before write).
To keep code backward compatible sfp's database is shifted by sizeof(sfpcount)
from the beginnig of the partition.
Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

By making struct wr_minic non static it is possible for mini SNMP to get RX/TX
counters' values directly from the memory instead of writing a separate
function that will call minic_get_stats. Avoiding extra function saves about
100 bytes.
Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

It happened that sdbfs_open_id returned error after 2 consecutive adds to
the SFP database using storage_get_sfp function (behaviour not seen when using
shell commands).
It looks like the problem was that reads were started before writes were
finished.
Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

Return 0 when successful, otherwise < 0.
Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

--Don't use "static char pn" top store sfp's pn.
--Print error when unable to read SFP
Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

EE_BASE_INIT did not include t24p and sfpcount. Due to that init script was overwriten
by adding the 4th SFP. Limit number of SFP in the database to 3. Keep init script's
starting address unchanged for backward compatibility.
SDB is not affected. Use maximum 4 SFPs in the database when SDB is used.
Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

For other parties using the stats interface with the softpll we need
the minimal file that can be easily used in other projects (like SNMP on
the wr-switch).

Move to the softpll_export.h:
--struct spll_stats
--defines of seq_state from softpll_ng.c (SEQ_* and AUX_*)
--defines of align_state from spll_external.c (ALIGN_*)
--defines of mode from softpll_ng.h (SPLL_MODE_*)
Signed-off-by: Adam Wujek <adam.wujek@cern.ch>

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

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

"-I." is there, so instead of "../lib/ipv4.h" prefer <lib/ipv4.h>.

I thought moving ipv4.h to include, but then the name is possibly ambiguous
with other files in the -I search path. Thus I wanted to move
it from lib/ipv4.h to include/wrc-ipv4.h but that would require several
files to be changed.
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

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

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

(one is just a comment update: most of that stanza was not true any more)
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

A WR socket registers using a specific mac address and the receiving code
uses the mac address to match the frame.  This is going to be a problem
with the new PTP code, as pdelay frames use a different mcast mac address.
Moreover, if we go to UDP, stuff gets worse.

Packet filter rules are already in place for the new mac addresses, and
we now need to relax the checking in the software stack.

As a side effect, we avoid a number of broadcast frames, because wrpc-sw
now replies to unicast ARP requests.

What happened before:

   16:27:07 00:0b:ab:7c:8e:4a > 00:26:7b:00:04:18 who-has ...107 tell ...200
   16:27:08 00:0b:ab:7c:8e:4a > 00:26:7b:00:04:18 who-has ...107 tell ...200
   16:27:09 00:0b:ab:7c:8e:4a > 00:26:7b:00:04:18 who-has ...107 tell ...200
   16:27:12 00:0b:ab:7c:8e:4a > ff:ff:ff:ff:ff:ff who-has ...107 tell ...200
   16:27:12 00:26:7b:00:04:18 > 00:0b:ab:7c:8e:4a ...107 is-at 00:26:7b:00:04:18

what happens now:

   16:42:27 00:0b:ab:7c:8e:4a > 00:26:7b:00:04:18 who-has ...107 tell ...200
   16:42:27 00:26:7b:00:04:18 > 00:0b:ab:7c:8e:4a ...107 is-at 00:26:7b:00:04:18
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

This commit removes the requirement for ARP frames to be broadcast
in the no-vlan case.  The simplified rule-set of a vlan setup already
accepts ARP unicast, and no harm is done.

Although we do not make ARP  requests so we won't receive unicast
replies, hosts do send unicast requests, to refresh an ARP entry
that is going to expire.

The next commit enacts this feature in software, as a side effect
of supporting pdelay PTP.
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

This is incompatible with the previous implementation

 - sequence number is 32 bits
 - frames are 1,2,3 not 0,1,2 (so to be *more* incompatible)
 - no fake latency values are printed if frames are lost
 - the message is one line instead of two, and cleaner too
 - the sender reminds it's sending every 10s.

The receiver's messages now include the sequence number, so we can
match different receivers on a network.  Also, The sender's message
report both TAI and sequence, so we can related frames to the time of
day.
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

This adds a tool to check the latency in the network. It is selected
at build time (config) time.  If you select CONFIG_LATENCY_PROBE you
are then asked for a CONFIG_LATENCY_ETHTYPE.

The sender node sends three frames, as broadcast in that ethertype
within the current vlan (or no vlan).  The first frame is at priority
7, the second at priority 6, and the third includes the egress
timestamps for the former ones. Each group has a sequence number
and group identifier.

If the tool is built in wrc.bin, every node acts as a receiver. To
enable a sender issuing the set of frames every 5 seconds, use "ltest 5".
To disable use "ltest 0".

The receiver prints the measured latency, and warns if it receives
frames that are not in the proper order, using the sequence and frame
type fields.

This is a successful run crossing two wr switches:

    latency prio7: 5142.775
    latency prio6: 4998.775
    latency prio7: 4822.773
    latency prio6: 5142.773
    latency prio7: 5142.771
    latency prio6: 5286.771

Later on, we'll make the thing less verbose, and we'll have threshold
to signal a problem if the network went slow. Currently we just print
all collected data.
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

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

This commit adds the Kconfig mechanism and the pfilter rules.

The latency test socket transmists frames of a specific ether type;
the receiver must receive all such frames.  To minimize the load on the
packet filter, this adds a single rule: we already accept all PTPv2
frames, so we now "OR" to this the new ethernet type.   If the feature
is configured off, the rule uses the same PTPv2 ethertye, thus
turning in practice into a NOP.
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>

This is used by the latency measurement, to send high-priority frames
Signed-off-by: Alessandro Rubini <rubini@gnudd.com>