Feature #25158
openSniff DHCP and TFTP network traffic and add them into audit
Description
Interesting idea which is done by MaaS is to sniff network traffic (we would do this via proxy) and report it back as events. This can be then nicely presented in the Host - Audit page. A host requested DHCP IP address, requested TFTP file etc. This can be extended to more services etc.
- https://github.com/maas/maas/blob/master/scripts/dhcp-monitor
- https://github.com/maas/maas/blob/master/scripts/network-monitor
- https://github.com/maas/maas/blob/master/scripts/beacon-monitor
Updated by Lukas Zapletal over 6 years ago
- Related to Tracker #25156: Ideas from MaaS added
Updated by Marek Hulán over 6 years ago
By audit you mean log right? not the audits we display in UI or is that the goal?
Updated by Lukas Zapletal over 6 years ago
In MaaS you really see it in a host detail (node detail) on events page (we have audits for the same). So I was really thinking Foreman audits table, with host associated records so we can show them easily per-host.
I still think that all audits are subject of storing outside of RDBM, I know there is some extra work around associations but we have grown by far out of scope of the audited gem. But this is a different topic :-)
Updated by Timo Goebel over 6 years ago
I love this feature, would really help to see what happens under the hood. Ideally, we could also enrich this data with access to templates, e.g. what https://github.com/ShimShtein/foreman_build_history does.
We actually don't need to sniff network packets to get the dhcp information. dhcpd can call scripts when certain events happen.