Jo-Philipp,
We started to talk about the following:
config host
option ip '192.168.1.25'
option mac 'd0:27:88:59:38:e8'
option name 'gwtest'
option tag 'client'
list dhcp_option 'option:domain-name,"acme.net"'
config global
option tag 'client'
list dhcp_option 'option:router,192.168.1.253'
list dhcp_option 'option:domain-search,"redfish-solutions.com"'
and this should result in:
dhcp-host=d0:27:88:59:38:e8,set:client,192.168.1.25,gwtest,option:domain-name,"acme.net"
dhcp-option=tag:client,option:router,192.168.1.253,option:domain-search,"redfish-solutions.com"
This would allow me to have a class of options associated with 'client'
machines (i.e. machines given to me by customers to use on contracts for
development that sit on my network) by simply associating them with the
'client' attribute, regardless of what network I put them on.
Ditto, I could have:
config mac
option mac '00:0e:08:*:*:*'
option tag 'sipura'
option tag 'sipphone'
config global
option tag 'sipphone'
list dhcp_option 'option:tftp-server,"pbx.redfish-solutions.com"'
list dhcp_option 'option:120,192.168.1.1'
config global
option tag 'sippura'
list dhcp_option 'option:bootfile-name,"/firmware/spa942.cfg"'
which would generate:
dhcp-mac=set:sipura,set:sipphone,00:0e:08:*:*:*
dhcp-option=tag:sipphone,option:tftp-server,"pbx.redfish-solutions.com",option:120,192.168.1.1
dhcp-option=tag:sipura,option:bootfile-name,"/firmware/spa942.cfg"
also thinking that the field 'force' would be useful, i.e.:
config global
option tag 'sipphone'
option force 1
list dhcp_option 'option:tftp-server,"pbx.redfish-solutions.com"'
list dhcp_option 'option:120,192.168.1.1'
dhcp-option-force=tag:sipphone,option:tftp-server,"pbx.redfish-solutions.com",option:120,192.168.1.1
what do you think?
-Philip
_______________________________________________
openwrt-devel mailing list
[email protected]
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
