aboutsummaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorpgf <pgf@69ca8d6d-28ef-0310-b511-8ec308f3f277>2006-03-29 23:01:33 +0000
committerpgf <pgf@69ca8d6d-28ef-0310-b511-8ec308f3f277>2006-03-29 23:01:33 +0000
commitc0503195d05e92fda33970c7ffcb4b385acacf01 (patch)
treee7d289b4713c770edf00f875f98540d197fdde45 /docs
parenta861bc8168145bf86cf9a28eac0da25cc2f89fe8 (diff)
downloadbusybox-w32-c0503195d05e92fda33970c7ffcb4b385acacf01.tar.gz
busybox-w32-c0503195d05e92fda33970c7ffcb4b385acacf01.tar.bz2
busybox-w32-c0503195d05e92fda33970c7ffcb4b385acacf01.zip
fix from David Daney, on busybox mailing list:
> The problem is that if the zcip protocol times out at about the same > time another ARP packet is being received, the newly calculated timeout > may be set to wait forever. This prevents the protocol from progressing > through its various states. > > The Fix is to set the timeout to zero if it used to be a positive > number, but it has already expired. This causes the next protocol state > to be entered immediately instead of never. > > If OK please commit. > > Also note that if you may have to apply the patch on this page: > > http://www.science.uva.nl/research/air/wiki/LinkLocalARPMeasurements > > To the linux kernel to get proper zcip behavior. > git-svn-id: svn://busybox.net/trunk/busybox@14698 69ca8d6d-28ef-0310-b511-8ec308f3f277
Diffstat (limited to 'docs')
0 files changed, 0 insertions, 0 deletions