Files
geedge-jira/md/OMPUB-966.md
2025-09-14 21:52:36 +00:00

96 lines
2.7 KiB
Markdown
Raw Blame History

This file contains invisible Unicode characters

This file contains invisible Unicode characters that are indistinguishable to humans but may be processed differently by a computer. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

# P19现场Deny动作未发送TCP Reset
| ID | Creation Date | Assignee | Status |
|----|----------------|----------|--------|
| OMPUB-966 | 2023-07-16T17:49:42.000+0800 | 杨威 | 开放 |
---
单向流? [~yangyubo] 贴日志上来**yangyubo** commented on *2023-07-17T12:15:52.136+0800*:
以MSH站点 10.10.20.161为例
!企业微信截图_16895671747484.png|thumbnail!
sapp 日志信息:
!image-2023-07-17-09-38-46-315.png|thumbnail!
---
**yangyubo** commented on *2023-07-17T12:53:47.323+0800*:
以tsg_master错误日志中出现的ip 111.88.41.21为过滤条件查询安全日志
!screenshot-1.png|thumbnail!
发现几乎98%均为单向流
以 37.111.167.173为例:
!image-2023-07-17-09-56-53-218.png|thumbnail!
发现几乎95%均为单向流
---
**yangwei** commented on *2023-07-17T13:39:27.938+0800*:
根据现场sapp的错误日志构造数据包失败的位置在组装GRE层
由于GRE上下行的callid不同当命中策略的会话为单向流时构造反方向如当前会话方向为C2S则S2C为反方向数据包如RST时缺乏callid信息会出现构造失败的错误日志
---
**yangwei** commented on *2023-07-17T14:43:05.669+0800*:
进一步地目前现场的运行参数需要严格按照原始包构造各层信息因此对于单向流即使不是GRE封装构造MAC地址、链路信息marsio发包所需要的ROUTE_CTX、sidlist等时也会报错但是为避免错误日志量爆炸大部分的该类因为缺乏信息构造失败的日志级别为info总体的计数可以通过metrics中的Snd_Err_Pkt或者sysinfo.log中的SEND-ERR获得
 
对于无法有效构造rst的会话对应的deny行为会由tcp reset退化为drop原则上不影响deny结果
---
**yangwei** commented on *2024-09-26T10:35:58.779+0800*:
单向流接入下,双向发送会话干扰包的解决思路
* 前提1存在额外注包链路
**  接入拓扑中包含三层注包链路例如镜像接入时的注包路由或者inline接入时额外提供注入路由
* 对应方案Firewall支持按三层信息构造干扰包并从指定链路注出
** 例如镜像/inline模式下支持TCP RST通过管理口注出
 
* 前提2无额外注包链路
* 对应方案通过SwarmKV在集群内同步单向流会话命中的策略ID
** C2S侧命中策略后发送C2S侧的干扰包并将策略ID同步至SwarmKV
** S2C侧同步到命中的策略ID发送S2C侧干扰包
---
## Attachments
**41375/image-2023-07-17-09-38-46-315.png**
---
**41380/image-2023-07-17-09-56-53-218.png**
---
**41379/screenshot-1.png**
---
**41374/企业微信截图_16895671747484.png**
---