Re: [pox-dev] match attribute of ofp_flow_mod()

2013-10-24 Thread Murphy McCauley
In OpenFlow 1.0, an unmatched packet is sent to the controller. This is described on page 2 of the OpenFlow 1.0 specification. -- Murphy On Oct 24, 2013, at 5:33 PM, durga wrote: > Thanks again Murphy. > So ofp_match typically creates a filter for further packets to 'match' > against. > if

Re: [pox-dev] match attribute of ofp_flow_mod()

2013-10-24 Thread durga
Thanks again Murphy. So ofp_match typically creates a filter for further packets to 'match' against. if incase a match is not created , then by default, the switch drops the 'msg' from controller ..is it? or does it matching all the packets when there is no match ? I am thinking on terms of ACLs

Re: [pox-dev] L2.multi and discovery

2013-10-24 Thread Murphy McCauley
I tried to recreate the experiment you describe, and it seems to work fine: http://www.noxathome.org/x/Murphy/l2_multi3.png Where am I going wrong? Note that depending on configuration, discovery and l2_multi may require a little time after startup before things will work (for a complete round

Re: [pox-dev] L2.multi and discovery

2013-10-24 Thread AMER
Hello, this is part of the debug: DEBUG:forwarding.l2_multi:Unlearned e6:b1:63:f8:d3:23 DEBUG:forwarding.l2_multi:Flood multicast from 7e:40:55:eb:86:05 INFO:openflow.discovery:link detected: 00-00-00-00-00-01.5 -> 00-00-00-00-00-01.4 DEBUG:forwarding.l2_multi:Unlearned 7e:40:55:eb:86:05 DEBUG:

Re: [pox-dev] Identifying number of users and number of flows

2013-10-24 Thread Sayed Qaiser Ali Shah Shah
Thanks a lot Murphy I did it. I was trying to find number of flows. I declared flow as variable and number of flows is flow value in that variable. I was trying to pass value from one file to another. I came up with an idea and did it accordingly. I declared global variable in separate file and the

Re: [pox-dev] L2.multi and discovery

2013-10-24 Thread Murphy McCauley
Can you post your logs from a run of l2_multi that doesn't work? -- Murphy On Oct 24, 2013, at 2:29 PM, Amer wrote: > Hello, > > Thank you > > I apologize, h1 and h3 are residing in different switch not subnet. h1 > 10.0.0.1 > h3 10.0.0.3. > Also, I tried the following statement and it is wo

Re: [pox-dev] L2.multi and discovery

2013-10-24 Thread Amer
Hello, Thank you I apologize, h1 and h3 are residing in different switch not subnet. h1 10.0.0.1 h3 10.0.0.3. Also, I tried the following statement and it is work fine: Pox.py forwarding.l2_learning I am using tree topology with fan=2 Best regards, Amer On ٢٤‏/١٠‏/٢٠١٣, at ٩:٣٠ م, Murphy McCaul

Re: [pox-dev] Identifying number of users and number of flows

2013-10-24 Thread Murphy McCauley
Can you fill us in more on what you're trying to accomplish? It's not clear to me what your end-goal is (or what you mean by "flow value"). -- Murphy On Oct 24, 2013, at 1:39 PM, Sayed Qaiser Ali Shah Shah <11msitqs...@seecs.edu.pk> wrote: > Thanks Alison Chan and Murphy McCauley for your hel

Re: [pox-dev] match attribute of ofp_flow_mod()

2013-10-24 Thread Murphy McCauley
On Oct 24, 2013, at 12:16 PM, durga wrote: > hmm.. ok , in l2_learning.py code, why did we 'match' msg with the parsed > packet?? > > > > msg = of.ofp_flow_mod() > > > msg.match = of.ofp_match.from_packet(packet, event.port) > > > > > > I thought ofp_match() is used

Re: [pox-dev] Identifying number of users and number of flows

2013-10-24 Thread Sayed Qaiser Ali Shah Shah
Thanks Alison Chan and Murphy McCauley for your help. I found number of flows by using https://github.com/alis0nc/poxstuff/blob/master/flow_stats.py script modified by Alison Chan. Now I am facing problem in passing the flow value which I found, to l2_learning.py in which I have defined queues. Can

Re: [pox-dev] match attribute of ofp_flow_mod()

2013-10-24 Thread durga
hmm.. ok , in l2_learning.py code, why did we 'match' msg with the parsed packet?? msg = of.ofp_flow_mod() msg.match = of.ofp_match.from_packet(packet, event.port) I thought ofp_match() is used only for comparison . But the debug above shows that, ofp_match() not only compares

Re: [pox-dev] match attribute of ofp_flow_mod()

2013-10-24 Thread Murphy McCauley
I'm afraid I don't follow the issue. Maybe you can post more code and try to further explain what you think is happening vs. what you think *should* be happening? -- Murphy On Oct 23, 2013, at 7:13 PM, durga wrote: > Hello All, > > Just needed a confirmation on my understanding about match

Re: [pox-dev] L2.multi and discovery

2013-10-24 Thread Murphy McCauley
Hmm... as far as I remember, l2_multi and l2_learning shouldn't behave differently in terms of L3. My memory is that with either of them, you're likely to run into the same problem -- it's not with POX or OpenFlow or anything -- it's with the hosts. The hosts will generally expect that they n

[pox-dev] L2.multi and discovery

2013-10-24 Thread Amer
Hello, I would like to thank you for your effort in responding to our questions I used the following command but it does not work Pox.py l2.multi openflow.discovery I could not ping between h1->h3 # reside in different subnets I tried this one, it works fine: Pox.py l2.learning openflow.disco