tech-net archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: Retiring dhclient

On Thu, Nov 24, 2011 at 01:36:22PM -0500, Nick Reilly wrote:
> Now I do agree that the last think you want is to end up going
> around in circles with the DHCP response driving a new MTU which
> resets the MAC and that triggers a new DHCP request. I believe that
> should be handled at the application level i.e. in dhcpd with a link
> down tolerance. It's the same idea but done in each application
> rather than the stack itself.

Yes, there should effectively be an anti-flap timer in the application
code.  However, in this case, the best thing is to *not change the MTU, thus
potentially triggering a link status change* (which would be genuine and
should not be suppressed by the kernel -- as Nick notes, there are times
when you really must know if the peer may have seen a link event) unless
the "change" actually *is* a change.

Thor Lancelot Simon                          
  "All of my opinions are consistent, but I cannot present them all
   at once."    -Jean-Jacques Rousseau, On The Social Contract

Home | Main Index | Thread Index | Old Index