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
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
with hostname (option ignored)
--dhcp-host=02:00:ac:10:00:11,set:foo,set:bar,set:baz,set:poo,set:mee,172.16.0.10,node1,infinite
Is it a bug or expected behavior?
Best Regards,
Andrei Kvapil
On Tue, Aug 4, 2020 at 4:09 PM kvaps wrote:
>
> On Tue, Aug 4, 2020 at 1:36 PM Geert Stappers
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
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
orking:
--dhcp-option=option:broadcast,172.16.0.255
numeric one is working fine:
--dhcp-option=28,172.16.0.255
Best Regards,
Andrei Kvapil
On Tue, Jun 9, 2020 at 9:27 PM Geert Stappers wrote:
>
> On Tue, Jun 09, 2020 at 09:10:11AM +0200, kvaps wrote:
> > Hi,
> >
> >
Hi,
I'm using Dnsmasq version 2.80 from on Alpine Linux 3.11.5 and I faced
with the strange issue:
When I change the SIADDR option for my pxe-clients, the Broadcast
address (option 28) is also changed to the same value.
my configuration:
# cat /etc/dnsmasq.d/dhcp-opts/ltsp1
uses leader election to prevent running multiple
DHCP-servers in one time.
Hopefully you'll find this useful:
https://github.com/kvaps/dnsmasq-controller/
- kvaps
___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
http
Simon,
You're amazing, thank you so much!
- kvaps
On Mon, Jan 6, 2020 at 12:06 AM Simon Kelley
wrote:
> On 30/12/2019 11:51, kvaps wrote:
> > Hi Simon,
> >
> > We're happy to use dnsmasq for organize network booting in Kubernetes,
> > it have everything need: D
ength 4
This is single port mode:
IP 172.17.0.2.56296 > 172.17.0.1.69: 22 RRQ "/some_file" netascii
IP 172.17.0.1.69 > 172.17.0.2.56296: 15 DATA block 1
IP 172.17.0.2.56296 > 172.17.0.1.69: 4 ACK block 1
- kvaps
On Tue, Dec 31, 2019 at 8:45 AM Kurt H Maier wrote:
> On Mon,
://github.com/kubernetes/kubernetes/issues/26718
On Tue, Dec 31, 2019, 07:20 john doe wrote:
> On 12/30/2019 6:34 PM, kvaps wrote:
> > On Mon, Dec 30, 2019 at 2:42 PM john doe wrote:
> >
> >> Isn't the below flag what you want from (1):
> >>
> >> "--tftp-po
> dnsmasq -d --enable-tftp --tftp-port-range=1069,1069
No way, because in this case it should also listen on 1069 port.
- kvaps
On Mon, Dec 30, 2019 at 9:11 PM Geert Stappers wrote:
> On Mon, Dec 30, 2019 at 06:36:49PM +0100, kvaps wrote:
> > On Mon, Dec 30, 2019 at 2:42 PM joh
ange=69,69
It reports an error:
dnsmasq-tftp: unable to get free port for TFTP
when I try to download any file from it
- kvaps
___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
.
In this way, the TFTP-packets can be simple NAT'ed back to the client side.
Take a look on unique features for go-tftp implementation:
https://github.com/vcabbage/go-tftp#unique-features
And its command line client:
https://github.com/kvaps/trivialt/
Best regards
- kvaps
14 matches
Mail list logo
