Lines Matching refs:VLAN
176 channel. The cdc_mbim driver models such IP sessions as 802.1q VLAN
178 VLAN ID Z for all values of Z greater than 0.
184 VLAN links prior to establishing MBIM IP sessions where the SessionId
185 is greater than 0. These links can be added by using the normal VLAN
200 sessions as another set of 802.1q VLAN subdevices of the master wwanY
201 device, mapping MBIM DSS session A to VLAN ID (256 + A) for all values
207 The DSS VLAN subdevices are used as a practical interface between the
240 Note that adding VLAN links for DSS sessions is entirely optional. A
242 directly to the master network device, using the received VLAN tags to
243 map frames to the correct DSS session and adding 18 byte VLAN ethernet
245 filter is recommended, matching only the DSS VLAN subset. This avoid
250 /* use special negative offsets to get VLAN tag */
254 /* verify DSS VLAN range */
256 BPF_JUMP(BPF_JMP|BPF_JGE|BPF_K, 256, 0, 4), /* 256 is first DSS VLAN */
257 BPF_JUMP(BPF_JMP|BPF_JGE|BPF_K, 512, 3, 0), /* 511 is last DSS VLAN */
269 Tagged IP session 0 VLAN
284 session 0 to a VLAN subdevice, similar to all other IP sessions. This
285 behaviour is triggered by adding a VLAN link for the magic VLAN ID
287 0 to this VLAN, and will drop untagged frames on the master wwanY
290 Tip: It might be less confusing to the end user to name this VLAN
291 subdevice after the MBIM SessionID instead of the VLAN ID. For
297 VLAN mapping
301 relationship between VLAN tags on the wwanY network device and MBIM
304 VLAN ID MBIM type MBIM SessionID Notes
312 a) if no VLAN ID 4094 link exists, else dropped
313 b) unsupported VLAN range, unconditionally dropped
314 c) if a VLAN ID 4094 link exists, else dropped