public inbox for
 help / color / mirror / Atom feed
* [ECOS] IPv6 stack timing out addresses too soon w/ 1ms system tick?
@ 2014-01-18 22:10 Grant Edwards
  0 siblings, 0 replies; only message in thread
From: Grant Edwards @ 2014-01-18 22:10 UTC (permalink / raw)
  To: ecos-discuss

I've got DHCPv6 client code that works great on one target, but on a
second target the IPv6 stack is timing out address assignments way too
soon (long before the lease expiry and long before the DHCPv6 client
thread asks for a lease renewal).

The target where the IPv6 stack times out addresses correctly has a
10ms timer tick.  The target where the stack is timing out addresses
too soon has a 1ms timer tick.  I have to change my test setup to
quatify "way too soon" but it does look like it might be timing out at
10% of the lease time.

Does the IPv6 stack require that the system timer tick be 10ms?

Grant Edwards               grant.b.edwards        Yow! Uh-oh!!  I'm having
                                  at               TOO MUCH FUN!!

Before posting, please read the FAQ:
and search the list archive:

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2014-01-18 22:10 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-01-18 22:10 [ECOS] IPv6 stack timing out addresses too soon w/ 1ms system tick? Grant Edwards

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).