-
-
Notifications
You must be signed in to change notification settings - Fork 414
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Log MODBUS/SNMPv1/v2 requests #14
Comments
Work to be done yet:
|
@glaslos Regarding logging, conpot will be covering quite a few protocols:
I am thinking of a generic approach (for hpfriends), something in the line of: //some modbus data
{'remote': ('1.2.3.4', 58988),
'data_type': 'modbus',
'data': {'request_pdu': '0f0001000801ff',
'response_pdu': '0f00010008'}}
//some snmp data
{'remote': ('1.2.3.4', 58994),
'data_type': 'snmpv2',
'data': {'request_message': '\x02\x01\x00\x04\x06public\xa1\x1a\x02\x04_\xaa\xadK\x02\x01\x00\x02\x01\x000\x0c0\n\x06\x06+\x06\x01\x02\x01\x01\x05\x00',
'response_message': '\x02\x01\x00\x04\x06public\xa24\
Any inputs/opinions on this? |
Sounds good to me. |
Are you still doing this nested per session? {'remote': ('1.2.3.4', 58988),
'data_type': 'modbus',
'session_id': 123123123,
'data': [
{
'2005-10-30 T 10:45 UTC',
'request_pdu': '0f0001000801ff',
'response_pdu': '0f00010008'
}
]
} |
yes, with some minor changes to align the data... I think modbus data would look like this when finished: {'remote': ('1.2.3.4', 58988),
'data_type': 'modbus',
'session_id': 123123123,
'data': {
'0': {
'request_pdu': '0f0001000801ff',
'response_pdu': '0f00010008'
}
'95': {
'request_pdu': '0f0001000801ff',
'response_pdu': '0f00010008'
}
'135': {
'request_pdu': '0f0001000801ff',
'response_pdu': '0f00010008'
}
}
} The keys of the data dictionary would be offset (in milliseconds). |
Whats the status on this? |
Hopefully i will throw in a few test cases for modbus/snmp logging tonight. I suggest that we move SNMP v3 logging to a separate workitem - and possibly also next milestone. |
No description provided.
The text was updated successfully, but these errors were encountered: