This was an intresting responce ---------- Forwarded message ---------- From: <<a href="mailto:bugzilla@redhat.com">bugzilla@redhat.com</a>> Date: Dec 17, 2012 9:28 AM Subject: [Bug 887369] dnsmasq not loading any of the information from the options file To: <<a href="mailto:prmarino1@gmail.com">prmarino1@gmail.com</a>> Product: Red Hat OpenStack <a href="https://bugzilla.redhat.com/show_bug.cgi?id=887369">https://bugzilla.redhat.com/show_bug.cgi?id=887369</a> Tomas Hozza <<a href="mailto:thozza@redhat.com">thozza@redhat.com</a>> changed: What |Removed |Added ---------------------------------------------------------------------------- Group| |redhat CC| |<a href="mailto:ykaul@redhat.com">ykaul@redhat.com</a> Component|dnsmasq |openstack-quantum Version|6.3 |unspecified Assignee|<a href="mailto:thozza@redhat.com">thozza@redhat.com</a> |<a href="mailto:rhos-maint@redhat.com">rhos-maint@redhat.com</a> Product|Red Hat Enterprise Linux 6 |Red Hat OpenStack Target Milestone|rc |RC QA Contact|<a href="mailto:qe-baseos-daemons@redhat.co">qe-baseos-daemons@redhat.co</a> |<a href="mailto:oblaut@redhat.com">oblaut@redhat.com</a> |m | --- Comment #2 from Tomas Hozza <<a href="mailto:thozza@redhat.com">thozza@redhat.com</a>> --- This is *NOT A BUG* in dnsmasq-2.48. If you read dnsmasq manual page, you will realise, that there is no such way to set TAGs by using "set:tag0" and also to refer to a TAG by "tag:tag0". Therefore it is not working with your options. There was a change in dnsmasq-2.53 which introduced the *NEW* TAGs setting and referring, but these options are *NOT AVAILABLE* in dnsmasq versions lower than 2.53. Regarding to dnsmasq-2.48 manual page, you can use existing options to SET the TAG and to refer to a TAG. In your case if you use: --dhcp-range=tag0,192.168.253.0,static,120s instead of --dhcp-range=set:tag0,192.168.253.0,static,120s and in the dhcp-optsfile: tag0,option:dns-server,10.254.254.42 tag0,option:router,192.168.253.1 instead of tag:tag0,option:dns-server,10.254.254.42 tag:tag0,option:router,192.168.253.1 everything will work. I tested it and server returned right options in DHCP reply. Changing Product to Red Hat OpenStack and component to openstack-quantum, since this is *NOT* a dnsmasq bug. OpenStack need to be fixed to use proper options when running dnsmasq! -- You are receiving this mail because: You reported the bug.