netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: etienne.champetier@free.fr
To: netdev@vger.kernel.org
Subject: tun and routing
Date: Mon, 14 Apr 2014 13:47:13 +0200 (CEST)	[thread overview]
Message-ID: <376498473.79151018.1397476033181.JavaMail.root@zimbra65-e11.priv.proxad.net> (raw)
In-Reply-To: <176092473.79093321.1397474889713.JavaMail.root@zimbra65-e11.priv.proxad.net>

Hi,

When the kernel gives a packet to a tun interface, you loose the "next-hop" information, because you only have L3+ infos.
So you have destination ip, but if it's out of the tun subnet, you have to do routing in your application. (with a tap interface the next-hop is the dest mac)

Is there a way to have this next-hop info, and remove "internal" (in the application) routing table?

If not what would be the cleanest way to sync the "internal" routing table with the kernel routing table?

Thanks in advance
Etienne

           reply	other threads:[~2014-04-14 11:47 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <176092473.79093321.1397474889713.JavaMail.root@zimbra65-e11.priv.proxad.net>]

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=376498473.79151018.1397476033181.JavaMail.root@zimbra65-e11.priv.proxad.net \
    --to=etienne.champetier@free.fr \
    --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;
as well as URLs for NNTP newsgroup(s).