Introduction of the FLOW On the SRX securtiy platform

本文介绍网络设备的关键组成部分,如输入/输出卡(I/O Card)、网络处理卡(Network Processing Card)等,并详细解析了数据包从进入平台到离开平台的物理与逻辑流程,包括状态检查、会话查找及各种安全策略的实施。

1. componets

IOC: input/output card

NPC: Network processing Card

SPC: services Processing Card

SCB: Switch Control Board

RE  : Routing Engine

 

2. Physical Packet Flow

1.  A packet enters the security platform through the IOC

2. The Packet traverses the switch fabiric from the IOC to the NPC. The NPC performs a flow lookup. If the packet belongs to an existing flow, the NPC forwards the packet to the SPC associsted with the packet's session. If the flow does not currentlu exist, the NPC installs a new session for the flow and assigns the flow to an SPC for processing. The NPC also performs QOS, plolcing and shaping.

3. The packet traverses the switch fabirc to its associated SPC, where security processing and forwarding or routing occurs.

4. The packet travers the switch fabric back to an NPC where additional packet processing such ad shaping and QOS occurs

5. The packet traverses the switch fabric to the IOC associated with the egress interface and travels to the attached physical medium.

 

3. Logical Packet Flow

1. The software applies staless policing filters and Cos classification to the packet at the ingress

2. If the packet does not drop, the software performs a session lookup to determine whether the packet belongs to an existing session. Junos softwere match on six elements of traffic information for this determination (source IP address, source port number, destination port number, protocol number, and a session token.

3. If the packet does not match an existing session, the software creates a new session for it. This process is refered to as the first-packet path. The packet matches a session, the software performs fast=path processing.

 

Detailed logical packet flow

first-path processing

1. Based on the protocal used and its session layer (TCP or UDP), the software starts a session timer. For TCP session, the default timeout is 30 minutes. FOr UDP session, the default timeout is 1 minutes. These values are the defaults, and you can change them.

2. The software applies firewall SCREEN options

3. If destination NAT is used, the software performs address allocation

4. Next, the software performs the route lookuo. If a route exists for the destination prefix, the software takes the next step. Otherwise, it drops the packet.

5. The software determines the packet's incoming zone by the interface though which if arrives. The software also determines the packet's outgoing zone by the forwarding lookuo.

6. Based on incoming and outgoing zones, the corresponding security policy is determined and a security policy lookup takes place. The software checke the packet against defined policies to determine how to treat the packet.

7. If source NAT is used, the software performs address allocation

8. The software sets up the ALG service vector

9. The software creates and installs the session. Futhermore, the software caches the decisions made for the first packet into a flow table, which subsequent packets of that flow use.

10. The packet now enters the fast-path processing.

 

Fast-path processing

1. The software applies firewall SCREEN options

2. The software performs TCP checks

3. The software applies NAT

4. The software applies an ALG

5. The software applies packet forwarding features, which include the following

    a. Stateless packet filters

    b. Traffic shaping by packet

    c. Packet encapsulation and transmission

 

 

 

**项目名称:** 基于Vue.js与Spring Cloud架构的博客系统设计与开发——微服务分布式应用实践 **项目概述:** 本项目为计算机科学与技术专业本科毕业设计成果,旨在设计并实现一个采用前后端分离架构的现代化博客平台。系统前端基于Vue.js框架构建,提供响应式用户界面;后端采用Spring Cloud微服务架构,通过服务拆分、注册发现、配置中心及网关路由等技术,构建高可用、易扩展的分布式应用体系。项目重点探讨微服务模式下的系统设计、服务治理、数据一致性及部署运维等关键问题,体现了分布式系统在Web应用中的实践价值。 **技术架构:** 1. **前端技术栈:** Vue.js 2.x、Vue Router、Vuex、Element UI、Axios 2. **后端技术栈:** Spring Boot 2.x、Spring Cloud (Eureka/Nacos、Feign/OpenFeign、Ribbon、Hystrix、Zuul/Gateway、Config) 3. **数据存储:** MySQL 8.0(主数据存储)、Redis(缓存与会话管理) 4. **服务通信:** RESTful API、消息队列(可选RabbitMQ/Kafka) 5. **部署与运维:** Docker容器化、Jenkins持续集成、Nginx负载均衡 **核心功能模块:** - 用户管理:注册登录、权限控制、个人中心 - 文章管理:富文本编辑、分类标签、发布审核、评论互动 - 内容展示:首页推荐、分类检索、全文搜索、热门排行 - 系统管理:后台仪表盘、用户与内容监控、日志审计 - 微服务治理:服务健康检测、动态配置更新、熔断降级策略 **设计特点:** 1. **架构解耦:** 前后端完全分离,通过API网关统一接入,支持独立开发与部署。 2. **服务拆分:** 按业务域划分为用户服务、文章服务、评论服务、文件服务等独立微服务。 3. **高可用设计:** 采用服务注册发现机制,配合负载均衡与熔断器,提升系统容错能力。 4. **可扩展性:** 模块化设计支持横向扩展,配置中心实现运行时动态调整。 **项目成果:** 完成了一个具备完整博客功能、具备微服务典型特征的分布式系统原型,通过容器化部署验证了多服务协同运行的可行性,为云原生应用开发提供了实践参考。 资源来源于网络分享,仅用于学习交流使用,请勿用于商业,如有侵权请联系我删除!
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值