aboutsummaryrefslogtreecommitdiffstats
path: root/package
diff options
context:
space:
mode:
authorJohn Crispin <blogic@openwrt.org>2015-07-24 09:10:47 +0000
committerJohn Crispin <blogic@openwrt.org>2015-07-24 09:10:47 +0000
commit78627872526bd19b0579db00cd8b4ec024c9d4e6 (patch)
tree150e59aaf9c4cd79ee94d6c2db1dce264fa9af2c /package
parent78b43002c7b0c8210b1f689cc35d274c8053eaaa (diff)
downloadmaster-187ad058-78627872526bd19b0579db00cd8b4ec024c9d4e6.tar.gz
master-187ad058-78627872526bd19b0579db00cd8b4ec024c9d4e6.tar.bz2
master-187ad058-78627872526bd19b0579db00cd8b4ec024c9d4e6.zip
generic: cdc_ncm: Add support for moving NDP to end of NCM frame
NCM specs are not actually mandating a specific position in the frame for the NDP (Network Datagram Pointer). However, some Huawei devices will ignore our aggregates if it is not placed after the datagrams it points to. Add support for doing just this, in a per-device configurable way. While at it, update NCM subdrivers, disabling this functionality in all of them, except in huawei_cdc_ncm where it is enabled instead. We aren't making any distinction between different Huawei NCM devices, based on what the vendor driver does. Standard NCM devices are left unaffected: if they are compliant, they should be always usable, still stay on the safe side. This change has been tested and working with a Huawei E3131 device (which works regardless of NDP position) and an E3372 device (which mandates NDP to be after indexed datagrams). Signed-off-by: Enrico Mioso <mrkiko.rs@gmail.com> Signed-off-by: Matti Laakso <malaakso@elisanet.fi> git-svn-id: svn://svn.openwrt.org/openwrt/trunk@46464 3c298f89-4303-0410-b956-a3cf2f4a3e73
Diffstat (limited to 'package')
0 files changed, 0 insertions, 0 deletions