diff options
author | Rémi Denis-Courmont <rdenis@simphalempin.com> | 2005-06-13 15:01:34 -0700 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2005-06-13 15:01:34 -0700 |
commit | 77bd91967a97e5b94ae36113efe1d9e4f68a716e (patch) | |
tree | 269b466f7b8d6d3821ae6fedd8bf802c865b324b /net/sctp | |
parent | 84427d533076a08137779b3182a71c37bf000b27 (diff) | |
download | op-kernel-dev-77bd91967a97e5b94ae36113efe1d9e4f68a716e.zip op-kernel-dev-77bd91967a97e5b94ae36113efe1d9e4f68a716e.tar.gz |
[IPv6] Don't generate temporary for TUN devices
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>
Acked-by: YOSHIFUJI Hideaki <yoshfuji@linux-ipv6.org>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/sctp')
0 files changed, 0 insertions, 0 deletions