Getting link list results in NLE_OPNOTSUPP

[Thomas Graf]

On Thu, Jan 26, 2012 at 06:24:52PM +0000, André Prata wrote:
> -- Debug: Sent Message:
> --------------------------   BEGIN NETLINK MESSAGE ---------------------------
>   [HEADER] 16 octets
>     .nlmsg_len = 20
>     .nlmsg_type = 18 <0x12>
>     .nlmsg_flags = 773 <REQUEST,ACK,ROOT,MATCH>
>     .nlmsg_seq = 1327602152
>     .nlmsg_pid = 1539
>   [PAYLOAD] 4 octets
>     00 00 00 00                                           ....
> ---------------------------  END NETLINK MESSAGE   ---------------------------
> -- Debug: Received Message:
> --------------------------   BEGIN NETLINK MESSAGE ---------------------------
>   [HEADER] 16 octets
>     .nlmsg_len = 40
>     .nlmsg_type = 2 <ERROR>
>     .nlmsg_flags = 0 <>
>     .nlmsg_seq = 1327602152
>     .nlmsg_pid = 1539
>   [ERRORMSG] 20 octets
>     .error = -95 "Operation not supported"
>   [ORIGINAL MESSAGE] 16 octets
>     .nlmsg_len = 16
>     .nlmsg_type = 18 <0x12>
>     .nlmsg_flags = 773 <REQUEST,ACK,ROOT,MATCH>
>     .nlmsg_seq = 1327602152
>     .nlmsg_pid = 1539
> ---------------------------  END NETLINK MESSAGE   ---------------------------

Are you using a NETLINK_ROUTE socket?

I can't think of a valid reason for EOPNOTSUPP to be returned if not
for an invalid address family. You obviously use AF_UNSPEC so this
should not be the case.