1. 02 3月, 2016 1 次提交
  2. 26 2月, 2016 1 次提交
  3. 17 2月, 2016 1 次提交
  4. 06 11月, 2015 1 次提交
  5. 03 11月, 2015 1 次提交
  6. 02 11月, 2015 1 次提交
  7. 22 10月, 2015 2 次提交
  8. 13 10月, 2015 1 次提交
    • V
      net: dsa: mv88e6xxx: fix hardware bridging · 5fe7f680
      Vivien Didelot 提交于
      Playing with the VLAN map of every port to implement "hardware bridging"
      in the 88E6352 driver was a hack until full 802.1Q was supported.
      
      Indeed with 802.1Q port mode "Disabled" or "Fallback", this feature is
      used to restrict which output ports an input port can egress frames to.
      
      A Linux bridge is an untagged VLAN. With full 802.1Q support, we don't
      need this hack anymore and can use the "Secure" strict 802.1Q port mode.
      
      With this mode, the port-based VLAN map still needs to be configured,
      but all the logic is VTU-centric. This means that the switch only cares
      about rules described in its hardware VLAN table, which is exactly what
      Linux bridge expects and what we want.
      
      Note also that the hardware bridging was broken with the previous
      flexible "Fallback" 802.1Q port mode. Here's an example:
      
      Port0 and Port1 belong to the same bridge. If Port0 sends crafted tagged
      frames with VID 200 to Port1, Port1 receives it. Even if Port1 is in
      hardware VLAN 200, but not Port0, Port1 will still receive it, because
      Fallback mode doesn't care about invalid VID or non-member source port.
      Signed-off-by: NVivien Didelot <vivien.didelot@savoirfairelinux.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      5fe7f680
  9. 11 10月, 2015 1 次提交
  10. 07 10月, 2015 1 次提交
  11. 01 9月, 2015 1 次提交
  12. 14 8月, 2015 3 次提交
  13. 12 8月, 2015 2 次提交
  14. 11 8月, 2015 1 次提交
  15. 10 8月, 2015 3 次提交
  16. 27 7月, 2015 1 次提交
  17. 10 7月, 2015 1 次提交
  18. 10 5月, 2015 4 次提交
  19. 02 4月, 2015 6 次提交
  20. 30 3月, 2015 5 次提交
  21. 08 3月, 2015 1 次提交
  22. 20 2月, 2015 1 次提交