[123attendees] Re: Issues with IPv4 address instability - only for people from Netherlands?

Warren Kumari <warren@kumari.net> Fri, 25 July 2025 10:45 UTC

Return-Path: <warren@kumari.net>
X-Original-To: 123attendees@mail2.ietf.org
Delivered-To: 123attendees@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 53F724B09417 for <123attendees@mail2.ietf.org>; Fri, 25 Jul 2025 03:45:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_IMAGE_RATIO_08=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=kumari.net
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LMT_1QkDEClm for <123attendees@mail2.ietf.org>; Fri, 25 Jul 2025 03:45:24 -0700 (PDT)
Received: from mail-ej1-x630.google.com (mail-ej1-x630.google.com [IPv6:2a00:1450:4864:20::630]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 52D044B093F2 for <123attendees@ietf.org>; Fri, 25 Jul 2025 03:45:24 -0700 (PDT)
Received: by mail-ej1-x630.google.com with SMTP id a640c23a62f3a-ae401ebcbc4so328545666b.1 for <123attendees@ietf.org>; Fri, 25 Jul 2025 03:45:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kumari.net; s=google; t=1753440323; x=1754045123; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=eH5kGqC9Gd/wjKzSPggrNxQwKLgDHwTy3/VMZmNvb0g=; b=ARE1ijN2WRiHqOe5X02AWT45NRMwaegCxHY1TGBHZNeBVVzOOmg23rkELWrFAADDJ1 8bfWGsWLO60RCAJni0KSwpU5MTNd9m++EkIXuxE//Hrlad0/FGFr9WXZjBWrAsHkhM43 IGSyMRkO6uyw5mq6vvTQ6wFIBFXORUrcJNUknGyTEO5afdOh0k5QNIhrNRJSlUQEc7SM bzroU4HaTd+ch0TMuVVdAyB4ZkifM/1PTk00DU7ykiUVL2phdMPz/s9vyzrXdigxid/T 344qj6+tBaHxBNjfjcfR5y/Mtj9EJxWvTTGpr4/BkTKR21bPhDvHTJ6BHBG+kEYFsJNP +VTg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1753440323; x=1754045123; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=eH5kGqC9Gd/wjKzSPggrNxQwKLgDHwTy3/VMZmNvb0g=; b=VKgpIrcC601Cg4EddDSP8U77hbaNCW10QegqPqHFK86ms64BCJbV7cZW7rui/DGp5N ZBy7XWUt6aDWScTWq/EO4nIPvVhRl0poMXZ5Q5KSgSCHvRhs9atwK+A6m75aXFee6VLp nZzM4VJxFrPyFV7rptyhx8PRBtWGSQEWbNV+AcpCYFa2NLJi120lVmtPxPdUDywApw9N tKnkn9DvyX5E8D6ExfQ6iqWyLzD+mmMXRz5GmLpj9Yixb1DkCW6PjkcsYYAobq6Fz9iW 01J3+8Jlex4gp/Pdjsv/9FQd1a2N+bJB5OMNp6WkxJJE2jObGnQ/EvQ9N6cRvjXbf636 jKDQ==
X-Forwarded-Encrypted: i=1; AJvYcCWpcPDAdsKgGoo2Lr5+uJGTTWePqPcUtLylJuMlfojRMmFY2ABtZV6L88uRVPbiRvYDjT9a/ukCEnO28lc=@ietf.org
X-Gm-Message-State: AOJu0YyptrrdrmKuWzCtDoMNqKLnKX2Iv/r3ccm354CuHrfCYMakEdAy GuwmAFVuM8CmbO4jtKNxRXmilKuUO5xHRc71bi4fE+i9MucqYIfihDjhfN6DCpjtqExt1jtTJS/ +D3iGWJuwj5cEj8eJY0096kR16u8pfuAv5TpoTJqF5w==
X-Gm-Gg: ASbGncuiWvtAGug3qaVMVsG/swnYa8xYuPM0Bxt0kthk93p3Ep/dK43r5oxlYE+ydYa 3JylhNP1V5OKO4kwa27q590tCl3FTAyRnq8Qc8EFUJrrKocjUXJVLkhLGmGTE8ioPkdt+HYj4Ry 5dXNf8J/Aj5Mw7i1bzmqOALQEdDTf4r9yFg8cfvpAo0ShSOsONe6fgAL0Wd1+m2QUqRlCueCteY qxbtbqew1osjrGC7ktTwZ1S8rMMqv0=
X-Google-Smtp-Source: AGHT+IE4BMqO+/NyH7WL4BnWyP66bAD/dpJq8kq2PfNxuiQ0HKduJkLF4ZZxdtGtGBzwGiWtDjR4Ghzb6rUfnrxz9nc=
X-Received: by 2002:a17:907:6d06:b0:ae0:c497:c5ca with SMTP id a640c23a62f3a-af6172096abmr177980066b.3.1753440322582; Fri, 25 Jul 2025 03:45:22 -0700 (PDT)
Received: from 649336022844 named unknown by gmailapi.google.com with HTTPREST; Fri, 25 Jul 2025 03:45:20 -0700
Received: from 649336022844 named unknown by gmailapi.google.com with HTTPREST; Fri, 25 Jul 2025 03:45:20 -0700
Mime-Version: 1.0
References: <CA+E65xR4=VFJwBoGFTng6i=pATN5E59Zs2PxuW_40GS3GXVmgw@mail.gmail.com> <CAPSJW7DdW7k3O4mGiduQzN-5E0DyHrRSFN5Jj0kMs-y1igA_uw@mail.gmail.com>
X-Superhuman-ID: mdip2x0h.c3d22345-8009-4c43-a968-da1790dc141c
X-Mailer: Superhuman iOS 11996
In-Reply-To: <CAPSJW7DdW7k3O4mGiduQzN-5E0DyHrRSFN5Jj0kMs-y1igA_uw@mail.gmail.com>
X-Superhuman-Draft-ID: draft004638318590fc48
From: Warren Kumari <warren@kumari.net>
Date: Fri, 25 Jul 2025 03:45:20 -0700
X-Gm-Features: Ac12FXyy1bVOoS8Uaz9mOXf7QR5qqsiR20bojU8hEr8olfGG1YiEEjiRbGcHSzo
Message-ID: <CAHw9_iJfhV_ypG1NNZJ7POtkTBA1pNcO+Vxv43kOtSVWenY9WQ@mail.gmail.com>
To: Benfeng Chen <benfeng@gmail.com>
Content-Type: multipart/related; boundary="000000000000909725063abea3bb"
Message-ID-Hash: 6UVJPSCEPWGYJWSYFH3EUNBFHXC5NTDH
X-Message-ID-Hash: 6UVJPSCEPWGYJWSYFH3EUNBFHXC5NTDH
X-MailFrom: warren@kumari.net
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: Ondřej Caletka <ondrej.caletka@gmail.com>, 123attendees <123attendees@ietf.org>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [123attendees] Re: Issues with IPv4 address instability - only for people from Netherlands?
List-Id: Mailing list for IETF 123 attendees <123attendees.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/123attendees/xqKtITDB2q8zEetja3L63j42Tv0>
List-Archive: <https://mailarchive.ietf.org/arch/browse/123attendees>
List-Help: <mailto:123attendees-request@ietf.org?subject=help>
List-Owner: <mailto:123attendees-owner@ietf.org>
List-Post: <mailto:123attendees@ietf.org>
List-Subscribe: <mailto:123attendees-join@ietf.org>
List-Unsubscribe: <mailto:123attendees-leave@ietf.org>

 Yeah, that's my fault.

This is working as intended... but the intent may have been incorrect :-p

The IETF network is unusual in that it lies dormant for around 4 months,
and then comes alive for a week, and then goes dormant again. This means
that some CDNs become startled by the zombies, and block list individual
IPs.

I decided to not make the NAT mapping deterministic ("address-persistent"
or "persistent-nat), so that if a CDN did this, the user could just refresh
their (almost definitely) browser page and would get a new address.

Almost all sites have moved away from IP addresses "verification" because
of things like multiple connections (WiFi and Cellular), CGNs, etc., but it
looks like this might have caused more issues than it helped... I believe
that the NOC is planning on twiddling the knob during tear down to test the
persistence behavior and may be persistent in Montreal...

Warren


On Wed, Jul 23, 2025 at 8:15 PM, Benfeng Chen <benfeng@gmail.com> wrote:

> I am seeing the same issue of IPv4 address instability.  With the same
> computer and the same browser, I saw different IPv4 addresses on different
> websites. If I refresh, the IP address changes to another one.
> [image: image.png]
> [image: image.png]
>
> [image: image.png]
>
>
>
> On Wed, Jul 23, 2025 at 7:28 PM Ondřej Caletka <ondrej.caletka@gmail.com>
> wrote:
>
>> Hey,
>>
>> I reported yesterday that the default network called ietf has issues
>> with some IPv4-only websites due to the fact that the current setup of
>> NAT64 maps each individual session to possibly different IPv4
>> addresses. You can see it by opening your favourite "What is my IPv4"
>> website and refreshing the browser a few times.
>>
>> This does not present a problem for most services, but there are some
>> websites whose authors didn't expect that a single user behind a
>> single browser can be accessing the web server from several IPv4
>> addresses. Typical cases are DRM protected video-on-demand websites
>> where the browser first asks for a license and this license/token is
>> then valid only for the IPv4 address from which it was requested.
>>
>> An example of such a website is https://nos.nl/l/2576078 but I also
>> noticed that HR software called AFAS Insite gets completely broken in
>> such a situation.
>> Since I have a theory that users tend to suffer in silence, I would
>> like to gauge if I am really the only one noticing this or if there is
>> anyone else who spotted something not working as usual but considered
>> it too minor to report. Please report broken websites (possibly also
>> to the owners of those websites.)
>>
>> --
>> Best regards,
>> Ondřej Caletka
>>
>> _______________________________________________
>> 123attendees mailing list -- 123attendees@ietf.org
>> To unsubscribe send an email to 123attendees-leave@ietf.org
>>
>
> _______________________________________________
> 123attendees mailing list -- 123attendees@ietf.org To unsubscribe send an
> email to 123attendees-leave@ietf.org
>