Closed dmgeurts closed 2 years ago
When did you deploy it? Did you use main or dev branch?
dev branch, and I think I've found the issue. We restrict the domains servers can connect to. So the new source hadn't been added to the firewall rules yet. Dumb ass user error.
But then I'm now struggling to get the format of the regex right for the following feed: https://urlhaus.abuse.ch/downloads/rpz/
What I initially had was: ^([A-Za-z0-9\._\-]+[A-Za-z])\ CNAME\ \.\ ;\ (Malware\ download|Test\ entry).*$
How does one debug the ioc2rpz process? It would be great to be able to query the sources in ioc2rpz.gui.
But then I'm now struggling to get the format of the regex right for the following feed:
It's Erlang's regex (https://www.erlang.org/doc/man/re.html) + you may need to escape the backslash it if you enter it in the GUI.
I'm using this regex (for urlhaus) ^([A-Za-z0-9\.]+) CNAME
on the community website.
How does one debug the ioc2rpz process? It would be great to be able to query the sources in ioc2rpz.gui.
The easies way to start erl shell with rebar3 shell
command. It will "compile" sources and start the service with provided configuration and in CLI you will be able to take a look on data in the ets tables (e.g. sources).
Other option to connect to a running node via CLI (erl).
Feeds data also available via API /api/[:api_ver]/feed/:rpz
ioc2rpz logs that the zone transfer went fine. However, the client throws errors.
Server logs:
However the client complains:
And when using dig:
I have other zones using the exact same TSIG key just fine, same ioc2rpz server and same clients (2 clients both complaining of the same issue)