Murphy Thanks for your prompt response and I appreciate it A LOT
Thanks =Senthil ________________________________ From: Murphy McCauley <[email protected]> To: senthil arumugam <[email protected]> Cc: "[email protected]" <[email protected]> Sent: Tuesday, March 26, 2013 6:09 PM Subject: Re: [pox-dev] Issue in the flow installed by POX application On Mar 26, 2013, at 8:59 AM, senthil arumugam wrote: When apps wants to install its own flow with 5 tuplets and let this packet be treated by normal switching. >Since it does not know what actual output port to send, it may like the >forwarding feature do the job. > Sure, though all of the other forwarding components take care of this without using normal. I thought by choosing'Normal' action, the above can be acheived. Looks like it may not work with controler..? > The controller itself isn't the problem. So what is the expected behavior when an app installs a flow with action : Normal. > This is up to the switch. I don't actually know what Linux OVS does. Boot it up to the normal network stack? When a packet that matches flow fields comes, shouldn't trigger the nromal control packets like arp and learns the right output port? > Maybe so, but what about answering the ARPs from the web server? These will hit OVS first, and l2_learning will forward them and the results will probably not be what you want. You probably want them to be handled by the NORMAL mechanism too. For that matter, you seem to have installed the NORMAL rule for this flow in one direction, but not the other. Maybe you should not try to combine l2_learning and NORMAL. Try writing a component that just installs a single rule: send all traffic to NORMAL. See if things work. If so, then try writing a higher priority rule to block traffic. -- Murphy
