Selfhosted

39250 readers

236 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:

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

Network Routing Monitor (lemmy.omat.nl)

submitted 1 year ago by toma@lemmy.omat.nl to c/selfhosted@lemmy.world

1 comments fedilink hide all child comments

Sometimes the connection to my server in the cloud fails. 9 out of 10 times there is a problem with the routing, like a router in the datacenter that fails or a backbone temporary down.

When the connection fails, i often run a traceroute to see where the route fails. But the problem is that I have no reference to what it looked like before this problem started.

So, my question is, is there software that monitors the routes/hops to my cloud servers and remembers the different 'normal' routes that can occur.

If there is problem it would be nice if I can look at that software and it indicates where the problem is?

I prefer some docker image or at least a webbased interface, but any suggestion for such a tool is welcome.

top 1 comments

sorted by: hot top controversial new old

[–] empireOfLove@lemmy.one 7 points 1 year ago* (last edited 1 year ago)

I dont know of any specific docker/web app, but its very simple command line job in linux actually if you just need to record what "normal" routing paths are for reference

Set up cron job to run a script once a day. in said bash script, get the current date using date "+%Y-%m-%d", store in a variable, then redirect the output of traceroute into a text file by doing traceroute > {variable}.txt Then you'll have a day by day snapshot of your typical routing stack saved to your hard disk.

It won't actively monitor it. But it'll save a record. You can increase the frequency to as much as you want (hourly?) if you want too.