From: "Rémi Denis-Courmont" <remi@remlab.net>
To: Ian Shorter <mcisho@yahoo.com>
Cc: netdev@vger.kernel.org
Subject: Re: Kernel bug 14839: Trying to use a TUN device for IPv6 traffic, cannot set destination address.
Date: Wed, 07 Jul 2010 17:25:01 +0200 [thread overview]
Message-ID: <4d0194fe8536c59196233b56548b0314@chewa.net> (raw)
In-Reply-To: <846562.91258.qm@web113913.mail.gq1.yahoo.com>
On Wed, 7 Jul 2010 08:04:33 -0700 (PDT), Ian Shorter <mcisho@yahoo.com>
wrote:
> I reported this kernel bug at the end of 2009. In February 2010 Stephen
> Hemminger said that the problem was not unique to TUN, and that I should
> bring it up on the network maintainers mailing list, which I am finally
> doing. Do I need to provide the problem description again?
I really do not see the point of setting a destination address on a TUN
device. Since a TUN device has no link-layer, the notions of gateway or
destination is rather void of meaning.
--
Rémi Denis-Courmont
http://www.remlab.net
http://fi.linkedin.com/in/remidenis
prev parent reply other threads:[~2010-07-07 15:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-07 15:04 Kernel bug 14839: Trying to use a TUN device for IPv6 traffic, cannot set destination address Ian Shorter
2010-07-07 15:25 ` Rémi Denis-Courmont [this message]
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=4d0194fe8536c59196233b56548b0314@chewa.net \
--to=remi@remlab.net \
--cc=mcisho@yahoo.com \
--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