[Dnsmasq-discuss] dhcp-range as a set doesn't seem to work for me.

2015-07-16 Thread David Cooper
Hi all,

So my question is why does the enclosed config not work? It never seems to
activate any of the sets unless I use pxe boot.

Here is some background:

I have large network. I have 11 subnets that need a dhcp proxy. I have a
Network Access Control (NAC) application that has a very limited DHCP
implementation that must be used on the registration networks. When the
techs unbox a machine, and try to image, the machine isn't known by the NAC
so it stays in the registration network. I am trying to use dnsmasq to give
bootp options to a tftpboot solution on different servers (10.99.1.72,
10.99.2.61).

I use ubuntu 14.04 LTS but removed the pre installed dnsmasq. I compiled
tarball currently on the site (2.73) using make and make install. Then
modified the /etc/init.d/dnsmasq file so it found the new location of the
file.

I am trying not to use PXE but left the information in there for reference.
If I use PXE, dnsmasq works but the filename gets the label put on and the
client tries to download SMSBoot\x64\wdsnbp.com.0 which doesn't exist.

I left the dhcp-boot in as I thought that should work and seems to be
formatted correctly if I didn't want to put the servername in my local
hosts file.

I have also included the syslog entries for my last test run to show no
sets are being done.

*** Config ***

port=0

log-dhcp

dhcp-no-override

dhcp-range=set:South, 10.201.0.0, proxy, 255.255.0.0

dhcp-range=set:South, 10.202.0.0, proxy, 255.255.0.0

dhcp-range=set:South, 10.204.0.0, proxy, 255.255.0.0

dhcp-range=set:South, 10.205.0.0, proxy, 255.255.0.0

dhcp-range=set:South, 10.207.0.0, proxy, 255.255.0.0

dhcp-range=set:South, 10.212.0.0, proxy, 255.255.0.0

dhcp-option=tag:South, 66, 10.99.1.72

dhcp-option=tag:South, 67, SMSBoot\x64\wdsnbp.com


#dhcp-boot=tag:South, SMSBoot\x64\wdsnbp.com,,10.99.1.72

#pxe-service=tag:South, X86PC, Boot from network,SMSBoot\x64\wdsnbp.com
,10.99.1.72


dhcp-range=set:North, 10.206.0.0, proxy, 255.255.0.0

dhcp-range=set:North, 10.214.0.0, proxy, 255.255.0.0

dhcp-range=set:North, 10.216.0.0, proxy, 255.255.0.0

dhcp-range=set:North, 10.217.0.0, proxy, 255.255.0.0

dhcp-range=set:North, 10.219.0.0, proxy, 255.255.0.0

dhcp-boot=tag:North, SMSBoot\x64\wdsnbp.com, 10.99.2.61, 10.99.2.61


 Syslog 

Jul 16 15:02:39 fog-helper-s dnsmasq[25873]: started, version 2.73 DNS
disabled

Jul 16 15:02:39 fog-helper-s dnsmasq[25873]: compile time options: IPv6
GNU-getopt no-DBus no-i18n no-IDN DHCP DHCPv6 no-Lua TFTP no-conntrack
ipset auth no-DNSSEC loop-detect inotify

Jul 16 15:02:39 fog-helper-s dnsmasq-dhcp[25873]: DHCP, proxy on subnet
10.219.0.0

Jul 16 15:02:39 fog-helper-s dnsmasq-dhcp[25873]: DHCP, proxy on subnet
10.217.0.0

Jul 16 15:02:39 fog-helper-s dnsmasq-dhcp[25873]: DHCP, proxy on subnet
10.216.0.0

Jul 16 15:02:39 fog-helper-s dnsmasq-dhcp[25873]: DHCP, proxy on subnet
10.214.0.0

Jul 16 15:02:39 fog-helper-s dnsmasq-dhcp[25873]: DHCP, proxy on subnet
10.206.0.0

Jul 16 15:02:39 fog-helper-s dnsmasq-dhcp[25873]: DHCP, proxy on subnet
10.212.0.0

Jul 16 15:02:39 fog-helper-s dnsmasq-dhcp[25873]: DHCP, proxy on subnet
10.207.0.0

Jul 16 15:02:39 fog-helper-s dnsmasq-dhcp[25873]: DHCP, proxy on subnet
10.205.0.0

Jul 16 15:02:39 fog-helper-s dnsmasq-dhcp[25873]: DHCP, proxy on subnet
10.204.0.0

Jul 16 15:02:39 fog-helper-s dnsmasq-dhcp[25873]: DHCP, proxy on subnet
10.202.0.0

Jul 16 15:02:39 fog-helper-s dnsmasq-dhcp[25873]: DHCP, proxy on subnet
10.201.0.0

Jul 16 15:03:06 fog-helper-s dnsmasq-dhcp[25873]: 3115234045 available DHCP
subnet: 10.205.0.0/255.255.0.0

Jul 16 15:03:06 fog-helper-s dnsmasq-dhcp[25873]: 3115234045 vendor class:
PXEClient:Arch:0:UNDI:002001

Jul 16 15:03:21 fog-helper-s dnsmasq-dhcp[25873]: 3081679613 available DHCP
subnet: 10.205.0.0/255.255.0.0

Jul 16 15:03:21 fog-helper-s dnsmasq-dhcp[25873]: 3081679613 vendor class:
PXEClient:Arch:0:UNDI:002001

Jul 16 15:03:23 fog-helper-s dnsmasq-dhcp[25873]: 3098456829 available DHCP
subnet: 10.205.0.0/255.255.0.0

Jul 16 15:03:23 fog-helper-s dnsmasq-dhcp[25873]: 3098456829 vendor class:
PXEClient:Arch:0:UNDI:002001

Jul 16 15:03:53 fog-helper-s dnsmasq-dhcp[25873]: 517559989 available DHCP
subnet: 10.205.0.0/255.255.0.0
-- 
David R. Cooper
Network Analyst
East Stroudsburg Area School District
http://www.esasd.net
david-coo...@esasd.net
570-424-8500 x10613

-- 

--
CONFIDENTIALITY NOTICE:  This email message, including any attachments, is 
for the sole use of the intended recipient(s) and contains confidential and 
privileged information. Any unauthorized review, use, disclosure or 
distribution is prohibited. If you are not the intended recipient, please 
contact the sender by reply email, and destroy all copies of the original 
message.
___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss


[Dnsmasq-discuss] Using dnsmasq for multiple subnets

2013-08-07 Thread David Cooper
Hi all!

Scratching my head here on why this isn't working. I believe I am
somehow not understanding how the set and tag system works. Hopefully
someone can point me in the right direction.

Recently I started using a Network Access Control (NAC) system. This
system provides DHCP for the isolation network. However, I have a need
to PXE boot but cannot alter the NAC system. Furthermore I have multiple
imaging servers that service specific subnets.

My solution is to provide one dnsmasq server to point certain subnets to
the correct imaging server for PXE boot.

I have:
- setup dnsmasq 2.59 on Ubuntu 12.04 (precise pangolin) LTS on ip
address 1.1.1.1/16 from the cd-rom repository.
- added the ip helper-address 1.1.1.1 on the 2.2.0.0/16 network.
- For purposes of the example, my imaging server is 3.3.3.3
- deleted the dnsmasq.conf and replaced it with the following contents.
port=0
log-dhcp
dhcp-boot=pxelinux.0
dhcp-no-override
pxe-prompt=Press F8 for boot menu, 0
dhcp-range=set:site1,2.2.0.0,proxy,255.255.0.0
pxe-service=tag:site1,X86PC, Boot from blah,pxelinux,3.3.3.3
dhcp-boot=tag:site1,pxelinux.0,site1.net,3.3.3.3

I boot the machine, get the dhcp address from the isolation network, get
the proxy ip for 1.1.1.1. But it does not go to server 3.3.3.3. for the
address.

Adjusting the dnsmasq.conf, I remove the set anda tag options and it
works fine. While this is obviously a solution, when I go to add another
subnet to the mix I will need to send a different server ip.

I believe the set commands set an identifier. That identifier is used by
the tag lines to denote when they should act.

What am I doing wrong?

-- 
David R. Cooper
Network Analyst
East Stroudsburg Area School District
Technology Learning Center
2002 Milford Road
East Stroudsburg, PA 18301
http://www.esasd.net
david-coo...@esasd.net
570-424-8500 x1614

___
Dnsmasq-discuss mailing list
Dnsmasq-discuss@lists.thekelleys.org.uk
http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss