ng_one2many heartbeat algorithm for LAN fault tolerance

[Maxim Sobolev]

Well, I've took closer look at the patch today and found that two things 
  need to be done to get it to the commitable shape:

1. Make it working independently of the layer on which one2many 
operates. For example, I use it for doing ip-over-udp multilink tunnel 
between two points. Since one2many is protocol agnostic heartbeat 
feature should not make any assumptions regarding type of protocol (e.g. 
ethernet, ip, udp etc).

This is not trivial, I know, maybe the best way to address it is to make 
content of heartbeat packet configurable, so that one can put in 
whatever is appropriate for his task. Then you can put guidelines about 
configuring it for ethernet into man page. For example, in my situation 
I can put single 0 byte as a heartbeat payloas since it will be used as 
a payload to UDP packet, so that no real header is necessary.

2. It would be very nice to extend heartbeat algorithm with recovery 
function, so that it will keep sending heartbeats over links that were 
detected as dead ones previously to see if any of them have recovered.

Please let me know what do you think about it.

Regards,

Maxim

Evgeny Dolgopiat wrote:
> Ok. Do you need something from me (some patches, docs etc.)? 
> 
> 
>>I can after some testing. ;-)
>>
>>-Maxim
> 
> 
> 
>