Re: Ieee802154 socket problem with SIOCGIFADDR

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, May 11, 2015 at 06:58:11PM +0200, Matteo Petracca wrote:
> This is basically what I have in my program:
> 
>   int socketfd = 0;
>   struct ifreq ifr;
>   static const char *wpandevs[] = {
>        "wpan0"
>   };
> 
> 
>  socket_config_wpan = wpandevs[0];
>  socketfd = socket(PF_IEEE802154, SOCK_RAW, 0);
> 
> strncpy(ifr.ifr_name, socket_config_wpan, IF_NAMESIZE);
>   ret = ioctl(socketfd, SIOCGIFADDR, &ifr);
>   if (ret < 0) {
>       fprintf(stderr,"ioctl: SIOCGIFADDR error\n");
>       return;
>    }
> 
>  In can say that in kernel 3.8.13 it works with no problems.
> 

I wrote a dirty hack [0]. Run it on my side and detected no issue.

The output is:

pan_id 0xabcd
short_addr 0x2

and that's my current pan_id and short_addr setting.

- Alex

[0] http://pastebin.com/EE5wGZ5Q
--
To unsubscribe from this list: send the line "unsubscribe linux-wpan" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Linux Audio Users]     [Photo]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux