Skip to content
Snippets Groups Projects
  • Dmitry Fleytman's avatar
    d241a2c0
    DHCP: Repeat DHCP discovery on timeout · d241a2c0
    Dmitry Fleytman authored
    
    It is a bad practice to have DHCP discovery without timeout
    and retries. In case discovery packet gets lost boot stucks.
    
    Beside this there is an interesting phenomena on some systems.
    A few first DHCP discovery packets sent on boot get lost in some cases.
    
    This started to happen from time to time on my KVM system and almost
    every time on my Xen system after installing recent Fedora Core updates.
    Packet leaves VM's interface but never arrives to bridge interface.
    The packet itself built properly and arrives to DHCP server just fine
    after a few retransmissions.
    
    Most probably this phenomena is a bug (or limitation) in the current
    Linux bridge version so this patch is actually a work-around, but
    since in general case it is a good idea to have DHCP timeouts/retries
    it worth to have it anyway.
    
    Signed-off-by: default avatarDmitry Fleytman <dmitry@daynix.com>
    Signed-off-by: default avatarPekka Enberg <penberg@cloudius-systems.com>
    d241a2c0
    History
    DHCP: Repeat DHCP discovery on timeout
    Dmitry Fleytman authored
    
    It is a bad practice to have DHCP discovery without timeout
    and retries. In case discovery packet gets lost boot stucks.
    
    Beside this there is an interesting phenomena on some systems.
    A few first DHCP discovery packets sent on boot get lost in some cases.
    
    This started to happen from time to time on my KVM system and almost
    every time on my Xen system after installing recent Fedora Core updates.
    Packet leaves VM's interface but never arrives to bridge interface.
    The packet itself built properly and arrives to DHCP server just fine
    after a few retransmissions.
    
    Most probably this phenomena is a bug (or limitation) in the current
    Linux bridge version so this patch is actually a work-around, but
    since in general case it is a good idea to have DHCP timeouts/retries
    it worth to have it anyway.
    
    Signed-off-by: default avatarDmitry Fleytman <dmitry@daynix.com>
    Signed-off-by: default avatarPekka Enberg <penberg@cloudius-systems.com>