Hi Kyriakos,

Thank you very much for this clear answer, now I don't get  the error. I
will have an other question. Now, when I ping between two host, I get the
information of this ping on my controller, I use the NOX GUI right now and
I have tried a lot of different controller. But all the time, I get almost
the same problem. I don't see any flow. I was thinking by pinging between
two host the informations  would go to my controller and these informations
wil be display on the GUI. In my case, I just get the topology, not more.


2012/5/9 Kyriakos Zarifis <[email protected]>

> Hi Julien,
>
> you get this because your network has a loop, and pyswitch doesn't deal
> with loop (unless you run  spanning_tree with it)
> pyswitch initially floods packets for which it doesn't know where the
> destination is, and keeps track of where it received packets from given
> source hosts.
> For example, in your plan1 topology, when client1 sends a packet to
> client2 or client3, OFswitch1 will register that client1 is on its port1,
> and will then flood the packet to the other 2 ports.
> Since there is a loop, however, those flooded packets will return back to
> those 2 "internal" ports (2 and 3), and that's when you get that message.
>
>
> On Wed, May 9, 2012 at 5:30 AM, Julien Ratinaud <[email protected]>wrote:
>
>> Hello everybody,
>>
>> I am student in Bachelor Computer Networks and Telecommunications and the
>> project I have to realized for the end of my year is to create an Openflow
>> network. I am currently using a NOX controller which is connected to three
>> openflow switch. My three Openflow switch are well connected to my
>> controller. But, when I am launching a ping for example, I am getting this
>> error on my controller  :
>>
>> *pyswitch|ERR:'**warning** learned port = inport'*
>> *pyswitch|ERR:'**warning** learned port = inport'*
>> *
>> *
>> *My topology** : **http://hpics.li/f8a9209 and http://hpics.li/ee64160*
>> *
>> *
>> Thank You !
>> *
>> *
>> *
>> *
>> *
>> *
>>
>> *
>> *
>> * *
>> *
>> *
>> *
>> *
>> *
>> *
>> *
>> *
>>
>
>

Reply via email to