July 01, 2026 | By Admin User | 10 min read

Our first PPPOE Set Up in Uganda: Luxenetworks

Views: 97

Our first PPPOE Set Up in Uganda: Luxenetworks

How We Set Up PPPoE for a Client: A Luxenetworks Walkthrough

At Luxenetworks, we get a lot of calls that start the same way: "My internet was working fine, then the ISP switched us to a new connection type, and now nothing works." More often than not, the culprit is PPPoE (Point-to-Point Protocol over Ethernet). Last week, we handled exactly this kind of job at a 50-unit apartment complex whose ISP had just migrated the property onto a PPPoE-based connection. Here's how we approached it, the equipment we used, and the steps we took, in case it helps you understand what a proper PPPoE setup actually involves at scale.

First, What Is PPPoE and Why Does It Matter?

PPPoE is a networking protocol that many ISPs, especially DSL and fibre providers, use to authenticate and manage customer connections. Instead of your router just grabbing an IP address automatically (like with DHCP), PPPoE requires your router to "dial in" using a username and password supplied by the ISP, much like old-school dial-up internet, just running over Ethernet instead of a phone line.

The upside for ISPs is better control over billing, session management, and security. The downside for customers is that if it's not configured correctly, the connection simply won't come up: no internet, no clear error message, just a blinking light and a frustrated household.

The Property and the Situation

This job was for a 50-unit apartment complex. The building had just been switched over to a new connection by their ISP, and the property manager reached out after residents across multiple units started reporting the same issue: Wi-Fi showing as connected, but no actual internet access. With that many units relying on one shared connection point, even a small misconfiguration at the network core cascades into a building-wide outage, so we prioritized the visit.

They called us with three symptoms:

  • The core router showed a physical link to the ISP's line but no internet access
  • The ISP-provided PPPoE username and password weren't being accepted
  • Wi-Fi devices connecting through the access points on different floors could see the local network but had no external connectivity

This is a textbook PPPoE misconfiguration, so we scheduled a visit.

The Equipment We Used

For a property of this size, we relied on a compact but capable equipment stack:

  • MikroTik RB951: our core router, chosen for its RouterOS flexibility, reliable PPPoE handling, and the ability to manage NAT and firewall rules for the whole building from a single point
  • Managed switch: sitting between the RB951 and the rest of the building, distributing wired connections out to each access point
  • Tenda F6 wireless routers (x2): repurposed as dedicated Wi-Fi access points to extend coverage across the property, rather than acting as independent routers
  • ISP-provided line: the incoming connection requiring PPPoE authentication
  • Cat5e/Cat6 patch cabling: connecting the ISP termination point, RB951, switch, and each Tenda F6 in the chain

This combination gave us a single, centrally managed PPPoE session at the RB951, with the switch and Tenda F6s doing what they do best: distributing that connection cleanly across a larger property without introducing conflicting routers or duplicate DHCP servers.

Step 1: Confirming the Physical Layer First

Before touching any settings, we always rule out physical and cabling issues. With this setup, the chain ran: ISP line in, then the RB951 WAN port, then the managed switch, then the Tenda F6 access points on different floors, then resident devices. We checked that:

  • The ISP's incoming line was active and delivering a stable signal
  • The cable running from the ISP termination point to the RB951's WAN port was properly seated and undamaged
  • The RB951's WAN port link light was active
  • The cable from the RB951's LAN port into the managed switch was solid, and the switch itself was passing traffic (link lights active on every relevant port)
  • The cabling running from the switch out to each Tenda F6 access point was intact

It's tempting to jump straight into software configuration, but a good chunk of "PPPoE won't connect" calls turn out to be a loose cable, a faulty switch port, or a bad patch lead, and in a multi-floor property, tracing that down first saves a lot of guesswork later. In this case, the physical layer was clean end to end, so we moved on.

Step 2: Gathering the Correct PPPoE Credentials

This is where most self-installs go wrong. PPPoE credentials are not the same as your Wi-Fi password, and they're often formatted in ways that trip people up: extra characters, case sensitivity, or a required domain suffix (like username@isp.net instead of just username).

We contacted the ISP's provisioning line to confirm the exact credentials issued to the account, and verified there was no realm/domain suffix required for this particular provider. Small detail, but it's a common point of failure.

Step 3: Configuring PPPoE on the RB951

An important decision in a multi-device, multi-floor setup like this is choosing exactly one device to handle the PPPoE dial-up. You never want two devices both trying to authenticate the same session, especially on a property serving 50 units. We chose the RB951 as the PPPoE client, since it's the device sitting closest to the ISP line and has the routing horsepower to handle NAT and firewall duties for the entire building.

With confirmed credentials in hand, we logged into the RB951 via WinBox and:

  1. Created a new PPPoE client interface bound to the WAN-facing Ethernet port (ether1), rather than leaving it on a plain DHCP client
  2. Entered the username and password exactly as provided by the ISP, double-checking for trailing spaces, a surprisingly common issue when credentials are copy-pasted from an email
  3. Set the MTU to 1492, the standard value for PPPoE, since it accounts for the protocol's overhead compared to a normal 1500-byte Ethernet frame
  4. Set "Add Default Route" and "Use Peer DNS" so the RB951 would automatically pick up routing and DNS information from the ISP once connected
  5. Configured NAT masquerading on the PPPoE interface so devices on the LAN side could share the single public IP
  6. Enabled the connection and confirmed the PPPoE interface came up with a "running" status and a valid public IP address

Step 4: Setting the Switch and Tenda F6s to Their Proper Roles

With the RB951 handling PPPoE and routing, everything downstream just needed to pass traffic correctly across the building:

  • The managed switch was configured to carry traffic cleanly from the RB951's LAN port out to every Tenda F6 access point and any wired connections on the property
  • Each Tenda F6 was set to Access Point mode rather than its default router mode, with DHCP disabled on both units. This is a critical step, because if a Tenda F6 is left in router mode, it will try to hand out its own IP addresses and NAT traffic, creating a double-NAT situation that causes exactly the kind of "connected but no internet" symptom residents were seeing
  • Both F6s were connected to the switch via their LAN ports (not WAN), configured with static management IPs on the same subnet as the RB951, and set to the same Wi-Fi SSID and password so residents could roam between coverage areas seamlessly as they moved around the property

Step 5: Verifying the Connection End to End

With the PPPoE session up on the RB951 and the F6s reconfigured as access points, we ran through our standard checks:

  • Confirmed the RB951's PPPoE interface held a stable public IP with no repeated drops
  • Pinged an external IP from the RB951 to confirm outbound connectivity
  • Resolved a domain name to confirm DNS was working correctly (thanks to "Use Peer DNS" pulling the ISP's DNS servers automatically)
  • Tested speeds on a wired device through the switch and on Wi-Fi through each Tenda F6
  • Walked the property between coverage areas with a phone to confirm seamless roaming on the shared SSID, with internet access holding throughout
  • Spot-checked connectivity with a few residents on different floors to confirm the fix had resolved the outage building-wide, not just near the core router

Everything came back clean.

Step 6: Locking In Reliability

Getting PPPoE to connect once isn't the whole job. We wanted to make sure it stayed connected. So we also:

  • Enabled the RB951's built-in PPPoE keep-alive behaviour so a brief ISP-side blip wouldn't require a manual reboot or an on-site visit
  • Double-checked that DHCP was fully disabled on both Tenda F6s, so there was no risk of them silently re-enabling and causing IP conflicts across the building
  • Checked firmware/RouterOS versions on the RB951 and the F6s and applied available updates, since outdated firmware is a common cause of intermittent PPPoE drops and Wi-Fi instability
  • Documented the full topology and working configuration (RB951 PPPoE settings, switch layout, and F6 access point settings) securely for the property manager, in case a device ever needs to be replaced or the network expanded to cover more of the building

Common PPPoE Pitfalls We See Again and Again

If you're attempting a PPPoE setup yourself, especially with more than one networking device on site, here are the mistakes we run into most often:

  • Letting more than one device try to handle PPPoE. If your main router and a secondary access point (like a Tenda F6) both attempt to dial the PPPoE session, or both run DHCP and NAT, you end up with conflicts and double-NAT issues that are painful to diagnose.
  • Leaving access points in router mode. The Tenda F6 is a capable router in its own right, but when it's meant to just extend Wi-Fi, it needs to be switched into access point mode with DHCP turned off. Otherwise it'll hand out its own conflicting IP addresses.
  • Mistyped or copy-pasted credentials with hidden characters. Always type PPPoE credentials manually if pasting isn't working reliably.
  • Ignoring MTU settings. An incorrect MTU on the PPPoE interface can cause some websites to load while others time out, a confusing, hard-to-diagnose symptom.
  • No keep-alive configured on the dialing device. Without it, the connection drops and needs manual intervention, often at the worst possible time.
  • Assuming the switch and cabling are fine without checking link lights first. Physical issues on a switch port masquerade as configuration issues constantly.

Wrapping Up

For this 50-unit property, the whole process, from diagnosis to a fully stable, building-wide connection, took under a few hours once we were on site. PPPoE isn't inherently complicated, but it does require getting several small details right: correct credentials, correct connection type, sensible MTU, and a reliable reconnect policy. At scale, it also means making sure every downstream device (switch, access points) is configured to complement the core router rather than compete with it.

If you're dealing with a similar situation, a new ISP connection that just won't come online, whether it's a single home or a full apartment complex, it's often faster and less frustrating to have someone experienced take a look rather than guessing through router menus. That's exactly the kind of job our team at Luxenetworks handles regularly, and we're always happy to help get your connection stable and secure.

Related Insights

May 17, 2026

Starlink Finally Lands in Uganda: What It Means for Internet Access

For years, Ugandans have heard about Starlink — the satellite internet service from SpaceX — transforming connectivity in remote parts of the world. Now, after months of speculation, negotiations, and regulatory discussions, Starlink is officially coming to Uganda. The development could mark one of the biggest shifts in Uganda’s internet landscape in years. Uganda Gives Starlink the Green Light In May 2026, the Ugandan government officially approved Starlink to operate in the country after reaching an agreement with the Uganda Communications Commission (UCC). The deal followed extensive talks around licensing, taxation, national security, and compliance with local telecom laws. Government officials described the agreement as a major step toward expanding internet access across the country — especially in regions where traditional telecom infrastructure has struggled to reach. Before the approval, Starlink had faced regulatory resistance. Earlier in the year, Ugandan authorities warned citizens against using unauthorized Starlink equipment because the company had not yet received an operating license. That situation has now changed. Why Starlink Matters in Uganda Internet access in Uganda has improved significantly over the past decade, but large gaps still remain. In many urban areas like Kampala, users can access fiber internet and relatively strong 4G or 5G networks. But in rural districts, connectivity is often slow, expensive, or unavailable altogether. That’s where Starlink becomes interesting. Unlike traditional internet providers that rely on cell towers or underground fiber cables, Starlink uses thousands of low-Earth orbit satellites to deliver broadband internet directly to a small dish installed at a home, school, or business. This means places that were previously difficult or expensive to connect could suddenly gain access to high-speed internet. Potential beneficiaries include: Rural schools needing online learning tools Health centers requiring telemedicine access Farmers using digital market platforms Remote businesses and tourism lodges NGOs and humanitarian operations Content creators and remote workers outside major cities Could Starlink Change Internet Prices? That’s the big question. Uganda’s internet market is currently dominated by major telecom providers like MTN Uganda and Airtel Uganda. These companies already serve millions of users through mobile data and fiber services. Starlink’s arrival introduces a new kind of competition. While Starlink is unlikely to replace mobile internet for most people anytime soon, it could pressure providers to improve speeds, reliability, and pricing — especially for home and business broadband customers. However, affordability may still be a challenge. In many African countries where Starlink already operates, the initial hardware kit can cost several hundred dollars, with monthly subscriptions also priced higher than standard mobile bundles. Uganda’s official pricing has not yet been fully announced, but many observers expect cost to be one of the biggest barriers to widespread adoption. Where to Buy Starlink in Uganda As Starlink officially enters Uganda, customers are expected to purchase kits through: Authorized local resellers and technology stores Online ordering through the official Starlink website Selected internet and ICT service providers Installation partners offering setup services for homes and businesses Customers should always confirm that the seller is authorized and that the equipment is genuine before making payment. For inquiries, installation assistance, or Starlink updates in Uganda: WhatsApp: https://wa.me/256763206676 The Bigger Picture: Africa’s Internet Race Uganda joins a growing list of African countries embracing satellite internet technology. Across the continent, governments are under pressure to close the digital divide and improve access to education, e-commerce, fintech, and digital public services. Reliable internet is increasingly viewed as essential infrastructure — just like roads and electricity. Starlink’s expansion into Uganda reflects a broader trend: global tech companies are seeing Africa as a major growth market for connectivity. At the same time, regulators are trying to balance innovation with concerns about sovereignty, taxation, cybersecurity, and market fairness. What Happens Next? Several details are still expected in the coming months: Official Ugandan pricing for Starlink packages Retail and installation partnerships Importation procedures for Starlink kits Coverage expansion timelines Customer support structures inside Uganda For now, one thing is clear: Uganda’s internet sector is entering a new phase. Whether Starlink becomes a niche premium service or a true connectivity revolution will depend on pricing, accessibility, and how quickly the company can scale across the country. But after years of waiting, the satellite internet era has officially arrived in Uganda.
Jun 21, 2026

Starlink's Kenya Problem: When Satellite Internet Meets Its Own Success

When Starlink landed in Kenya in July 2023, it arrived with a simple promise: beam fast internet down from space, skip the messy business of digging trenches and laying cable, and connect places fiber would never reach. For a while, it delivered. Speeds hit 200 Mbps. Rural lodges in the Maasai Mara, off-grid farms, and households fed up with patchy local ISPs signed up in droves. Three years later, the story looks more complicated. The Numbers Tell the Story As of March 2026, Starlink's median download speed in Kenya had fallen to 34.55 Mbps  a 26% drop from the previous year and an all-time low for the service in the country. That's a long way down from the 200 Mbps users enjoyed at launch. The cause isn't a technical failure. It's success outpacing capacity. Starlink now counts close to 25,000 active subscribers in Kenya, and each satellite beam can only handle so many users in a given radius before everyone's connection starts to slow down. The more people who sign up in a concentrated area, the more the network strains — and the worse it gets for everyone sharing that beam. This Has Happened Before If this sounds familiar, it's because Kenya already lived through a version of this story. In November 2024, Starlink froze new residential sign-ups across Nairobi, Kiambu, Machakos, Kajiado, and Murang'a — the country's busiest, most densely populated counties — after capacity ran out. Anyone trying to subscribe was met with a blunt "sold out" message. The freeze lasted seven months. That pause cost Starlink dearly. Existing customers watched speeds crater to around 45 Mbps. The Communications Authority of Kenya's data showed the company lost roughly 2,000 subscribers in a single quarter, and its market share slipped from 1.1% down to 0.8%. Starlink did eventually add capacity and reopen sign-ups, clawing back some of the lost subscribers but never the market share. Now, in 2026, congestion is back, and it's arguably worse than the first time. Losing Ground to Local Rivals While Starlink has been wrestling with its own bandwidth math, Kenya's terrestrial ISPs haven't been standing still. Safaricom alone controls nearly 35% of the fixed internet market, offering fiber and 5G router packages with speeds up to 1,000 Mbps — at a fraction of Starlink's cost. JTL Faiba holds another 20%. Smaller players like Vilcom Networks, Ahadi Wireless, and Mawingu have all grown faster than Starlink over the past two years. The result: Starlink's once-dominant speed advantage over local providers has shrunk to just 2.24 times faster down from a much wider gap at launch. For many urban and peri-urban customers, that's no longer enough to justify the higher price tag, which still runs about three to four times what comparable local fiber packages cost. Put simply: Starlink disrupted the market just enough to wake up the competition, and the competition responded. Where Starlink Still Wins None of this means Starlink has failed in Kenya. It's just found a narrower lane than originally advertised. The satellite segment as a whole posted nearly 14% subscriber growth last quarter, driven almost entirely by exactly the customers Starlink was built for: rural households, remote businesses, NGOs, schools, and tourist camps where fiber will likely never arrive. Starlink has also leaned into that identity. It now sells hardware through retail partnerships at major Kenyan chains, alongside everyday electronics a sign the company is settling into a steady, if unglamorous, role as rural connectivity's default option rather than the urban broadband disruptor it was once pitched as. What's Next More competition is coming, not less. Amazon's Project Kuiper is working through regulatory approval to enter the Kenyan market, with plans for the company's first African ground station to be based there. That will only intensify pressure on an already strained satellite internet sector and could force Starlink to either invest seriously in local infrastructure or cede the rural niche it's carved out. For now, the pattern looks set to repeat: rapid uptake, congestion, a pullback, and a slow climb back  with each cycle leaving Starlink a little further from the broadband revolution it once promised, and a little more comfortable as Kenya's connectivity option of last resort.
Aug 27, 2026

Brand Guide? The Hidden Gem in Developing your brand

What Is a Brand Guide (And Why It's the First File Every Developer Should Open)   Ever landed on two pages of the same website and felt like you'd wandered into two different companies? Different blues. Different fonts. A logo squished to fit a header. That disconnect almost always traces back to one missing thing: a brand guide. A brand guide — sometimes called brand guidelines or a style guide — is the rulebook for how a company looks, sounds, and feels everywhere it shows up. It's not a nice-to-have for the design team only. It's a working document that designers, marketers, developers, and outside vendors all pull from so the brand stays recognizable no matter who's building what. What's Actually Inside One Visual identity Logo usage — approved versions, clear space, minimum size, and the misuses to avoid (stretching, recoloring, cramming it onto a busy background) Color palette — primary and secondary colors, specified in HEX, RGB, and CMYK so they render the same on a screen and in print Typography — approved typefaces for headlines and body copy, with sizing and hierarchy rules Imagery style — the mood of photography, illustration style, and iconography Voice and messaging Brand voice — the personality behind the words (playful, authoritative, warm — whatever it is), usually shown with do's and don'ts Taglines and messaging pillars — the core phrases that shouldn't be reworded on a whim Tone shifts — how voice bends between a support email and a launch campaign Application examples Mockups of the brand in the wild: business cards, social posts, packaging, slide decks Ready-made templates so nobody starts from a blank page Governance Side-by-side do's and don'ts Trademark and legal notes on using the logo or name correctly Why It Matters (Beyond Looking Nice) Consistency builds recognition. People start to know a brand by its color or type alone, before they even read a word. Efficiency. New hires and outside vendors get up to speed fast instead of guessing. Trust. A cohesive look and voice quietly signals "this company has its act together." The Part Most Brand Guides Forget: Developers and Designers Marketing usually commissions the brand guide, but nobody depends on it more than the people actually building the product. Here's why it matters specifically for developers and website designers: 1. It removes guesswork from implementation. A guide with exact HEX values, font files, and spacing rules means a developer isn't eyeballing "close enough" blue from a PDF screenshot. That precision is the difference between a design that gets built once, correctly, and one that gets patched five times after launch. 2. It becomes the source of truth for a design system. Modern brand guides increasingly double as the seed for a design system — the color tokens, type scale, and spacing units in the guide map almost directly to CSS variables, Tailwind config, or a component library. A developer building a button component isn't inventing padding and border-radius from scratch; they're translating the guide into code.   3. It prevents brand drift across a growing codebase. As a site or app scales — more pages, more contributors, more third-party embeds — small inconsistencies creep in fast. A brand guide (especially paired with a component library) acts as a constant reference point so a contractor's landing page still looks like it belongs to the same company as the core product. 4. It speeds up handoff between design and dev. When a designer's Figma file and the brand guide agree on every value, there's far less back-and-forth over "is this the right green?" or "which font weight is this?" That saved time compounds across every sprint. 5. It protects responsive and accessible design. Good brand guides increasingly specify color contrast ratios, minimum touch-target sizes, and font fallbacks — details a developer needs to hit accessibility standards (like WCAG) without having to make judgment calls that legal or design will later flag. 6. It's a safeguard during redesigns and rebrands. When a brand evolves, a well-documented guide tells a developer exactly what changed — a new primary color, an updated logo file, a revised type scale — so the migration is a checklist, not an archaeology dig through old style sheets. The Bottom Line A brand guide isn't paperwork sitting in a marketing drive. For a developer or website designer, it's closer to a technical spec: it tells you the exact values to build with, the constraints to respect, and the reasoning behind them. Treat it that way, and the gap between "what the brand should look like" and "what actually ships" gets a lot smaller.