Moin zusammen!
Heute mal eine Fachfrage an die Linuxspezialisten hier im Fediverse.
Vor nicht allzu langer Zeit haben wir unser Heimnetz etwas umgestellt. Aufgrund der Geräteanzahl und "schöneren" Adressen haben wir nun folgende Konfiguration (Ziffern geändert), derzeit noch mit der Routerdomain "fritz.box". Grundsätzlich funktioniert auch alles, wobei ich grundsätzlich mit DHCP arbeite und die IPs vom Router (fest) verteilen lasse:
Subnetz: 192.168.0.0/23
Netzmaske: 255.255.254.0
Gateway: 192.168.1.1
DNS (Pihole): 192.168.1.254 - alternativ habe ich aber auch 8.8.8.8 & Co getestet
Wenn ich jetzt bei VMs/LXCs das DHCP ausschalte und eine statische IP-Konfiguration eingebe, klappt gefühlt gar nix mehr. Innerhalb des Heimnetzes sind die IPs weiterhin erreichbar und reagieren z.B. auf ein Ping ...
Aber nach draußen passiert gar nix. Pings z.B. an google.de schlagen fehl, die Linux-Repositories sind nicht erreichbar, allgmein klappt keine DNS-Auflösung. Egal was ich konfiguriere.
Das Kuriose:
Schalte ich DHCP wieder ein und gebe vom Router aus die identische Konfiguration vor, dann klappt alles ohne jegliche Probleme.
Hintergedanke:
Ich möchte (zunächst testweise) einen Samba-Server als AD/LDAP Controller aufsetzen, da wäre ja eine statische IP schon besser.
Suchergebnisse bei Google führten bisher leider zu nichts ...
Hat irgendjemand eine Idee, wo ich noch so schauen könnte?!
@landley @pmevzek @jschauma @ryanc @0xabad1dea @ripencc mostly because addresses get reused (Dynamic IPs were always the norm for consumers!) and because big block allocations get sold off and deallocated.
The fact that the #US #DoD has multiple /8 blocks hoarded that ain't even publicly routed is the most extreme example: The have enough static IPv4's to assign every past and current servicemember and every military vehicle one and would still have enough to spare.
In fact they have enough static #IPv4's to give everyone in the USA one and would still have propably more to spare than the entire rest of #NATO & #ANZUS / #14Eyes' #MILINTEL have combined.
Instead we have a giant cottage industry that deals with the artificial scarcity of IPv4's like digital real estate brokers, collecting value-removing fees for every transfer they can make which is explicitly rewarding #GAFAMs like #Apple that got a /8 early on and are now propping up their corporate valuation because that address block alone is propably worth a billion if not more.
@landley @pmevzek @jschauma @ryanc @0xabad1dea And that is espechally baffling considering that #APNIC as #RIR ran out of #IPv4|s first.
Cuz people telling me "Oh, just use HEnet's Tunnelbroker"" never experienced the shitshow that is #Geoblocking and #GDPR-#Noncompliance with #Malvertising to slap their faces!
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.
https://michael.kjorling.se/blog/2025/ip-address-of-network-interface-linux/
Also ich hatte noch nie Probleme mit #IPv6.
Die Probleme gehen immer nur von den IPv6-Verweigerern aus, die meinen, der restlichen Welt irgendein veraltetes Legacyprotokoll aufzwingen zu müssen, bei dem seit 30 Jahren Konsens ist, dass es verschwinden soll.
@troed @dalai @foone The problem will be that one will have to reimplement the "#API" as #api0 from scratch by running inspectors in browsers all the time...
It'll necessitate all api 0
calls to come from the same #IPv4 and/or #IPv6 as the end-user and hide itself with a fake #UserAgent to prevent countermeasures like #RateLimiting and #blocking.
@drscriptt Naive question: WHEN does the average #Internet #user ever open up a webpage with an #IP address instead of a #domain or even #FQDN?
The Idea if !SSL / #TLD for #IPaddresses makes me feel like Jeff Goldblum!
@drscriptt again: I'd see this as more error-prone than #DNSSEC and only hindering the transition from #IPv4 to #IPv6 if not bricking proper #DualStack…
@niklas @mattgrayyes worse even if one doesn't setup an account just to watch videos!
Then one cannot disable that shite which solely selects the used language based off vibes, which is really annoying when one has different #GeoIP "localizations" depending on whetger #IPv4, #IPv6 and whether one is on #Mobile or at home or at work!
Really makes me angry af!
Yes, The Book of PF, 4th Edition Is Coming Soon https://nxdomain.no/~peter/yes_the_book_of_pf_4th_ed_is_coming.html
Long rumored and eagerly anticipated by some, the fourth edition of The Book of PF is now available for preorder https://nostarch.com/book-of-pf-4th-edition #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!
1.
Obviously...2.
Not gonna argue with that.3.
as long as there are #IPv4only services and applications, I do at least need proper #DualStack. Regulators like @BNetzA refuse to mandate #IPv6 connectivity and I only get #IPv4 from my #ISP.
It’s 2025, And We Still Need IPv4! What Happens When We Lose It? https://hackaday.com/2025/07/03/its-2025-and-we-still-need-ipv4-what-happens-when-we-lose-it/ #CurrentEvents #NetworkHacks #ipv4 #IPv6
It’s 2025, And We Still Need IPv4! What Happens When We Lose It? - Some time last year, a weird thing happened in the hackerspace where this is being... - https://hackaday.com/2025/07/03/its-2025-and-we-still-need-ipv4-what-happens-when-we-lose-it/ #currentevents #networkhacks #ipv4 #ipv6
Hallo #fedipower!
Für meinen #Glasfaser-Anschluss denke ich über einen Wechsel von #Stiegeler zu #Leonet nach. Sind hier Leonet-Kunden anwesend?
Bei Stiegeler habe ich eine "echte" IPv4 (ohne CGNAT) und ein /54 IPv6-Präfix. Wie sieht das bei Leonet aus? Habe nichts dazu gefunden.
Using the Internet without IPv4 connectivity
https://jamesmcm.github.io/blog/no-ipv4/
#HackerNews #Using #the #Internet #without #IPv4 #connectivity
internet #connectivity #ipv4 #technology #networking #future