l0crian1

> ntopng seems to propagate the policy to nProbe as expected: > > {"policy":{"id":3,"default_marker":"pass","markers":{"continents":[],"categories":[],"countries":[],"hostnames":{"test.com":"drop"},"protocols":[]},"name":"Pool 2 rules","flow_risk":{"marker":"drop","bitmap":0},"root":0}} > > we need to check on the nProbe side if this is honoured...

Thanks @cardigliano! Quick question on both methods for host filter (definitions and rules syntax), is it just blocking DNS requests with those (sub)domains, or will it also block on the...

I ran into this issue as well when helping someone with an issue they were having. The behavior is not as simple as the peering comes up when it shouldn't,...

> @ton31337, @l0crian1 > > Could you please explain, why this is a buggy scenario? I don't know if I'd fully classify it as a bug, but the behavior is...

After some further testing, blocks against custom protocols work if they're hosts. 'ip', 'tcp/udp', and 'nbpf' do not work, though they do show as being identified in the log (except...

> This has been fixed, please update and let us know I tested this. Working great for UDP/TCP, but if I use IP for a protocol, the engine doesn't match...