FWPM_LAYER_ALE_AUTH_CONNECT_V4_DISCARD和FWPM_LAYER_ALE_ENDPOINT_CLOSURE_V4 [英] FWPM_LAYER_ALE_AUTH_CONNECT_V4_DISCARD and FWPM_LAYER_ALE_ENDPOINT_CLOSURE_V4

查看:277
本文介绍了FWPM_LAYER_ALE_AUTH_CONNECT_V4_DISCARD和FWPM_LAYER_ALE_ENDPOINT_CLOSURE_V4的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

FWPM_LAYER_ALE_ENDPOINT_CLOSURE_V4层的分类是否会在FWPM_LAYER_ALE_AUTH_CONNECT_V4_DISCARD之后发生?



1. 

客户连接:

    FWPM_LAYER_ALE_AUTH_CONNECT_V4 classifyFn被称为

   一个过滤器返回FWPM_ACTION_BLOCK

    FWPM_LAYER_ALE_AUTH_CONNECT_V4_DISCARD  classifyFn名为

    FWPM_LAYER_ALE_ENDPOINT_CLOSURE_V4 classifyFn将被调用????
$


2.

客户dows连接

    FWPM_LAYER_ALE_AUTH_CONNECT_V4 classifyFn被称为

   所有过滤器返回FWP_ACTION_PERMIT

    FWPM_LAYER_STREAM_ESTABLISHED_V4 classifyFn被称为

   已建立连接



   有人在FWPM_LAYER_ALE_AUTH_CONNECT_V4中添加了一个过滤器。
   使用FWP_CONDITION_FLAG_IS_REAUTHORIZE标志调用FWPM_LAYER_ALE_AUTH_CONNECT_V4 classifyFn为
   一个过滤器返回FWPM_ACTION_BLOCK

    FWPM_LAYER_ALE_AUTH_CONNECT_V4_DISCARD  classifyFn被称为????

    FWPM_LAYER_ALE_ENDPOINT_CLOSURE_V4 classifyFn将被调用????
$


3. 

可以睡眠或休眠导致FWPM_LAYER_ALE_AUTH_CONNECT_V4_DISCARD分类?

我在休眠期间有一个很少重现的bug。 



Will the classify at FWPM_LAYER_ALE_ENDPOINT_CLOSURE_V4 layer occur after FWPM_LAYER_ALE_AUTH_CONNECT_V4_DISCARD ?

1. 
Client does connect:
   FWPM_LAYER_ALE_AUTH_CONNECT_V4 classifyFn is called
   one filter returns FWPM_ACTION_BLOCK
   FWPM_LAYER_ALE_AUTH_CONNECT_V4_DISCARD  classifyFn is called
   FWPM_LAYER_ALE_ENDPOINT_CLOSURE_V4 classifyFn will be called ????

2.
Client dows connect
    FWPM_LAYER_ALE_AUTH_CONNECT_V4 classifyFn is called
    all filters return FWP_ACTION_PERMIT
    FWPM_LAYER_STREAM_ESTABLISHED_V4 classifyFn is called
    Connection is etablished

    Someone adds a filter  at  FWPM_LAYER_ALE_AUTH_CONNECT_V4
    FWPM_LAYER_ALE_AUTH_CONNECT_V4 classifyFn is called with FWP_CONDITION_FLAG_IS_REAUTHORIZE flag
    one filter returns FWPM_ACTION_BLOCK
    FWPM_LAYER_ALE_AUTH_CONNECT_V4_DISCARD  classifyFn is called ????
    FWPM_LAYER_ALE_ENDPOINT_CLOSURE_V4 classifyFn will be called ????

3. 
Can Sleep or Hibernate lead to classification at FWPM_LAYER_ALE_AUTH_CONNECT_V4_DISCARD ?
I have one rarely reproduced bug during hibernate. 


推荐答案

1)将调用FWPM_LAYER_ALE_ENDPOINT_CLOSURE_V4

1) FWPM_LAYER_ALE_ENDPOINT_CLOSURE_V4 will be called

2)应该调用FWPM_LAYER_ALE_AUTH_CONNECT_V4_DISCARD。 将调用FWPM_LAYER_ALE_ENDPOINT_CLOSURE_V4。

2) FWPM_LAYER_ALE_AUTH_CONNECT_V4_DISCARD should be called.  FWPM_LAYER_ALE_ENDPOINT_CLOSURE_V4 will be called.

3)电源状态本身不会触发分类。 然而,由于电源状态转换,许多产品将添加/删除过滤器,其中 可能导致该块,随后是FWPM_LAYER_ALE_AUTH_CONNECT_V4_DISCARD分类。

3) Power States themselves will not trigger classifies.  However many products will add / remove filters due to the power state transition, which  may cause the block, and subsequently the FWPM_LAYER_ALE_AUTH_CONNECT_V4_DISCARD classification.

希望这会有所帮助,


这篇关于FWPM_LAYER_ALE_AUTH_CONNECT_V4_DISCARD和FWPM_LAYER_ALE_ENDPOINT_CLOSURE_V4的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
相关文章
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆