----- Original Message ----- From: "Dan Talayco" <dtala...@stanford.edu> To: "Aaron Rosen" <aro...@clemson.edu> Cc: openflow-discuss@lists.stanford.edu Sent: Wednesday, May 16, 2012 5:51:07 PM Subject: Re: [openflow-discuss] Issue Rewriting Source Mac address of Pronto 3290s
Inline In my case however, the packet: 1. arrives at dpid1 2. is tx to the controller 3. I insert an action to rewrite the mac address such as 00:00:00:00:00:fc 4. I verify that the flow mod was installed using dpctl on the switch 5. However, the pkt is not transmitted to the next dpid, ie dpid2. Rather, srcHost, tx yet a second pkt to dpid1 and so on. What is "the packet"? Is this a packet out the controller is expected to send? Or some subsequent packet? >"the packet" (in 2.) is the first packet of a stream of icmp packets (pings) >transmitted by the srcHost. Note that the table action for packet out is not supported on Indigo, so if you're counting on the switch to carry out the action of changing the dest-MAC on a packet-out packet, it won't happen. > Can you expound some more? Assuming the flow mod was installed successfully, > I was under the impression that for all subsequent packets from srcHost, the > switch would rewrite (i.e. if the mac address is x, rewrite it with y) the > destination Mac address of all packets and transmit these packets to the next > dpid on the way to the destination. Assuming I am wrong, what exactly does it > mean if indigo supports the "OFPAT_SET_DL_SRC" action? Where is this > rewriting taking place? At the controller? -Dan I have realized that if the rewritten mac address is the same as the destination address (i.e. 00:25:64:a4:5c:f5 and NOT 00:00:00:00:00:fc), the pkt leaves dpid1, is transmitted to dpid2 just fine. -Ali Thanks, Dan On Wed, May 16, 2012 at 8:28 AM, Ali Sydney < asyd...@k-state.edu > wrote: Hi Everyone, I am having some issues with rewriting the destination mac address on the Pronto 3290. Below is my current setup: srcHost <--> dpid1 <--> dpid2 <--> dpid3 <--> dstHost REF: srcHost Mac: b8:ac:6f:2a:6a:ea dstHost Mac: 00:25:64:a4:5c:f5 Ideally, when I tx a pkt from srcHost to dstHost, at the controller, I see ip packets entering the dpids in the following order: 1. dpid1 2. dpid2 3. dpid3 As an example, assuming I am sending a pkt from srcHost to dstHost, and I rewrite the destination mac address as follows: actions = [[openflow.OFPAT_SET_DL_DST,"00:25:64:a4:5c:f5"],[openflow.OFPAT_OUTPUT, [0, prt[0]]]] using dpctl at dpid1, I see the flow installed with the actions above (NB. I am using the actual dstHost Mac address). This works just fine, and the next dpid accessed on this path is "dpid2". However, this is not the case if I change the destination mac address as follows: actions = [[openflow.OFPAT_SET_DL_DST,"00:00:00:00:00:fc"],[openflow.OFPAT_OUTPUT, [0, prt[0]]]] For these actions, the flow mod is registered at the switch (as I verified using dpctl). However, the next packet arrives at "dpid1" (which implies that perhaps the flow was not actually installed though it appears on the switch). As in the previous example, I would expect the next packet to arrive at "dpid2". Can you please provide some feedback? BTW. I am running the "indigo 12.03.19" firmware on all switches. Cheers! Syd _______________________________________________ openflow-discuss mailing list openflow-discuss@lists.stanford.edu https://mailman.stanford.edu/mailman/listinfo/openflow-discuss _______________________________________________ openflow-discuss mailing list openflow-discuss@lists.stanford.edu https://mailman.stanford.edu/mailman/listinfo/openflow-discuss _______________________________________________ openflow-discuss mailing list openflow-discuss@lists.stanford.edu https://mailman.stanford.edu/mailman/listinfo/openflow-discuss
