Selfhosted

39905 readers

318 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago

MODERATORS

[email protected]

[Solved] New Network Stack with an Unknown Issue..? (slrpnk.net)

submitted 3 months ago* (last edited 3 months ago) by [email protected] to c/[email protected]

23 comments fedilink hide all child comments

Update: It was DNS... its always DNS...

Hello there! I'm in a bit of a pickle.. I've recently bought the full budget Tp-link omada stack for my homelab. I got the following devices in my stack:

ER605 Router
OC200 Controller
SG2008P PoE Switch
EAP610 Wireless AP
EAP625 Wireless AP (getting soon)

I've set it all up and it was working fine for the first few days of using it. However, last few days it's been working very much on and off randomly(?) . Basically devices will state they are connected to WiFi/Ethernet, but they are not actually getting it. (As seen in the picture). This is happening with our phones(Pixel7+S23U) and my server(NAS:Unraid), have not noticed any problems on our desktop PCs. So it is happening on both wired and wireless, as my server and desktop PC is connected to the switch.

I haven't done many configurations in the omada software yet, but am assuming it's something I have done that causes this... Would greatly appreciate any advice to solve/troubleshoot this!

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 38 points 3 months ago (2 children)

It’s not DNS.
There’s no way it’s DNS.
It was DNS.

-SSBroski

[–] [email protected] 5 points 3 months ago

omg i cant believe it actually was DNS... hahahah

I had it at default settings - but all of my devices are connected over Tailscale which uses NextDNS. Somehow when connected to the WiFi i guess things weren't compatible...? Anyway i changed my Omada system to use NextDNS and voila! all devices connects flawlessly!

[–] [email protected] 6 points 3 months ago

A buddy experienced the exact same issue as OP just the other day. We ran diagnostics and it turns out his computer was running deprecated DNS IPs for a popular ad-blocking DNS provider.

It was DNS.