Selfhosted

40347 readers

363 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

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

-1

Server not reachable after while (lemmy.eco.br)

submitted 1 year ago* (last edited 1 year ago) by BaalInvoker@lemmy.eco.br to c/selfhosted@lemmy.world

10 comments fedilink hide all child comments

Summary

I have a old laptop that's serving me as a Technitium DNS server and Tailscale exit node.

My setup is behind a CGNAT, but the Tailscale make its way around and that's not an issue. My VPN exit node works flawlessly.

However I also set my router to make my laptop as DNS server, so all my lan network is passing through the Technitium. So, in theory all my local network is using my selfhosted DNS server.

Issue

The issue here is not the server itself, cause it's working as intended - when I can connect to it.

What's going on is that my server for once in a while become unreachable from lan. If I try to ping it from another device in local network, it returns that it's unreachable, but my server still connected to the internet (I can ping Google, for example). So to solve it, I must do one of the below:

Kick the server from the router, forcing it to reconnect
Connect to the Tailscale VPN and ping it from the Tailscale ip
Reboot my server

It anoys me because it's not supposed to the server become unreachable in local randomly!

It's important to comment that the server isn't connected through ethernet, but it uses wifi because I can't put my laptop near the router. The laptop is close enough to not have any wifi interference, however.

What can I do to prevent my server to become unreachable?

My setup

Server

An old Acer laptop connected to the wifi
Static IP configured
SO: Arch Linux (as server, no GUI at all)

Router

D-Link DIR-842

Thank you in advance

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

[–] Toes@ani.social 0 points 1 year ago* (last edited 1 year ago) (1 children)

Try switching to openwrt firmware on the router.

D-Link stock firmware tends to be rather buggy in my experiences.

Power saving features sounds like a strong possibility.

I've seen a problem like this where it was related to the client switching between 2.4ghz and 5ghz and the router switching channels rather frequently.

Try writing a keep alive job. Every ten seconds ping Google.

[–] BaalInvoker@lemmy.eco.br -1 points 1 year ago

The router is not mine... I'll not change the firmware cause the router is borrowed from the ISP and I must give it back if I change my ISP

I'm trying the power saving mode and hoping that is the issue!

Another guy suggested ping the router from the server for once in a while as well and I think it must "remember" the router about the existence of the server