Discussion:
[Dnsmasq-discuss] DHCP Proxy Problem
Joe Giles
2013-01-17 20:59:27 UTC
Permalink
Hi again list,

I have a PXE boot connection issue with machines on my network. Here is a little techical data:

1. PXE/DHCPProxy server - 10.226.152.70
2. MS DHCP Server 10.226.152.16
3. Using HP Procurve switches

I have DHCP Option 066 set in MS DHCP proxy to point to my PXE/DHCPProxy server (10.226.152.70).

I have added helper IPs to the procure switch because they are on a different vlan. I added the MS
DHCP server and the PXE/DHCPProxy server address as a helper IP as well.

When I launch dnsmasq, I get errors stating:

dnsmasq-dhcp[9710]: no address range available for DHCP request via 10.226.77.254 - Which is the gateway for the vlan.
But I also get:

dnsmasq-dhcp[9710]: no address range available for DHCP request via 10.226.77.253 - Which is the switch for the vlan.

My host never hits the PXE/DHCPProxy server, and I verified by using wireshark.

Here is the config for dnsmasq:


port=0
interface=eth0
listen-address=10.226.152.70,127.0.0.1
log-dhcp
tftp-root=/var/lib/tftpboot
dhcp-ignore=tag:tobeignored
dhcp-boot=pxelinux.0
dhcp-option=vendor:PXEClient,6,2b
dhcp-no-override
pxe-prompt="Press F8 for boot menu", 0
pxe-service=X86PC, "Boot from network", pxelinux
pxe-service=X86PC, "Boot from local hard disk", 0
dhcp-range=10.226.152.70,proxy
dhcp-mac=set:tobeignored,00:30:6E:4A:42:43
dhcp-mac=set:tobeignored,00:30:6E:0C:7A:C2


I think I have something not configured proporly, but have no idea what that could be. When I was testing this in my own
network area (No switches), it worked just fine. But I am not sure if there is extra configuration needed on the switches,
dnsmasq, or MS DHCP server.

Can someone give me an idea where to look?

Thanks!
Joe
Joe Giles
2013-01-18 02:01:00 UTC
Permalink
I think I found a solution to this, but need more help...

Looking around in the mailing list, I saw a thread titled:
[Dnsmasq-discuss] PXE service across subnets

And in it, the solution was to add the netmask to the end of the
dhcp-range proxy:

dhcp-range=10.226.77.255,proxy,255.255.254.0

However, we have over 50 sub networks, so would there be some "Catch
All" address I could use for this?

If not, can I add each network on a seperate line like so:

dhcp-range=10.226.77.255,proxy,255.255.254.0
dhcp-range=10.226.87.255,proxy,255.255.254.0
dhcp-range=10.226.97.255,proxy,255.255.254.0

Etc...

Thanks!
Joe
Post by Joe Giles
Hi again list,
1. PXE/DHCPProxy server - 10.226.152.70
2. MS DHCP Server 10.226.152.16
3. Using HP Procurve switches
I have DHCP Option 066 set in MS DHCP proxy to point to my PXE/DHCPProxy server (10.226.152.70).
I have added helper IPs to the procure switch because they are on a different vlan. I added the MS
DHCP server and the PXE/DHCPProxy server address as a helper IP as well.
dnsmasq-dhcp[9710]: no address range available for DHCP request via 10.226.77.254 - Which is the gateway for the vlan.
dnsmasq-dhcp[9710]: no address range available for DHCP request via 10.226.77.253 - Which is the switch for the vlan.
My host never hits the PXE/DHCPProxy server, and I verified by using wireshark.
port=0
interface=eth0
listen-address=10.226.152.70,127.0.0.1
log-dhcp
tftp-root=/var/lib/tftpboot
dhcp-ignore=tag:tobeignored
dhcp-boot=pxelinux.0
dhcp-option=vendor:PXEClient,6,2b
dhcp-no-override
pxe-prompt="Press F8 for boot menu", 0
pxe-service=X86PC, "Boot from network", pxelinux
pxe-service=X86PC, "Boot from local hard disk", 0
dhcp-range=10.226.152.70,proxy
dhcp-mac=set:tobeignored,00:30:6E:4A:42:43
dhcp-mac=set:tobeignored,00:30:6E:0C:7A:C2
I think I have something not configured proporly, but have no idea what that could be. When I was testing this in my own
network area (No switches), it worked just fine. But I am not sure if there is extra configuration needed on the switches,
dnsmasq, or MS DHCP server.
Can someone give me an idea where to look?
Thanks!
Joe
_______________________________________________
Dnsmasq-discuss mailing list
http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
Simon Kelley
2013-01-18 15:18:06 UTC
Permalink
Post by Joe Giles
I think I found a solution to this, but need more help...
[Dnsmasq-discuss] PXE service across subnets
And in it, the solution was to add the netmask to the end of the
dhcp-range=10.226.77.255,proxy,255.255.254.0
However, we have over 50 sub networks, so would there be some "Catch
All" address I could use for this?
dhcp-range=10.226.77.255,proxy,255.255.254.0
dhcp-range=10.226.87.255,proxy,255.255.254.0
dhcp-range=10.226.97.255,proxy,255.255.254.0
You can certainly do that.

As you're only using dnsmasq to do PXE, which address allocation
elsewhere, it will _probably_ work to have a single dhcp-range line with
a smaller netmask, ie

dhcp-range=10.226.0.0,255.255.0.0

Give it a try.


Cheers,

Simon.
Joe Giles
2013-01-18 16:22:01 UTC
Permalink
Post by Simon Kelley
Post by Joe Giles
I think I found a solution to this, but need more help...
[Dnsmasq-discuss] PXE service across subnets
And in it, the solution was to add the netmask to the end of the
dhcp-range=10.226.77.255,proxy,255.255.254.0
However, we have over 50 sub networks, so would there be some "Catch
All" address I could use for this?
dhcp-range=10.226.77.255,proxy,255.255.254.0
dhcp-range=10.226.87.255,proxy,255.255.254.0
dhcp-range=10.226.97.255,proxy,255.255.254.0
Hi Simon :)

This is very cool... I have added all our vlans into the script and it works like a charm!

I have some other questions about redirection, but will start another thread for that.

Thanks again!
Joe
Post by Simon Kelley
You can certainly do that.
As you're only using dnsmasq to do PXE, which address allocation
elsewhere, it will _probably_ work to have a single dhcp-range line
with a smaller netmask, ie
dhcp-range=10.226.0.0,255.255.0.0
Give it a try.
Cheers,
Simon.
_______________________________________________
Dnsmasq-discuss mailing list
http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss
Continue reading on narkive:
Loading...