Hi XH NOX does not provide IP routing services in the conventional sense (as mentioned in the doc). So, the IP gateway in your model must be a non-OF device. If the gateway for your subnet is OpenFlow-enabled and NOX is the controller, the routing module will not be able to perform what you need to get the two hosts on different subnets to communicate with each other. You will have to extend it to pay attention to the IP address instead.
I'm not too familiar with authenticator to say how dst_locations and route_destinations are initialized. I believe it is based on a combination of MAC and IP. But, I may be wrong. Srini. On Fri, Apr 1, 2011 at 12:40 AM, xuhong713 <xuhong...@gmail.com> wrote: > Hi all, > In NOX's documentation, it says that routing does not refer to standard IP > based routing. "Routing" identifies hosts by their MACs and sets up routes > per-flow. If routing doesn't know the location of the destination MAC, it > floods the packet. > But this raises a doubt: whenever a host wants to ping another host in > another subnet, it always send packet to its gateway, a packet whose dst MAC > address is the MAC address of the port of that router. So how does the > router determine the location of the destination host's location if it is > functioning according to the MAC address? Or if there is any facility > provided by Authenticator that can transfer dst IP address into full dst > location information? > I see that authenticator raise a flow-in event, and the event has a struct > dst_locations and route_destinations, how does authenticator fill these > places? > > Thanks. > > XH > > 2011-04-01 > ________________________________ > xuhong713 > _______________________________________________ > 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
