- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
03-10-2017 02:29 AM
Hi @timothyyip,
if you are using all the ransomwaretracker feeds that could be normal, as the RW_* feeds already include the contents of the single TC, LY, ... feeds. Aggregators remove duplicates.
Are you seeing indicators in the output nodes now ?
03-09-2017 02:43 AM
Hi @timothyyip,
you don't see any indicator in outbound* and inbound* feeds ? when you click on the feed URLs, are they empty ?
luigi
03-09-2017 02:52 AM
Please, could you export your config text from CONFIG page using the export button and share it ?
Thanks,
luigi
03-09-2017 11:44 PM
Hi @timothyyip,
I have tried loading your config on a MM test instance and it works for me.
Which version of MM are you running ? If it's older than 0.9.32, could you update it ? If not, was it upgraded from an older version ?
Couple of notes on your config:
- as all the IP feeds are already connected to IPv4Aggregator, connection from outboundaggregator and inboundaggregator to IPv4Aggregator are not really needed.
- ransomwaretracker.RW_* feeds already contains the indicators of ransomwaretracker.TC_*, LY_*, ... You could simplify your config and keep all your indicators by removing the ransomwaretracker.TC_*, LY_* , TL_* feeds.
03-10-2017 02:29 AM
Hi @timothyyip,
if you are using all the ransomwaretracker feeds that could be normal, as the RW_* feeds already include the contents of the single TC, LY, ... feeds. Aggregators remove duplicates.
Are you seeing indicators in the output nodes now ?
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!