From: "Rémi Denis-Courmont" <rdenis@simphalempin.com>
To: davem@davemloft.net, pekkas@netcore.fi
Cc: yoshfuji@linux-ipv6.org, netdev@oss.sgi.com
Subject: [PATCH] networking: [IPv6] Don't generate temporary for TUN devices
Date: Sat, 11 Jun 2005 15:12:40 +0200 [thread overview]
Message-ID: <200506111512.42592.rdenis@simphalempin.com> (raw)
Hello,
Userland layer-2 tunneling devices allocated through the TUNTAP driver
(drivers/net/tun.c) have a type of ARPHRD_NONE, and have no link-layer
address. The kernel complains at regular interval when IPv6 Privacy
extension are enabled because it can't find an hardware address :
Dec 29 11:02:04 auguste kernel: __ipv6_regen_rndid(idev=cb3e0c00):
cannot get EUI64 identifier; use random bytes.
IPv6 Privacy extensions should probably be disabled on that sort of
device. They won't work anyway. If userland wants a more usual
Ethernet-ish interface with usual IPv6 autoconfiguration, it will use a
TAP device with an emulated link-layer and a random hardware address
rather than a TUN device.
As far as I could fine, TUN virtual device from TUNTAP is the very only
sort of device using ARPHRD_NONE as kernel device type.
Signed-off-by: Rémi Denis-Courmont <rdenis@simphalempin.com>
--- a/net/ipv6/addrconf.c.orig 2004-12-29 10:50:27.000000000 +0100
+++ b/net/ipv6/addrconf.c 2004-12-29 10:50:41.000000000 +0100
@@ -372,6 +372,7 @@
ndev->regen_timer.data = (unsigned long) ndev;
if ((dev->flags&IFF_LOOPBACK) ||
dev->type == ARPHRD_TUNNEL ||
+ dev->type == ARPHRD_NONE ||
dev->type == ARPHRD_SIT) {
printk(KERN_INFO
"Disabled Privacy Extensions on device %p(%s)\n",
--
Rémi Denis-Courmont
http://www.simphalempin.com/home/
next reply other threads:[~2005-06-11 13:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-11 13:12 Rémi Denis-Courmont [this message]
2005-06-11 13:32 ` [PATCH] networking: [IPv6] Don't generate temporary for TUN devices YOSHIFUJI Hideaki / 吉藤英明
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=200506111512.42592.rdenis@simphalempin.com \
--to=rdenis@simphalempin.com \
--cc=davem@davemloft.net \
--cc=netdev@oss.sgi.com \
--cc=pekkas@netcore.fi \
--cc=yoshfuji@linux-ipv6.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).