Recent posts

#1
netflector 0.16.0 and plugin 0.1.6 are released. The main change is addition of generic UDP relay (udp_ports, udp_groups, udp_broadcast) to support other discovery protocols (like Roon's SOOD) and peers (source_peers, target_peers) to support interfaces without multicast/broadcast domains.
#2
26.7 Series / Re: LAN unresponsive after fir...
Last post by nero355 - Today at 09:39:11 PM
This is your issue :



Dump the NIC and replace it with any Intel Quad Port NIC and you are DONE! :)
#3
General Discussion / Re: Unable to upgrade v25.7.11...
Last post by nero355 - Today at 09:31:54 PM
Quote from: chrisb on Today at 04:14:27 PMI have followed a couple of suggestions I could find, nothing resolved the problem.
Which ones exactly ?!

Most common solutions and issues as far as I know :
- Solution : Forcing IPv4 instead of IPv6 because usually the WAN does not have it's own IPv6 Prefix and that's why the connection fails.
- Issue : Mobile Connections being used and the update process failing because of it for whatever reason...
#4
General Discussion / Re: Unbound DNS hard restarts ...
Last post by franco - Today at 08:55:05 PM
> Unbound DNS performs a hard restart (losing its entire cache

Unbound hasn't lost its cache on restart by default for many years...

community/21.7/21.7:o unbound: allow to retain cache on service reload


Cheers,
Franco
#5
26.7 Series / Re: [SOLVED] GeoIP Update Beha...
Last post by meyergru - Today at 07:52:29 PM
I suppose you could ask @Monviech (Cedrik) about that - AFAIK he writes most of the documentation.
#6
26.7 Series / Re: GeoIP Update Behavior
Last post by wiring8228 - Today at 06:58:45 PM
Hey MeyerGru,

Thanks for your answer 🙂

It bothered me because I read somewhere that you would have to manually set an update task as a cron job, but I couldn't find any more information about that. On top of that, I wanted to know if there's a way to get more control over the GeoIP updates, but I guess this isn't possible for now.

Would it make sense to perhaps add a note to the documentation stating that the GeoIP data is automatically updated approximately every 24 hours?
#7
26.7 Series / Re: GeoIP Update Behavior
Last post by meyergru - Today at 05:57:02 PM
It is approximately every 24h, with the expression "if (time.time() - fstat.st_mtime) < (86400 - 90)" refering to the timestamp of the last update (see geoip.py).

But why does that bother you, when you can even update the alias on the spot via Firewall: Aliases -> Actions -> Update GeoIP?
#8
26.7 Series / Re: GeoIP Update Behavior
Last post by wiring8228 - Today at 05:41:46 PM
Unfortunately, I haven't found an answer to my question yet, even though I've looked over the source code again. Of course, I hope that the update occurs automatically at least every 24 hours, or that there is a mechanism that automatically detects when the GeoIP data has been updated and then triggers an update without further delay.
#9
26.7 Series / Re: Firewall Aliases – Functio...
Last post by wiring8228 - Today at 05:39:20 PM
I'm using a GeoIP alias that gets used in firewall rules to only allow traffic to some countries (whitelist principle).
#10
Run a connectivity audit and post the result.