TP-Link Omada Managed Switch Guide

Estimated reading time: 4 minutes

From a budget minded home lab beginner

Introduction

A TP-link ES208G from amazon just arrived in the mail and I want to understand it before I use it in my small home server. It is an 8 port managed network switch. I want to take you through the learning I’m doing in this project. From what I’m looking at, it is something a normal person at home like me can figure out – that is, unless I’ve been lying to myself about being normal. Side note, this is not a full enterprise grade switch giving you every setting under the sun. Its function is to provide more settings than your typical “Plug and play” “Easy switch.” For context, I wanted a real server feel. I want to experience some higher level server management tasks along the way and this particular switch was $28, only $3 dollars more than most new reputable easy switches online.

Getting started

I began with the question “how do I get into the switch to make adjustments?” I’m sitting at Starbucks right now with my server running at home connected to the switch in port 2, and the output of the router feeding port 1. I learned right away that remotely accessing your switch is a no-no unless you have configured your VPN (I’m using Tailscale) a certain way to where it allows you access to your home IP. More on that later. I expected it to be like routers I’ve worked on before where the default IP is consistent across routers as well. Easily enough, that’s all I needed though was to log in to my router, click on my devices connected, in my case there were 10 unassigned ones. The switch was identifiable as device “ES208G” with an IP address of 192.168.4.101

Type that IP into your web browser and you will find your device setup page. Create username and password first.

This is where an easy switch and managed switch differ from one another.

1. First thing I want to do is give the switch a permanent IP address to keep the login process consistent.
   • In the System Info dropdown, select IP Settings. You want to disable DHCP settings to ensure a static IP.
   • Choose and enter an IP that is freed up. I chose 192.168.4.101 was free because that’s what it originally was and I don’t need any extra help confusing anything.
   • Subnet mask should typically be 255.255.255.0
   • Gateway is a little more tricky, but find your routers IP address and enter that into Default Gateway. Click Apply. Make sure window is wide enough, my apply button was hiding off to the right side.

• Rename the switch. Let’s be honest, Tina has a much better ring than Camry. This will be in the initial first few setup questions, for me it was.
  • I named mine OmadaSwitch1
  • With potentially many network devices, this will make the switch easier to recognize.
  • Select Apply

• Rename Ports.
  • With this switch not being a full enterprise grade piece, we actually cannot rename the ports. However, if you’re following along with a different model/brand, this is one thing to do a little clicking around for. If I were able to, I name ports something like below:
    • Port 1 – Router Uplink
    • Port 2 – HP ProDesk Server
    • Port 3 – Security Camera/Access Point/Desktop/etc.
      • For my current build, I have: Modem –> Router –> Switch –> Server with the “–>” symbol indicating an ethernet cable
      • in my case I could create a txt file for instance with this information and potentially give to my local AI model to retrieve one day in case I forget.
• Leave speed and duplex on Auto
  • Unless we are trying to solve a specific issue here, my sources lead me to leave Auto Negotiation enabled, Speed set to Auto, as well as Duplex.
• Verify the link
  • In the Switching>Port Settings screen, you should see your configurations such as Speed + 1000M or 1 Gbps.
  • You should also see full duplex the ports you have in use’s state equaling “Enabled.”
  • In the Monitoring>Traffic Summary menu, you should see a number of Tx bytes and Rx bytes indicating that data is indeed being Transmitted and Received, respectively.

• Final steps
  • Ensure you have applied all your settings first, then close your browser instance. Re-open and verify your settings remain applied.

This is a good place to leave off for now. While this guide covered the basic configuration needed to bring my managed switch online, there’s still a lot left to explore. Features such as cable diagnostics, traffic monitoring, MAC address tables, VLANs, Spanning Tree Protocol (STP), QoS, link aggregation, and security settings each deserve their own deep dive. Rather than enabling features just because they’re available, I’d rather understand what problem each one solves first. As my homelab grows, I’ll revisit these tools one by one and document what I learn along the way.

Next Article: Why I no longer use the TP Link ES208G for my home lab main switch.