Hey,
I just found that dnsmasq v2.81 have no such issue.
Hooray!
Best Regards,
Andrei Kvapil
On Tue, Aug 4, 2020 at 6:46 PM kvaps wrote:
>
> Hi Dominik,
>
> You can try my docker image for the purity of the experiment:
>
> # Working (lease issued)
> docker run --net=host -ti --rm --entrypoint=dn
Hi Dominik,
You can try my docker image for the purity of the experiment:
# Working (lease issued)
docker run --net=host -ti --rm --entrypoint=dnsmasq
docker.io/kvaps/dnsmasq-controller:v0.5.1 --no-daemon --no-hosts
--port=0 --dhcp-broadcast --dhcp-authoritative
--dhcp-range=172.16.0.1,static,inf
Hey Andrei,
On 04.08.20 16:41, kvaps wrote:
> Ok I found out that only 5 options are allowed before hostname
> specified (no more), it can be any option: hwaddr, id:client_id,
> set:tag or ipaddr but only the total amount of options should not
> exceed 5 (or 6 if hostname non-specified)
>
> 7 opti
Ok I found out that only 5 options are allowed before hostname
specified (no more), it can be any option: hwaddr, id:client_id,
set:tag or ipaddr but only the total amount of options should not
exceed 5 (or 6 if hostname non-specified)
examples:
5 options
-
no hostname (works):
--dhcp
On Tue, Aug 04, 2020 at 04:09:48PM +0200, kvaps wrote:
> On Tue, Aug 4, 2020 at 1:36 PM Geert Stappers wrote:
> > On Tue, Aug 04, 2020, kvaps wrote:
> } } I'm trying to start dnsmasq with the following option
> } }
> --dhcp-host="02:00:ac:10:00:0a,id:*,set:foo,set:bar,set:baz,172.16.0.10,node1,
On Tue, Aug 04, 2020 at 04:41:45PM +0200, kvaps wrote:
> On Tue, Aug 4, 2020 at 4:09 PM kvaps wrote:
> > On Tue, Aug 4, 2020 at 1:36 PM Geert Stappers wrote:
> > > Please try
> > > }
> > > --dhcp-host="02:00:ac:10:00:0a,id:*,set:foo:bar:baz,172.16.0.10,node1,infinite
> > > and report back.
>
On Tue, Aug 04, 2020 at 08:55:34AM -0400, wkitt...@gmail.com wrote:
> On 8/4/20 7:15 AM, Geert Stappers wrote:
> > Please try
> > }
> > --dhcp-host="02:00:ac:10:00:0a,id:*,set:foo:bar:baz,172.16.0.10,node1,infinite
> > and report back.
>
> if this is the correct format, shouldn't the related
On Tue, Aug 4, 2020 at 1:36 PM Geert Stappers wrote:
> Please try
> }
> --dhcp-host="02:00:ac:10:00:0a,id:*,set:foo:bar:baz,172.16.0.10,node1,infinite
> and report back.
>
No, this format is not working, I also found:
> The set: construct sets the tag whenever this --dhcp-host directive is
On 8/4/20 7:15 AM, Geert Stappers wrote:
Please try
}
--dhcp-host="02:00:ac:10:00:0a,id:*,set:foo:bar:baz,172.16.0.10,node1,infinite
and report back.
if this is the correct format, shouldn't the related example command line
example be
[,set:[::]]
or similar?
--
NOTE: No off-list
On Tue, Aug 04, 2020 at 12:12:10PM +0200, kvaps wrote:
> Hi!
> Does dnsmasq support setting multiple tags for the dhcp clients?
>
> I'm trying to start dnsmasq with the following option
>
>
> --dhcp-host="02:00:ac:10:00:0a,id:*,set:foo,set:bar,set:baz,172.16.0.10,node1,infinite
>
> but it r
On Tue, Aug 04, 2020 at 08:18:24AM +0700, Bernd Prager wrote:
> On 8/4/20 3:36 AM, Andrew Miskell wrote:
> > On Aug 3, 2020, at 3:06 PM, Geert Stappers wrote:
> > > On Mon, Aug 03, 2020 at 07:04:47PM +0200, No Yes No Questions wrote:
> > > > On Mon, Aug 03, 2020 at 10:44:07PM +0700, Bernd Prager w
Hi!
Does dnsmasq support setting multiple tags for the dhcp clients?
I'm trying to start dnsmasq with the following option
--dhcp-host="02:00:ac:10:00:0a,id:*,set:foo,set:bar,set:baz,172.16.0.10,node1,infinite
but it responds:
dnsmasq: bad command line options: bad DHCP host name
Best
12 matches
Mail list logo
