Re: [ovs-discuss] OVS Controller connection port

2017-04-18 Thread 蘇于倫
Got it. I'll try it. Ethan Ben Pfaff 於 2017年4月19日 週三 上午2:08寫道: > I guess that if you know these kinds of specific properties of your > network, then perhaps you should disable in-band control and add your > own control flows. > > On Tue, Apr 18, 2017 at 05:31:37PM +, 蘇于倫

Re: [ovs-discuss] OVS Controller connection port

2017-04-18 Thread 蘇于倫
Thanks, Ben! In case of the last email content is hidden, I re-send the question again here: If I set the action of in-band hidden flows to be output: OFPP_PORT_X with X being the port number: 1, 2 or 3, etc, which are defined in openflow-1.0.h. Does it make sense to direct all in-band packet

Re: [ovs-discuss] OVS Controller connection port

2017-04-18 Thread Ben Pfaff
One way, which may not be satisfactory, is to use "ovs-appctl ofproto/trace" to simulate a packet from the switch to the controller. On Tue, Apr 18, 2017 at 03:39:24PM +, 蘇于倫 wrote: > Hi Farooq, > > Thanks for the comments. > > I use the command a lot. However, what I want to get is which

Re: [ovs-discuss] OVS Controller connection port

2017-04-18 Thread 蘇于倫
Hi Farooq, Thanks for the comments. I use the command a lot. However, what I want to get is which ports the OVS is using for hidden flow packet. The actions of default hidden flows are NORMAL (ports) which do not provide this info. If I got any misunderstanding, please kindly comment! Thanks

[ovs-discuss] OVS Controller connection port

2017-04-18 Thread 蘇于倫
Hi everyone, I'd like to know if we can see which ports the OVS is using to connect to controller in "in-band" mode? I use ovs-appctl fdb/show , and get the following table port VLAN MACAge 2 0 00:0c:29:30:04:484 1 0 00:0c:29:c2:d1:420 1 0