All, Note that the CAInterface_t structure is not used in the normal operation of IoTivity. It is only used in querying the interfaces, which is normally not needed, where the IPv4 address was included for backward compatibility with a previous API.
Normal operation uses the structures OCDevAddr and CAEndpoint_t, which are identical and provide complete addressing for all adapters. John -----Original Message----- From: iotivity-dev-bounces at lists.iotivity.org [mailto:[email protected]] On Behalf Of Thiago Macieira Sent: Wednesday, February 17, 2016 8:04 AM To: iotivity-dev at lists.iotivity.org Subject: Re: [dev] ipv6 addr support in CAInterface_t; On quarta-feira, 17 de fevereiro de 2016 10:58:42 PST Raghavendra Kakarla wrote: > Hi All, > > > I am trying to port the IoTivity to contiki. > > > While going through the code I found that the interface structure has > the only ipv4 addree member. > > > typedef struct > { > char name[INTERFACE_NAME_MAX]; > uint32_t index; > uint32_t flags; > uint16_t family; > uint32_t ipv4addr; /**< used for IPv4 only. */ > } CAInterface_t; > > > our platform have the all 6lowpan devices so, could please give me the > info where to add the IPV6 address in the code. You don't need the address. The interface index is enough. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center _______________________________________________ iotivity-dev mailing list iotivity-dev at lists.iotivity.org https://lists.iotivity.org/mailman/listinfo/iotivity-dev
