This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/ripe-atlas@ripe.net/
[atlas] Strange IPv6 problem with Atlas
- Previous message (by thread): [atlas] Strange IPv6 problem with Atlas
- Next message (by thread): [atlas] Cannot change network configuration
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Philip Homburg
philip.homburg at ripe.net
Tue Oct 2 09:34:15 CEST 2012
On 10/2/12 3:14 , Lorenzo Colitti wrote: > > > That said - why is SSH trying to communicate over IPv6 with a > link-local address in the first place? getaddrinfo should be ranking > the global IPv4 address above the link-local IPv6 address and thus > causing SSH to prefer IPv4... I have to check, but my guess is that no sorting is being done at all. The probe software is built on top of ucLinux. Large parts of ucLinux are reimplementations with a focus on compactness. I wondered why we never noticed this before. The reason is two fold. One is that dbclient is just about the only part in the Atlas software that can choose between IPv4 and IPv6. All other parts get told to do one or the other. The other reason is that a probe on an IPv4-only LAN will not have an IPv6 default router. So any attempt to use the link local address to connect will remain hidden within the probe.
- Previous message (by thread): [atlas] Strange IPv6 problem with Atlas
- Next message (by thread): [atlas] Cannot change network configuration
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]