Hi Murphy.

Thank you very much for help. Interesting.  I will consider the ethernet
addresses to change the destination, once the component is a L2 switch. Any
results I post a feedback here.


2011/6/3 Murphy McCauley <jam...@nau.edu>

> The switch component is an L2 learning switch, so it makes its decisions
> based
> on ethernet addresses.  It makes this decision for every new flow, but only
> based on the ethernet address.  Once the decision is made, an exact match
> flow
> is installed (if I recall correctly) that will direct that flow out
> whatever
> port it learned the destination ethernet address is connected to (or all
> ports
> if it doesn't know where the destination is).
> So if you want to use the switch component to send traffic somewhere
> specific,
> it's the ethernet address that's important.
> I'm not sure if that helps or not -- maybe we could provide a better answer
> if
> you explained more fully what you're trying to do.
> -- Murphy
> On Friday, June 03, 2011 09:50:08 AM Ricardo Bennesby wrote:
> > Hi all.
> >
> > I would like some help in how can I change the destination of a flow that
> > arrives on nox controller before send it back to switch.
> > For example, I want that in a network with three hosts, when a host 1
> > "pings" to host 2, the component (switch.cc) makes the datapath forward
> it
> > to host 3.
> > If I chande only the flow destination IP (from to, for
> > example) the packets continue being forwarded normally to host 2. Should
> I
> > change all the flow fields in switch component, like mac, in_port, etc?
> Is
> > this the right way?
> >
> > Thank you very much for your help and attention.
> >
> > Best regards.

Ricardo Bennesby da Silva
Ciência da Computação - UFAM
LabCIA - Laboratório de Computação Inteligente e Autonômica
nox-dev mailing list

Reply via email to