If you are on mininet's CLI, you can do something like "s1 dump-flows tcp:
127.0.0.1:<port>" where port is the port of the switch you want to query
(usually the first switch listens on 6634, the second on 6635 and so on)
("s1" is really irrelevant here, you could run the same command through any
running switch. It's the port that matters)
If you are on a console of the system where mininet is running (but not on
mininet's CLI), you can do "ovs-ofctl dump-flows tcp:127.0.0.1:<port>"
(I don't know if these are the best practices, but this is how I've been
doing it, particularly the first alternative, through mininet)
On Thu, May 31, 2012 at 8:07 AM, Anthony Salim <
[email protected]> wrote:
> Hi Andry,
>
> Not sure but usually i will ping from one host to another host and then i
> will ssh to the switch by using xterm (name of switch s1~sX) and inside of
> the switch i see the switch flow by using dpctl dump-flows tcp:127.0.0.1:(the
> port number switch listening to)
>
>
> Regards,
> Anthony
>
>
> On Thu, May 31, 2012 at 4:46 PM, Andry Anthony <
> [email protected]> wrote:
>
>> hi all ,
>> i am using mininet and want to see the flow entries of the switch ,
>> so i running this command ,
>>
>> mininet> dpctl dump-flows switch
>> *** s2
>> ------------------------------------------------------------------------
>> dpctl: field tcp:127.0.0.1:6634 missing value
>> *** s3
>> ------------------------------------------------------------------------
>> dpctl: field tcp:127.0.0.1:6635 missing value
>> *** s4
>> ------------------------------------------------------------------------
>> dpctl: field tcp:127.0.0.1:6636 missing value
>> *** s5
>> ------------------------------------------------------------------------
>> dpctl: field tcp:127.0.0.1:6637 missing value
>>
>>
>> did i miss something ?
>>
>>
>> thanks
>> Regards, Andry
>>
>
>
