Hi, Here's one example of what Christian has mentioned. http://conferences.sigcomm.org/sigcomm/2010/papers/sigcomm/p465.pdf Cheers, HIDE
_____ From: [email protected] [mailto:[email protected]] On Behalf Of Christian Esteve Rothenberg Sent: Tuesday, April 05, 2011 3:27 AM To: adashio Cc: [email protected] Subject: Re: [openflow-discuss] Source Routing in Openflow As far as I know, Source Route Option fields (or any IP Option) are not supported in current flow match structures. What you can do is overload some fields in the packet header, such as the 48-bit MAC destination and "encode" there some form of source route, provided you have the corresponding wildcarded / bitmasked flow entries in the switches. -Christian On Mon, Apr 4, 2011 at 10:07, adashio <[email protected]> wrote: Hello, is it possible to implement source routing in openflow? I'm thinking about the following scenario: packet comes to controller and based on criteria like MAC, IP address, etc. controller tells switch to rewrite IP Header with source route option: Source Route Option ------------------- +--------+--------+--------+---------//--------+ |00000011| length | source route | +--------+--------+--------+---------//--------+ Option=3 so packets will be routed through the path specified by controller. Openflow / NOX is new environment for me and I wanted to hear your opinion if it does makes sense and can be implemented in mininet. Thanks, Adam _______________________________________________ openflow-discuss mailing list [email protected] https://mailman.stanford.edu/mailman/listinfo/openflow-discuss -- Christian
_______________________________________________ openflow-discuss mailing list [email protected] https://mailman.stanford.edu/mailman/listinfo/openflow-discuss
