...
- INTEGER in ASN.1 is always signed, so when doing the BER encoding of such a value, one must add a leading zero for large numbers, otherwise interpreted as negative (2's complement). This is exactly what the faulty device doesn't do. If one likes to play around with such things a bit, there is https://lapo.it/asn1js/.
- tcpdump's output is not really correct; it seems to try to "fix" the value. One can do this by hand, BTW: -471450490 + 2^32 = 3823516806, which are the values we see above. This "fixing" is, in fact, incorrect; I guess it's tcpdump trying to be nice to the reader.
- The decoding on the Checkmk side is done by a rather standard library, which behaves in a totally correct way, so there is not much there that can be done on our side.
In a nutshell: Contact the manufacturer of your device; perhaps there is a firmware update or something like that which that fixes their bug.
Related articles
...
| Filter by label (Content by label) |
|---|
| showLabels | false |
|---|
| max | 5 |
|---|
| spaces | CON |
|---|
| showSpace | false |
|---|
| sort | modified |
|---|
| reverse | true |
|---|
| type | page |
|---|
| cql | label = in ("event_console","snmp","troubleshooting") and type = "page" and space = "CONKB" |
|---|
| labels | event_console |
|---|
|
...