which ipv6 feature is supported in ipv4 but is not commonly used
anycast
the otg port does not support isochronous mode when in device mode. hi [@tepper](/u/tepper),

[image] tepper:

i suspect this is because the feature is simply not offered on my phone

you are correct about that. the spam blocking feature you reference requires a newer republic compatible (a/k/a 3.0) phone using a my choice plan. the feature is not available for legacy repub… Hello,  


Please find below the answer for your questions

 QinQ Mapping

 Principles

QinQ mapping maps VLAN tags in user packets to specified tags before the user packets are transmitted across the public network.

* Before sending local VLAN frames, a sub-interface replaces the tags in the local frames with external VLAN tags.
* Before receiving frames from external VLANs, a sub-interface replaces the tags in the external VLANs with local VLAN tags.

QinQ mapping allows a device to map a user VLAN tag to a carrier VLAN tag, shielding different user VLAN IDs in packets.

QinQ mapping is deployed on edge devices of a Metro Ethernet. It is applied in but not limited to the following scenarios:

* VLAN IDs deployed at new sites and old sites conflict, but new sites need to communicate with old sites.
* VLAN IDs planned by each site on the public network conflict. These sites do not need to communicate.
* VLAN IDs on both ends of the public network are asymmetric.

Currently, only 1 to 1 QinQ mapping is supported. When a QinQ mapping-enabled sub-interface receives a single-tagged packet, the sub-interface replaces the VLAN ID in the frame with a specified VLAN ID.

Figure 7-8 QinQ mapping  
![imgDownload?uuid=4402391882494f24bacff41](https://download.huawei.com/mdl/imgDownload?uuid=4402391882494f24bacff41f1955d182.png)  


As shown in [Figure 7-8](https://support.huawei.com/enterprise/en/doc/EDOC1100055122/fbe6cdac/qinq-mapping#fig_dc_vrp_qinq_feature_003501), 1 to 1 QinQ mapping is configured on Sub-interfaces 1 on Switch 2 and Switch 3. If PC1 wants to communicate with PC2:

1. PC1 sends a frame to Switch 1.
2. Upon receipt, Switch 1 adds VLAN ID 10 to the frame, and forwards the frame to Switch 2. After Sub-interface1 on Switch 2 receives the frame with VLAN ID 10, Sub-interface 1 on Switch 2 replaces VLAN ID 10 with carrier VLAN ID 50. Interface 2 on Switch 2 then sends the frame with carrier VLAN ID 50 to the Internet service provider (ISP) network.
3. The ISP network transparently transmits the frame.
4. After Sub-interface 1 on Switch 3 receives the tagged frame from Switch 2, Sub-interface 1 on Switch 3 replaces the carrier VLAN ID 50 with VLAN ID 30.

PC2 communicates with PC1 in a similar manner.

 Comparison Between QinQ Mapping and VLAN Mapping

[Table 7-3](https://support.huawei.com/enterprise/en/doc/EDOC1100055122/fbe6cdac/qinq-mapping#tab_dc_vrp_qinq_feature_003501) describes the comparison between QinQ mapping and VLAN mapping.

Table 7-3 Comparison between QinQ mapping and VLAN mapping



| Mapping Type | Similarity | Difference |
|  |  |  |
| 1 to 1 | An interface maps the tag of a received single-tagged frame to the specified tag. | * QinQ mapping
	+ Performed on a sub-interface
	+ Used for VPLS access
* VLAN mapping
	+ Performed on an interface
	+ Used on Layer 2 networks where VLAN frames are forwarded
 |

  


  


Thanks i think it’s too early to think about h.266.

in any case if it will be supported then you need new hardware. i finally got it figured out. by default, iperf sends to the server.  so my 5.5 mbps throughput was only my upload speed.  when i ran iperf in reverse mode (-r) is downloads from the server.  i wasn't getting good results from a single tcp session, but when i increased it to 10, i was getting the results i was expecting (47 mbps).  if you want to try these tests for yourself you can use these commands for any public iperf server: *case sensitiveupload test      - iperf3 -c iperf.he.netdownload test  - iperf3 -r -c iperf.he.net -p10 i do not know what the bandwidth limitation is with this iperf server filter at the backend server only? not afaik

only android and ios use modbus read instead of modbus server > 
> **$\underline{\textit{Application layer VPN's}}$**
> 
> 
> This type of VPN will work with specific applications. The most common example of this type of VPN network is seen over the SSL connections that people use to purchase items online every day. The Application layer VPN provides encrypted communication between the web browser that the visitor is using to view the item and the server that is used to process the order. There are other applications that can be protected in this way, as well. This type of VPN security requires that each different application be supported.
> 
> 
> **$\underline{\textit{Network layer VPN's}}$**
> 
> 
> A $\textit{Network layer}$ VPN functions on layer 3. Unlike Application layer VPN security, Network layer VPN security will encrypt any traffic, regardless of the different applications being used. This type of VPN is used by some of the most well-known names in Internet security. For example, Cisco uses this layer for VPNs. These VPN servers are sometimes provided under the names L2TP and GRE.
> 
> 
> **$\underline{\textit{Data Link VPN's}}$**
> 
> 
> **$\textit{Data Link VPN}$** is used when two private networks need to communicate. It is one of the most expensive types of VPN connection. Normally, the protocol used over these connections does not provide encryption, so encryption needs to be added to the connection.
> 
> 
> looks like he’s using a texting app which uses data not texts