is connection to switch implemented by thread?
On Sat, May 24, 2014 at 9:26 AM, Murphy McCauley
<murphy.mccau...@gmail.com>wrote:
> How about disabling enough links in your topology so that it doesn't have
> loops and then trying? (I'm wondering if the second one has looped back to
> where it started somehow.)
>
> Another thought would be to wireshark all the ports of the switch where
> you're seeing two of these packets. Do you actually see the packet arrive
> twice? Leave twice? Etc.
>
> -- Murphy
>
> On May 23, 2014, at 9:51 PM, farshad tajedin <farshad.taje...@gmail.com>
> wrote:
>
> yes both of them are same except buffer id , i do this in mininet
>
>
> On Fri, May 23, 2014 at 2:53 PM, farshad tajedin <
> farshad.taje...@gmail.com> wrote:
>
>> yes both of them are same except buffer id , i do this in mininet
>>
>>
>> On Fri, May 23, 2014 at 1:23 PM, Murphy McCauley <
>> murphy.mccau...@gmail.com> wrote:
>>
>>> Are the packet-in messages and their payloads 100% identical?
>>>
>>> Are you doing this on real hardware, or in Mininet, or... ?
>>>
>>> -- Murphy
>>>
>>> On May 22, 2014, at 11:13 PM, farshad tajedin <farshad.taje...@gmail.com>
>>> wrote:
>>>
>>> hi murphy
>>> i have a path between two hosts(h1 and h2) in a data center,when i ping
>>> h2 from h1 since switches on this path have no flow entry for route icmp
>>> packet to h2 , the edge switch that h1 connected to it(e_s1) ,send icmp
>>> packet to controller. in controller i handle it and i add flow entry to
>>> each switch on this path in my controller code and at last send packet out
>>> msg to e_s1 to forward this packet. during this action (ping h2 from h1) i
>>> capture traffic of my network by wireshark and i see packet in msg from
>>> e_s1 two times sends to controller that i expect packet in msg must send
>>> once.
>>>
>>>
>>> On Fri, May 23, 2014 at 4:30 AM, Murphy McCauley <
>>> murphy.mccau...@gmail.com> wrote:
>>>
>>>> I think you'll need to provide a lot more detail.
>>>>
>>>> Are you saying that you're trying to proactively insert all the rules
>>>> into the switch when it connects, but you're getting packet-ins (from table
>>>> misses) anyway and you're not expecting them?
>>>>
>>>> How do packet-outs factor in here?
>>>>
>>>> -- Murphy
>>>>
>>>> On May 22, 2014, at 5:45 AM, farshad tajedin <farshad.taje...@gmail.com>
>>>> wrote:
>>>>
>>>> i must say that i use 1.add flow message and 2.packet out message
>>>> sequensialy
>>>>
>>>>
>>>> On Thu, May 22, 2014 at 3:17 PM, farshad tajedin <
>>>> farshad.taje...@gmail.com> wrote:
>>>>
>>>>> hi all
>>>>>
>>>>> i have a fat-tree topology, when i ping a host from another host i
>>>>> found that first host 2 times send packet in message to controller and i
>>>>> dont know why. can anybody help me ?
>>>>>
>>>>> P.S i use core.openflow.addListenerByName("ConnectionUp",
>>>>> start_switch) for event handling.
>>>>>
>>>>> --
>>>>> Best Regards
>>>>>
>>>>> Farshad Tajedin
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Best Regards
>>>>
>>>> Farshad Tajedin
>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>> Best Regards
>>>
>>> Farshad Tajedin
>>>
>>>
>>>
>>
>>
>> --
>> Best Regards
>>
>> Farshad Tajedin
>>
>
>
>
> --
> Best Regards
>
> Farshad Tajedin
>
>
>
--
Best Regards
Farshad Tajedin
