Idea is to embed the port numbers of the path in the packet and carry out source routing From floodlight I get the normal port numbers. If I embed these regular port numbers then the difficulty is that the switches recognise only the datapath port numbers. So I cannot carry out routing as I expect. Instead if I was able to embed the datapath port numbers as such from the controller then it would have been fine!
On Mon, Nov 16, 2015 at 12:44 PM, Justin Pettit <jpet...@cs.stanford.edu> wrote: > > > On Nov 15, 2015, at 10:51 PM, Sree Vidya S D <vidya...@gmail.com> wrote: > > > > Hey Justin, > > > > Thanks for clearing it out > > I am trying to implement source routing using port numbers. > > It turned out that > > void ovs_dp_process_received_packet(struct vport *p, struct sk_buff *skb) > > uses datapath port numbers. For my implementation purpose I need those > port numbers. > > If you're doing local processing, why do you need that information in > Floodlight? Do you have some sort of agent on the local box that > communicates with Floodlight? Not sure if it's helpful, but you can get > the OpenFlow to datapath port mappings with "ovs-appctl dpif/show". > > --Justin > > > -- -- *яєgαя∂ѕ, sreevidya* *There is a beautiful intricacy in law!* _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
