Hi, still using 2.2.9, I've two directors, and these directors use both IPv4/IPv6 addresses. `host directors.<domain>` returns one A and AAA for each of the two directors: directors.<domain> has address 149.x.y.96 (director1) directors.<domain> has address 149.x.y.97 (director2) directors.<domain> has IPv6 address 2001:x:y:f33::5:1 (director1) directors.<domain> has IPv6 address 2001:x:y:f33::5:2 (director2) But connecting the the neighbor director gives: Oct 13 21:23:29 director1 dovecot: director: Warning: Director 2001:x:y:f33::5:2:9090/left disconnected us with reason: Invalid input: ME 149.x.y.96 9090 Oct 13 21:23:29 director1 dovecot: director: Error: director(149.x.y.97:9090/out): connect() failed: Connection refused Oct 13 21:23:29 director1 dovecot: director: Warning: net_connect_ip(): ip->family != my_ip->family Oct 13 21:23:29 director1 dovecot: director: Error: Remote director thinks it's someone else (connected to 2001:x:y:f33::5:1:9090, remote says it's 149.x.y.96:9090) I assume it's because the director uses only one (IPv4 OR IPv6) address for it's own identity, right? Best regards from Dresden/Germany Viele Gr??e aus Dresden Heiko Schlittermann -- SCHLITTERMANN.de ---------------------------- internet & unix support - Heiko Schlittermann, Dipl.-Ing. (TU) - {fon,fax}: +49.351.802998{1,3} - gnupg encrypted messages are welcome --------------- key ID: F69376CE - ! key id 7CBF764A and 972EAC9F are revoked since 2015-01 ------------ - -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 473 bytes Desc: Digital signature URL: <http://dovecot.org/pipermail/dovecot/attachments/20151013/8278e62d/attachment.sig>
On 13 Oct 2015, at 22:31, Heiko Schlittermann <hs at schlittermann.de> wrote:> > Hi, > > still using 2.2.9, I've two directors, and these directors > use both IPv4/IPv6 addresses. > > `host directors.<domain>` returns one A and AAA for each > of the two directors: > > directors.<domain> has address 149.x.y.96 (director1) > directors.<domain> has address 149.x.y.97 (director2) > directors.<domain> has IPv6 address 2001:x:y:f33::5:1 (director1) > directors.<domain> has IPv6 address 2001:x:y:f33::5:2 (director2) > > But connecting the the neighbor director gives: > > Oct 13 21:23:29 director1 dovecot: director: Warning: Director 2001:x:y:f33::5:2:9090/left disconnected us with reason: Invalid input: ME 149.x.y.96 9090 > Oct 13 21:23:29 director1 dovecot: director: Error: director(149.x.y.97:9090/out): connect() failed: Connection refused > Oct 13 21:23:29 director1 dovecot: director: Warning: net_connect_ip(): ip->family != my_ip->family > Oct 13 21:23:29 director1 dovecot: director: Error: Remote director thinks it's someone else (connected to 2001:x:y:f33::5:1:9090, remote says it's 149.x.y.96:9090) > > I assume it's because the director uses only one (IPv4 OR IPv6) address > for it's own identity, right?Right. I thought I did something to fix this crash, but probably not. In any case it's not a supported configuration even if it didn't crash.
Timo Sirainen <tss at iki.fi> (Di 13 Okt 2015 21:42:41 CEST): ?> > Oct 13 21:23:29 director1 dovecot: director: Error: director(149.x.y.97:9090/out): connect() failed: Connection refused > > Oct 13 21:23:29 director1 dovecot: director: Warning: net_connect_ip(): ip->family != my_ip->family > > Oct 13 21:23:29 director1 dovecot: director: Error: Remote director thinks it's someone else (connected to 2001:x:y:f33::5:1:9090, remote says it's 149.x.y.96:9090) > > > > I assume it's because the director uses only one (IPv4 OR IPv6) address > > for it's own identity, right? > > Right. I thought I did something to fix this crash, but probably not. In any case it's not a supported configuration even if it didn't crash.Ok, maybe it should be mentioned in the Wiki, that having multiple addresses per directors isn't supported for director-director communication. But anyway, thanks for the information, it helps. -- Heiko -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 473 bytes Desc: Digital signature URL: <http://dovecot.org/pipermail/dovecot/attachments/20151013/1575122c/attachment.sig>
Seemingly Similar Threads
- Dualstack IPv4/IPv6 setup with directors
- TLS communication director -> backend with X.509 cert checks?
- LMTP proxy does not pass RCPT TO: ... 5xx response back
- TLS communication director -> backend with X.509 cert checks?
- TLS communication director -> backend with X.509 cert checks?