Dan Winship 9f739d0c61 rdisc: properly handle RDNSS/DNSSL forced expiration ... If the router sends an RA with an RDNSS or DNSSL lifetime of "0", that means to immediately stop using the corresponding server/domain name. NMLNDPRDisc knew this, but messed up its handling of it, and so if this happened, it might end up sending out an RS to get new data every 0 seconds... (Noticed while investigating bgo 735325, though it turned out to be irrelevant there.)		2014-10-29 09:13:36 -04:00
..
tests	libnm: add NetworkManager.h, disallow including individual headers	2014-08-01 14:34:40 -04:00
Makefile.am	trivial: allow building tests from rdisc directory	2013-07-30 11:40:18 +02:00
nm-fake-rdisc.c	rdisc: obey rtr_solicitations and rtr_solicitation_interval	2014-03-04 17:04:01 -05:00
nm-fake-rdisc.h	all: fix up multiple-include-guard defines	2014-08-16 10:17:14 -04:00
nm-lndp-rdisc.c	rdisc: properly handle RDNSS/DNSSL forced expiration	2014-10-29 09:13:36 -04:00
nm-lndp-rdisc.h	all: fix up multiple-include-guard defines	2014-08-16 10:17:14 -04:00
nm-rdisc.c	rdisc: add RA wait timeout	2014-08-29 16:03:36 -05:00
nm-rdisc.h	rdisc,device: set MTU if an appropriate option is present in a RA	2014-10-20 14:32:38 +02:00