Wireguard Unbound DNS Access List
-
Hello,
I have created a new, third Wireguard Interface. The clients, which connect to that new tunnel, cannot access the unbound server.
The others tunnel work fine for the clients regarding access to unbound.Then I found these settings and wonder, why my third new wireguard tunnel has not been added hier automatically?
When are those entries generated and why could one of my tunnels be missing?
-
@renegade Is it working now with you manually created list? What are the ip-addresses of those new clients?
-
@Bob-Dig Yes, I added it manually and it works. Cost me some headache the last hours ;-)
Range for tunnel 3 is:
10.252.1.0/24Tunnel 1 and 2, where the generation was automatically:
-
@renegade I don't have this list so I don't get it. It looks like you created that list by yourself. But why are there the ranges in it that worked in the beginning?
-
@Bob-Dig That's what I also wonder about.
I am sure, they were added automatically. Maybe by an older PfSense+ version. -
@renegade I have both, CE and plus and none is showing this. So get rid of this I guess.
