Oh for fuck's sake
-
Oh for fuck's sake.
Looks like traffic to/from Comcast (AS7922) to my ASN falls over somewhere around the handoff between two of the intermediate AS's.Somewhere around Internet2 and/or NoX, I think.
brb, explaining to an internal outage chat group that, in fact, this is not a thing I can fix.
-
Oh for fuck's sake.
Looks like traffic to/from Comcast (AS7922) to my ASN falls over somewhere around the handoff between two of the intermediate AS's.Somewhere around Internet2 and/or NoX, I think.
brb, explaining to an internal outage chat group that, in fact, this is not a thing I can fix.
@rmd1023 oh no! Good luck on the explaining... hopefully the fix will be quick...
-
@rmd1023 oh no! Good luck on the explaining... hopefully the fix will be quick...
@stonebear2
It's definitely not something I can fix on this side. I've got an upstream person poking comcast about it. Looks like our traffic is going out fine, but inbound traffic dies in comcast's network.I've got a remote user who has them as an ISP and apparently in that part of comcast's network, traffic to me gets routed via Level3/Lumen rather than over the failing path.
A traceroute to the user's pubic IP shows responses up to the point there's a handoff to comcast, then a bunch of "* * *" and then we start getting successful traceroute responses. I'm guessing that's where the comcast best-path to me changes to Lumen. But that all makes me think everything outbound is working and comcast is busted for traffic in to me, so I can't even fix this by pushing AS7922 to a different path out.
-
@stonebear2
It's definitely not something I can fix on this side. I've got an upstream person poking comcast about it. Looks like our traffic is going out fine, but inbound traffic dies in comcast's network.I've got a remote user who has them as an ISP and apparently in that part of comcast's network, traffic to me gets routed via Level3/Lumen rather than over the failing path.
A traceroute to the user's pubic IP shows responses up to the point there's a handoff to comcast, then a bunch of "* * *" and then we start getting successful traceroute responses. I'm guessing that's where the comcast best-path to me changes to Lumen. But that all makes me think everything outbound is working and comcast is busted for traffic in to me, so I can't even fix this by pushing AS7922 to a different path out.
@rmd1023 @stonebear2 If Comcast is involved, I would not expect the fix to be particularly quick.
NOT THAT I'M CYNICAL ABOUT COMCAST OR ANYTHING
-
@rmd1023 @stonebear2 If Comcast is involved, I would not expect the fix to be particularly quick.
NOT THAT I'M CYNICAL ABOUT COMCAST OR ANYTHING
@annathepiper Same, but it's on the serious internet engineering side, not the consumer side, so slightly better chance of a quicker fix.
Ah! I thought they'd fixed it but the ISP between us and them has dropped their link to Comcast until they get their stuff fixed. So things will route around that and work.
Sorry to all of my users who were using it as a reason to not work. "Had to go to the bar with wifi that's showing soccer games!"
-
@rmd1023 @stonebear2 If Comcast is involved, I would not expect the fix to be particularly quick.
NOT THAT I'M CYNICAL ABOUT COMCAST OR ANYTHING
-
Oh for fuck's sake.
Looks like traffic to/from Comcast (AS7922) to my ASN falls over somewhere around the handoff between two of the intermediate AS's.Somewhere around Internet2 and/or NoX, I think.
brb, explaining to an internal outage chat group that, in fact, this is not a thing I can fix.
Okay, the ISP between here and there has put a temporary fix in place so things can route around the problem til Comcast gets their side fixed.
-
R relay@relay.infosec.exchange shared this topic
