Jim Alles
2016-12-23 01:06:55 UTC
Hi.
I am not familiar with operating PXE boot.
I am not clear on the meaning of your "Server IP = " line.
I am looking closely at
http://www.thekelleys.org.uk/dnsmasq/docs/dnsmasq-man.html.
In your range line, it seems the range you define is 10.161.0.0 to
10.161.255.254, and your 10.161.254.158 <http://10.161.254.158/24> is in
that range.
The network number 10.161.254.0/24 is also in that range.
Don't confuse a network host address with a network number.
You previously said "I've configured dnsmasq to reply on subnet=
10.160.37.0/24, ", but I am not sure dnsmasq understood.
You did not show an interface with 10.160.37.0/24 configured.
I think maybe dnsmasq has a right to be confused?
The hosts on the wire should have all the same netmask (network number)
except for unusual cases.
could you please post your dnsmasq.conf?
And Merry Christmas to you, and yours!
Jim A.
I am not familiar with operating PXE boot.
I am not clear on the meaning of your "Server IP = " line.
I am looking closely at
http://www.thekelleys.org.uk/dnsmasq/docs/dnsmasq-man.html.
In your range line, it seems the range you define is 10.161.0.0 to
10.161.255.254, and your 10.161.254.158 <http://10.161.254.158/24> is in
that range.
The network number 10.161.254.0/24 is also in that range.
Don't confuse a network host address with a network number.
You previously said "I've configured dnsmasq to reply on subnet=
10.160.37.0/24, ", but I am not sure dnsmasq understood.
You did not show an interface with 10.160.37.0/24 configured.
I think maybe dnsmasq has a right to be confused?
The hosts on the wire should have all the same netmask (network number)
except for unusual cases.
could you please post your dnsmasq.conf?
And Merry Christmas to you, and yours!
Jim A.
Hi Jim, thank you very much for your feedback,
yup it does sound netmask related although I still think it's a bug and
not just a misconfiguration issue.
Server IP =10.161.254.158/24
dhcp-range=10.161.254.0,proxy,255.255.0.0
Then I restarted dnsmasq while networking was up, and it still replied to
the DHCP clients, even though it shouldn't, as the /16 network that I
configured is different from the /24 that I was using, right?
Merry Christmas!
yup it does sound netmask related although I still think it's a bug and
not just a misconfiguration issue.
Server IP =10.161.254.158/24
dhcp-range=10.161.254.0,proxy,255.255.0.0
Then I restarted dnsmasq while networking was up, and it still replied to
the DHCP clients, even though it shouldn't, as the /16 network that I
configured is different from the /24 that I was using, right?
Merry Christmas!
I am fuzzy on this, I have not haz coffee, so this is just to suggest a
I think, if dnsmasq has to guess at an IP range, it considers the
_class_ of network the IP address it is given. so an address
192.168.12.20 becomes 192.168.12.0/24 <http://192.168.12.0/24>
your address is in a class A network. If you want a /24 subnet, tell
dnsmasq /24.
just a guess.
Merry Christmas!
I think, if dnsmasq has to guess at an IP range, it considers the
_class_ of network the IP address it is given. so an address
192.168.12.20 becomes 192.168.12.0/24 <http://192.168.12.0/24>
your address is in a class A network. If you want a /24 subnet, tell
dnsmasq /24.
just a guess.
Merry Christmas!