Re: why does it use mcastaddr family to parse bindnetaddr into totem_config?

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

 



On 12/19/2011 10:12 PM, Oscar Ben wrote:
> Dear Sir,
>     There's a "bug" if I configure(in corosync conf) mcastaddr with an
> IPV6 address, while configuring bindnetaddr with an IPV4 address. The
> bindnet is parsed into an 'IPV6' addr then.
>     As shown in func'totem-config-read' in file
> 'corosync/exec/totemconfig c'(line:393/v1: 4: 2), it uses mcastaddr's IP
> version to parse bindnet, is there any purpose of realizing it this way,
> or, is it an clerical error?
> Thanks in advance!
> 
> Oscar
> 
> 
> 
IPV6 works, but most everyone uses IPV4.  As a result, these sorts of
problems don't pop up often.

The model of corosync re IPV4 or IPV6, is if IPV6 is configured,
everything should use IPV6.  (even with redundant ring).

Thanks for the bug report.

Regards
-steve

> 
> _______________________________________________
> discuss mailing list
> discuss@xxxxxxxxxxxx
> http://lists.corosync.org/mailman/listinfo/discuss

_______________________________________________
discuss mailing list
discuss@xxxxxxxxxxxx
http://lists.corosync.org/mailman/listinfo/discuss


[Index of Archives]     [Linux Clusters]     [Corosync Project]     [Linux USB Devel]     [Linux Audio Users]     [Photo]     [Yosemite News]    [Yosemite Photos]    [Linux Kernel]     [Linux SCSI]     [X.Org]

  Powered by Linux