It has now been a week since I’ve been active and here’s some early impressions. In general it’s been a successful week. In addition to the dedicated file transfer test computer, I’ve now connected all of my office computers to the fiber network. I have yet to suffer any outage and the speed of the network is very good.

So far I’ve received 31 gb in 67 m frames from the Internet and sent 28 gb in 42 m frames into the Internet, all with 0 errors and 0 frame drops. Uptime has been 100% over the 7 days and 2 hours as I am writing.

As an example of the performance gains, I ran the Okla speedtest on both my old Spectrum 200 mb (300?) network and the new YS fiber 300 mb network. Here’s the clickable download results:

Shown are the results of three runs. The first (bottom) was on 1/3/23, via Spectrum. It shows a ping response time of 22 msec, download of 105.7 mb, upload of 11.8 mb. The latest test was on 1/10/23, via the YS fiber. It shows a ping of 5 msec, download of 802.3 mb, upload of 709.9 mb. The middle test, run on 1/9/23, was an early YS fiber run.

You may have noticed the “in general” in the second sentence above. My reservations so far center on configuring the ONT. I’ll cover this topic in following posts and pages, but for now I’ll just say that I can’t mess with the ONT as much as I’d like to. The network weenies have restricted what you the end user can configure. One might reasonably argue that end users shouldn’t be messing with things that can potentially break their connection (leading to those weenies having to fix it).

Those restrictions generally won’t affect the typical home user – in fact most of us can make use of the box without ever doing a thing to it. But if you want to, for example, host your own publicly-accessible server you’ll have some interesting decisions to make. More details on the various configuration details are available on the configuration pages.