- Device.DHCPv{4,6}.Client.{i}: fix add/delete method
- Device.DHCPv4.Client.{i}: fix set method of Interface parameter
- Remove automatic and unwanted DHCPv4.Client instances from the config
- Creation of new Device.DHCPv4.Client object should not automatically create a new Device.IP.Interface object instance
- Align DHCPv{4,6}.Client parameters with the new changes
- Comment out Device.IP.Interface.{i}.AutoIPEnable parameter
Some parameters must be specified with microsecond precision such as:
- Device.IP.Diagnostics.DownloadDiagnostics.(ROMTime, BOMTime, EOMTime, TCPOpenResponseTime, etc)
- Device.IP.Diagnostics.UploadDiagnostics.(ROMTime, BOMTime, EOMTime, TCPOpenResponseTime, etc)
- Device.WiFi.Radio.1.SupportedStandards : fix its value
- Device.WiFi.EndPoint.1.WPS.ConfigMethodsEnabled : fix its set value
- Device.WiFi.EndPoint.1.WPS.PIN : fix its set value
- Device.WiFi.EndPoint. : fix segfault when calling delete_obj all
Adds input and output arguments for each operate call
Arguments are stored in the data field on USP_LIST_OPERATE
NOTE: Dynamic operates need to be recomplied when running libbbf
with this commit, hence the op_cmd struct has changed
Signed-off-by: Daniel Danzberger <daniel@dd-wrt.com>
- Fix memleak of not free'd json_tokener_parse memory
- Make read-only memory const
Note that this commit changes the operation input argument from
'char *' to 'json_object *', which breaks older dynamic_operate
implementations from outisde the bbf source tree.
Signed-off-by: Daniel Danzberger <daniel@dd-wrt.com>
- Move missing mcast functions from dmcommon file to mcast file
- Remove extern from function declarations
- Fix some indentation
- Comment unsupported parameters
- Obuspa required to register the schema present in DUT, in the
current methods, for multi-instance objects the instance is only
visible if at-least one object/instance present, this leads to
anomaly in obuspa, when some objects getting created in run-time.
e.g: Device.WiFi.AccessPoint.1.AssociatedDevice.
- This change will dump the complete schema irrespective of that node/object
availability.
It was observed on dg400prime that the uci config was not correctly
generated when wan was of type anywan, this has been taken care of in
this patch. For anywan type IP interface, the list of upstream interfaces
is generated to keep each interface in mind. So, Device.IP.Interface.2
in this case will generate
list upstream_interface 'eth5.1'
list upstream_interface 'atm0.1'
list upstream_interface 'ptm0.1'
test:
- Verify that config is correctly generated for normal interface.
- Verify that config is correctly generated for anywan interface.
- Verify that config is correctly generated for bridge interface.
