From: jamal <hadi@cyberus.ca>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: David Miller <davem@davemloft.net>, netdev@vger.kernel.org
Subject: Re: [RFC][IPSEC]: tunnel mode processing
Date: Fri, 01 Sep 2006 08:17:14 -0400 [thread overview]
Message-ID: <1157113034.5057.62.camel@jzny2> (raw)
In-Reply-To: <20060901040713.GA9840@gondor.apana.org.au>
On Fri, 2006-01-09 at 14:07 +1000, Herbert Xu wrote:
> On Thu, Aug 31, 2006 at 08:55:27PM -0400, jamal wrote:
> >
> > Would it be reasonable to do a check so that incase a skb->dst doesnt
> > exist, the inner headers values can be used i.e something along
> > xfrm4_tunnel_output()::
>
> If you didn't care what values they were, couldn't you just stuff some
> bogus dst into the skb?
That bogus dst is NULL ;->
> If this packet is going somewhere you're going
> to have a dst one way or another :)
If i was going to use routing/layer 3, then true. At the pktgen level
"somewhere" is just "shove down the ether". Actually (i havent thought
clearly about this) wouldnt a bump in the wire implementation aka
bridging level also not care about route details?
Note: This does not absolve the need for a secure ipid or a proper ttl.
> Also, the IPID is only generated if DF is not set on the packet.
> Otherwise this path is already as fast as it can be.
In the case of traffic generation, if i could shave even more cycles the
better since i want to generate high speed. In this case the cycles
would be in creating a fake dst and attaching it some fake values.
I do agree that it is an awkward way of achieving my goals - but i dont
know of a clever way to do it ;->
cheers,
jamal
next prev parent reply other threads:[~2006-09-01 12:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-01 0:55 [RFC][IPSEC]: tunnel mode processing jamal
2006-09-01 4:07 ` Herbert Xu
2006-09-01 12:17 ` jamal [this message]
2006-09-01 12:22 ` Herbert Xu
2006-09-01 12:56 ` jamal
2006-09-01 13:04 ` Herbert Xu
2006-09-01 13:12 ` jamal
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1157113034.5057.62.camel@jzny2 \
--to=hadi@cyberus.ca \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox