Summary: | dnsmasq doesn't provide ip addresses when dhcp is turned on | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Gabriel Devenyi <ace> |
Component: | New packages | Assignee: | Jon Portnoy (RETIRED) <avenj> |
Status: | RESOLVED UPSTREAM | ||
Severity: | normal | CC: | tigger |
Priority: | High | ||
Version: | 2005.0 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | Config File |
Description
Gabriel Devenyi
2005-08-05 17:57:51 UTC
(In reply to comment #0) > I set the following in dnsmasq.conf You set the following - hmm, I cannot see anything following here. I set *this* in dnsmasq.conf... I always had trouble with fridays.... dhcp-range=192.168.1.50,192.168.1.150,12h So whats going on here... Is this a configuration issue or a broken dnsmasq What version of dnsmasq? Also, can you please attach your dnsmasq.conf? Created attachment 65761 [details]
Config File
Version 2.22 configuration file, only slightly modified
Is this a gentoo bug or should I be going upstream? I don't see any uncommented dhcp-range entries in the attached dnsmasq.conf. Line above is the command I used, as I currently am running dnsmasq and dhcpd so the line is commented until I can nail down the issue. Line 110 is where I uncommented the above. One last question.. with the dhcp server enabled in dnsmasq what's the output of `netstat -pan --inet | grep dnsmasq` ? (I don't use the dnsmasq dhcp server personally and can only do limited testing here. CC'ing tigger, I seem to recall he was using dnsmasq's dhcp at some point) tcp 0 0 0.0.0.0:53 0.0.0.0:* LISTEN 24449/dnsmasq udp 0 0 0.0.0.0:33452 0.0.0.0:* 24449/dnsmasq udp 0 0 0.0.0.0:53 0.0.0.0:* 24449/dnsmasq udp 0 0 0.0.0.0:67 0.0.0.0:* 24449/dnsmasq raw 0 0 0.0.0.0:1 0.0.0.0:* 7 24449/dnsmasq (Slightly edited to make it smaller) That looks correct. Is this the only DHCP server on the network? Tried it without dhcp-authoritative? Removed dhcp-authoratative, no change, as far as other servers, definitely not, as this is my network and I know all equipment connected to it. Config looks OK, netstat looks OK, no other similar reported issues with 2.22... I'm afraid I'm going to have to send this one upstream and see what Simon has to say about it. http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss Am you sending it upstream, or am I? Probably be easier for both you and upstream if you did. I suggest mailing the dnsmasq mailing list and referencing this bug. Simon tends to be quite helpful and responsive. |