Hi Ben,

tcpdump shows packets are coming on veths.

ovn@ovn-VirtualBox:~/ovs/tutorial$ ovs-ofctl show br-int
OFPT_FEATURES_REPLY (xid=0x2): dpid:0000468b623a8547
n_tables:254, n_buffers:256
capabilities: FLOW_STATS TABLE_STATS PORT_STATS QUEUE_STATS ARP_MATCH_IP
actions: output enqueue set_vlan_vid set_vlan_pcp strip_vlan mod_dl_src 
mod_dl_dst mod_nw_src mod_nw_dst mod_nw_tos mod_tp_src mod_tp_dst
 1(veth_H1-1): addr:aa:55:aa:55:02:35
     config:     PORT_DOWN
     state:      LINK_DOWN
     speed: 0 Mbps now, 0 Mbps max
 2(veth_H2-1): addr:aa:55:aa:55:02:36
     config:     PORT_DOWN
     state:      LINK_DOWN
     speed: 0 Mbps now, 0 Mbps max
 LOCAL(br-int): addr:46:8b:62:3a:85:47
     config:     PORT_DOWN
     state:      LINK_DOWN
     speed: 0 Mbps now, 0 Mbps max
OFPT_GET_CONFIG_REPLY (xid=0x4): frags=normal miss_send_len=0
ovn@ovn-VirtualBox:~/ovs/tutorial$ sudo tcpdump -i veth_H1-1 
tcpdump: WARNING: veth_H1-1: no IPv4 address assigned
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on veth_H1-1, link-type EN10MB (Ethernet), capture size 65535 bytes
14:46:19.781495 ARP, Request who-has 1.1.1.2 tell 1.1.1.1, length 28
14:46:20.785863 ARP, Request who-has 1.1.1.2 tell 1.1.1.1, length 28
14:46:21.784116 ARP, Request who-has 1.1.1.2 tell 1.1.1.1, length 28
14:46:22.793937 ARP, Request who-has 1.1.1.2 tell 1.1.1.1, length 28
14:46:23.792133 ARP, Request who-has 1.1.1.2 tell 1.1.1.1, length 28
14:46:24.793920 ARP, Request who-has 1.1.1.2 tell 1.1.1.1, length 28
^C
6 packets captured
6 packets received by filter
0 packets dropped by kernel
ovn@ovn-VirtualBox:~/ovs/tutorial$ sudo tcpdump -i veth_H2-1 
tcpdump: WARNING: veth_H2-1: no IPv4 address assigned
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on veth_H2-1, link-type EN10MB (Ethernet), capture size 65535 bytes
14:46:43.006131 ARP, Request who-has 1.1.1.1 tell 1.1.1.2, length 28
14:46:44.004463 ARP, Request who-has 1.1.1.1 tell 1.1.1.2, length 28
14:46:45.004820 ARP, Request who-has 1.1.1.1 tell 1.1.1.2, length 28
14:46:46.019951 ARP, Request who-has 1.1.1.1 tell 1.1.1.2, length 28
14:46:47.016585 ARP, Request who-has 1.1.1.1 tell 1.1.1.2, length 28
14:46:48.016147 ARP, Request who-has 1.1.1.1 tell 1.1.1.2, length 28
14:46:49.034906 ARP, Request who-has 1.1.1.1 tell 1.1.1.2, length 28
14:46:50.032382 ARP, Request who-has 1.1.1.1 tell 1.1.1.2, length 28
14:46:51.033053 ARP, Request who-has 1.1.1.1 tell 1.1.1.2, length 28

Port counters show 0 packets received.

ovn@ovn-VirtualBox:~/ovs/tutorial$ ovs-ofctl dump-ports br-int
OFPST_PORT reply (xid=0x2): 3 ports
  port LOCAL: rx pkts=0, bytes=0, drop=0, errs=0, frame=0, over=0, crc=0
           tx pkts=0, bytes=0, drop=0, errs=0, coll=0
  port  1: rx pkts=0, bytes=0, drop=0, errs=0, frame=0, over=0, crc=0
           tx pkts=0, bytes=0, drop=0, errs=0, coll=0
  port  2: rx pkts=0, bytes=0, drop=0, errs=0, frame=0, over=0, crc=0
           tx pkts=0, bytes=0, drop=0, errs=0, coll=0
ovn@ovn-VirtualBox:~/ovs/tutorial$

Could this be a sandbox issue? Similar setup (Linux containers and OVS) works 
with ODL controller by programming the flows manually.

Maurice

-----Original Message-----
From: Ben Pfaff [mailto:b...@ovn.org] 
Sent: Sunday, May 08, 2016 9:34 AM
To: Maurice Qureshi <maurice.qure...@calix.com>
Cc: Justin Pettit <jpet...@ovn.org>; discuss@openvswitch.org
Subject: Re: [ovs-discuss] OVN Questions

On Fri, May 06, 2016 at 11:02:54PM +0000, Maurice Qureshi wrote:
> Thank Ben. 
> 
> Now in order to see if traffic is really getting forwarded by the flows 
> created by OVN and OVS, I have done following.
> 
> 1) Created two Linux Containers with MAC addresses as 00::01 and 00::02. They 
> are in both same subnet (1.1.1.1/24 and 1.1.1.2/24) with their default gw as 
> 1.1.1.254.
> 
> 2) Modified the ovn/env1/setup.sh to add Linux Containers ports instead 
> lport1 and lport2. The new script looks as following as last two lines:
> 
> ovs-vsctl add-port br-int veth_H1-1 -- set Interface veth_H1-1 
> external_ids:iface-id=sw0-port1 ovs-vsctl add-port br-int veth_H2-1 -- 
> set Interface veth_H2-1 external_ids:iface-id=sw0-port2
> 
> After having done that, that is how the output of "ovs-ofctl show br-int" 
> looks like.
> 
> ovn@ovn-VirtualBox:~/ovs/tutorial$ ovs-ofctl show br-int 
> OFPT_FEATURES_REPLY (xid=0x2): dpid:0000468b623a8547 n_tables:254, 
> n_buffers:256
> capabilities: FLOW_STATS TABLE_STATS PORT_STATS QUEUE_STATS 
> ARP_MATCH_IP
> actions: output enqueue set_vlan_vid set_vlan_pcp strip_vlan 
> mod_dl_src mod_dl_dst mod_nw_src mod_nw_dst mod_nw_tos mod_tp_src 
> mod_tp_dst
>  1(veth_H1-1): addr:aa:55:aa:55:02:35
>      config:     PORT_DOWN
>      state:      LINK_DOWN
>      speed: 0 Mbps now, 0 Mbps max
>  2(veth_H2-1): addr:aa:55:aa:55:02:36
>      config:     PORT_DOWN
>      state:      LINK_DOWN
>      speed: 0 Mbps now, 0 Mbps max
>  LOCAL(br-int): addr:46:8b:62:3a:85:47
>      config:     PORT_DOWN
>      state:      LINK_DOWN
>      speed: 0 Mbps now, 0 Mbps max
> OFPT_GET_CONFIG_REPLY (xid=0x4): frags=normal miss_send_len=0 
> ovn@ovn-VirtualBox:~/ovs/tutorial$
> 
> 
> But the ping between two Linux containers doesn't work. None of the flow 
> counters increase. Could it because the link config and state are down? If 
> so, how can I bring them up. Tried "ovn-nbctl lport-set-enabled sw0-port1 
> enabled" command for both ports, but to no avail.
> 
> 
> Below are the flows. 
> 
> ovn@ovn-VirtualBox:~/ovs/tutorial$ ovs-ofctl dump-flows br-int 
> NXST_FLOW reply (xid=0x4):
>  cookie=0x0, duration=12552.047s, table=0, n_packets=0, n_bytes=0, 
> idle_age=12552, priority=100,in_port=1 
> actions=load:0x1->NXM_NX_REG5[],load:0x1->OXM_OF_METADATA[],load:0x1->
> NXM_NX_REG6[],resubmit(,16)  cookie=0x0, duration=12527.316s, table=0, 
> n_packets=0, n_bytes=0, idle_age=12527, priority=100,in_port=2 
> actions=load:0x2->NXM_NX_REG5[],load:0x1->OXM_OF_METADATA[],load:0x2->
> NXM_NX_REG6[],resubmit(,16)

It must be something pretty basic, since the ingress flows above for packets 
coming into the system directly from the veths don't show any packets.  Try 
running tcpdump on the veths to see that some packets are actually coming in on 
them.
_______________________________________________
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss

Reply via email to