netdev - tun and routing

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date:	Mon, 14 Apr 2014 13:47:13 +0200 (CEST)
From:	etienne.champetier@...e.fr
To:	netdev@...r.kernel.org
Subject: tun and routing

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
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html