Open t3chn0m4g3 opened 3 years ago
You're seeing this because this used to be a debug-level message rather than a warning until recently.
The fix is to remove ifOutUNcastPkts
from the template, but read on if you want to keep it.
When @pudii added the IEC104 template, their IF-MIB (or maybe the device they modelled the template after) must have included ifOutUNcastPkts
. However, the common IF-MIB definition does not. But the latter is the IF-MIB that's likely installed on your system or that Conpot has downloaded on-demand.
So, to keep ifOutUNcastPkts
you need to find an IF-MIB definition that contains ifOutUNcastPkts
.
Put differently, since (what appears to be) the canonical IF-MIB does not include ifOutUNcastPkts
I would classify the warning as a bug and remove the OID from all Conpot templates.
@t3chn0m4g3 how exactly did you integrate the MIB into conpot? I tried, but I wasn't able to do it at all.
@soso288 I did it, so you do not have to. You can see this in the docker folder for T-Pot.
Thanks for your fast answer. I think I did it the same way (1. download IF-MIB 2. extend the template 3. start conpot with -m "MIB-directory" parameter) but the MIBBrowser I'm using is only showing the default MIB and "snmpInPkts, snmpOutPkts, snmpInBadVersions..." with value=0 after that. What could be the problem?
The reason was given in the comment of @srenfo.
Thank you I was able to fix it
For IEC104 I am getting the following warning:
I am using the following MIB database:
Do you have any suggestions?