Re: [ovs-discuss] the meaning of FLOW_WC_SEQ

2014-01-24 Thread linaishan
reason is the bit field I used in the new struct flow, but I change /*/ u_int8_t doff:4; u_int8_t ack:1; u_int8_t rst:1; u_int8_t syn:1; u_int8_t fin:1; /*/ to u_int8_t tcp_ctl; or ovs_be16 tcp_lrf; still get the same error. don't understand. linaishan From: Ben

[ovs-discuss] the meaning of FLOW_WC_SEQ

2014-01-24 Thread linaishan
Hi all, I want to extend the struct flow in lib/flow.h. at line 130 there is a description: /* Remember to update FLOW_WC_SEQ when changing 'struct flow'. */ BUILD_ASSERT_DECL(sizeof(struct flow) == sizeof(struct flow_tnl) + 160 && FLOW_WC_SEQ == 20); what's the meaning of FLOW_W

Re: [ovs-discuss] the default config of ovs

2013-09-04 Thread linaishan
; The function of the two formats is equal. Cloud you tell me where can find the format you given, I guess maybe there are some other assets. The content of "man ovs-vswitchd.conf.db" is too much, I haven't read them. Hope what you will give is not the content of "man ovs-vswi

[ovs-discuss] the default config of ovs

2013-09-04 Thread linaishan
Hi all, I have a question about ovs with no controller. At the beginning, I find the hosts linked to ovs with no controller couldn't ping each other, which just like the situation in mininet, if you don't set a controller, the host1 could't reach to host2. But recently, I find that even there's n