Re: [ovs-discuss] No packet-in with ofp_action_output + OFPP_CONTROLLER

2011-02-16 Thread Ben Pfaff
On Wed, Feb 16, 2011 at 5:31 PM, kk yap wrote: > I am not sure what is wrong here.  Seems like a bug to me at this > point.  Any advice is appreciated. It sounds like a bug to me, too. I'll try to look at this tomorrow. -- "I don't normally do acked-by's.  I think it's my way of avoiding gettin

[ovs-discuss] No packet-in with ofp_action_output + OFPP_CONTROLLER

2011-02-16 Thread kk yap
Hi, I am OVS kernel datapath with ovs-openflowd. I have installed the following flow entries. cookie=0x0, duration=292.116s, table_id=0, n_packets=0, n_bytes=0, priority=24576,icmp actions=CONTROLLER:1500 cookie=0x0, duration=292.116s, table_id=0, n_packets=189, n_bytes=36725, priority=24576,u

Re: [ovs-discuss] ovs-openflowd dying with invalid argument warning

2011-02-16 Thread kk yap
Hi Ben, I move forward to the head of master and that seems to work. Seems like some bugs is fixed in between. Should have thought of git pull --rebase. Sorry for the trouble. Thanks. Regards KK On 16 February 2011 16:07, Ben Pfaff wrote: > On Wed, Feb 16, 2011 at 04:01:57PM -0800, kk yap w

Re: [ovs-discuss] ovs-openflowd dying with invalid argument warning

2011-02-16 Thread kk yap
As a follow-up, I am getting warning like Feb 16 16:03:38|6|dpif|WARN|system@dp0: failed to put[create][modify][zero] (Invalid argument) in_port(1),eth(src=f0:7b:cb:a1:3c:c6,dst=ff:ff:ff:ff:ff:ff),eth_type(0x0806),arp(sip=10.33.0.132,tip=10.33.0.1,op=1), packets:0, bytes:0, used:never Feb 16

Re: [ovs-discuss] ovs-openflowd dying with invalid argument warning

2011-02-16 Thread Ben Pfaff
On Wed, Feb 16, 2011 at 04:01:57PM -0800, kk yap wrote: > I am running OVS with ovs-openflowd (version 1.1.0pre2). openflowd > seems to be killing itself for some reason which I cannot figure out. > Attached is the verbose output of ovs-openflowd and the pcap of the > OpenFlow traffic going on dur

Re: [ovs-discuss] Flow removed message bug

2011-02-16 Thread Justin Pettit
Okay, that makes a bit more sense. My guess is that if you look in ovs-vswitchd's logs, you'll see some messages about "normalization changed ofp_match". Internally, we're clearing those other wildcard bits, since they're meaningless for non-IP/ARP flows (such as your flow definition with eth

Re: [ovs-discuss] Flow removed message bug

2011-02-16 Thread Derek Cormier
Great. I also made a mistake about the field. It was dl_type, not dl_src. It actually works fine for dl_src. - Derek On 02/16/2011 05:36 PM, Justin Pettit wrote: No problem. Most of us are subscribed to both. :-) We'll take a look at it in the morning, California time. I don't expect it w

Re: [ovs-discuss] Flow removed message bug

2011-02-16 Thread Justin Pettit
No problem. Most of us are subscribed to both. :-) We'll take a look at it in the morning, California time. I don't expect it will be a difficult fix. Thanks for reporting it. --Justin On Feb 16, 2011, at 12:26 AM, Derek Cormier wrote: > Now that I think about it, this should have been po

Re: [ovs-discuss] Flow removed message bug

2011-02-16 Thread Derek Cormier
Now that I think about it, this should have been posted to the dev board. Sorry about that! - Derek ___ discuss mailing list discuss@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss_openvswitch.org