VRRP advertisements over multiple interfaces

Robert Groenenberg <[email protected]> Mon, 7 May 2018 23:30:33 +0200
Newsgroups gmane.linux.keepalived.devel
Message-ID <[email protected]> 
This is a multi-part message in MIME format.
--===============0836718297028162718==
Content-Type: multipart/alternative;
 boundary="------------EFE5D90E56A8C6A2E63E0EF6"
Content-Language: en-GB

This is a multi-part message in MIME format.
--------------EFE5D90E56A8C6A2E63E0EF6
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

Hi Quentin, Alexandre, others,

In order to have more reliable communication between two (or more) nodes 
and reducing the risk of a split-brain situation, I have been looking 
into the option of sending the advertisements over multiple interfaces. 
It involves each VRRP instance to have a list of 'vrrp interfaces' with 
the ifp, source address, etc. instead of a single ifp, etc., which 
requires some substantial amount changes in the code. I do have a first 
version working, both for multicast and unicast. All configurable per 
VRRP instance in the config file.

Although I think it kind of conflicts with the RFC to tie a single 
virtual router to multiple interfaces, I have seen questions from others 
for such behaviour for the same reason.
Would there be interest to take this functionality on board?

Kind regards,
Robert

--------------EFE5D90E56A8C6A2E63E0EF6
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit

<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <font face="DejaVu Sans">Hi Quentin, Alexandre, others,<br>
      <br>
      In order to have more reliable communication between two (or more)
      nodes and reducing the risk of a split-brain situation, I have
      been looking into the option of sending the advertisements over
      multiple interfaces. It involves each VRRP instance to have a list
      of 'vrrp interfaces' with the ifp, source address, etc. instead of
      a single ifp, etc., which requires some substantial amount changes
      in the code. I do have a first version working, both for multicast
      and unicast. All configurable per VRRP instance in the config
      file.<br>
      <br>
      Although I think it kind of conflicts with the RFC to tie a single
      virtual router to multiple interfaces, I have seen questions from
      others for such behaviour for the same reason.<br>
      Would there be interest to take this functionality on board?<br>
      <br>
      Kind regards,<br>
      Robert<br>
    </font>
  </body>
</html>

--------------EFE5D90E56A8C6A2E63E0EF6--


--===============0836718297028162718==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
--===============0836718297028162718==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Keepalived-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/keepalived-devel

--===============0836718297028162718==--