"
So do you see that same message
(unbound), jid xx, uid xx, was killed: failed to reclaim memory
Also, _Mike, are you using blocklists?
(unbound), jid xx, uid xx, was killed: failed to reclaim memory
Also, _Mike, are you using blocklists?
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Pages1
#2
26.7 Series / Re: UDP Broadcast Relay – Blocking outbound broadcasts on specific interfaces
August 26, 2026, 03:04:46 PM
I misread your question and mistakenly assumed you were using the os-mdns-repeater plugin while you are using the os-udpbroadcastrelay plugin.
That doesn't really change the story though.
This plugin does have the source IP option which appears to be a hack intended for a different purpose. I don't know how it interacts with what you are seeing from the firewall side.
But again, it doesn't change the story because even if you change the source IP address, you're still changing the address of both the queries and responses and that would not allow you to block queries while allowing responses and vice versa.
That doesn't really change the story though.
This plugin does have the source IP option which appears to be a hack intended for a different purpose. I don't know how it interacts with what you are seeing from the firewall side.
But again, it doesn't change the story because even if you change the source IP address, you're still changing the address of both the queries and responses and that would not allow you to block queries while allowing responses and vice versa.
#3
26.7 Series / Re: UDP Broadcast Relay – Blocking outbound broadcasts on specific interfaces
August 25, 2026, 05:52:21 PM
If a machine wants to resolve an mDNS name, it sends a multicast message to port 5353. All the other machines see this message, and the ones that want to claim that name respond with a multicast message to port 5353.
What the relay does is simply listen to all these messages and for every message that comes in on one of the configured interfaces, repeat it on all of the other configured interfaces.
So with simple firewall rules you can't really distinguish between the requests and replies and what you want to achieve is not possible. You would have to use a different relay that allows you to be more selective. I don't know if that exists and if the results would be what you want.
What the relay does is simply listen to all these messages and for every message that comes in on one of the configured interfaces, repeat it on all of the other configured interfaces.
So with simple firewall rules you can't really distinguish between the requests and replies and what you want to achieve is not possible. You would have to use a different relay that allows you to be more selective. I don't know if that exists and if the results would be what you want.
#4
26.7 Series / Re: Unbound stopps suddenly
August 25, 2026, 03:21:41 PM
The message "failed to reclaim memory" is sent by the operating system kernel if it runs out of memory and kills a process to avoid crashing the complete system.
I can see two reasons:
So I suggest checking if the system has a reasonable amount of memory to work with, and if not, you either have to do less (less large blocklists, disable things that consume large amounts of memory) or increase the amount of available memory.
I can see two reasons:
- The hardware or VM just has too little memory for what you're trying to do.
- You're loading a lot of large block lists which consume unexpectedly large amounts of memory.
So I suggest checking if the system has a reasonable amount of memory to work with, and if not, you either have to do less (less large blocklists, disable things that consume large amounts of memory) or increase the amount of available memory.
Pages1
