Re: Interface friendly names for AF_INET6

2016-05-20 Thread Corinna Vinschen
On May 13 17:00, Marco Atzeri wrote: > On 10/03/2016 18:41, Corinna Vinschen wrote: > > > > > > I assume the ifall structures are not visible outside cygwin internal, > > > correct ? > > > > > > If so a ifall_data pointer should cover my current trial. > > > > Try the latest snapshot. The ifa_d

Re: Interface friendly names for AF_INET6

2016-05-13 Thread Marco Atzeri
On 10/03/2016 18:41, Corinna Vinschen wrote: I assume the ifall structures are not visible outside cygwin internal, correct ? If so a ifall_data pointer should cover my current trial. Try the latest snapshot. The ifa_data member now contains a pointer to a struct ifa_hwdata which is defined

Re: Interface friendly names for AF_INET6

2016-03-10 Thread Corinna Vinschen
On Mar 10 15:30, Marco Atzeri wrote: > > > On 10/03/2016 14:49, Corinna Vinschen wrote: > >On Mar 10 14:32, Corinna Vinschen wrote: > >>Hi Marco, > >> > > >>>I am using getifaddrs to obtain all the AF_INET and AF_INET6 > >>>interface, however I can only obtain the friendly name of the > >>>AF_IN

Re: Interface friendly names for AF_INET6

2016-03-10 Thread Marco Atzeri
On 10/03/2016 15:03, Corinna Vinschen wrote: On Mar 10 12:10, Marco Atzeri wrote: I am trying to put a small interface info tool to debug some hangs reported on openmpi. The aim is to produce something like {9F4F7FD2-5E44-4796-ABE0-0785CF76C11E} AF_INET6 (23) flags: up running multi

Re: Interface friendly names for AF_INET6

2016-03-10 Thread Marco Atzeri
On 10/03/2016 14:49, Corinna Vinschen wrote: On Mar 10 14:32, Corinna Vinschen wrote: Hi Marco, I am using getifaddrs to obtain all the AF_INET and AF_INET6 interface, however I can only obtain the friendly name of the AF_INET using ioctl(sock, SIOCGIFFRNDLYNAM getifaddrs should retur

Re: Interface friendly names for AF_INET6

2016-03-10 Thread Corinna Vinschen
On Mar 10 12:10, Marco Atzeri wrote: > I am trying to put a small interface info tool > to debug some hangs reported on openmpi. > > The aim is to produce something like > > {9F4F7FD2-5E44-4796-ABE0-0785CF76C11E} AF_INET6 (23) > flags: up running multicast > address: > Lo

Re: Interface friendly names for AF_INET6

2016-03-10 Thread Corinna Vinschen
On Mar 10 14:32, Corinna Vinschen wrote: > Hi Marco, > > On Mar 10 12:10, Marco Atzeri wrote: > > I am trying to put a small interface info tool > > to debug some hangs reported on openmpi. > > > > The aim is to produce something like > > > > {9F4F7FD2-5E44-4796-ABE0-0785CF76C11E} AF_INET6 (23)

Re: Interface friendly names for AF_INET6

2016-03-10 Thread Corinna Vinschen
Hi Marco, On Mar 10 12:10, Marco Atzeri wrote: > I am trying to put a small interface info tool > to debug some hangs reported on openmpi. > > The aim is to produce something like > > {9F4F7FD2-5E44-4796-ABE0-0785CF76C11E} AF_INET6 (23) > flags: up running multicast > address: >

Interface friendly names for AF_INET6

2016-03-10 Thread Marco Atzeri
I am trying to put a small interface info tool to debug some hangs reported on openmpi. The aim is to produce something like {9F4F7FD2-5E44-4796-ABE0-0785CF76C11E} AF_INET6 (23) flags: up running multicast address: Local Area Connection {9F4F7FD2-5E44-4796-ABE0-0785CF76C