Hi,
We had to add all our subnets to the access lists in unbound to get
resolving working between our sites.
Knut Petter
On 08/09/2016 08:53 AM, Philipp Tölke wrote:
Hi Lars, hi all,
I spooled up a Linux-VM, installed DJBs dnscache on it and have the pfSense
NAT incoming DNS-Queries on the
Hi,
Anyone else encountered this? Whenever I save my config it will add a /
to /var/etc/quagga/zebra.conf ontop of all the other prefix list
entries.
It will look like this.
log syslog
ip prefix-list ACCEPTFILTER deny /
ip prefix-list ACCEPTFILTER deny 172.16.21.0/30
Tried generating a back
On 02/10/2015 11:05 PM, Espen Johansen wrote:
A seperator might make sense. But grouping and hiding rules is a bad
idea based on my experience.
A tree structure that is allways collapsed is annoying when you need
overview of all rules.
And defaulting to a expanded look will just act as a s
On 02/10/2015 07:04 PM, Christoph Hanle wrote:
On 10.02.2015 14:44, kpolb...@olberg.name wrote:
Hi,
Is there any possibility to create "groups" or otherwise have seperators
between rules on the firewall page? Basically what I'm trying to do is
make it easier to see which rules are "connected"
Hi,
Is there any possibility to create "groups" or otherwise have seperators
between rules on the firewall page? Basically what I'm trying to do is
make it easier to see which rules are "connected" could be based on host
or service. So it would be nice to have some sort of visual seperator to
