submit patch for udhcpc - addition of Option 43

Denys Vlasenko vda.linux at googlemail.com
Fri Apr 2 07:42:02 UTC 2010


On Wednesday 24 March 2010 00:47, Christopher Barry wrote:
> > >> udhcpd already does something like that
> > >> in order to handle udhcpd.conf which can contain
> > >> directives like:
> > >>
> > >> opt     dns     192.168.10.2 192.168.10.10
> > >> option  subnet  255.255.255.0
> > >> opt     router  192.168.10.2
> > >> opt     wins    192.168.10.10
> > >> option  dns     129.219.13.81   # appended to above DNS servers for a total of 3
> > >> option  domain  local
> > >> option  lease   864000          # default: 10 days
> > >
> > > Also, since udhcpd uses a config file for multiple options, why not allow udhcpc to use a similar config file?  Example:
> > >
> > > /etc/udhcpc.conf
> > > opt     vendorclass     OpenCable2.1
> > > option  vendorspecific  2=ESTB 3=ECM:ESTB 4=SN00000001
> > 
> > How would you pass spaces in suboption values if you need to?
> > 
> > > opt     script          /etc/udhcpc.script
> > >
> > > Where the 2nd parameter could match the udhcpc_longopts[] name.
> > 
> > I don't know why, but I am perfectly happy with udhcpc having
> > only a command-line interface.
> 
> As a user, from my perspective, having a single, simple conf file that
> always gets read specifying the desired options to request (or set)
> would be the optimum solution. Using -c <config_file> would allow using
> any correctly formatted file for this purpose.

I know what config files are in general.

I implemented -x "optname:optval".

Feel free to submit a patch which adds "vendorinfo" option.
All the other needed machinery is in place.
-- 
vda


More information about the busybox mailing list