Posted: Sun Mar 04, 2012 15:39 Post subject: DHCP client fail on linux (with DNSMasq activated)
Hello
I'm currently on a E4200 router. If I ever activate DNSMasq for DHCP all my Linux based dhcp client will not get the proper info (but windows client will), so they can automatically get the network info (ip, netmask, dns, ...)
It's doing the same thing on my old wrt54gl. But I know for a fact with previous revision of the dd-wrt version it was working. I can't remember with which revision it was working but it definitely was.
The weird part come here. All my windows client manage to get the DHCP info and setup the network, but all Linux based can't.
Any clue what could cause this problem ? Anyone else having this problem ?
There is a bug with DNSmasq and enabling Filter WAN NAT Redirection. Solution: use dhcpd instead of DNSmasq or disable that option. _________________ 2 times APU2 Opnsense 21.1 with Sensei
2 times RT-AC56U running DD-WRT 45493 (one as Gateway, the other as AP, both bridged with LAN cable)
3 times Asus RT-N16 shelved
E4200 V1 running freshtomato 2020.8 (bridged with LAN cable)
3 times Linksys WRT610N V2 converted to E3000 and 1 original E3000 running freshtomato 2020.8 (bridged with LAN cable)
Posted: Mon Mar 05, 2012 15:03 Post subject: Re: DHCP client fail on linux (with DNSMasq activated)
Mastah wrote:
Hello
I'm currently on a E4200 router. If I ever activate DNSMasq for DHCP all my Linux based dhcp client will not get the proper info (but windows client will), so they can automatically get the network info (ip, netmask, dns, ...)
It's doing the same thing on my old wrt54gl. But I know for a fact with previous revision of the dd-wrt version it was working. I can't remember with which revision it was working but it definitely was.
Well, then load an older version of dd-wrt onto the wrt54gl and test if it works, I don't think your problem is the dd-wrt firmware.
There is no general Linux incompatibility with dnsmasq, I' running 2 Ubuntu clients, 2 linux based sat receivers, and 2 WRT54GL behind my main router (Asus RT-N16) and none of these linux clients has any problem with pulling a dhcp lease from the Asus.
What linux flavour are you using?
Have you checked if there is any known problems with it? _________________ Kernel panic: Aiee, killing interrupt handler!
It seem to be a bug that does occur when you activate NAT "port/port range/..." forward.
I've also discovered that if you reboot the router, during it's reboot phase, it will provide proper information to DHCP client so they'll get network info (and change ethernet settings according to them)
(Take care: in the DNSMasq options should be no domain=yourdomainname entry!)
Click Apply.
Third, under Setup / Basic Setup choose:
DHCP Type: DHCP Server
DHCP Server Enable
Check Use DNSMasq for DHCP, Use DNSMasq for DNS and DHCP-Authoritative. Click Apply. _________________ 2 times APU2 Opnsense 21.1 with Sensei
2 times RT-AC56U running DD-WRT 45493 (one as Gateway, the other as AP, both bridged with LAN cable)
3 times Asus RT-N16 shelved
E4200 V1 running freshtomato 2020.8 (bridged with LAN cable)
3 times Linksys WRT610N V2 converted to E3000 and 1 original E3000 running freshtomato 2020.8 (bridged with LAN cable)