Re: Re: Survey on barriers for RPKI adoption

2024-09-10 Thread Lancheng via NANOG
Hi Sofia, I am currently an Assistant Researcher in Zhongguancun Lab, Beijing, China. Although I am not a network operator, I am very interested in this topic. Last year, I also did a survey asking network operators about the barriers to adopting ROA and ROV. That work has been accepted by N

ATT contact

2024-09-10 Thread Doug Barrett
We’re seeing 30-50% packet loss on a hop around what we believe is Chicago area.  Please reach out off-list if you can help. ->  voiptest.sea.telecomsvc.com(64.282024-09-10T11:02:57-0500      

Re: ATT contact

2024-09-10 Thread Brandon Jackson
You have 0% packet loss on any hop past that hop, and 0% packet loss at the destination... Learn what ICMP deprioritization is, there is no packet loss shown in that. On Tue, Sep 10, 2024, 12:30 Doug Barrett wrote: > We’re seeing 30-50% packet loss on a hop around what we believe is Chicago >

Re: ATT contact

2024-09-10 Thread Matt Erculiani
Doug, I'd recommend giving this a read: https://www.linode.com/docs/guides/diagnosing-network-issues-with-mtr/#verify-packet-loss Your trace shows nothing of concern. -Matt On Tue, Sep 10, 2024 at 10:28 AM Doug Barrett wrote: > We’re seeing 30-50% packet loss on a hop around what we believe

Third Party VoIP Over Xfinity

2024-09-10 Thread Matt Hoppes
I have an employee who has recently switched to Xfinity cable service. Ever since they switched their internet service their work phones will not stay registered for more than about 3 minutes. These same phones have been used on many ISPs without issues. The same config has been used behind m

Re: Third Party VoIP Over Xfinity

2024-09-10 Thread Norman Jester via NANOG
Your message is timely for me. I literally have the exact same issue. I setup phones for my daughter’s home and she got Xfinity. Everything worked for a few minutes then I could not keep phones registered after. Norman Jester > On Sep 10, 2024, at 12:18 PM, Matt Hoppes > wrote: > > I have

Re: Third Party VoIP Over Xfinity

2024-09-10 Thread Matt Hoppes
Well this is curious Same issue... they are breaking something with registration. What region are you in? We are in North Central PA so we're routing On 9/10/24 3:25 PM, Norman Jester wrote: Your message is timely for me. I literally have the exact same issue. I setup phones for my dau

Re: Third Party VoIP Over Xfinity

2024-09-10 Thread Norman Jester via NANOG
Saint Helena, CA near Napa Norman Jester > On Sep 10, 2024, at 12:52 PM, Matt Hoppes > wrote: > > Well this is curious > > Same issue... they are breaking something with registration. What region are > you in? We are in North Central PA so we're routing > >> On 9/10/24 3:25 PM, Nor

Re: Third Party VoIP Over Xfinity

2024-09-10 Thread Matt Hoppes
So not even the same area then. We've now spent 2 hours on the phone and have gotten nowhere with support. Hoping someone here at XFinity can chime in and provide some offline assistance. On 9/10/24 3:59 PM, Norman Jester wrote: Saint Helena, CA near Napa Norman Jester On Sep 10, 2024,

Cloudfront Blocking IP ranges

2024-09-10 Thread Brad Bendy
Does anyone know the best way to get a hold of Amazon and get out off the naughty list on Cloudfront? I've got some ranges that appear to be blocked totally by Cloudfront. Thanks in advance

Re: Third Party VoIP Over Xfinity

2024-09-10 Thread Jon Lewis
Are you aware of whether or not Xfinity is doing CGNAT for either of you? Googling, I get conflicting results, some saying they use CGNAT, some saying they don't. If they do, I wonder if their CGNAT routers have SIP ALG enabled or disabled. Unfortunately, these are the sorts of questions I su

Re: Third Party VoIP Over Xfinity

2024-09-10 Thread Matt Hoppes
For me there does not *appear* to be CGNAT as I can ping the client IP and if we kill power to the modem the pings stop. On 9/10/24 4:27 PM, Jon Lewis wrote: Are you aware of whether or not Xfinity is doing CGNAT for either of you? Googling, I get conflicting results, some saying they use CGNAT

Re: Third Party VoIP Over Xfinity

2024-09-10 Thread Mark Wiater
What happens when you decrease your registration frequency? Do the phones stay registered? Have you tried TLS for the SIP transport by chance? I manage a few phones on comcast across the country and have no problems. On 9/10/2024 3:52 PM, Matt Hoppes wrote: Well this is curious Same issue

Re: Third Party VoIP Over Xfinity

2024-09-10 Thread Matt Hoppes
Have not tried TLS... but yes I reduced the registration frequency to something absurd like 60 seconds and it still would timeout after about 3 minutes. On 9/10/24 4:36 PM, Mark Wiater wrote: What happens when you decrease your registration frequency? Do the phones stay registered? Have you tr

Re: Third Party VoIP Over Xfinity

2024-09-10 Thread Aaron C. de Bruyn via NANOG
Two things that seem to help whenever I'm dealing with bizarre Comcast issueshave her call in and: * Ask for "Security Edge" to be disabled if it's enabled (last time we did this Comcast told us they couldn't permanently disable it unless we paid a lot more per month for service and it would au

Re: Third Party VoIP Over Xfinity

2024-09-10 Thread Michael Thomas
On 9/10/24 1:36 PM, Mark Wiater wrote: What happens when you decrease your registration frequency? Do the phones stay registered? Have you tried TLS for the SIP transport by chance? I manage a few phones on comcast across the country and have no problems. In this day and age TLS isn't the

Re: Third Party VoIP Over Xfinity

2024-09-10 Thread Brandon Jackson
At my previous MSP $dayjob, I ran into a few clients with Xfinity and Spectrum who both would mess with our VoIP solution UNLESS we enabled TLS SIP registration, we already used TCP on a non 5060 port by default to help with UDP timeouts and such. Now the RTP traffic could stay clear UDP, this was

Incorrect Reverse DNS in Verizon Fios NYC core router traceroute

2024-09-10 Thread Neel Chauhan
Hi, I got Fios installed today in my NYC apartment, as I just moved back from Seattle after a 4-month stay in Connecticut. When doing a traceroute, I am noticing an incorrect Reverse DNS entry: [root@twin ~]# traceroute 1.1.1.1 traceroute to 1.1.1.1 (1.1.1.1), 30 hops max, 60 byte packets 1

Re: Third Party VoIP Over Xfinity

2024-09-10 Thread Mike Hammett
We've just moved to tunneling anything VoIP if on Comcast's network. - Mike Hammett Intelligent Computing Solutions Midwest Internet Exchange The Brothers WISP - Original Message - From: "Matt Hoppes" To: nanog@nanog.org Sent: Tuesday, September 10, 2024 2:17:37 PM Sub

Re: Third Party VoIP Over Xfinity

2024-09-10 Thread Michael Thomas
If you're using SRTP and passing keys in the SDP announcement, it would be rather pointless. I don't know how common it is to do the inline keying for SRTP which I understand is how VoLTE works, but seriously I can't imagine why anybody would not use SIPS: Nothing good came come of that. Mike

Re: Third Party VoIP Over Xfinity

2024-09-10 Thread Jim Shankland via NANOG
Same experience here, with Comcast, at least 15 years ago. What was striking was that the tunnel had to be encrypted; plain old GRE tunneling worked for everything else, but GRE-encapsulated VoIP packets never arrived at the other end of the tunnel. We ended up just backhauling all traffic from

Re: Third Party VoIP Over Xfinity

2024-09-10 Thread Norman Jester
I did the same…. No progress at all. Norman Jester > On Sep 10, 2024, at 1:00 PM, Matt Hoppes > wrote: > > So not even the same area then. > > We've now spent 2 hours on the phone and have gotten nowhere with support. > > Hoping someone here at XFinity can chime in and provide some offlin

Re: Incorrect Reverse DNS in Verizon Fios NYC core router traceroute

2024-09-10 Thread Daniel Sterling
Just a bystander here, but what leads you to believe the packets aren't going thru a router in Pittsburgh? -- Dan On Tue, Sep 10, 2024, 5:21 PM Neel Chauhan wrote: > Hi, > > I got Fios installed today in my NYC apartment, as I just moved back > from Seattle after a 4-month stay in Connecticut.

Re: Third Party VoIP Over Xfinity

2024-09-10 Thread chris
None of this should be a surprise to anyone. Remember that Comcast was one of the earliest isps to do DPI at large scale with Sandvine in the early days. Today's Comcast network has "smartedge" which is the latest flavor of deep packet interception and manipulation. Also remember isps are in the da

Re: Re: Survey on barriers for RPKI adoption

2024-09-10 Thread Sofia Silva Berenguer
Thanks so much for your interest and for sharing that article Lancheng! I was aware of this paper and it was part of my initial reading work earlier this year to catch up on where things were at. Thanks so much for bringing this back to my attention! I’ll read it again and make sure we consider

Re: Third Party VoIP Over Xfinity

2024-09-10 Thread Tim Burke
Have you tried placing the CPE in “bridged" mode? It’s been a while since I’ve done anything with Comcast CPE, but I remember their CPE doing SIP ALG when acting as a router. > On Sep 10, 2024, at 2:17 PM, Matt Hoppes > wrote: > > I have an employee who has recently switched to Xfinity cable

Re: Incorrect Reverse DNS in Verizon Fios NYC core router traceroute

2024-09-10 Thread Tim Burke
Can’t go from NYC to Pittsburgh in 1.7ms. NYC<>Pittsburgh is approx 800 miles round trip, speed of light would roughly be 4ms. On Sep 10, 2024, at 5:11 PM, Daniel Sterling wrote: Just a bystander here, but what leads you to believe the packets aren't going thru a router in Pittsburgh? -- Dan

Re: Incorrect Reverse DNS in Verizon Fios NYC core router traceroute

2024-09-10 Thread sronan
Could be the border router facing a connection to Pittsburgh.ShaneOn Sep 10, 2024, at 9:28 PM, Tim Burke wrote: Can’t go from NYC to Pittsburgh in 1.7ms. NYC<>Pittsburgh is approx 800 miles round trip, speed of light would roughly be 4ms.  On Sep 10, 2024, at 5:11 PM, Daniel Sterling wrote

Re: Third Party VoIP Over Xfinity

2024-09-10 Thread Norman Jester via NANOG
Mine will not longer register at all. They registered maybe three times and then just stopped. Norman Jester > On Sep 10, 2024, at 1:43 PM, Matt Hoppes > wrote: > > Have not tried TLS... but yes I reduced the registration frequency to > something absurd like 60 seconds and it still would t