* Re: Sending sk_buffs without being tied to a struct sock
[not found] ` <3E21A5AE.5060607@trash.net>
@ 2003-01-13 3:11 ` Joshua Stewart
0 siblings, 0 replies; only message in thread
From: Joshua Stewart @ 2003-01-13 3:11 UTC (permalink / raw)
To: Patrick McHardy, Linux Kernel Mailing List
At this point, if I call skb->dst->output() what should skb->data point
to? A properly crafted IP packet? Checksummed and all? I shouldn't
need any layer 2 info in my skb at all to use this solution, should I?
Thanks for the help. I think this will do the trick.
J
On Sun, 2003-01-12 at 12:28, Patrick McHardy wrote:
> Joshua Stewart wrote:
>
> >
> >I'm trying to take "hand-built" sk_buffs with little more than some data
> >and a dev member and push them to the NIC for transmission. I would
> >like to simply give them to dev_queue_xmit. Does anybody know what
> >state I should have them in before handing them to dev_queue_xmit?
> >Should skb->data point to the start of a MAC header or an IP header?
> >
> >Also, given an IP address in skb->nh.iph->daddr, what's the easiest way
> >to get the appropriate MAC address?
> >
> use ip_route_output_key() and then skb->dst->output(), that way it will work on all media
> and you don't have to care about l2 resolving at all.
>
>
> Patrick
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-net" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2003-01-13 3:03 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <1042301388.8667.0.camel@localhost.localdomain>
[not found] ` <3E21A5AE.5060607@trash.net>
2003-01-13 3:11 ` Sending sk_buffs without being tied to a struct sock Joshua Stewart
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).