"2025-12-06T12:42:00 Error firewall alias resolve error IP_PublicDNS (error fetching alias url https://raw.githubusercontent.com/jpgpi250/piholemanual/master/DOHipv4.txt)"So I had missed that alias failing to update and I can see why.Quote from: Seimus on December 04, 2025, 06:57:40 PMTime based rules are not possible with the ipfw ruleset (FW > shaper > Rules) but they are possible when using the pf rules + Traffic shaping feature (FW > Rules (option Traffic Shaping)). However there is a BUG in regards of that feature for reverse-direction if NAT is involved see:Hmmm.. can you help me a little bit how this works all together?
https://forum.opnsense.org/index.php?topic=47716.msg254051
Quote from: cookiemonster on December 08, 2025, 03:22:06 PMWhat I mean is that your process is perfectly valid but unknown to us here on how it works.Quoteyes I'm keeping the list in remote server. Firewall Aliases has a rules ( URL IP's tabele) who is checking every 60 sec for update the remote black list. from this rule i got Floating who does actual restriction to the network.It is impossible to tell why "this does not work anymore", your mechanism to fetch the list I imagine is the Alias automation on OPN. But the content might not be "correct".
Before the update if I want restrict an IP, just have to add it to the remote server black list. And Firewall Aliases fetching this list automatic and blocking the new ip's.
Now this doesn't work anymore , to do so i need to go to Firewall: Diagnostics: States: find were is the new ip or IP's and manual drop it. And then the actual block comes in force.
Maybe use the Diagnostic part of the alias in OPN, to look into the table.
Or when you say "this doesn't work anymore". Does it mean nothing is fetched or something else?
Quote from: timlab55 on December 08, 2025, 02:06:28 PM[...]Even my maintenance can't get back in.[...]