Fix Get/Set value of these parameters which has a hexbinary encoded value according to the TR-181 standard
- Device.DHCPv4.Server.Pool.{i}.Option.{i}.Value
- Device.DHCPv4.Client.{i}.SentOption.{i}.Value
- Device.DHCPv4.Relay.Forwarding.{i}.UserClassID
- Device.DHCPv6.Server.Pool.{i}.VendorClassID
- Device.DHCPv6.Server.Pool.{i}.UserClassID
- Device.DHCPv6.Server.Pool.{i}.Option.{i}.Value
- 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
- Move missing mcast functions from dmcommon file to mcast file
- Remove extern from function declarations
- Fix some indentation
- Comment unsupported parameters
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.
Calling this dm_strword with an emtpy 'str' can cause invalid memory
access. This commit checks for an empty string.
NOTE: This function is insecure and can cause segfaults
when 'str' is larger than 'source'
Signed-off-by: Daniel Danzberger <daniel@dd-wrt.com>
For the changes done in branch, some changes in dmcommon were overwritten
accidentally, reverting the same. Only leaves snooping mode related
changes in the branch now.
Added support for MLD configuration using the new proposed data
model.
Resolve bug in IGMP to be able to delete child objects when
parents are deleted from the dmmap_mcast file.
Remove the hard coded value of Filter.Enable and added configuration
support for the same.
Note: With this, I think I am ready to raise merge request for this,
I will finalise the mcastmngr changes now and then raise a merge request
once that is in iopsys devel
Changes done are:
1. Interfaces in the proxy uci section are called upstream_interface
and downstream_interface as against proxy_interface and snooping_interface
earlier.
2. The interface now bears the value of the actual linux interface, so,
the upstream interface for example is now eth4.1 instead of wan.
3. A bug in the determining of bridging instance was identified and fixed.
The UCI looks as follows now:
root@iopsys:~# cat /etc/config/mcast
config proxy 'mproxy_1'
option enable '0'
option proto 'igmp'
option version '2'
option robustness '2'
option aggregation '0'
option last_member_query_interval '10'
option query_interval '120'
option query_response_interval '10'
list downstream_interface 'br-wan100'
list upstream_interface 'eth4.1'
config snooping 'msnoop_1'
option enable '0'
option proto 'igmp'
option version '2'
option robustness '2'
option aggregation '0'
option interface 'br-wan100'
- Fixed issue in Ethernet Link deletion.
- Fixed deletion of untagged interfaces section from UCI.
- Fixed in setting lower layers for Ethernet link in case of untagged management interface.
- Fixed issue of adding same ports with different vlan id under different bridge.
