Hi, pyswitch itself is really not aware of any topology. It only stores state that is relevant to switches separately (i.e. it stores a mapping of mac addresses to local ports for a switch).
Now, whether a control packet (like a packet_in) will reach the controller if it's not directly physically connected to it is another issue, and is irrelevant to what NOX application (eg pyswitch) is running. Switches are connected to the controller through a separate control channel, so as long as this channel has been established (which is when the switch first connects to NOX), then the packet_ins will find their way to NOX through that (irrespective of dataplane connectivity, which is established by NOX applications) (another thing to consider is whether the switch-controller connection is in-bound/out-of-bound) Does this make sense? On Wed, Oct 19, 2011 at 5:20 PM, scolfield <kscolfi...@gmail.com> wrote: > Hi, > > The pyswitch example can learn topology of networks? Such as a corporation > architecture when > there are hierarchical switches interconnected one to another creating > several "layers" of switches, > at this case, the one openflow controller connected to two distinct > switches, can learn which ports > to send a ping packets, for example? The packet in messages will be > forwarded automatically through > switches until reach a controller? > > -- > scolfield > > _______________________________________________ > nox-dev mailing list > nox-dev@noxrepo.org > http://noxrepo.org/mailman/listinfo/nox-dev > >
_______________________________________________ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev
