[ovs-dev] packet_out with modified mac headers

Sree Vidya S D vidya426 at gmail.com
Mon Oct 27 18:55:49 UTC 2014


thanx for clearing that !

On Mon, Oct 27, 2014 at 9:24 PM, Ben Pfaff <blp at nicira.com> wrote:

> Please don't drop the list.
>
> handle_packet_out().
>
> On Mon, Oct 27, 2014 at 11:13:01AM +0530, Sree Vidya S D wrote:
> > So which function should I monitor for handling packet_out messages from
> > controller?
> > Can you please help?
> >
> > On Mon, Oct 27, 2014 at 12:52 AM, Ben Pfaff <blp at nicira.com> wrote:
> >
> > > On Sun, Oct 26, 2014 at 02:20:30PM +0530, Sree Vidya S D wrote:
> > > > h1-----(1)s1(2)---(2)s2(3)---(2)s3(3)----(2)s4(1)---h4
> > > >                                 |               |
> > > >                                (1)           (1)
> > > >                                 h2           h3
> > > >
> > > > With this topology when I do h1 ping h4 the ICMP packet from h1 goes
> to
> > > > switch s1.
> > > > s1 is unaware about the flow so it will send the packet -in message
> to
> > > the
> > > > controller.
> > > > Iam using floodlight as the remote controller.
> > > > In floodlight controller Iam editing the mac headers of the packet in
> > > > message and replacing it with the port numbers the packet has to go
> > > through
> > > > to reach h4.
> > > > I can see the modified packet in wireshark but I think
> > > > "void ovs_dp_process_received_packet(struct vport *p, struct sk_buff
> > > *skb)"
> > > > function in datapath.c isnt receiving that particular packet-out
> message.
> > >
> > > A packet-out wouldn't go through there, since it isn't received from a
> > > port but from the controller.
> > >
> >
> >
> >
> > --
> > --
> >
> > *яєgαя∂ѕ, sreevidya*
>



-- 
-- 

*яєgαя∂ѕ, sreevidya*



More information about the dev mailing list