[lwip-devel] [bug #28798] IGMP "Max Response Time" processing bug

[Stephane Lesage]

Follow-up Comment #8, bug #28798 (project lwip):


>What do you think, is using the supplied value OK or do we have to set the
timer lower than that?

The RFC says:
"Each timer is set to a different random value, using the highest clock
granularity available on the host, selected from the range (0, Max Response
Time]"

(In order to spread responses and avoid duplicate answers when we have
multiple devices)

As the next call to igmp_tmr() may actually be faster than 100ms, I think
it's ok to use the supplied value.

Anyway, if it didn't receive any answer to a general query, an IGMP-enabled
switch will actually send & retry group-specific queries with a fast timeout.

(We could also change the fixed timer and group-list parsing and use
sys_timeout for each group)


    _______________________________________________________

Reply to this item at:

  <http://savannah.nongnu.org/bugs/?28798>

_______________________________________________
  Message posté via/par Savannah
  http://savannah.nongnu.org/