Bradley Taunt
@bt@mastodon.bsd.cafe  ·  activity timestamp 2 days ago

Was ordering myself a new X220 keyboard and a small, fan-less Intel-based router caught my eye (on sale!). I snagged both :)

When it gets here, I plan to swap out my hacked-together router (2012 mac mini) for it. The next goal would be to repurpose that same mac Mini as a web server my personal, public websites.

Only time will tell if I fail...

#openbsd #networking #router
Bradley Taunt
@bt@mastodon.bsd.cafe  ·  activity timestamp 2 days ago

Was ordering myself a new X220 keyboard and a small, fan-less Intel-based router caught my eye (on sale!). I snagged both :)

When it gets here, I plan to swap out my hacked-together router (2012 mac mini) for it. The next goal would be to repurpose that same mac Mini as a web server my personal, public websites.

Only time will tell if I fail...

#openbsd #networking #router
Landgraab Industries 🏙️
@Landgraab_Industries@mstdn.games  ·  activity timestamp 5 days ago

Tower Networking Inc., an ISP/networking management game with physical switch connection and an in-game command line interface, released in early access on Steam.

https://store.steampowered.com/app/2939600/Tower_Networking_Inc/

Discussion: https://lemmy.world/post/33897286

#indiegame #tycoon #networking#ISP
Eugene :emacs: :freebsd:
@evgandr@mas.to  ·  activity timestamp last week

> "If you’re an app developer reading this, can you tell me, off the top of your head, how your app behaves on a link with 40 kbps available bandwidth, 1,000 ms latency, occasional jitter of up to 2,000 ms, packet loss of 10%, and a complete 15-second connectivity dropout every few minutes?"

https://brr.fyi/posts/engineering-for-slow-internet

#SlowNet #permacomputing#Internet #networking
musicmatze :rust: :nixos:
@musicmatze@social.linux.pizza  ·  activity timestamp last week

I have a very weird issue with my #tailscale + #mumble server setup:

I have a murmur (mumble) server that binds to the tailscale interface on my server.

I have shared that endpoint with a friend and we're both connecting via tailscale to that mumble server to talk.

Every few minutes (3, 5, something like that), one of us gets reconnected. Mumble (client) says "Server failed to respond to TCP ping". On the server it says (murmur log): "Connection closed: The remote host closed the connection".

The tailscale log on the server says something like "adding connection to derp-* for ..." at that very moment of reconnecting.

How to debug this issue? I don't even know where to start. It looks like (to me, as a networking noob) that tailscale reconfigures connections and breaks the mumble connection.

#followerpower #linuxadmin #NetworkEngineering #networking #sysadmin

CC @tailscale

Please boost boost_ok
musicmatze :rust: :nixos:
@musicmatze@social.linux.pizza  ·  activity timestamp last week

I have a very weird issue with my #tailscale + #mumble server setup:

I have a murmur (mumble) server that binds to the tailscale interface on my server.

I have shared that endpoint with a friend and we're both connecting via tailscale to that mumble server to talk.

Every few minutes (3, 5, something like that), one of us gets reconnected. Mumble (client) says "Server failed to respond to TCP ping". On the server it says (murmur log): "Connection closed: The remote host closed the connection".

The tailscale log on the server says something like "adding connection to derp-* for ..." at that very moment of reconnecting.

How to debug this issue? I don't even know where to start. It looks like (to me, as a networking noob) that tailscale reconfigures connections and breaks the mumble connection.

#followerpower #linuxadmin #NetworkEngineering #networking #sysadmin

CC @tailscale

Please boost boost_ok