Hi Aaron, The "posioning" of the old entries sounds right, but the encapsulation can be an issue. You might need to wait for OpenFlow 1.1 if you want to control encapsulation using OpenFlow.
Regards KK I don't believe there are switches that encaps packets now. You have t On 26 October 2010 17:14, Aaron Rosen <aro...@clemson.edu> wrote: > Hello, > > I'm trying to write a mobile IP like module for nox. Basically I think it > would work in the following way: > > When a client moves to a different openflow switch I can detect that from > his packet.src coming from a different DPID. At this point I want to delete > the current flow entries associated with this host from the DPID that he was > on. > > Now when those packets come to the controller, I want to encapsulate them > in an IP packet with a unique ip.type value, and send those packets to the > ip address of the new DPID that the host is on (This ip address will > probably have to be known before I'm guessing). (Also this new dpid is in a > different subnet and the host will be keeping his ip address). > > At this point, the openflow switch will send the packet to the controller > which should exam the packet to see the unique ip.type and then rip off the > ip header I added and send the packet to the correct end host. > > > Does this seem doable? Is there an easy way to encapsulate a packet in an > ip packet in openflow? Any pointers for code I should be looking at that may > help? > > Thanks > > Aaron > > -- > Aaron O. Rosen > Masters Student - Network Communication > 306B Fluor Daniel > 843.425.9777 > > > _______________________________________________ > nox-dev mailing list > nox-dev@noxrepo.org > http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org > >
_______________________________________________ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev_noxrepo.org
