eupolicy.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
This Mastodon server is a friendly and respectful discussion space for people working in areas related to EU policy. When you request to create an account, please tell us something about you.

Server stats:

206
active users

#ipv4

1 post1 participant0 posts today

#Homelab/#Networking question: I just realise that 'setting a static #IPv6 address' on a (#Linux) server is not as simple as it'd be with #IPv4 - one of the reasons being, realising, that the address prefix changes when my router restarts (i.e. due to any configuration changes).

When that network address prefix changes, obviously, any 'static' IPv6 address I'd like to set for my server would just be rendered
invalid, since the network address portion/prefix is no longer applicable.

On my
#TP-Link router, under IPv6 LAN settings, I saw an option to configure the Address Prefix - however, this field is currently prefilled with the network address prefix my servers/client devices are currently using/assigned to, and it is immutable (not configurable). To make it configurable, I could set a different setting on the same page called Prefix Delegation to Disable instead of its default, Enable.

My idea is to disable it, set an address prefix, and save/apply it - my expectation is, after the router restarts, all IPv6 addresses on my network will have that prefix, and it'll never change unless I explicitly do so (again, on the router). Is my idea right? or am I getting it tooootally wrong (which is possible bcos IPv6 is something else)?

This may sound like a dumb question, but with IPv6 am I supposed to ... learn the addresses like I have for IPv4?

With IPv4 I feel as if I have had a reasonable chance of learning some of the important blocks, but with IPv6... I genuinely hesitate to "adopt" because I fear having to learn the new addressing scheme.

If not, how should I ... "think" about IPv6 coming from the perspective of actually knowing IPv4-addresses?

Replied in thread

Mir gefällt ganz grundsätzlich die Idee, RZ grüner zu machen.

Aber den Punkt mit den Dieselaggregaten kann ich nicht so recht nachvollziehen. Die sind doch nur für den Notfall und haben dementsprechend nur geringe Betriebszeiten.

Wichtiger wäre es m. M. n., dass mal #IPv6 vorangetrieben wird. Dann würde uns endlich der zusätzliche STromverbrauch durch NAT, CGNAT und NAT-Traversal erspart bleiben.

Der BUND Naturschutz sollte hier mit gutem Beispiel vorangehen.

@bitsundbaeume_berlin #ipv4

If, like me, you've ever been annoyed at people just saying to grep the output of ifconfig for inet, and the likes, to get the assigned IP address of a network interface.

I got annoyed one time too many.

Have a *proper* solution.

May or may not also work on for example the *BSDs, but should definitely work on any modern typical-userland Linux.

michael.kjorling.se/blog/2025/

Michael Kjörling · Getting the IP address of a network interface, on Linux

Yes, The Book of PF, 4th Edition Is Coming Soon nxdomain.no/~peter/yes_the_boo

Long rumored and eagerly anticipated by some, the fourth edition of The Book of PF is now available for preorder nostarch.com/book-of-pf-4th-ed #openbsd #pf #packetfilter #freebsd #networking #security #tcpip #ipv6 #ipv4 #bookofpf

... and of course somebody had to ask, "when can we expect a fifth edition", to which the answer was "let's get this one out the door first"

That said, watch this space for further announcements!

nxdomain.noYes, The Book of PF, 4th Edition Is Coming Soon

So, #OpenAI thinks they are developing the next big thing that will replace everything else?
You know what they still can't even implement and replace? #IPv4 with #IPv6, their website is still IPv4 only, lol.

Seriously people, if you're ipv6 enabled its only a matter of months before more than half your global traffic will be #ipv6. Stop writing software and documentation that assumes IP addresses are #ipv4 only.

People are stuck in 2010 because they're just not paying attention and shit is happening fast.

#ipv4
#rip
labs.ripe.net/media/documents/

"Participants in the interviews conducted by NEXOP
said they believed that IPv4 will remain the primary
protocol for Internet connectivity for the next
decade or two. This prevailing sentiment highlights
the perceived necessity of IPv4 for most Internet
users in the foreseeable future. Many operators
also thought that the complexity of deploying IPv6
in large networks was underestimated."

🤦

Replied in thread

More or less, I do the same but on IP level. Having my own /29 subnet (out of my /24) for #IPv4 and /48 (out of my /32) for #IPv6 I simply attach them by GRE at locations where I want to use them. No dns updates, nothing. Tunnel up/down - served from where I want.

@jwildeboer

Replied in thread

Thanks!

I just noticed your repo is only reachable by #IPv4. This means that I can't reach it from my test server. Looks like I have to take a detour...

# wget repos.goffi.org/libervia-backe
--2025-05-30 12:24:05-- repos.goffi.org/libervia-backe
Resolving repos.goffi.org (repos.goffi.org)... 51.15.21.97
Connecting to repos.goffi.org (repos.goffi.org)|51.15.21.97|:443... failed: Network is unreachable.

@Goffi @liaizon