[Top][All Lists]

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

Re: [lwip-users] STABLE-1.4.1 IPv6 Initialization Examples or Guidance

From: Grant Erickson
Subject: Re: [lwip-users] STABLE-1.4.1 IPv6 Initialization Examples or Guidance
Date: Tue, 18 Dec 2012 09:00:32 -0800

On Dec 14, 2012, at 2:42 PM, Ivan Delamer wrote:
>> Thanks for the feedback; I'll give that a try.
>> I've also since discovered that netif->ip6_autoconfig_enabled must be
>> explicitly set to 1. Which is somewhat confusing since I thought that's
>> what would have happened when I asserted LWIP_IPV6_AUTOCONFIG in
>> lwipopts.h.
>> So, if the link local address must be set manually, what is it that
>> ip6_autoconfig / LWIP_IPV6_AUTOCONFIG is supposed to accomplish?
> Good question.
> LWIP_IPV6_AUTOCONFIG enables the autoconfig code, if this is disabled the
> code is not included in order to save memory.
> You can then choose on each netif whether you want address
> autoconfiguration to happen or not via netif->ip6_autoconfig_enabled = 1
> With multiple netifs, this may or may not be required, so you can set it
> individually.
> The question is, should the default be netif->ip6_autoconfig_enabled = 1?
> I'm happy setting it manually per netif, I guess the solution is to
> document this better.


Thanks for the pointers. At this point, I have a link-local address at index 0 
getting set correctly and the stack is correctly responding to inbound ICMPv6 
"ping" requests.

However, the stack doesn't appear to be taking on SLAAC addresses 
auto-configured from router advertisements on the subnet. Any pointers or 
tricks in coaxing this into functioning?

Finally, what's the preferred semantics for setting a unique link-local address 



reply via email to

[Prev in Thread] Current Thread [Next in Thread]