Skip to main content

Project: Optimizing Wi-Fi For a Residence.


 A 5-year old house is not quite optimized for ideal wireless setup. Let's help them.

*Not an accurate representation to maintain security.

Issue: The Wi-Fi router from Verizon is in the back of the house. Around 70% of the house can receive the signal, but not the office in the very front.

Equipment:

Netgear router (not extender)
Netgear extender.
Home router from Verizon
Cable boxes
Other things that use Wi-Fi.







🌟 There are ports for coax cables in every non bathroom, closet, pantry, or kitchen room. There is also not one in the designated office. The family is not interested in changing the office to one of the rooms.

🌟 Most of the coax cables are already in use by cable boxes. The one free one is being used by the Home Router from Verizon. That is placed at the back of the house, and the office is in the front.


🌟 There is an extender in place, and it is a little patchy. It fits in discreetly with the decor and has two antennas.




🌟 The Verizon box is in a bedroom, and it's a bit distracting when someone is trying to sleep. There is also other equipment needed to be directly connected via an Ethernet cable.

Possible solutions:

🤔 Make the Netgear router into an extender and place it within the kitchen for better coverage.
❌ Microwave interference.
❌ Not discreet.
❌ It would be pointing toward a zone with no devices.

🤔Connect the Verizon box to the splitter that works with the main cable box in the living room.
❌ Not easily accessible - There's heavy furniture - For troubleshooting equipment.
❌ Other equipment may not be able to be attached.
✅ Could possibly eschew extender.

🤔 Make Netgear router into an extender and connect via splitter in main cable box.
✅ Verizon equipment and others left as is, where is easily accessible.
❌ Still distracting.
✅ Extender wouldn't need to be restarted often.


🙋🏿‍♀️ Implemented Solution:

Netgear router made into extender by entering settings and putting it into repeater mode. Placed in awkward spot connected to cable splitter to main cable box.

📝Notes: 

Could also put a power strip behind the television and move the Verizon equipment there, but I'd prefer decent air flow. That may make it too crowded with the additional equipment that needs to be connected via Ethernet.


How to do this in your home:

  •  Consider how big your home is and where interference can happen - Microwaves, certain materials in your walls, and of course, distance.
  • Remember that you can use a laptop docking station with an ethernet port. Use a Cat5 Cable to connect from that port on the dock to one of the LAN ports on your router, if you must have a steady connection.
  •  Make sure your Wi-Fi channels do not overlap with others in your neighborhood. Most people are probably using channels 1, 6, and 11, as they do not overlap, but if 4 people are using channel 6, there's going to be some interference.

Help others fix their 'fi -

Comments

Popular posts from this blog

Connecting IoT Devices to a Registration Server (Packet Tracer, Cisco)

In Packet Tracer, a demo software made by Cisco Systems. It certainly has changed a lot since 2016. It's almost an Olympic feat to even get started with it now, but it does look snazzy. This is for the new CCNA, that integrates, among other things, IoT and Automation, which I've worked on here before. Instructions here . I don't know if this is an aspect of "Let's make sure people are paying attention and not simply following blindly", or an oversight - The instructions indicate a Meraki Server, when a regular one is the working option here. I have to enable the IoT service on this server. Also, we assign the server an IPv4 address from a DHCP pool instead of giving it a static one. For something that handles our IoT business, perhaps that's safer; Getting a new IPv4 address every week or so is a minimal step against an intruder, but it is a step. There are no devices associated with this new server; In an earlier lab (not shown), I attached them to 'H

Securing Terraform and You Part 1 -- rego, Tfsec, and Terrascan

9/20: The open source version of Terraform is now  OpenTofu     Sometimes, I write articles even when things don't work. It's about showing a learning process.  Using IaC means consistency, and one thing you don't want to do is have 5 open S3 buckets on AWS that anyone on the internet can reach.  That's where tools such as Terrascan and Tfsec come in, where we can make our own policies and rules to be checked against our code before we init.  As this was contract work, I can't show you the exact code used, but I can tell you that this blog post by Cesar Rodriguez of Cloud Security Musings was quite helpful, as well as this one by Chris Ayers . The issue is using Rego; I found a cool VS Code Extension; Terrascan Rego Editor , as well as several courses on Styra Academy; Policy Authoring and Policy Essentials . The big issue was figuring out how to tell Terrascan to follow a certain policy; I made it, put it in a directory, and ran the program while in that directory

Create a Simple Network (Packet Tracer) + A Walkthrough

Again; I've done this, but now there's so many new things, I'm doing it again. The truly new portions were...everything on the right side of this diagram; The cloud needed a coax connector and a copper Ethernet connector. It's all easy to install, turn off the cloud (Weird), install the modules. Getting the Cable section of Connections was an unusual struggle - The other drop down menu had nothing within. It required going into the Ethernet options and setting the Provider Network to 'cable', which is the next step AFTER the drop-downs. The rest was typical DHCP and DNS setups, mainly on the Cisco server down there. The post is rather short - How about adding a video to it? Find out what A Record means - This site says 'Maps a name to an IP address', which is DNS. So it's another name for DNS? You can change them (presumably in a local context) to associate an IP address to another name.