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 <[email protected]> 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 work fine: > Pox.py forwarding.l2_learning > I am using tree topology with fan=2 > > Best regards, > Amer > > On ٢٤/١٠/٢٠١٣, at ٩:٣٠ م, Murphy McCauley <[email protected]> wrote: > >> 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 >> need a gateway to communicate with another subnet. If you reconfigure their >> routing tables so that they don't, things will work fine. IIRC, l3_learning >> gets around this by establishing "fake" gateways. >> >> -- Murphy >> >> On Oct 24, 2013, at 8:44 AM, Amer <[email protected]> wrote: >> >>> 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.discovery >>> >>> I can ping between >>> h1->h3 # reside in different subnets >>> >>> Thank you again >>> Best regards, >>> Amer >>> >>> >>> Sent from my iPhone >> >>
