I just committed a patch to do this. I chose the tag "known-othernet"
just because it seemed more descriptive.
Cheers,
Simon.
On 19/04/17 19:36, Todd Sankey wrote:
> I tried a different approach. I created a patch (attached) so that the
> tag "knownother" is applied if there is a host definiti
I like this. (Almost) completely backwards compatible, obvious to use,
solves a problem. What do people think?
I think the implementation is over-complex: calling find_config() with
the context set to NULL is all that's needed to implementthe search, but
that's a detail.
Cheers,
Simon.
On 19/0
I tried a different approach. I created a patch (attached) so that the tag
"knownother" is applied if there is a host definition that applies to a
different context. In our setup, we then added "dhcp-ignore=tag:knownother".
On Wed, Mar 15, 2017 at 1:14 PM, Todd Sankey wrote:
> Our setup has two
Our setup has two wifi networks with different network addresses, one for
employees and one for guests. On the employee network, the hosts all have
static host entries that include IP addresses. The guest network has no
static host entries. What we would like to do is prevent the employee
machines
