• State TI Thinks Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 2 answers
  • Subscribers 40 subscribers
  • Views 346 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CC3220SF-LAUNCHXL: receiving excessive SL_NETAPP_EVENT_IPV6_ACQUIRED events from NWP

Christopher Deckard74
Intellectual 790 points
Part Number: CC3220SF-LAUNCHXL

Hi, I seem to be receiving excessive 

SL_NETAPP_EVENT_IPV6_ACQUIRED

signals from the NWP.  Can someone fill me in on why this may be happening, or if there's something I need to do to keep the NWP from generating these?

I'm admittedly a bit fuzzy on how IPV6 currently coexists with IPV4 -- and I typically ignore IPV6 and just live in my simple IPV4 world :)

Thanks,

Chris

  • 0
    TI__Mastermind 30225 points

    Hi Chris,

    The following should disable IPv6

    /* Disable IPV6 */
    ifBitmap = 0;
    status = sl_NetCfgSet(SL_NETCFG_IF, SL_NETCFG_IF_STATE,\
            sizeof(ifBitmap), (uint8_t *)&ifBitmap);

    Best Regards,

    Ben M

  • 0 in reply to Benjamin Moore
    Intellectual 790 points
    Hi Ben, do I want to disable IPv6? isn't it a good thing(tm) to use?

    that is, what if I want my device to be compatible -- what is causing the stream of IPV6 events?
  • 0 in reply to Christopher Deckard74
    TI__Mastermind 30225 points

    Hi Chris,

    It depends on whether the system you are creating needs to support access to IPv6 networks. If you want to dive more into why you are seeing these events, it would be helpful for you to share which IPv6 local link acquisition method you are using, capture NWP logs from the device and get a sniffer capture of the network where you are seeing it occur.
    processors.wiki.ti.com/.../CC3120_&_CC3220_Capture_NWP_Logs

    Best,
    Ben M

  • 0 in reply to Benjamin Moore
    Intellectual 790 points
    Well, it seems that for forward compatibility, it seems that I would want ipv6, yes? On the other hand, I certainly don't want to dive into it since there are many other aspects of the project I'm grappling with. What is the recommended IPv6 local link acquisition method? Is this something that gets set in simplelink? If that's the case, I'm using whatever the default is.

    Chris
  • 0 in reply to Christopher Deckard74
    TI__Mastermind 30225 points

    Hi Chris,

    It really only matters if you will need your device's IP address to be publicly available. This is not necessary for most applications now, which sit behind a router that performs NAT and on a network with limited number of devices. Plus, it's not always supported by the AP. There is no real recommended method for all applications. If you don't have any specific requirements, the stateless auto configuration should be fine. Refer to section 5.3.2 of the Network Processor Programmer's guide for details on the different options.

    http://www.ti.com/lit/swru455

    Best,

    Ben M