- Test - lists.nanog.org

Google.com SSL cert issues
by Mark Stevens 21 Sep '22

21 Sep '22

Is anyone else getting the following error when trying to access any of google's services? SSL_ERROR_RX_RECORD_TOO_LONG This started about an hour ago and is not dependent on browser type but rather geographic location. I have servers on different networks and some can no longer access google.com due to the SSL error. Thanks Mark

5 5

Imperva / Apple Private Relay issues
by Lyndon Nerenberg (VE7TFX/VE6BBM) 21 Sep '22

21 Sep '22

We have been receiving a steady stream of calls from customers complaining they cannot reach our websites when they have Apple's Private Relay enabled. For those in the dark, Private Relay sends (only) Safari connections through an assortment of CDNs to anonymize the client's IP address. What we are seeing is that, more often than not, connections to our public servers that route through Imperva's DDoS service do not go through. When we look on the uplink interfaces on our firewalls, there is nothing from those addresses. But connections to other hosts in the same cage, but which bypass Imperva, connect fine. We've opened a ticket, but thus far Imperva's support team has been unhelpful. What I'm wondering is if anyone else is seeing similar behaviour with their Imperva-protected hosts. A quick way to test is to turn on Private Relay on an iPhone (System Preferences -> iCloud -> iCloud -> Private Relay) and then try connecting to a web service hosted behind Imperva's DDoS service. For our servers, not all the connections fail, but a large percentage do, and it's definitely tied to the proxy address you get assigned (verified using whatismyip.com) We are seeing failures on connections relayed through both Cloudflare and Akamai. Apple could be using other CDNs as well, but those are the two we have specifically identified as having unusable addresses. --lyndon

3 3

WSJ Explainer: Taiwan has 14 submarine cables
by Sean Donelan 21 Sep '22

21 Sep '22

https://www.wsj.com/video/series/wsj-explains/how-chinas-military-drills-co… How China’s Military Drills Could Choke Off Taiwan’s Internet Taiwan has 14 submarine cables that connect the island to the rest of the world By Wall Street Journal Sep 21, 2022 5:15 am Taiwan’s internet relies on undersea cables that also connect much of Asia to the web, but tensions with Beijing have raised concerns about the network’s vulnerability. WSJ maps out how China could limit the island’s communications, and how Taipei is preparing.

1 0

Experiences with operational cost increases
by John Kristoff 21 Sep '22

21 Sep '22

Friends, Like many of you I'm sure, I'm seeing an irregular rise in prices for a variety of network services (e.g., IP addresses, connectivity, remote hands, hosting). The increases seem to be most common and pronounced in and around the European region thus far. I'm not here to talk about fundamental causes of what is being attributed to inflationary pressures. Rather, I'm curious how, what it any, effect it has had on net operations generally. I'm not sure if there are network graphs that can visualize these changing market conditions, but if this is changing what you do and how your network is operating, what would go in your lightning talk? And yes, you should consider submitting one for the upcoming NANOG if you have something measurable or insightful to say about it. John

1 0

Island-wide power blackout in Puerto Rico
by Sean Donelan 21 Sep '22

21 Sep '22

Puerto Rico is experiencing an island-wide power blackout (100%). Today's (based on yesterday's information) FCC Communication Status Report only reports 6.9% of cell towers out of service. I expect tomorrow's report (based on today's information) will be worse.

2 3

Article: DoD, DoJ press FCC for industry-wide BGP security standard
by Fletcher Kittredge 20 Sep '22

20 Sep '22

Fierce Telecom: DoD, DoJ press FCC for industry-wide BGP security standard <https://www.fiercetelecom.com/telecom/dod-doj-press-fcc-industry-wide-bgp-s…>

6 7

Normal ARIN registration service fees for LRSA entrants after 31 Dec 2023 (was: Fwd: [arin-announce] Availability of the Legacy Fee Cap for New LRSA Entrants Ending as of 31 December 2023)
by John Curran 20 Sep '22

20 Sep '22

NANOGers - At present ARIN continues to provide the favorable annual maintenance fee cap for legacy resource holders who enter into an LRSA with ARIN, but this cap on total maintenance fees not be offered to those entering an LRSA after 31 Dec 2023 and they will instead paying the same registration services plan fees as all other ARIN customers. See attached announcement for details. We strongly encourage all legacy resource holders who have not yet signed an LRSA to cover their legacy resources to consider doing so before 31 December 2023 in order to secure the most favorable fees for their ARIN Services as well as being able to access ARIN’s more advanced services such as the Internet Routing Registry (IRR) and Resource Public Key Infrastructure (RPKI) services. FYI, /John John Curran President and CEO American Registry for Internet Numbers Begin forwarded message: From: ARIN <info(a)arin.net<mailto:info@arin.net>> Subject: [arin-announce] Availability of the Legacy Fee Cap for New LRSA Entrants Ending as of 31 December 2023 Date: 13 September 2022 at 2:54:03 PM EDT To: "arin-announce(a)arin.net<mailto:arin-announce@arin.net>" <arin-announce(a)arin.net<mailto:arin-announce@arin.net>> On 11 October 2007, ARIN implemented the first version of the Legacy Registration Services Agreement (LRSA). This agreement and the fees associated with legacy resources have been modified several times over the past 15 years. The most recent change was in 2022 when ARIN transitioned all customers with IPv4 and/or IPv6 number resources to the same Registration Services Plan (RSP) Fee Schedule which has fee categories based on the total amount of resources held. This most recent change brought those organizations that were issued resources before the formation of ARIN (also known as “legacy resource holders”) into the new Fee Schedule. ARIN also continued providing legacy resource holders a cap on the total amount of maintenance fees due annually – the “annual legacy maintenance fee cap” – that has been offered since the introduction of the LRSA to encourage entry into an LRSA and normalization of these customers’ contractual relationship with ARIN. The “annual legacy maintenance fee cap” is presently set at $150 per year (and will increase by $25 in each subsequent year.) On 4 August 2022, the ARIN Board of Trustees voted unanimously in favor of ending the annual legacy maintenance fee cap applied to legacy resources brought under an LRSA beginning 1 January 2024. All organizations with active LRSA agreements entered prior to 1 January 2024 will continue to have their fees limited for legacy resources covered before that date per the annual legacy maintenance fee cap as noted above. Any new legacy resources brought under an LRSA as of 1 January 2024 forward will fall under the full, normal RSP fees. We strongly encourage all legacy resource holders who have not yet signed an LRSA to cover their legacy resources to consider doing so before 31 December 2023 in order to secure the most favorable fees for their ARIN Services as well as being able to access ARIN’s more advanced services such as the Internet Routing Registry (IRR) and Resource Public Key Infrastructure (RPKI) services. If you have any questions about billing or the 2022 Fee Schedule, please contact 2022Fees(a)arin.net<mailto:2022Fees@arin.net>. Regards, John Curran President and CEO American Registry for Internet Numbers (ARIN) ----------- REFERENCE LINKS 11 October 2007 Announcement: https://www.arin.net/vault/announcements/2007/20071011.html ARIN Fee Schedule: https://www.arin.net/resources/fees/ August 2022 Board of Trustees Minutes: https://www.arin.net/about/welcome/board/meetings/2022_0803/ ARIN Services Available to Legacy Organizations: https://www.arin.net/resources/guide/legacy/services/ _______________________________________________ ARIN-Announce You are receiving this message because you are subscribed to the ARIN Announce Mailing List (ARIN-announce(a)arin.net<mailto:ARIN-announce@arin.net>). Unsubscribe or manage your mailing list subscription at: https://lists.arin.net/mailman/listinfo/arin-announce Please contact info(a)arin.net if you experience any issues.

18 93

bufferbloat-beating customer shaping via LibreQoS
by Dave Taht 18 Sep '22

18 Sep '22

There's been a huge uptake in interest lately in doing better per device and per customer shaping, especially for ISPs, in the libreQoS.io project, which is leveraging the best ideas bufferbloat project members have had over the past decade (cake, bpf, xdp) to push an x86 middlebox well past the 10Gbit barrier, on sub-2k boxes, with really good stats on backlogs, drops, and ecn marks. I've long primarily tried to get fq_codel and cake running on the CPE (most recently mikrotik), and that's been taking too long. I have no idea to what extent members of this list have interest in this, but if you know of a smaller ISP with bad bufferbloat, please pass that link along? It's got ridiculously easier to set up as a vm of late. There is presently a design discussion going on over here: https://github.com/rchac/LibreQoS/issues/57 And by mentioning it here, today, I'm mostly asking what other real life use cases we should try to tackle? What backend tools should we try to integrate with? -- FQ World Domination pending: https://blog.cerowrt.org/post/state_of_fq_codel/ Dave Täht CEO, TekLibre, LLC

3 2

Samsung too?
by Jared Mauch 17 Sep '22

17 Sep '22

1 0

Contact info for Level 3 CDN GeoIP
by Christopher Munz-Michielin 17 Sep '22

17 Sep '22

Hey All, For my dayjob I help run an Anycast DNS network and we've recently had complaints from our users in the APAC region that sites using Level 3's CDN have poor performance. Upon looking into this, it seems that they (Level 3) have incorrect geolocation data for some of our Singapore servers and are returning IPs for CDN servers in Australia. I've validated the WHOIS information for the blocks in question is correct, and every GeoIP site I check against comes back as Singapore, so this must be some internal database. I've tried emailing the whois contact, as well as the technical contact for the domain footprint.net but have yet to receive a response. Wonder if anyone else has been able to get in touch with the CDN people at Level 3? Cheers! Chris

2 2