[ipv6-wg] IPv4-mapped addresses in AAAA records (was: RIPE 88, presentations and a co chair change..)
- Previous message (by thread): [ipv6-wg] IPv4-mapped addresses in AAAA records (was: RIPE 88, presentations and a co chair change..)
- Next message (by thread): [ipv6-wg] RIPE 88, presentations and a co chair change.....
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Gert Doering
gert at space.net
Wed Mar 27 09:32:39 CET 2024
Hi, On Wed, Mar 27, 2024 at 02:34:41PM +1100, Michael Richardson wrote: > My take home from this github incident is that one should do IPv6 deployment > first, and then treat IPv4 as a subset via mapped IPv4 addresses. > (Open)SSH had been using the mapped addresses for ages, and they showed up > that way for ages. It has stopped for unknown reasons. I guess that someone was upset with the way they showed up in the logs... (OpenVPN has extra code to ensure that "we received an IPv4 connection on a dual-stack IPv6 socket" gets logged the same as "IPv4 on IPv4 socket", because that reduces the number of confused users down...) Gert Doering -- NetMaster -- have you enabled IPv6 on something today...? SpaceNet AG Vorstand: Sebastian v. Bomhard, Michael Emmer, Ingo Lalla, Karin Schuler Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann D-80807 Muenchen HRB: 136055 (AG Muenchen) Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: <https://lists.ripe.net/ripe/mail/archives/ipv6-wg/attachments/20240327/012f2c79/attachment-0001.sig>
- Previous message (by thread): [ipv6-wg] IPv4-mapped addresses in AAAA records (was: RIPE 88, presentations and a co chair change..)
- Next message (by thread): [ipv6-wg] RIPE 88, presentations and a co chair change.....
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[ ipv6-wg Archives ]