Skip to content
  1. Jun 17, 2019
    • Stéphane Veyret's avatar
      netfilter: nft_ct: add ct expectations support · 857b4602
      Stéphane Veyret authored
      
      
      This patch allows to add, list and delete expectations via nft objref
      infrastructure and assigning these expectations via nft rule.
      
      This allows manual port triggering when no helper is defined to manage a
      specific protocol. For example, if I have an online game which protocol
      is based on initial connection to TCP port 9753 of the server, and where
      the server opens a connection to port 9876, I can set rules as follow:
      
      table ip filter {
          ct expectation mygame {
              protocol udp;
              dport 9876;
              timeout 2m;
              size 1;
          }
      
          chain input {
              type filter hook input priority 0; policy drop;
              tcp dport 9753 ct expectation set "mygame";
          }
      
          chain output {
              type filter hook output priority 0; policy drop;
              udp dport 9876 ct status expected accept;
          }
      }
      
      Signed-off-by: default avatarStéphane Veyret <sveyret@gmail.com>
      Signed-off-by: default avatarPablo Neira Ayuso <pablo@netfilter.org>
      857b4602
  2. Jun 06, 2019
  3. Jun 05, 2019
    • David S. Miller's avatar
      Merge branch 'net-dsa-mv88e6xxx-support-for-mv88e6250' · 2a99283c
      David S. Miller authored
      
      
      Rasmus Villemoes says:
      
      ====================
      net: dsa: mv88e6xxx: support for mv88e6250
      
      This adds support for the mv88e6250 chip. Initially based on the
      mv88e6240, this time around, I've been through each ->ops callback and
      checked that it makes sense, either replacing with a 6250 specific
      variant or dropping it if no equivalent functionality seems to exist
      for the 6250. Along the way, I found a few oddities in the existing
      code, mostly sent as separate patches/questions.
      
      The one relevant to the 6250 is the ieee_pri_map callback, where the
      existing mv88e6085_g1_ieee_pri_map() is actually wrong for many of the
      existing users. I've put the mv88e6250_g1_ieee_pri_map() patch first
      in case some of the existing chips get switched over to use that and
      it is deemed important enough for -stable.
      
      v4:
      - fix style issue in 1/10
      - add Andrew's reviewed-by to 1,6,7,8,9,10.
      
      v3:
      - rebase on top of net-next/master
      - add reviewed-bys to patches unchanged from v2 (2,3,4,5)
      - add 6250-specific ->ieee_pri_map, ->port_set_speed, ->port_link_state (1,6,7)
      - in addition, use mv88e6065_phylink_validate for ->phylink_validate,
        and don't implement ->port_get_cmode, ->port_set_jumbo_size,
        ->port_disable_learn_limit, ->rmu_disable
      - drop ptp support
      - add patch adding the compatible string to the DT binding (9)
      - add small refactoring patch (10)
      
      v2:
      - rebase on top of net-next/master
      - add reviewed-by to two patches unchanged from v1 (2,3)
      - add separate watchdog_ops
      ====================
      
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      2a99283c