NXST_FLOW reply (xid=0x4): cookie=0x0, duration=2938.314s, table=0, n_packets=0, n_bytes=0, idle_age=2938, in_port=1 actions=output:2 cookie=0x0, duration=2943.819s, table=0, n_packets=130, n_bytes=20082, idle_age=11, in_port=2 actions=output:1
Just forward all flow from 1 to 2 and 2 to 1. 2013/7/24 Jesse Gross <[email protected]> > On Tue, Jul 23, 2013 at 7:11 AM, Can Zhang <[email protected]> wrote: > > Hello, > > > > Firstly I'll describe a simple scenario I tried: > > > > peer packets --- eth0 ---- ovs ---- tap0 > > > > I configured tap0 with IP 192.168.57.100, two flows to forward packets > from eth0 and tap0 to the other side, and pinged from outside to the IP. I > did capture ARP request on eth0 using wireshark, but could not see any > packets on tap0. It seems that after attach a port to ovs, the IP address > is no longer effective. > > > > My goal is to use a machine installed with ovs as a openflow switch but > it can also handle some packets(say, a normal socket server can still > work). So I'm thinking of extract some packets to tap0 and make the server > listen on it. But the experiments I did failed as above. I have no idea > what to try next so I come to see if somebody could give me some > suggestions. > > What do the flows that you installed look like? At the Open vSwitch > level, IP addresses on the interfaces do not matter. > -- Best regards, Can Zhang
_______________________________________________ discuss mailing list [email protected] http://openvswitch.org/mailman/listinfo/discuss
