[pox-dev] openflow, pox tplink

[Murphy McCauley]

On Feb 7, 2013, at 10:01 PM, Shabbir Ahmed wrote:

> another reason could be that the switch in tp-link is not 100% openflow compatible?

Well, the switch you're running is pretty much all software, so that's not likely to be it.

> can u guide me how to confirm if im doing the right thing (troubleshooting cmds), and OpenFlow is working? and u can give some links to learn more, wat was wrong with l2_forwaring?

The problem with l2_forwarding is that it's seeing everything as coming from the same port.  This is actually going to stop l2_pairs or anything from working correctly, pretty much.  Without being able to control ports independently, you're fairly limited in what you can do.

It's fairly common for cheap switches to have like three real ports.  One is the "WAN" port used to connect to the internet.  One is the wireless adapter.  The other is a single port which is connected to a dumb switch or hub and then fanned out into like four other ports (as viewed by OpenFlow, these are all a single port).

You might want to find out if this is the case with your switch.  You can probably find a reference to it somewhere.  Also, if you run POX with no components and can still ping between the ports, they're probably all switched/hubbed together. Also... if the back of your switch has like five ports on it, but there are only like three interfaces in your ifconfig list, this is probably the case.

-- Murphy