Login

Recent searches

No recent searches

Search options

Not available on writing.exchange.
writing.exchange is one of the many independent Mastodon servers you can use to participate in the fediverse.
A small, intentional community for poets, authors, and every kind of writer.

Administered by:

Server stats:

334
active users

writing.exchange: AboutProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.3.7

#ipv6

15 posts14 participants4 posts today
Public
Larvitz :fedora: :redhat:

Some statistics from a smaller Germany based Mastodon instance (burningboard.net)

We currently have 109 active users (logged in during the last 30 days).

The PostgreSQL Database size is 16.6GB

The media-data (S3) size is 201 GB with 775544 files.

The monthly traffic is around 900GB, 82% of that is IPv6 and just 18% is legacy IPv4.

Hardware (VM Sizing):
- 8 Altara Neoverse-N1 ARM64 CPU cores
- 16 GB DDR4 Ram
- 100 GB NVMe SSD

Software-Stack:
- Debian GNU/Linux 12 (bookworm) aarch64
- Mastodon v4.3.7
- PostgreSQL 17.4
- Ruby 3.4.2
- Monitoring through Grafana/Loki and Uptime Kuma

The low-power ARM system can handle the Mastodon instance without issues and even has some headroom left for future growth 🙂

#mastoadmin#mastodon#statistics
Public
Robin

I complained a while back about #homeassistant periodically changing the #IPv6 address on the host that it's running on, and said at the time I'll probably just fix it by putting a static address in /etc/network/interfaces. And now I discovered that it overrides that too! Logged into the host and see that my static address has vanished from the IPs on the interface. It's still in the file, so restarting networking fixes it for now, but this is very annoying, especially as it doubles as the SSH jump host into my network, which I think I'll need to change.

Any hints on how I can tell home assistant that it shouldn't be screwing with my networking would be appreciated!

Replied in thread
Public
Kajetan Staszkiewicz

@matdevdug According to github.com/netbirdio/netbird/i Netbird still does not support the *current* Internet Protocol. I've evaluated it last year to replace the #IPSec VPN at $WORK and lack of IPv6 was the reason I had to give up on Netbird. I have quite many #IPv6 -only hosts and my colleagues need to be able to access them.

Hello, In the README I only see IPv4 subnets, is wiretrustee working with IPv6 subnets? If not, is it possible to add a support for IPv6?
GitHubFeature Request: internal IPv6 support · Issue #46 · netbirdio/netbirdBy unixfox
Replied in thread
Public
Vincent 🐡

So, here are the last logs of my Forgejo from nginx :

vinishor@www.home.arpa > sudo cat gitea-access.log
(/var/log/nginx)
vinishor@www.home.arpa > ls -l gitea-access.log*
-rw-r----- 1 www-data adm 0 Apr 8 00:00 gitea-access.log

This is not a joke.
Best way to fight against AI : #ipv6

Public
gyptazy

Oops! The MXP01 (Italy) peer had some fuck ups, followed by some insane traffic f*ckups at 3AM & 6AM on the other instances.

Rule Nr. 1: Even changing a single character can result in f*ckups. Always test!

#devops#bgp#peering
Replied in thread
Public
Jens Link

@ryan

for the authoritative side:

When you put AAAA and A records into DNS, IPv6 enabled clients will try IPv6 first and then fall back to IPv4. So Configure and test your systems first, then configure the DNS records.

HTTP / HTTPS are an exception here, they are using something called HappyEyeballs.

datatracker.ietf.org/doc/html/

Logo of the IETF
IETF DatatrackerRFC 8305: Happy Eyeballs Version 2: Better Connectivity Using ConcurrencyMany communication protocols operating over the modern Internet use hostnames. These often resolve to multiple IP addresses, each of which may have different performance and connectivity characteristics. Since specific addresses or address families (IPv4 or IPv6) may be blocked, broken, or sub-optimal on a network, clients that attempt multiple connections in parallel have a chance of establishing a connection more quickly. This document specifies requirements for algorithms that reduce this user-visible delay and provides an example algorithm, referred to as "Happy Eyeballs". This document obsoletes the original algorithm description in RFC 6555.
#IPV6
ExploreLive feeds
About