Thanks, please report it upstream - many thanks!
@dibdot is it ok to combine doh and https dns proxy? And why does doh block https://one.one.one.one ?
Because it's also a DoH endpoint.
I don't know, I'm not using crappy DoH at all.
Yes, I also use https-dns-proxy on the router and have banip with DoH as one of the enabled feeds.
BanIP will only set firewall blocking on the client side and never block the router itself. DoH feed blocks known DoH public servers and set by default to port 80 and 443. https-dns-proxy won't be affected.
2 Likes
I reported to their e-mail but no reply so far.
1 Like
Hi,
I started noticing this error since yesterday:
processing for feed 'cinsscore.v4' failed, rc: 4
Try to get in touch with them. Maybe you'll have better chances. Their website works fine but I received no reply from their support email.
2 Likes
They have a contact email on the link on the header, but there is a different one on the footer.
I submitted a ticket at https://helpdesk.nomicnetworks.com/
1 Like
It's working again. They answered:
"...Thanks for bringing this to our attention.
The issue was escalated to our engineering team and should be fixed now..."
6 Likes
Hello everyone, I am having trouble fetching feeds (doh, hagezi) while in 'allowlistonly'
I can fetch both of them while not in 'allowlistonly'
Here is my config:
config banip 'global'
option ban_enabled '1'
option ban_debug '0'
option ban_autodetect '1'
list ban_logterm 'Exit before auth from'
list ban_logterm 'luci: failed login'
option ban_fetchretry '20'
option ban_nicelimit '0'
option ban_filelimit '1024'
option ban_deduplicate '1'
option ban_nftpriority '-150'
option ban_icmplimit '0'
option ban_synlimit '0'
option ban_udplimit '0'
option ban_nftpolicy 'memory'
option ban_nftretry '5'
option ban_blockpolicy 'drop'
option ban_nftloglevel 'warn'
option ban_logprerouting '1'
option ban_loginbound '1'
option ban_logoutbound '1'
option ban_loglimit '100'
option ban_logratelimit '0'
option ban_autoallowlist '1'
option ban_autoallowuplink 'subnet'
option ban_autoblocklist '1'
option ban_allowlistonly '1'
list ban_feed 'doh'
list ban_feed 'hagezi'
option ban_autoblocksubnet '1'
list ban_feedout 'blocklist'
list ban_feedout 'doh'
list ban_feedout 'hagezi'
list ban_vlanblock 'br-lan'
list ban_trigger 'gem'
list ban_trigger 'iot'
list ban_trigger 'lan'
list ban_trigger 'tv'
list ban_trigger 'wan'
list ban_trigger 'wan6'
option ban_nftcount '1'
option ban_fetchcmd 'uclient-fetch'
option ban_protov4 '1'
list ban_ifv4 'wan'
list ban_feedin 'allowlist
That's by design. In allowlistonly mode banIP only builds the allow side — local allowlist plus external allowlist feeds (ban_allowurl) — and skips external blocklist feeds like doh/hagezi, since everything not on the allowlist is blocked anyway. See the readme for details ... and the processing log is also clear, e.g. "skip external feeds in allowlistonly mode" ...
I configured BanIP to only block outgoing but it is showing Wan In block for banIP/pre-ct/ . WHat is it and how to stop it ?