[prev in list] [next in list] [prev in thread] [next in thread] 

List:       openvswitch-discuss
Subject:    [ovs-discuss] Adding IP options field in IP header
From:       blp () nicira ! com (Ben Pfaff)
Date:       2013-04-23 16:51:16
Message-ID: 20130423165116.GH22342 () nicira ! com
[Download RAW message or body]

Please don't drop the mailing list.

I don't think it's difficult to handle IP options.  It just isn't
normally very useful.  If you want to add extra information to the IP
header in every packet, then IP options are the way to go.

On Tue, Apr 23, 2013 at 04:03:29PM +0900, ??? wrote:
> Actually, I want to add some extra information to IP header.
> So, I think IP option field is a good candidate for my purpose.
> As you mentioned, it is difficult to handle IP options. Do you have any suggestion?
> should I use payload to put additional information? 
> -----Original Message-----
> From: "Ben Pfaff"<blp at nicira.com> 
> To: "?????????"<kimguji at naver.com>; 
> Cc: <discuss at openvswitch.org>; 
> Sent: 2013-04-23 (?) 01:24:35
> Subject: Re: [ovs-discuss] Adding IP options field in IP header
> 
> On Tue, Apr 23, 2013 at 01:02:34AM +0900, ????????? wrote:
> > I want to add IP options field to receive packet in OVSwitch.
> > In OVS  source code, however, no structure for IP options. 
> 
> If you want to add IP options support, it is because IP options are not
> yet supported, so your conclusion that IP options are not yet supported
> should really not be a big surprise.
> 
> What's your higher-level goal?  It seems to me that it is not too useful
> to match on most IP options, because they can vary per-packet
> (e.g. timestamp) or because they are not widely used (all of them).
> Perhaps you just want to match on the presence of any IP option?
> 
> 

[prev in list] [next in list] [prev in thread] [next in thread]