This is final error message.. after this no dns works and dnsmasq needs to
be rebooted.. I also checked google and found numerous users have same
issue back a year or more.
Error sending DHCP packet to 172.16.6.50: Resource temporarily
unavailable
l
On Tue, May 28, 2019 at 3:15 AM Russell
> "Denis" == Denis Periša writes:
Denis> There is no other dhcp in network, it's routed connection RB435G
Denis> with multiple cards wlan. this is config example:
Denis> interface=eth0 except-interface=eth1 interface=wlan3
Denis> interface=wlan0 interface=wlan1 interface=wlan2
Denis>
There is no other dhcp in network, it's routed connection RB435G with
multiple cards wlan.
this is config example:
interface=eth0
except-interface=eth1
interface=wlan3
interface=wlan0
interface=wlan1
interface=wlan2
dhcp-range=172.17.3.20,172.17.3.253,255.255.255.0,1h
Yes, dnsmasq is still running but lease is not given.. I don't know how to
debug it more.
Configuration is simple, one subnet range 192.168.0.10 to 192.168.0.200 on
wlan0 interface for example. But it's not wifi issue, local also.
It sends mail as soon as error is detected and restarts dnsmasq
Hi Denis,
I don't have such problems. Please post your configuration and device setup and
try to
get some logs. As far as I understand dnsmasq is unresponsible, but still runs?!
What do you mean with "restart messages"? Are your devices rebooting?
Regards,
Vincent Wiemann
On 27.05.19 13:43,
Hi all,
This "bug" is following me for some time now.. a year at least. I'm hoping
day after day that someone might find reason and fix it. I've set a script
that checks dnsmasq and restarts it.
-->
if ! ( dhcping -q -h 00:99:99:99:99:99 -s 10.0.0.1 ) #Jos jedna
provjera
