webex broken for public IPv4
Michael Richardson <mcr+ietf@sandelman.ca> Tue, 12 May 2020 10:46 UTC
Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 360603A0D62 for <wgchairs@ietfa.amsl.com>; Tue, 12 May 2020 03:46:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id k7wegpsBReVQ for <wgchairs@ietfa.amsl.com>; Tue, 12 May 2020 03:46:33 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5E99D3A09BC for <wgchairs@ietf.org>; Tue, 12 May 2020 03:46:33 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id A1179389A6; Tue, 12 May 2020 06:44:26 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id jM74qfOjtCuS; Tue, 12 May 2020 06:44:25 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 6E776389A4; Tue, 12 May 2020 06:44:25 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 740C95E; Tue, 12 May 2020 06:46:29 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: WG Chairs <wgchairs@ietf.org>
cc: Henk Birkholz <henk.birkholz@sit.fraunhofer.de>
Subject: webex broken for public IPv4
X-Attribution: mcr
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Tue, 12 May 2020 06:46:29 -0400
Message-ID: <14791.1589280389@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/xWyLumablVX8178an4iBqBtjNvU>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 12 May 2020 10:46:35 -0000
Two weeks ago, webex audio stopped working for me on my desktop. It had worked great for a few YEARS with the webrtc version on Linux. I kept seeing: [5803:5808:0512/063438.704895:ERROR:socket_udp.cc(219)] Received unexpected data packet from 173.39.232.161:9000 before STUN binding is finished. on the console/terminal of my browser. The STUN message suggested to me that something was broken if I *don't* have NAT44. I have an IPv4/32 routed to my desktop out of the /28 that I have. I might be among the few, but Henk points out that "Global EDUroam" on his campus also gives out public IPv4, only he can't use that while in lockdown to validate my bug report. I added to my routing an exception that routed 173.39.232.161 with a NAT44 src address. Details somewhat specific to my setup, but happy to give details. netstat now shows a mix of connections as they move over to the rfc1918 address, and AUDIO WORKS. Henk and I now discuss details of German un-lock-down vs R>1. tcp 0 0 209.87.249.21:52404 173.39.232.161:5004 TIME_WAIT tcp 0 0 172.30.2.21:33066 173.39.232.161:80 TIME_WAIT tcp 0 0 209.87.249.21:49426 173.39.232.161:80 TIME_WAIT tcp 0 0 172.30.2.21:37582 173.39.232.161:5004 ESTABLISHED tcp 0 0 172.30.2.21:37558 173.39.232.161:5004 ESTABLISHED ... I had opened a ticket two weeks, but no acknowledgement at all. This bug would have shown up **immediately** if they had IPv6 support. -- Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works -= IPv6 IoT consulting =-
- webex broken for public IPv4 Michael Richardson
- Re: webex broken for public IPv4 Michael Richardson
- Re: webex broken for public IPv4 Michael Richardson
- Re: webex broken for public IPv4 Michael Richardson
- Re: webex broken for public IPv4 Colin Perkins
- Re: webex broken for public IPv4 Christopher Morrow
- Re: webex broken for public IPv4 Michael Richardson
- Re: webex broken for public IPv4 Michael Richardson
- Re: webex broken for public IPv4 Christopher Morrow
- Re: webex broken for public IPv4 Carsten Bormann
- Re: webex broken for public IPv4 Michael Richardson
- Re: webex broken for public IPv4 Christopher Morrow
- Re: webex broken for public IPv4 Michael Richardson
- Re: webex broken for public IPv4 Christopher Morrow
- Re: webex broken for public IPv4 Carsten Bormann
- Re: webex broken for public IPv4 Ted Hardie
- Re: webex broken for public IPv4 Henk Birkholz
- Re: webex broken for public IPv4 Carsten Bormann