101010.pl is one of the many independent Mastodon servers you can use to participate in the fediverse.
101010.pl czyli najstarszy polski serwer Mastodon. Posiadamy wpisy do 2048 znaków.

Server stats:

476
active users

#ipv6

7 posts7 participants0 posts today

In general, I like netcup. The FediMeteo VPS rocks and they're quite reliable but....their IPv6 implementation is such a mess! Hetzner allows you to route, so each vnet jail can have its own IPv6 address. On netcup, I have never been able to achieve such a result.

Kann einer dem Dobrindt mal sagen, dass er bei der Vorratsdatenspeicherung nur die #IPv6 Adressen speichern muss, weil sich die Kriminellen damit sicher fühlen. Ich wäre da z.B raus. IPv4 💘

Continued thread
Burning it in for 12 hours now. It consumes 17W at idle running #OpenBSD 7.7 without apmd and ramps to 35W during KARL. Firmware was updated to the latest supported for the model and VT-x extensions have been turned off, this is just a firewall.

Thermals are good with the case back together. In 20 degrees ambient, they are reporting:
hw.sensors.cpu0.temp0=39.00 degC
hw.sensors.acpitz0.temp0=27.80 degC (zone temperature)
hw.sensors.nvme0.temp0=40.00 degC, OK

I did clean the heat sink and CPU, then applied new thermal paste. Time to build some ansible playbooks for management and then apply them, ready for production. #firewall #IPv6

When an ISP offers #IPv6 without a stable prefix for each customer, all IPv6 addresses would become invalid whenever the WAN reconnects due to sudden prefix changes. As a workaround, RFC 9096 requires routers to detect Flash Renumbering and invalidate stale prefixes - still largely unimplemented (WIP in OpenWrt). As a fail-safe, RFC 9096 also requires preferred/valid address timeouts of 45/90 minutes to prevent indefinite IPv6 outage - up to 7/30 days per RFC 4861 defaults.

Here's how to implement it in
#OpenWrt - trickier than you thought:

1. Upgrade to 24.10.2 - because earlier versions had a
bug, you couldn't override the "preferred" timeout obtained from the WAN.
2. Set DHCPv4's lifetime to 90 minutes (
option leasetime, in Interfaces -> LAN -> DHCP Server -> Lease time) - because there's currently no way to change IPv6's "valid" address timeout without changing DHCPv4's timeout - I checked the source code. Bug report submitted.
3. Set IPv6's preferred timeout to 45 minutes (
option preferred_lifetime, in Interfaces -> LAN -> DHCP Server -> IPv6 Setting -> IPv6 Prefix Lifetime).

This is how I spent my entire night on adjusting two timers.
:woozy_baa:

Replied in thread

@deuxnise я б порадив готувати мило користувачам #Yggdrasil, #Mycelium та інших #IPv6 інтерфейсів, бо тоді торенти та ігрові сокети, оголошені на "::" підуть на рандомний інтерфейс а не Інтернет.

Більшість клієнтів підтримують тільки dual-stack IPv4/IPv6 і до цього проблема була не помітною, адже функцію публічного інтерфейсу на себе саме брав "монокль" IPv4, а IPv6 працював на 1 рандомному з доступних.

Hello to our friends in Singapore 🇸🇬!

We’re happy to announce that we just opened up a new POP in Sin1, SG to come even closer to you! What does it mean?! IP-Space in Singapore including GEO objects & lower latencies in your area 🥳

Thanks to Route64 and @gyptazy !

Pleasantly surprised to see that "GNOME Connections" 48 works reasonably well for RDP nowadays, over LAN (or via direct IPv6 over WAN if you hack your /etc/hosts file).

The only security feature truly missing for me to see it as a viable alternative to Remmina for my usecases would be support for RDP over SSH tunnels: gitlab.gnome.org/GNOME/gnome-c

Here's the naughty workaround for IPv6 using /etc/hosts : gitlab.gnome.org/GNOME/gnome-c

GitLabSSH tunnelled connections (#70) · Issues · GNOME / Connections · GitLabRDP etc are often insecure and a way for Windows machines accepting connections to be hacked. This has been pretty prevalent since the lockdown since the malware bots...

Finland tends to be a bit different. This includes @UpCloud. If you slap #OpenBSD on a VM: IPv4 and IPv6 are two different NICs. Works great if you are aware of this - if they ever get a wiki I pinky swear I'll write it down on some relevant page.

Adding a poll because it is all the rage in Helsinki.

I really want to create my own simple router with FreeBSD for NIDS use. However, that's a future wish that I want to do later. My current target is to create a simulation with multiple jails that act as clients and routers. With IPv6 addressing, I want to connect them and pass the traffic between different networks. My current problem is how to do packet forwarding(?) like a normal router does. But I want to do it FreeBSD style. Any hints or help are appreciated

My current knowledge: I am familiar with basic jail, the epair mechanism, and a small bit of pf configurations.