[Dnsmasq-discuss] RFC: allowing arbitrarily long options

Neil Jerram neil at tigera.io
Sun Jan 7 14:25:23 GMT 2018


Calico [1] with OpenStack (
https://docs.projectcalico.org/v2.6/getting-started/openstack/) uses
dnsmasq with a very long --bridge-interface option:

--bridge-interface=<context-if-name>,<alias-if-name>,<alias-if-name>,...,

where each occurrence of ",<alias-if-name>" occupies 15 characters, and
there can in principle be as many <alias-if-name>s as you can have VMs on a
single OpenStack compute host.  Currently an option arg is limited in
dnsmasq to 1025 chars overall, which only allows for 67 <alias-if-name>s,
which is not necessarily enough, on a powerful compute host.

So I wonder what folk would think about reallocating as necessary to allow
an option arg to be arbitrarily long?  (Or at least, as long as getopt and
the containing shell will allow.)  For reference I've attached a patch that
I think would implement that - but I haven't yet been able to test it at
all, so please don't merge it yet!

Thanks in advance for your thoughts!
      Neil
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/attachments/20180107/56253308/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-Allow-options-longer-than-1025-chars.patch
Type: text/x-patch
Size: 2035 bytes
Desc: not available
URL: <http://lists.thekelleys.org.uk/pipermail/dnsmasq-discuss/attachments/20180107/56253308/attachment.bin>


More information about the Dnsmasq-discuss mailing list