Utilizing current phone lines as Ethernet connections is feasible.
Utilizing current phone lines as Ethernet connections is feasible.
The RJ11 phone lines were connected with Cat 5e Ethernet cables and linked together in a daisy chain. It’s feasible to convert them to RJ45 connectors, route the cables through switches, and provide internet access throughout your home. Potential challenges include bandwidth distribution (1000Mbps split among all devices) and latency issues like ping. Image 1 displays two Ethernet cables connected in series, with the pink one acting as a junction point. Image 2 illustrates the current setup of the RJ11 keystones. My plan involves upgrading to a proper switch or router to handle the full bandwidth efficiently. Would using a wired network without switches be a more effective solution?
If direct routing isn't feasible, employing several switches can consolidate your wall-jacks into a unified network. However, later connections will need to share bandwidth with earlier ones. This setup might lead to congestion if Gigabit speeds become saturated on the LAN, affecting users downstream. Unlike older analog RJ-11 gear, you can't stack Ethernet ports in a line. At the data plane, each wall jack requires its own dedicated switch port.
I could try running specific cables to a central point if that doesn’t work. If I follow what I suggested, each run between keystones would act like a patch cable and switches would group them together. Is that right? We have eight additional Ethernet ports, all Cat 5e with dedicated connections to the main switch, but I’d like to extend Ethernet to other areas (swapping the phone system would be the simplest option). I’m not concerned the devices will overload the 1000Mbps connection. Could Ethernet Cable Couplers help link “patch cables” without needing an Ethernet keystone? Would I need to worry about reaching saturation if we get gigabit internet? Edited March 21, 2021 – FireEagle244 noted I’m aiming for gigabit connectivity.
Imagine a central trunk with branches extending outward. Each branch needs a connection switch, but fewer switches mean better performance. It works for a small number of clients, but scaling becomes tough when many devices are linked in sequence. This setup simply extends the Ethernet cable length—acceptable if you don’t need a keystone port. Remember, keep the total length under 100 meters. Cat5e supports Gigabit speeds continuously. The challenge arises when bandwidth is shared among users; unless you’re using a local server, you’ll likely hit limitations set by your ISP. Unless you have Gigabit internet and fully utilize it.
There should likely be 2-3 switches connected in series. The cables won’t exceed 100 meters. I have some nearby servers each with their own dedicated cable, and the computers moving to them also use theirs. My goal is to add more Ethernet ports to other spots in my house where the existing phone lines are found.
Two or three is fine. Five or six users online seems common now. This might lead to delays based on habits. That should be okay. The setup won’t add much delay, and the main concern would be bandwidth competition. Unless those ports get busy, it shouldn’t matter. For optimal performance, a central switch in a network closet with centralized management is ideal.
What is the purpose here? Avoid running Ethernet directly from each keystone to the central switch. Prevent creating long daisy chains. Adding more failure points would be risky. At connection points, keep the Ethernet straight to the switch. Ensure conduits have enough room for the cables. If space allows, use two Ethernet cables per keystone or wall plate for future growth.