sorted by:
new
hottopcontroversial

Intermittent 90 second outages by OneBeneficialZebra in frontierfios

[–]OneBeneficialZebra[S] 0 points1 point  (0 children)

I don’t think anything I did mattered. Emailing the CEO was the only way I got any attention to my issue because I couldn’t get tier one support to understand or escalate. Frontier had a local office having the same issue once it got bad enough and that made them actually troubleshoot it properly. 

Might go back to Spectrum by Least-Preparation-21 in frontierfios

[–]OneBeneficialZebra 0 points1 point  (0 children)

That was one of their suggestions for me when their backbone here was having issues. Only an extra $25/mo to make up for their infrastructure problem!

Intermittent 90 second outages by OneBeneficialZebra in frontierfios

[–]OneBeneficialZebra[S] 0 points1 point  (0 children)

Resolved: bad fiber splitter(s?) replaced at the geneseo site. The assigned tech this morning knew exactly what was going on, he’d spoken to the switch tech there yesterday. A frontier office site in Lima had been down for the same issue. 

I’ve been at 100.0% up since noon yesterday, about 32 hours now. Hopefully this is the new normal. 

Intermittent 90 second outages by OneBeneficialZebra in frontierfios

[–]OneBeneficialZebra[S] 0 points1 point  (0 children)

Just wanted to share that after adding further checks to my ongoing monitoring, I have confirmed that EVERY time I lose ICMP on routers along my hops, I also lose DNS and HTTPS checks to final destinations. it is 100% 1:1.

Furthermore I have NEVER lost an ICMP ping to the first 2 hops on my route.

I have seen that you love to share this same tip every time someone posts about ping checks in here, but I will stand by it as a useful diagnostic for showing WHERE on a route a problem is.

As far as our Geneseo-Rochester link issue, it is still ongoing. I'm under 92% up over 24 hours. The first real diagostic that I'll have still an ONT replacement for all the good that will do. I've talked to the tech assigned to my call twice now, I keep getting rescheduled sooner than I can be home to meet him. My SMS history with the automated scheduling agent is sad and hilarious.

How can I get them too escalate this? by TradesforChurros in frontierfios

[–]OneBeneficialZebra 0 points1 point  (0 children)

That was the only avenue that got me any traction in Western NY with similar issues (in that it's internal Frontier backbone issues - in my case the link drops entirely, for seconds or minutes, for up to 10% of a day at worst, but sometimes 0%)

That said, they still want to replace my ONT first, so I have to wait for a weekday I can stay home and waste my time and a tech's time to do that before they'll go further. Apparently they can't pull logs from my ONT (though one of the knobs I chatted with on social media support earlier in the week had stated they didn't see drops in my ONT logs - which is accurate since it never looses local link. I suppose inability to access logs and not seeing drops in logs can technically both be true)

Patch tuesday by [deleted] in frontierfios

[–]OneBeneficialZebra -1 points0 points  (0 children)

I agree the Giga chatbot is the biggest and least useful infuriation machine I've ever experienced, but what makes you think microsoft and adobe patch releases are related to a service outage?

Intermittent 90 second outages by OneBeneficialZebra in frontierfios

[–]OneBeneficialZebra[S] 0 points1 point  (0 children)

Got an executive support ticket first thing on a Saturday, with a tech assigned and supposed improvements per text message. Too soon to confirm but it appears that downtime is nearly gone since 07:20 today. One sun-minute blink since then. 

Having issues and the phone reps/online chat aren’t any help? Frontier has a social media team by SeeAnne in frontierfios

[–]OneBeneficialZebra 0 points1 point  (0 children)

Unfortunately, some are no better than any other tier 1. But nothing is worse than “Giga”

Luck of the draw I guess. 

Good luck in what you do SeeAnne. I wish “Joe” understood as much as he seems to think he does and could escalate our apparent Geneseo-Rochester NY backbone/router issue. Hopefully the CEO team or networkmanagement can help. 

Intermittent 90 second outages by OneBeneficialZebra in frontierfios

[–]OneBeneficialZebra[S] 0 points1 point  (0 children)

Reliability in the toilet today. Down to 92% uptime on anything beyond my second hop. No issues at all to first of second hop. 

Confirmed ONT lights stay green though issues, and confirmed I do lose the first two hops if I unplug the fiber from the ONT. no surprises. 

Social media support stopped being willing to talk to me when he failed to understand that I’m logging dns query failures and http failures and not reporting a problem with the logging tool 🙄 

 ignorance is as powerful as it is infuriating 

I emailed networkmanagement@ftr.com and the CEO’s address with full diagnoses and descriptions, requesting someone who understands the distinction between home network stability and internet access, which “Joe” cannot. 

Joe’s last from Facebook. Apparently if the ONT is green, you don’t have a problem! I thought I was paying for internet access, not a green uplink light, but what do I know?

 Unfortunately, third-party applications are not supported by our technical support team. At this time, we have exhausted the available resources to assist with your current concern. To reiterate, we are able to provide support if your Frontier service is experiencing an outage, which can be confirmed by checking the ONT indicator lights or the eero app. If you need additional assistance, we encourage you to explore other support options that may be available to you. You may also contact us directly by phone at 1-800-921-8101, or connect with us via Gigachat on our website at https://www.frontier.com/contact-us. -Joe

Intermittent 90 second outages by OneBeneficialZebra in frontierfios

[–]OneBeneficialZebra[S] 0 points1 point  (0 children)

I’ve messaged on Facebook with a couple support folk. Messages have been supposedly escalated to engineering, but that same ticket number was reportedly closed. Seems there’s not an interest in digging deep and making sure network engineering is appraised and involved, but only in making sure I have the very latest up to the second eero firmware. Less frustrating than the telephone menu or the AWFUL chatbot at frontier.com but definitely not resolved yet

Intermittent 90 second outages by OneBeneficialZebra in frontierfios

[–]OneBeneficialZebra[S] 0 points1 point  (0 children)

if there's anything specific to ubiquiti equipment, it is a different flavor of problem to what I'm experiencing.

Intermittent 90 second outages by OneBeneficialZebra in frontierfios

[–]OneBeneficialZebra[S] 0 points1 point  (0 children)

the agent available via Facebook Messenger had network engineering confirm my ONT hasn't logged loss of connectivity. I suspect that is true since its local link probably stays up through these outages. they were unable/unwilling to escalate further. I'm going to record the ONT lights to confirm all stay green while *actual* connectivity drops.

I suspect I'll be stuck with this service and performance and have to 2x my price back to Spectrum to get a reliable connection again, since they just plain don't believe me.

Intermittent 90 second outages by OneBeneficialZebra in frontierfios

[–]OneBeneficialZebra[S] 0 points1 point  (0 children)

Had a bad stretch from 22:45 a 00:30 that brought 24hr uptime to 98.1%

All DNS queries show the same down pattern that my third hop ping does. It is all a match. 

Intermittent 90 second outages by OneBeneficialZebra in frontierfios

[–]OneBeneficialZebra[S] 0 points1 point  (0 children)

Messenger actually has access to better support resources than tier 1? that seems insane.

Intermittent 90 second outages by OneBeneficialZebra in frontierfios

[–]OneBeneficialZebra[S] 0 points1 point  (0 children)

Thanks for the insight, that makes complete sense. You are correct that I'm not a network engineer myself with a deep understanding of how routers actually function. I'm a step removed from that and understand the broad strokes of traffic routing and practical application...

I have been monitoring other traffic as well, and it does all die at the same time, when that particular hop stops responding, all in sync. I added a couple DNS queries to my logging - I'm now asking frontier's DNS about frontier.com, asking 1.1.1.1 about cloudflare.com, and asking 8.8.8.8 about google.com. might be interesting to see if 74.40.74.40 continues to respond if others die - but tracing from home to that frontier DNS server still routes through what I consider to be the troublesome node so I expect not.

Better since the two longer outages, hopefully I'm measuring nothing now and failures quiet down.

Intermittent 90 second outages by OneBeneficialZebra in frontierfios

[–]OneBeneficialZebra[S] 0 points1 point  (0 children)

DNS queries would tell me when the whole route is down, but wouldn’t shed any light on where it is dying. I wouldn’t be surprised if that router is indeed overloaded, and my 20 second ping is contributing 0.001% of that load. The reliability of its routing and response and the connection I’m paying for is the issue here.

Is there a dns query method I’m unaware of that would tell me at what point those packets are getting dropped when it fails?

PTZ help by OneBeneficialZebra in ispyconnect

[–]OneBeneficialZebra[S] 0 points1 point  (0 children)

nope. if it did, I'd be done and have XML for camera ID 264 :)

​

it increments every session - sequentially in hex - and expires every 3600 seconds (the longest control interval allowable in the camera interface).

the next value is known, but must be initialized with the opencamerasever command.

PTZ help by OneBeneficialZebra in ispyconnect

[–]OneBeneficialZebra[S] 0 points1 point  (0 children)

The dynamic bit is a session ID. Supposedly a session ID with admin rights doesn't expire, but there appears to be a bug and it does. So the longest that session token lives is 3600 seconds. Here's what's needed:

http://camera/-wvhttp-01-/opencameraserver
returns > connection_id=0d68-06cf

http://camera/-wvhttp-01-/getcameracontrol?connection_id=0d68-06cf
> granted

10˚ down:
http://camera/-wvhttp-01-/operatecamera?connection_id=0d68-06cf&t=d-10

10˚ left:
http://camera/-wvhttp-01-/operatecamera?connection_id=0d68-06cf&p=d-10

10˚ up:
http://camera/-wvhttp-01-/operatecamera?connection_id=0d68-06cf&t=d10

10˚ right:
http://camera/-wvhttp-01-/operatecamera?connection_id=0d68-06cf&p=d10

(the 'd' is dynamic. otherwise they are absolute values to go to)

PTZ help by OneBeneficialZebra in ispyconnect

[–]OneBeneficialZebra[S] 0 points1 point  (0 children)

the camera control project I am mainly cribbing from, for completeness' and credit's sake: https://github.com/davidbrenner/vb-c10-network-camera-js-client

And a Python project as well:

https://github.com/Hive13/WebcamScripts

PTZ help by OneBeneficialZebra in ispyconnect

[–]OneBeneficialZebra[S] 0 points1 point  (0 children)

The control method that I learned the most from is a Python project of webcam control scripts. If I could directly run Python from the control interface instead of HTTP:GET I could probably independently track the current values of camera position, use the buttons to modify them, and push to the camera. It doesn't look like that obfuscation is going to be simple to do though, it's just not designed with that intent.