netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vincent Guffens <guffens@auto.ucl.ac.be>
To: Zdenek Radouch <zdenek@rcn.com>
Cc: netdev@oss.sgi.com, linux-net@vger.kernel.org
Subject: Re: Do you know the linux TCP stack?
Date: Sat, 05 Mar 2005 17:34:31 +0100	[thread overview]
Message-ID: <4229DF97.2040500@auto.ucl.ac.be> (raw)
In-Reply-To: <E1D7aML-0007Wp-00@smtp01.mrf.mail.rcn.net>

Zdenek Radouch wrote:
> I ran out of ideas.  Can't find the answers in any docs,
> and I don't have time to read and analyze the source right now.
> 
> I will hire you to help me; I need the following to be done in
> my net device driver:
> 
> With the ARP disabled (this is well documented so I believe I've done that),
> while queueing the physical output, I need to get hold of the IP address
> of where the packet is being sent.  Yes, I mean IP address, not
> Ethernet address, and yes this is not the destination addresses in
> the IP header.

can you not use the routing table ? In a normal setup, either the 
network part of your destination IP matches the network part of a 
directly connected network and the address your are looking for is the 
destination IP in the packet or it does not match and the next IP is the 
  IP of the gateway found by routing.

Is it what you are looking for ?


-- 
				Vincent Guffens
				PhD Student UCL/CESAME
				tel:   +32 10 47 80 30
Value your freedom, or you will lose it, teaches history.
"Don't bother us with politics," respond those who don't want to learn.
	      	-- Richard M. Stallman

  reply	other threads:[~2005-03-05 16:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-05 14:31 Do you know the linux TCP stack? Zdenek Radouch
2005-03-05 16:34 ` Vincent Guffens [this message]
2005-03-05 17:11   ` Zdenek Radouch
2005-03-05 18:39     ` David S. Miller
2005-03-05 18:34 ` Andi Kleen

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=4229DF97.2040500@auto.ucl.ac.be \
    --to=guffens@auto.ucl.ac.be \
    --cc=linux-net@vger.kernel.org \
    --cc=netdev@oss.sgi.com \
    --cc=zdenek@rcn.com \
    /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;
as well as URLs for NNTP newsgroup(s).