I had a similar question when I got hit by clients behind a NAT failing to connect [1] to the cluster. [1] http://tracker.ceph.com/issues/20049 On Fri, Oct 20, 2017 at 11:25 AM, Ricardo Dias <rdias@xxxxxxxx> wrote: > Hi, > > In the current messenger protocol, upon accepting a new connection, the > messenger sends it's address and the connecting peer address along with > the banner string. Why does the connecting peer need these addresses? > Moreover, the connecting peer uses the connecting peer address (sent > from the server) to set as it's own address. > > What happens if the network is rewriting addresses because of NAT, or > whatever other strange reasons? > > I also saw that the code that encodes these addresses have a comment > saying "// legacy". Should we remove these addresses from the new V2 > protocol, or do we still need them? > > Thanks, > Ricardo > > -- > Ricardo Dias > Senior Software Engineer - Storage Team > SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, > HRB 21284 > (AG Nürnberg) > -- > To unsubscribe from this list: send the line "unsubscribe ceph-devel" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html -- Jason -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
