FiOS Router Issues and Non-Technical Landlords
-
@thecreativeone91 said:
@JaredBusch said:
Now stop being stupid.
I don't think anyone is really saying @thanksajdotcom is stupid. Or at least that's not my intent. Sorry if it comes across that way. If we thought that we wouldn't even try. The point is to be more careful about the thinks you post online. There's a lot of people on here and spiceworks. It's not unlikely that someone you work with or would otherwise be a contact would be on here to see these things. Weather it's illegal or not it's going to be perceived as questionable. with will reflect on their opinion & judgment of your character - even if it shouldn't, it does.
Just Posting the following:
Does anyone know off-hand if you can schedule tasks in a FiOS router? I believe you can but I won't know for sure until I get another look at it.
And maybe stating that it needed to be a reboot would suffice and avoid the possibility of issues and maintain professionalism.
Noted.
-
Cron job has been setup. I am logging the results. I have two cron jobs setup to run at 5AM on one server, and 5:01AM on another. In theory, the second one should always fail, but if it doesn't, or that one server is having an issue, I'm covered. It's during a time no one is ever consciously online.
-
@scottalanmiller said:
@PSX_Defector said:
@IRJ said:
Back to the thread, I have noticed that AT&T definitely throttles my connection. I get a better speed when using VPN. AT&T slows certain things down like Netflix, Hulu, Youtube, and other high traffic sources. Videos play 10 times better when I use anonymous VPN even though my connection is technically slower.
It's not throttled, it's a peering issue.
Net neutrality rules do not fix this.
If they get better speeds through a different peer, isn't it a routing issue?
There's only one route to Netflix though. And considering they peer with Level3, which tons of traffic goes through as well, it will cause a bottleneck to them.
Netflix et. al. are doing the best they can to get things over to their CDNs, which will ease congestion on that link. They also are working with ISPs on getting a peer box inside of the network to send that traffic towards instead. These things have been done in the ISP scape since the earliest days of the internet. My old ISP had upstream links with InterNAP, which would pump out super clean traffic across pipes to various game servers. When your ping is super low, as in sub 10ms to the game server, it was great.
-
That doesn't explain how a VPN fixes the performance issues, though. That suggests that a VPN could not fix it. If a VPN fixes it it sounds like either there is alternate route or it is really being throttled.
-
@scottalanmiller - if still hosting a WP site on a home network, that could be eating up the additional bandwidth, causing Verizon to throttle the connection. IMHO, the landlord isn't incorrect in saying that it was fine until the extra traffic started being passed on his FiOS connection. I would be a little upset myself.
-
@Bill-Kindle said:
@scottalanmiller - if still hosting a WP site on a home network, that could be eating up the additional bandwidth, causing Verizon to throttle the connection. IMHO, the landlord isn't incorrect in saying that it was fine until the extra traffic started being passed on his FiOS connection. I would be a little upset myself.
WP traffic is just HTTP, and it's not like I'm getting thousands of hits a day. Very minimal impact from any website.
-
@scottalanmiller said:
That doesn't explain how a VPN fixes the performance issues, though. That suggests that a VPN could not fix it. If a VPN fixes it it sounds like either there is alternate route or it is really being throttled.
Peers are not equal from place to place. My OC-192 might be saturated but someone else's OC-3 is pretty wide open. Netflix would have a giant pipe because they would allow in everything and load balanced to other pipes. A very normal thing.
It is routing, and it is not routing. Its a complex issue that net neutrality doesn't necessarily fix. It's just inherent in the nature of the backbone traffic management.
-
@PSX_Defector said:
@scottalanmiller said:
That doesn't explain how a VPN fixes the performance issues, though. That suggests that a VPN could not fix it. If a VPN fixes it it sounds like either there is alternate route or it is really being throttled.
Peers are not equal from place to place. My OC-192 might be saturated but someone else's OC-3 is pretty wide open. Netflix would have a giant pipe because they would allow in everything and load balanced to other pipes. A very normal thing.
It is routing, and it is not routing. Its a complex issue that net neutrality doesn't necessarily fix. It's just inherent in the nature of the backbone traffic management.
Net neutrality doesn't fix it at that level or that point along the chain.. but it does fix it at the likes of comcast's network, or any other ISP that's throttling it.
-
@Dashrender said:
@PSX_Defector said:
@scottalanmiller said:
That doesn't explain how a VPN fixes the performance issues, though. That suggests that a VPN could not fix it. If a VPN fixes it it sounds like either there is alternate route or it is really being throttled.
Peers are not equal from place to place. My OC-192 might be saturated but someone else's OC-3 is pretty wide open. Netflix would have a giant pipe because they would allow in everything and load balanced to other pipes. A very normal thing.
It is routing, and it is not routing. Its a complex issue that net neutrality doesn't necessarily fix. It's just inherent in the nature of the backbone traffic management.
Net neutrality doesn't fix it at that level or that point along the chain.. but it does fix it at the likes of comcast's network, or any other ISP that's throttling it.
Which a lot of the Netflix hubbub was not actually about. Comcast actually was putting traffic shaping into their pipes. Like 15 years ago. But people have rioted and screamed about that for years. Deep packet inspection is a pipe dream at the moment for ISPs bigger than your typical rural WISP. The amount of hardware and software required for it would be immense. And just doing per route shenanigans doesn't help when you have a CDN that can change the destinations on a whim.
It's a super complicated issue.
-
@PSX_Defector said:
Which a lot of the Netflix hubbub was not actually about. Comcast actually was putting traffic shaping into their pipes. Like 15 years ago. But people have rioted and screamed about that for years. Deep packet inspection is a pipe dream at the moment for ISPs bigger than your typical rural WISP. The amount of hardware and software required for it would be immense. And just doing per route shenanigans doesn't help when you have a CDN that can change the destinations on a whim.
It's a super complicated issue.
So what was the hubbub about then? I understand the peering point discussion and agree that (CDNs not withstanding) that who ever Netflix's original ISP was, that provider was probably violating their peering agreement with the rest. But that isn't Netflix's problem, that's their ISP's problem. If the ISP now needs to pay off all of it's peers because its peering usage was unfair, fine.. if they needed to pass that fee along to Netflix, again probably fine.
I'm sure I'm overly simplifying it and would love to know more about it.
