Hi Vladimir, Thanks for the review. > I was also going to plan asking Andy what is his plan on making > switchdev digest this. Since switchdev switches don't seem to support this, I wasn't planning on making switchdev digest this. I was thinking that it should just be disabled for those hardware switches. >The switch ASICs I'm most familiar with can learn > on inner VID or outer VID, but not both. I don't know of a switch ASIC that supports this. Is that a problem? I thought that it would be OK to add features to a software bridge that don't exist in any hardware bridge. I've tried to see if anyone else was facing this same problem. All I found were concerns about the fact that the provider bridge needed to learn all the customer's MACs. As a result, it looks like 802.1Qay was created. It seems that 802.1Qay is primarily addressing a concern about TCAM limitations, and decoupling the provider and customer networks. I think it's possible that 802.1Qay has inadvertently fixed this issue for provider backbone bridges. But for my use case, I'm not concerned about TCAM usage. I just want isolation between the inner vlans.
