Re: dhclient cause up/down cycle after 239356 ?

看板FB_current作者時間13年前 (2012/08/23 10:01), 編輯推噓0(000)
留言0則, 0人參與, 最新討論串11/15 (看更多)
--45Z9DzgjV8m4Oswq Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2012-Aug-22 15:35:01 -0400, John Baldwin <jhb@freebsd.org> wrote: >Hmm. Perhaps we could use a debouncer to ignore "short" link flaps? Kind= of >gross (and OpenBSD doesn't do this). For now this change basically ignores >link up events if they occur with 5 seconds of the link down event. The 5= is >hardcoded which is kind of yuck. I'm also a bit concerned about this for similar reasons to adrian@. We need to distinguish between short link outages caused by (eg) a switch admin reconfiguring the switch (which needs the lease to be re-checked) and those caused by broken NICs which report link status changes when they are touched. Maybe an alternative is to just ignore link flaps when they occur within a few seconds of a script_go(). (And/or make the ignore timeout configurable). Apart from fxp(4), does anyone know how many NICs are similarly broken? Does anyone know why this issue doesn't bite OpenBSD? Does it have a work-around to avoid resetting the link, not report link status changes or just no-one has noticed the issue? BTW to jhb: Can you check your mailer's list configuration. You appear to be adding <freebsd-current@freebsd.org> and leaving <current@freebsd.org> in the Cc list. --=20 Peter Jeremy --45Z9DzgjV8m4Oswq Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iEYEARECAAYFAlA1iOYACgkQ/opHv/APuIer+ACfR5VFu11ub75m+ZPCxoYdXZtj iQ4An1RghY5dCpCEMt5tDEAqREGAWhEY =izBM -----END PGP SIGNATURE----- --45Z9DzgjV8m4Oswq--
文章代碼(AID): #1GDOxUK7 (FB_current)
討論串 (同標題文章)
文章代碼(AID): #1GDOxUK7 (FB_current)