[Catching up on email]
Benedikt,
Note that https://tools.ietf.org/html/draft-ietf-6man-rs-refresh-00 is
an attempt at addressing refresh without a multicast RA every 3 seconds,
by only having the host do this refresh when it knows that the router
doesn't default to multicasting solicited
Hi Lorenzo and list,
Lorenzo Colitti lore...@google.com writes:
On Thu, Jun 11, 2015 at 6:56 PM, Benedikt Stockebrand
b...@stepladder-it.com wrote:
they should at least send an RS when they wake up and ensure their
configuration is still up to date.
That sounds like a bad
Hi folks,
I can't give you a decisive reference for where it's defined, but the
default maximum interval is 600 seconds and the minimum interval is one
third of that (200 seconds, not 180). The 1800s value may be a
misinterpretation of the router lifetime field in the RAs, which has a
default
Hi,
On Thu, Jun 11, 2015 at 09:56:45AM +, Benedikt Stockebrand wrote:
As far as tweaking these values to deal with some sleepy devices is
concerned: I'd personally prefer to consider these devices broken; they
should at least send an RS when they wake up and ensure their
configuration is
Please read some IETF draft related to NDP/multicast/WiFi issues (Lorenzo
is very active there).
Multicast RA are not really needed anyway, some 'high market' (see my
email address) AP have dozens of tricks to reply to RS with a UNIcast RA,
and trying to reduce the amount of NDP mcast.
If you
I see that. I don’t think the problem is confined to Samsung or that it can
be completed solved in isolation from fixing wireless AP router behaviour.
At the edge of the WiFi network I also see the IPv6 connectivity dropping
while IPv4 stays up. I’ve a ZyXEL home router that sends periodic
