diff options
author | Vladislav Grishenko <themiron@mail.ru> | 2011-10-18 01:37:47 +0200 |
---|---|---|
committer | Denys Vlasenko <vda.linux@googlemail.com> | 2011-10-18 01:37:47 +0200 |
commit | 6464f15ddb67f7c3fac9eb99a1336965537c4d67 (patch) | |
tree | c6fcacf1e864a9449fd0bbbfdcb8d90756610c5a /scripts/kconfig/confdata.c | |
parent | 6c9c0a1dc9de48b59c103600a1f574a4a234b3d6 (diff) | |
download | busybox-6464f15ddb67f7c3fac9eb99a1336965537c4d67.tar.gz |
udhcpc: on SIGUSR1, limit renew attempts time to 20 seconds; then do total reconfig
Scenario:
1. udhcpc gets lease for 86400 secs and sleeps for 43200 before renew attempt
2. PC gets physically disconnected and connected to another network
3. some phy control software sends SIGUSR1 to renew the lease, SIGUSR2 isn't
used because newly connected network could be the same as before
4. udhcpc sends unicast renew requests until lease timeout fall to 60 sec.
They are ignored by new network dhcp servers
5. udhcpc sends broadcast rebind requests for 60 seconds, which are NAKed
or ignored too
6. udhcpc deconfigs and starting from discover state, gets new lease for the
new network
So, pt.4+5 it could take up to 86400 secs without correct lease, which is
too long and not acceptable.
Second SIGUSR1 will immediately run into deconfig/discover state, which is
not preferable in case of the same subnet replugged.
This patch makes sure after SIGUSR1 timeout is no more than -A NUM
(usually 20 sec). It means that renew will be requested via broadcast,
and if no replies come back, full deconf/reconf cycle will be initiated
in 20 seconds.
Signed-off-by: Vladislav Grishenko <themiron@mail.ru>
Signed-off-by: Denys Vlasenko <vda.linux@googlemail.com>
Diffstat (limited to 'scripts/kconfig/confdata.c')
0 files changed, 0 insertions, 0 deletions