- NANOG - lists.nanog.org

China internet issues
by Vinod Ola 22 May '24

22 May '24

Hi, Can anyone please help me to get view of China ISP issues and backbone issues? We always have issues within china and always blind to know what caused Sent from my iPhone

4 5

Geolocation IP help
by Sam Kretchmer 22 May '24

22 May '24

To anyone who might be able to help me reach someone clued at the State of Illinois website. We (Coeo Solutions) had to acquire an IP block, 213.159.132.0/22, from RIPE many years ago. This was due to availability issues at the time for acquiring new IP’s. This block was transferred to ARIN and assigned to Coeo. Before this transfer this IP block was sourced out of Dublin IRE. Now, the majority of Geo-location systems show these as being in the USA correctly, but, apparently whatever the Illinois State uses for their Geo-location verification is still showing these IP’s as being located in Dublin, and because that is outside the USA, they are blocking access to my customers using these IP’s. I have spent months sending emails and filling change requests with every Geo-location database service I can get to respond to me, but apparently none of them are what the St of Illinois uses for their Geo-location filtering. Any assistance I can find in getting this issue resolved so all my users can have full access to the State of Illinois websites would be greatly appreciated! Thanks

5 9

google imap timeouts / slowness from Toronto Canada ?
by mike tancsa 22 May '24

22 May '24

Anyone else seeing google imap timeouts / slowness ? We hit their services in Toronto Canada for ipv6 and ipv4 via gtt (However, ipv4 seems to come back via Torix). I am not seeing packet loss, just a lot of slowness in response at the app layer. google status says all ok. Problems started around 3:30am EST. My traffic comes out of AS11647. tcp acks come back super quick. Just random delays in the Push of the app response. example pcap below of "slow" and one "normal" traceroute6 to imap.gmail.com (2607:f8b0:4004:c1b::6d) from *2607:f3e0::12*, 64 hops max, 16 byte packets 1 host6 0.169 ms 2 toronto-torix-6 7.452 ms 3 * 4 google-b.ip6.torontointernetxchange.net 5.442 ms 5 2001:4860:0:1::322f 5.456 ms 6 2001:4860:0:1::3244 6.075 ms 7 2001:4860::c:4002:fc1a 27.485 ms 8 2001:4860::c:4002:6523 26.352 ms 9 2001:4860::c:4002:332e 26.528 ms 10 2001:4860::c:4002:a29a 27.551 ms 11 2001:4860::cc:4001:efe0 55.962 ms 12 2001:4860:0:1::e63 26.644 ms 13 * 14 * 15 * src ip 64.7.153.12 2 gtt-core1-10G (67.43.129.247) 5.225 ms 3 ae4-68.cr5-tor1.ip4.gtt.net (69.174.3.205) 7.868 ms 4 ae2.cr2-tor1.ip4.gtt.net (141.136.105.230) 10.595 ms 5 74.125.147.196 (74.125.147.196) 8.620 ms 6 192.178.98.45 (192.178.98.45) 8.997 ms 7 192.178.98.54 (192.178.98.54) 8.943 ms 8 142.251.231.171 (142.251.231.171) 18.056 ms 9 142.251.68.58 (142.251.68.58) 21.095 ms 10 142.251.69.191 (142.251.69.191) 27.531 ms 11 142.251.226.101 (142.251.226.101) 27.294 ms 12 216.239.57.97 (216.239.57.97) 27.101 ms 13 142.251.245.105 (142.251.245.105) 27.056 ms 14 * 15 * slow 12:27:25.602118 IP6 2607:f3e0::12.56498 > 2607:f8b0:4004:c19::6c.993: Flags [S], seq 3558477261, win 65535, options [mss 1440,nop,wscale 6,sackOK,TS val 366746043 ecr 0], length 0 12:27:25.629789 IP6 2607:f8b0:4004:c19::6c.993 > 2607:f3e0::12.56498: Flags [S.], seq 3828362457, ack 3558477262, win 65535, options [mss 1440,sackOK,TS val 998507935 ecr 366746043,nop,wscale 8], length 0 12:27:25.629824 IP6 2607:f3e0::12.56498 > 2607:f8b0:4004:c19::6c.993: Flags [.], ack 1, win 1026, options [nop,nop,TS val 366746071 ecr 998507935], length 0 12:27:25.630041 IP6 2607:f3e0::12.56498 > 2607:f8b0:4004:c19::6c.993: Flags [P.], seq 1:206, ack 1, win 1026, options [nop,nop,TS val 366746071 ecr 998507935], length 205 12:27:25.657752 IP6 2607:f8b0:4004:c19::6c.993 > 2607:f3e0::12.56498: Flags [.], ack 206, win 261, options [nop,nop,TS val 998507963 ecr 366746071], length 0 12:27:25.659493 IP6 2607:f8b0:4004:c19::6c.993 > 2607:f3e0::12.56498: Flags [.], seq 1:1209, ack 206, win 261, options [nop,nop,TS val 998507965 ecr 366746071], length 1208 12:27:25.659504 IP6 2607:f8b0:4004:c19::6c.993 > 2607:f3e0::12.56498: Flags [P.], seq 1209:2417, ack 206, win 261, options [nop,nop,TS val 998507965 ecr 366746071], length 1208 12:27:25.659518 IP6 2607:f3e0::12.56498 > 2607:f8b0:4004:c19::6c.993: Flags [.], ack 2417, win 988, options [nop,nop,TS val 366746100 ecr 998507965], length 0 12:27:25.659617 IP6 2607:f8b0:4004:c19::6c.993 > 2607:f3e0::12.56498: Flags [.], seq 2417:3625, ack 206, win 261, options [nop,nop,TS val 998507965 ecr 366746071], length 1208 12:27:25.659627 IP6 2607:f8b0:4004:c19::6c.993 > 2607:f3e0::12.56498: Flags [P.], seq 3625:4227, ack 206, win 261, options [nop,nop,TS val 998507965 ecr 366746071], length 602 12:27:25.659641 IP6 2607:f3e0::12.56498 > 2607:f8b0:4004:c19::6c.993: Flags [.], ack 4227, win 1016, options [nop,nop,TS val 366746100 ecr 998507965], length 0 12:27:25.669774 IP6 2607:f3e0::12.56498 > 2607:f8b0:4004:c19::6c.993: Flags [P.], seq 206:332, ack 4227, win 1026, options [nop,nop,TS val 366746110 ecr 998507965], length 126 12:27:25.697747 IP6 2607:f8b0:4004:c19::6c.993 > 2607:f3e0::12.56498: Flags [P.], seq 4227:4517, ack 332, win 261, options [nop,nop,TS val 998508003 ecr 366746110], length 290 12:27:25.705534 IP6 2607:f8b0:4004:c19::6c.993 > 2607:f3e0::12.56498: Flags [P.], seq 4517:4613, ack 332, win 261, options [nop,nop,TS val 998508011 ecr 366746110], length 96 12:27:25.705550 IP6 2607:f3e0::12.56498 > 2607:f8b0:4004:c19::6c.993: Flags [.], ack 4613, win 1024, options [nop,nop,TS val 366746146 ecr 998508003], length 0 12:27:25.705945 IP6 2607:f3e0::12.56498 > 2607:f8b0:4004:c19::6c.993: Flags [P.], seq 332:408, ack 4613, win 1026, options [nop,nop,TS val 366746146 ecr 998508003], length 76 12:27:25.738466 IP6 2607:f8b0:4004:c19::6c.993 > 2607:f3e0::12.56498: Flags [.], ack 408, win 261, options [nop,nop,TS val 998508044 ecr 366746146], length 0 12:27:57.854752 IP6 2607:f8b0:4004:c19::6c.993 > 2607:f3e0::12.56498: Flags [P.], seq 4613:4911, ack 408, win 261, options [nop,nop,TS val 998540161 ecr 366746146], length 298 12:27:57.855295 IP6 2607:f3e0::12.56498 > 2607:f8b0:4004:c19::6c.993: Flags [P.], seq 408:453, ack 4911, win 1026, options [nop,nop,TS val 366778296 ecr 998540161], length 45 12:27:57.882290 IP6 2607:f8b0:4004:c19::6c.993 > 2607:f3e0::12.56498: Flags [.], ack 453, win 261, options [nop,nop,TS val 998540188 ecr 366778296], length 0 12:28:17.420682 IP6 2607:f8b0:4004:c19::6c.993 > 2607:f3e0::12.56498: Flags [P.], seq 4911:5313, ack 453, win 261, options [nop,nop,TS val 998559726 ecr 366778296], length 402 12:28:17.421214 IP6 2607:f3e0::12.56498 > 2607:f8b0:4004:c19::6c.993: Flags [P.], seq 453:498, ack 5313, win 1026, options [nop,nop,TS val 366797862 ecr 998559726], length 45 12:28:17.448170 IP6 2607:f8b0:4004:c19::6c.993 > 2607:f3e0::12.56498: Flags [.], ack 498, win 261, options [nop,nop,TS val 998559754 ecr 366797862], length 0 12:28:20.195617 IP6 2607:f3e0::12.56498 > 2607:f8b0:4004:c19::6c.993: Flags [F.], seq 498, ack 5313, win 1026, options [nop,nop,TS val 366800636 ecr 998559754], length 0 12:28:20.227391 IP6 2607:f8b0:4004:c19::6c.993 > 2607:f3e0::12.56498: Flags [.], ack 499, win 261, options [nop,nop,TS val 998562533 ecr 366800636], length 0 12:28:42.746300 IP6 2607:f8b0:4004:c19::6c.993 > 2607:f3e0::12.56498: Flags [F.], seq 5313, ack 499, win 261, options [nop,nop,TS val 998585052 ecr 366800636], length 0 12:28:42.746330 IP6 2607:f3e0::12.56498 > 2607:f8b0:4004:c19::6c.993: Flags [.], ack 5314, win 1026, options [nop,nop,TS val 366823187 ecr 998585052], length 0 not slow 12:27:54.345307 IP6 2607:f3e0::12.56605 > 2607:f8b0:4004:c19::6c.993: Flags [S], seq 860170822, win 65535, options [mss 1440,nop,wscale 6,sackOK,TS val 366774786 ecr 0], length 0 12:27:54.371528 IP6 2607:f8b0:4004:c19::6c.993 > 2607:f3e0::12.56605: Flags [S.], seq 1855952390, ack 860170823, win 65535, options [mss 1440,sackOK,TS val 485305487 ecr 366774786,nop,wscale 8], length 0 12:27:54.371563 IP6 2607:f3e0::12.56605 > 2607:f8b0:4004:c19::6c.993: Flags [.], ack 1, win 1026, options [nop,nop,TS val 366774812 ecr 485305487], length 0 12:27:54.371768 IP6 2607:f3e0::12.56605 > 2607:f8b0:4004:c19::6c.993: Flags [P.], seq 1:206, ack 1, win 1026, options [nop,nop,TS val 366774812 ecr 485305487], length 205 12:27:54.397925 IP6 2607:f8b0:4004:c19::6c.993 > 2607:f3e0::12.56605: Flags [.], ack 206, win 261, options [nop,nop,TS val 485305513 ecr 366774812], length 0 12:27:54.398455 IP6 2607:f8b0:4004:c19::6c.993 > 2607:f3e0::12.56605: Flags [.], seq 1:1209, ack 206, win 261, options [nop,nop,TS val 485305514 ecr 366774812], length 1208 12:27:54.398466 IP6 2607:f8b0:4004:c19::6c.993 > 2607:f3e0::12.56605: Flags [P.], seq 1209:2417, ack 206, win 261, options [nop,nop,TS val 485305514 ecr 366774812], length 1208 12:27:54.398481 IP6 2607:f3e0::12.56605 > 2607:f8b0:4004:c19::6c.993: Flags [.], ack 2417, win 988, options [nop,nop,TS val 366774839 ecr 485305514], length 0 12:27:54.398579 IP6 2607:f8b0:4004:c19::6c.993 > 2607:f3e0::12.56605: Flags [.], seq 2417:3625, ack 206, win 261, options [nop,nop,TS val 485305514 ecr 366774812], length 1208 12:27:54.398591 IP6 2607:f8b0:4004:c19::6c.993 > 2607:f3e0::12.56605: Flags [P.], seq 3625:4227, ack 206, win 261, options [nop,nop,TS val 485305514 ecr 366774812], length 602 12:27:54.398604 IP6 2607:f3e0::12.56605 > 2607:f8b0:4004:c19::6c.993: Flags [.], ack 4227, win 1016, options [nop,nop,TS val 366774839 ecr 485305514], length 0 12:27:54.408741 IP6 2607:f3e0::12.56605 > 2607:f8b0:4004:c19::6c.993: Flags [P.], seq 206:332, ack 4227, win 1026, options [nop,nop,TS val 366774849 ecr 485305514], length 126 12:27:54.435121 IP6 2607:f8b0:4004:c19::6c.993 > 2607:f3e0::12.56605: Flags [P.], seq 4227:4517, ack 332, win 261, options [nop,nop,TS val 485305550 ecr 366774849], length 290 12:27:54.444165 IP6 2607:f8b0:4004:c19::6c.993 > 2607:f3e0::12.56605: Flags [P.], seq 4517:4613, ack 332, win 261, options [nop,nop,TS val 485305559 ecr 366774849], length 96 12:27:54.444181 IP6 2607:f3e0::12.56605 > 2607:f8b0:4004:c19::6c.993: Flags [.], ack 4613, win 1024, options [nop,nop,TS val 366774885 ecr 485305550], length 0 12:27:54.444567 IP6 2607:f3e0::12.56605 > 2607:f8b0:4004:c19::6c.993: Flags [P.], seq 332:408, ack 4613, win 1026, options [nop,nop,TS val 366774885 ecr 485305550], length 76 12:27:54.475386 IP6 2607:f8b0:4004:c19::6c.993 > 2607:f3e0::12.56605: Flags [.], ack 408, win 261, options [nop,nop,TS val 485305591 ecr 366774885], length 0 12:28:31.106366 IP6 2607:f8b0:4004:c19::6c.993 > 2607:f3e0::12.56605: Flags [P.], seq 4613:4911, ack 408, win 261, options [nop,nop,TS val 485342221 ecr 366774885], length 298 12:28:31.106783 IP6 2607:f3e0::12.56605 > 2607:f8b0:4004:c19::6c.993: Flags [P.], seq 408:453, ack 4911, win 1026, options [nop,nop,TS val 366811547 ecr 485342221], length 45 12:28:31.132930 IP6 2607:f8b0:4004:c19::6c.993 > 2607:f3e0::12.56605: Flags [.], ack 453, win 261, options [nop,nop,TS val 485342248 ecr 366811547], length 0 12:28:48.110633 IP6 2607:f3e0::12.56605 > 2607:f8b0:4004:c19::6c.993: Flags [F.], seq 453, ack 4911, win 1026, options [nop,nop,TS val 366828551 ecr 485342248], length 0 12:28:48.141972 IP6 2607:f8b0:4004:c19::6c.993 > 2607:f3e0::12.56605: Flags [.], ack 454, win 261, options [nop,nop,TS val 485359257 ecr 366828551], length 0 12:28:53.819032 IP6 2607:f8b0:4004:c19::6c.993 > 2607:f3e0::12.56605: Flags [F.], seq 4911, ack 454, win 261, options [nop,nop,TS val 485364934 ecr 366828551], length 0 12:28:53.819062 IP6 2607:f3e0::12.56605 > 2607:f8b0:4004:c19::6c.993: Flags [.], ack 4912, win 1026, options [nop,nop,TS val 366834260 ecr 485364934], length 0

2 1

Packet loss and latency between Akamai and NTT in Miami
by Carlos Martinez-Cagnazzo 22 May '24

22 May '24

Any contacts with either Akamai or NTT here ? This is kind of important as this is affecting three of our RPKI publication servers (servers which I have de-priorized in Route53 to prevent any issues for RPs) I have a ticket open with Akamai but I'm not directly an NTT customer so any help is appreciated. A sample MTR report, see between hops 7 and 8. Funnily enough this is periodic and has a cycle of between 15 and 25 minutes. %% START MTR TCP IPV4 en 20240517-16:10 Start: 2024-05-17T16:10:01+0000 HOST: rpki-fe-45-79-203-193.rrdp. Loss% Snt Last Avg Best Wrst StDev 1.|-- 10.204.6.21 0.0% 20 0.5 0.2 0.1 0.5 0.1 2.|-- 10.204.35.59 0.0% 20 0.3 0.3 0.2 0.6 0.1 10.204.35.60 3.|-- 10.204.64.38 0.0% 20 0.3 0.3 0.2 0.6 0.1 10.204.64.37 4.|-- lo0-0.gw3.atl1.us.linode. 0.0% 20 19.9 4.1 0.4 19.9 6.1 lo0-0.gw4.atl1.us.linode.com 5.|-- ae45.r12.atl01.ien.netarc 0.0% 20 0.5 0.5 0.4 0.7 0.1 ae48.r11.atl01.ien.netarch.akamai.com 6.|-- ae-41.a03.atlnga05.us.bb. 0.0% 20 5.2 2.3 0.4 14.8 3.7 ae0.r11.atl01.ien.netarch.akamai.com 7.|-- ae-41.a03.atlnga05.us.bb. 0.0% 20 3.3 11.4 0.9 38.5 11.0 ae-2.r25.atlnga05.us.bb.gin.ntt.net 8.|-- ae-1.r22.miamfl02.us.bb.g 20.0% 20 7271. 1816. 0.8 7271. 3236.6 ae-2.r25.atlnga05.us.bb.gin.ntt.net 9.|-- ae-1.r22.miamfl02.us.bb.g 5.0% 20 7201. 1684. 13.3 7256. 2970.2 ae-0.r23.miamfl02.us.bb.gin.ntt.net 10.|-- ae-11.a00.saplbr02.br.bb. 0.0% 20 123.2 206.8 13.1 3035. 667.7 ae-0.r23.miamfl02.us.bb.gin.ntt.net 11.|-- ae1-1326.gw1.nu.registro. 0.0% 20 129.2 125.2 116.7 139.5 5.8 ae-11.a00.saplbr02.br.bb.gin.ntt.net 12.|-- xe-0-1-2-0.core1.nu.regis 0.0% 20 117.9 174.0 117.6 1133. 225.9 ae1-1326.gw1.nu.registro.br Thanks Carlos -- -- ========================= Carlos M. Martinez-Cagnazzo http://cagnazzo.me =========================

3 3

Re: Fast backbone to NA from Asia
by Mark Tinka 22 May '24

22 May '24

On 5/22/24 16:55, Scott Q. wrote: > Hi Mark, > > thank you for the very informative post! In the meantime, our own > provider moved some routes from GTT to...Cogent and the times > decreased within the normal range. Also a few VPS providers such as > EdgeNext are using NTT & Cogent and show no issues either. So it seems > some providers experience an extra 80ms delay for some reason, I > wonder why. This is our new traceroute Yeah - best thing to do would be to reach out to a problematic provider and ask them for an explanation. Usually, if they have bought directly from a subsea provider, then restoring from a subsea outage may be complex depending on how well they secured themselves both from a diversity and capacity standpoint. If they are a customer of a major transit provider, then their provider's subsea inventory situation is similar to my point above. It is very hard to tell unless you ask someone on the inside, but as these things do, when cables get cut, latency and packet loss increases are not unexpected, especially for small/local/regional ISP's that can't afford to have direct access to multiple subsea systems. And in cases where alternative options are either too costly or non-existent, the latency and packet loss penalty would be sustained longer than necessary. Depending on where you are in the food chain, subsea restoration efforts following a major cut can increase normal pricing by 3X - 5X, particularly if the restoration capacity is taken on a short-term basis, e.g., 3 months. Mark.

1 0

Fast backbone to NA from Asia
by Scott Q. 22 May '24

22 May '24

I apologize if this is off-topic, but I am looking to purchase some VPS in Asia on a network that has really fast transit to NA and not affected by the latest peering disputes. The network should have really good connectivity to India / Indonesia / Thailand and ideally Australia as well. Please reply off-list.

5 6

Passpoint ONTs
by Mike Hammett 22 May '24

22 May '24

I know that this list is normally big picture Internet-centric, but I have a last-mile question for the group. Have you seen any Passpoint-certified residential ONTs? The use case is to provide cellular offload over our last-mile fiber infrastructure. Often these projects are pitched towards venues with high traffic because dedicated investments are being made. If the investment in deploying these ONTs all over God's creation is already being made, one might as well find additional revenue streams for them. ----- Mike Hammett Intelligent Computing Solutions http://www.ics-il.com Midwest-IX http://www.midwest-ix.com

1 0

Frontier AS5650 IPv6 Peering
by Nick Olsen 21 May '24

21 May '24

Anyone with a clue from 5650 monitoring this list? I'm in the process of turning up a new transit circuit from 5650 and my account management team has been less than helpful. The normal contacts aren't getting me anywhere. Thank you!

2 1

Should FCC look at SS7 vulnerabilities or BGP vulnerabilities
by Sean Donelan 20 May '24

20 May '24

Should FCC focus on SS7 vulnerabilities or BGP vulnerabilities? https://www.404media.co/email/79f7367c-bd3c-4bff-ac9f-85c738d08bec/ https://www.fcc.gov/ecfs/document/10427582404839/1 Additional comments from Kevin Briggs: "I have seen what appears to be reliable information related to numerous other exploits based on SS7 and Diameter that go beyond location tracking. Some of these involve issues like (1) the monitoring of voice and text messages, (2) the delivery of spyware to targeted devices, and (3) the influencing of U.S. voters by overseas countries using text messages." On Wed, 15 May 2024, Job Snijders via NANOG wrote: > Dear all, > FYI: https://docs.fcc.gov/public/attachments/DOC-402579A1.pdf

14 22

[Event] NetUK1 Call for Presentations open
by Matt Jepp 20 May '24

20 May '24

Hi NANOG List, NetUK1 will take place on the 8th and 9th of July 2024 at IET London: Savoy Place in London, this will be an in-person meeting. Tickets are also available at: www.netuk.org/netuk1/ <http://www.netuk.org/netuk1/> NetUK helps people learn at every stage of their career. Our talks help Internet veterans stay current and gives people at the start of their career an opportunity to learn about new technologies, forge new connections, and share what they have learned to an international audience. If your team has a presentation you'd like to submit to NetUK1, consider having a junior team member give the presentation to boost their experience with the UK community. We are open to a range of in-person presentation formats. Agenda slots can be as short as 10 minutes and as long as an hour. Proposals on any subject relevant to networking and interconnection are welcome, both technical and non-technical. Perhaps tell us about a new technology you're implementing. If you’ve been working on a project, solved a problem, or are thinking about a challenge, bring it to NetUK! Please submit your proposals using the "Submit new abstract" function in our Indico instance available at https://indico.netuk.org/ . If you are proposing a presentation, please upload a draft of your proposed presentation slides to assist the PC in considering your submission. If you are proposing a panel, please include detail of the proposed speakers as well as the abstract of the panel's topics. NOTE: To preserve editorial neutrality, the PC does not accept abstract submissions for presentations by commercial organisations that are also sponsors of the same NetUK event. If you would like one of our sponsored presentation slots, please contact us. NetUK is run on a non-profit basis and is not in a position to reimburse expenses or time for speakers at its meetings, however we do provide an event ticket for accepted speakers. If you have any queries, please contact the Programme Committee by email at pc(a)netuk.org -- NetUK Programme Committee https://indico.netuk.org/ pc(a)netuk.org

1 0