New: RTNLGRP_ND_USEROPT does not report ifindex
Subsystems (2)
A message that is not in the archive (sent off-list or not yet received): [email protected]/
Quoted 39 lines · On Sun, 11 Nov 2007 10:52:41 -0800 (PST) [email protected] wrote:
http://bugzilla.kernel.org/show_bug.cgi?id=9349
Summary: RTNLGRP_ND_USEROPT does not report ifindex Product: Networking Version: 2.5 KernelVersion: 2.6.24-rc Platform: All OS/Version: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: IPV6 AssignedTo: [email protected] ReportedBy: [email protected]Most recent kernel where this bug did not occur: none
Distribution: N/A
Hardware Environment: any
Software Environment: any
Problem Description:
TheRTNLGRP_ND_USEROPTNetLink message introduced in 2.6.24 does not seem to include any information as to which netif the user options come from:struct nduseroptmsg
{ unsigned char nduseropt_family; unsigned char nduseropt_pad1; unsigned short nduseropt_opts_len; /* Total length of options */ __u8 nduseropt_icmp_type; __u8 nduseropt_icmp_code; unsigned short nduseropt_pad2; /* Followed by one or more ND options */ };Considering this is meant to carry data that is heavily link-layer involved, this seems like a feature bug. Could an ifindex field be added there??
Quoted 5 lines · On Sun, 11 Nov 2007 10:52:41 -0800 (PST) [email protected] wrote:
The
RTNLGRP_ND_USEROPTNetLink message introduced in 2.6.24 does not seem to include any information as to which netif the user options come from. Considering this is meant to carry data that is heavily link-layer involved, this seems like a feature bug. Could an ifindex field be added there??
Ok, I am seeing to this.
Signature · 3 lines
Pierre Ynard For hire in Quebec City, Canada, during Fall 2007 "Une âme dans un corps, c'est comme un dessin sur une feuille de papier."