OVN conntrack flag

 1 The following flags describe the state of the tracking:
 2              0x01: new
 3                      This is the beginning of a new connection. This flag  may
 4                      only be present for uncommitted connections.
 5
 6               0x02: est
 7                      This is part of an already existing connection. This flag
 8                      may only be present for committed connections.
 9
10               0x04: rel
11                      This is a connection that is related to an existing  con‐
12                      nection, for instance ICMP "destination unreachable" mes‐
13                      sages or FTP data connections.  This  flag  may  only  be
14                      present for committed connections.
15
16               0x08: rpl
17                      The  flow  is  in the reply direction, meaning it did not
18                      initiate the connection. This flag may  only  be  present
19                      for committed connections.
20
21               0x10: inv
22                      The state is invalid, meaning that the connection tracker
23                      couldn‘t identify the connection. This flag is  a  catch-
24                      all  for  any  problems  that  the connection tracker may
25                      have, for example:
26
27                      - L3/L4 protocol handler is not loaded/unavailable.  With
28                      the  Linux  kernel  datapath,  this  may  mean  that  the
29                      "nf_conntrack_ipv4" or  "nf_conntrack_ipv6"  modules  are
30                      not loaded.
31
32                      -  L3/L4  protocol  handler determines that the packet is
33                      malformed.
34
35                      - Packets are unexpected length for protocol.
36
37               0x20: trk
38                      This packet is tracked, meaning that  it  has  previously
39                      traversed  the  connection  tracker.  If this flag is not
40                      set, then no other flags will be set.  If  this  flag  is
41                      set,  then the packet is tracked and other flags may also
42                      be set.
43
44               0x40: snat
45                      This packet was transformed by source address/port trans‐
46                      lation by a preceding ct action.
47
48               0x80: dnat
49                      This  packet  was transformed by destination address/port
50                      translation by a preceding ct action
51
52 Connection State Machine  : http://www.iptables.info/en/connection-state.html
时间: 2024-12-17 17:31:35

OVN conntrack flag的相关文章

js 上传文件后缀名的判断 var flag=false;应用

js 上传文件后缀名的判断  var flag=false;应用 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml"> <head> &

Docker源码解读:1.flag解读

我是怎么想到要先看docker中的flag呢,就是因为docker采用了c/s结构,而且daemon和client都是用同一个程序的,因此,为了做出区分,肯定是要用参数来区分的.先来看位于./docker/docker/docker.go下面的main函数代码: func main() { //第一次肯定是返回false的,因为没有任何initializer if reexec.Init() { return } // Set terminal emulation based on platfo

iptables conntrack有什么用

iptables conntrack有什么用 http://zhidao.baidu.com/link?url=Eh5SRuplbsY_WkxxGkH4bpEyfMnHAe1RwJYSVlRYGKFUovI2F7tMP9TczuEnxzHkwZWodVY7dJARY0GmqiFO9ZJTNjAewJUUhLZtJA9obZ3 ip_conntrack:数据包的链接跟踪处理 我们先来看看怎样阅读/proc/net/ip_conntrack里的conntrack记录.这些记录表示的是当前被跟踪的连接

Activity的启动模式与flag详解(转载)

Activity有四种加载模式:standard(默认), singleTop, singleTask和 singleInstance.以下逐一举例说明他们的区别: standard:Activity的默认加载方法,即使某个Activity在 Task栈中已经存在,另一个activity通过Intent跳转到该activity,同样会新创建一个实例压入栈中.例如:现在栈的情况为:A B C D,在D这个Activity中通过Intent跳转到D,那么现在的栈情况为: A B C D D .此时如

zoj Capture the Flag 比较难的模拟题

Capture the Flag Time Limit: 2 Seconds      Memory Limit: 65536 KB      Special Judge In computer security, Capture the Flag (CTF) is a computer security competition. CTF contests are usually designed to serve as an educational exercise to give parti

协议栈处理中的conntrack HASH查找/Bloom过滤/CACHE查找/大包与小包/分层处理风格

1.路由CACHE的优势与劣势 分级存储体系已经存在好多年了,其精髓在于"将最快的存储器最小化,将最慢的存储器最大化",这样的结果就使资源利用率的最大化,既提高了访问效率,又节省了资源.这是所有的CACHE设计的基本原则. 对于内存访问,几乎所有的CPU都内置了一级cache,二级cache,亲和力好的几个核心甚至设计了三级cache乃至四级cache,然后才是物理 内存,然后是经过精密优化的磁盘交换分区,最后是远程的存储器,这些存储空间逐级变大,访问开销也逐级变大,构成了一个金字塔型

Activity的启动模式与flag详解

Activity有四种加载模式:standard(默认), singleTop, singleTask和 singleInstance.以下逐一举例说明他们的区别: standard:Activity的默认加载方法,即使某个Activity在 Task栈中已经存在,另一个activity通过Intent跳转到该activity,同样会新创建一个实例压入栈中.例如:现在栈的情况为:A B C D,在D这个Activity中通过Intent跳转到D,那么现在的栈情况为: A B C D D .此时如

冒泡排序--注意flag变量的设置

代码: #include<stdio.h> void BubbleSort(int a[],int n){ int i,j; int temp; int flag = 1; // 此处flag变量的设置可以提高算法的效率 for(i=0;i<n-1&&flag;i++){ flag=0; for(j=1;j<n-i;j++){ if(a[j]<a[j-1]){ temp = a[j]; a[j] = a[j-1]; a[j-1] = temp; flag=1;

立flag

反思一下最近的学习 首先最颓废的一点:数据结构的学习太不认真了 第三第四作业没交,上课不怎么听.即使老师口音之类的太严重,也应该好好学,这门课的重要性在复习电路的时候也有小感触 高数,电路,大物的作业也落下了很多,要补回来 这两天的考试确实也发现了挺多问题 都说中国应试考试那一套怎么怎么样,大学的学习我觉得反而应该高考化一点 不管怎么说,以后找找题目刷是很有必要的 四级考试也快到了 只刷了几套卷子,虚的不行,期中过了,该好好刷刷英语了 这周末还要体测,平时还要挤时间练球. 加油吧阿权 flag这