On 26/04/2018 11:24, Harald Dunkel wrote:
> maybe I am too blind to see, but apparently something like
>
> dhcp-range=em1,10.0.0.10,10.0.0.254,12h
> dhcp-range=em2,10.0.1.10,10.0.1.254,12h
>
> is not mentioned in the man page. Is it possible that the
> interface part was lost?
If you're
Looking at the patch again, I think there's a problem with the original
Ubus patch. Because of where the ubus code is called in log_packet, Ubus
broadcasts will be suppressed by --quiet-dhcp. I doubt that's intended
behaviour.
It should at least be noted the both the UBus and metrics patches are
On 24/04/18 08:30, Julian Kornberger wrote:
> On 24.04.2018 01:07, Simon Kelley wrote:
>>> Where does the DBUS raise a fatal error if support is missing? I
>>> couldn't find anything in the code.
>> src/dnsmasq.c:
> Ok, I only searched in src/option.c
>
>>> General questions:
>>> - Is there any
On 4/26/18 12:24 PM, Harald Dunkel wrote:
Hi folks,
maybe I am too blind to see, but apparently something like
dhcp-range=em1,10.0.0.10,10.0.0.254,12h
dhcp-range=em2,10.0.1.10,10.0.1.254,12h
is not mentioned in the man page. Is it possible that the
interface part was lost?
PS: is
Hi folks,
maybe I am too blind to see, but apparently something like
dhcp-range=em1,10.0.0.10,10.0.0.254,12h
dhcp-range=em2,10.0.1.10,10.0.1.254,12h
is not mentioned in the man page. Is it possible that the
interface part was lost?
Regards
Harri
On Thu, Apr 26, 2018 at 12:24:56PM +0200, Harald Dunkel wrote:
>
> maybe I am too blind to see, but apparently something like
>
> dhcp-range=em1,10.0.0.10,10.0.0.254,12h
> dhcp-range=em2,10.0.1.10,10.0.1.254,12h
>
> is not mentioned in the man page. Is it possible that the
>
On 26/04/2018 12:52, Harald Dunkel wrote:
> So it should be
>
> dhcp-range=tag:em1,10.0.0.10,10.0.0.254,12h
> dhcp-range=tag:em2,10.0.1.10,10.0.1.254,12h
>
> Or is it
>
> dhcp-range=set:em1,10.0.0.10,10.0.0.254,12h
> dhcp-range=set:em2,10.0.1.10,10.0.1.254,12h
Assuming your
On 4/26/18 1:03 PM, Chris Novakovic wrote:
If you're referring to the ability to limit particular DHCP ranges to
particular interfaces, the information's all in there (albeit admittedly
in pieces):
The tag system works as follows: For each DHCP request, dnsmasq collects a set of valid tags
On 26/04/2018 12:52, Harald Dunkel wrote:
> So it should be
>
> dhcp-range=tag:em1,10.0.0.10,10.0.0.254,12h
> dhcp-range=tag:em2,10.0.1.10,10.0.1.254,12h
>
> Or is it
>
> dhcp-range=set:em1,10.0.0.10,10.0.0.254,12h
> dhcp-range=set:em2,10.0.1.10,10.0.1.254,12h
Assuming your
While i can't give you exact configurations, i can say it's a
simple configuration on dnsmasq feeding some ipset sets based on domains
(plain simple configuration) and those sets being used by iptables rules.
While the set sizes simply doesn't matter when you have Gbs of RAM,
when
On 4/26/18 2:07 PM, Chris Novakovic wrote:
On 26/04/2018 12:52, Harald Dunkel wrote:
So it should be
dhcp-range=tag:em1,10.0.0.10,10.0.0.254,12h
dhcp-range=tag:em2,10.0.1.10,10.0.1.254,12h
Or is it
dhcp-range=set:em1,10.0.0.10,10.0.0.254,12h
11 matches
Mail list logo
