On 05/01/2012 08:10 AM, Bryan Bartone wrote: > First, thanks for taking the time to read this email. I am using > corosync and pacemaker on a security appliance we manufacture. I am > running udpu mode. I see that for each interface I define, there is a > udp listening socket using the mcastport I defined in corosync.conf and > two other ephemeral listening ports. The mcastaddr port is bound to the > interface I defined in corosync.conf. The ephemeral ports are bound to > all interfaces. I would like to know what the purpose of those ports > are, and why they are bound to 0.0.0.0. Thanks. > > > > > > _______________________________________________ > discuss mailing list > discuss@xxxxxxxxxxxx > http://lists.corosync.org/mailman/listinfo/discuss Probably a bug (udpu is a new feature). There should be one port for incoming packets and one port for outgoing packets, all bound to the proper interface. One of the listening ports may be a unix domain socke (used to setup shared memory ipc)t, are you sure that isn't the case? _______________________________________________ discuss mailing list discuss@xxxxxxxxxxxx http://lists.corosync.org/mailman/listinfo/discuss
