diff options
| author |   henning <henning@openbsd.org> | 2004-09-16 17:44:36 +0000 |
|---|---|---|
| committer | henning <henning@openbsd.org> | 2004-09-16 17:44:36 +0000 |
| commit | aa8a6cc6f6368a7602673fdd00e5dd03081108dd (patch) | |
| tree | ace1237378d2e74f4f9d284bf25c5f7ac2feda4b /usr.sbin/cron/crontab.c | |
| parent | cope with imsg API change (diff) | |
| download | wireguard-openbsd-aa8a6cc6f6368a7602673fdd00e5dd03081108dd.tar.xz wireguard-openbsd-aa8a6cc6f6368a7602673fdd00e5dd03081108dd.zip | |
when a cloned peer goes back to IDLE state, don't remove him immediately
but keep him around for some more time (an hour here).
fixes an issue Arvid was reporting: when a cloned neighbor rejects our OPEN
message due to capability negotiation (or missing implementation of those),
we set a marker and retry without. However, if we remove the peer immediately,
it gets freshly cloned on the next trial, with default settings, thus including
capability negotiation, and thus failes again.
this will also help with route flap dampening.
ok claudio
Diffstat (limited to 'usr.sbin/cron/crontab.c')
0 files changed, 0 insertions, 0 deletions