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:

199
active users

#ipv4

3 posts3 participants0 posts today
Max Resing<p>Apparently, there exists a website called <code>ipv4[.]games</code>, where you can register HTTP web requests from hosts where you have access to. Once accessed, you can "claim" the requesting <a href="https://infosec.exchange/tags/IPv4" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IPv4</span></a> address with an <a href="https://infosec.exchange/tags/HTTP" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>HTTP</span></a> GET request on <code>/claim?name=&lt;NAME&gt;</code>.</p><p>The leaderboard leads the person which claims most addresses of various <code>/8</code> networks.</p><p>It is wild to see partially 6-digit numbers for various <code>/8</code>s claimed by one and the same user.</p><p>My guess is: Either they leverage residential proxies, or leverage perhaps mass-spamming on having millions of people world-wide clicking links, or alternatively, leveraging modern software design to do the lookup for them (e.g. website previews on social media, or anti-phishing services that do a lookup, before they forward the mail to you).</p><p>No matter what, I am sure that millions of these IP addresses in there can be harvested as <a href="https://infosec.exchange/tags/open" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>open</span></a> <a href="https://infosec.exchange/tags/proxies" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>proxies</span></a> </p><p>Other than that, I like the idea, and love how gamification leads to some people developing creative ways on making millions of hosts on the Internet access this website. It probably still invites to unsolicited requests from strangers unknowingly participating in the game of a tech-savvy person.</p><p><a href="https://infosec.exchange/tags/Spamming" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Spamming</span></a> <a href="https://infosec.exchange/tags/spoofing" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>spoofing</span></a></p>
Bryan Whitehead<p>It’s criminal. <a href="https://dusty.ninja/tags/digitalocean" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DigitalOcean</span></a> makes each droplet spun up <a href="https://dusty.ninja/tags/ipv4" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IPv4</span></a> only by default. You have to specifically make sure the <a href="https://dusty.ninja/tags/ipv6" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IPv6</span></a> checkbox is selected, or you’re stuck with v4 without a bunch of annoying steps to get v6 working later. Infuriating.<br><br>I really don’t understand why v6 isn’t on by default. Terrible. End rant.</p>
Mika<p><a href="https://sakurajima.social/tags/Homelab" rel="nofollow noopener" target="_blank">#Homelab</a>/<a href="https://sakurajima.social/tags/Networking" rel="nofollow noopener" target="_blank">#Networking</a> question: I just realise that 'setting a static <a href="https://sakurajima.social/tags/IPv6" rel="nofollow noopener" target="_blank">#IPv6</a> address' on a (<a href="https://sakurajima.social/tags/Linux" rel="nofollow noopener" target="_blank">#Linux</a>) server is not as simple as it'd be with <a href="https://sakurajima.social/tags/IPv4" rel="nofollow noopener" target="_blank">#IPv4</a><span> - one of the reasons being, realising, that the address prefix changes when my router restarts (i.e. due to any configuration changes).<br><br>When that network address prefix changes, obviously, any 'static' IPv6 address I'd like to set for my server would just be rendered </span><i>invalid</i><span>, since the network address portion/prefix is no longer applicable.<br><br>On my </span><a href="https://sakurajima.social/tags/TP-Link" rel="nofollow noopener" target="_blank">#TP-Link</a> router, under IPv6 LAN settings, I saw an option to configure the <code>Address Prefix</code> - 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 <code>Prefix Delegation</code> to <code>Disable</code> instead of its default, <code>Enable</code><span>.<br><br>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)?</span></p>
Christoffer S.<p>This may sound like a dumb question, but with IPv6 am I supposed to ... learn the addresses like I have for IPv4?</p><p>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.</p><p>If not, how should I ... "think" about IPv6 coming from the perspective of actually knowing IPv4-addresses?</p><p><a href="https://swecyb.com/tags/Networking" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Networking</span></a> <a href="https://swecyb.com/tags/IPv6" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IPv6</span></a> <a href="https://swecyb.com/tags/IPv4" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IPv4</span></a></p>
hallunke23 🇺🇦:nona:<p>Mir gefällt ganz grundsätzlich die Idee, RZ grüner zu machen.</p><p>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.</p><p>Wichtiger wäre es m. M. n., dass mal <a href="https://troet.cafe/tags/IPv6" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IPv6</span></a> vorangetrieben wird. Dann würde uns endlich der zusätzliche STromverbrauch durch NAT, CGNAT und NAT-Traversal erspart bleiben.</p><p>Der BUND Naturschutz sollte hier mit gutem Beispiel vorangehen.</p><p><span class="h-card" translate="no"><a href="https://mastodon.bits-und-baeume.org/@bitsundbaeume_berlin" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>bitsundbaeume_berlin</span></a></span> <a href="https://troet.cafe/tags/ipv4" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ipv4</span></a></p>
Thomas Schäfer<p>There are still LIRs without <a href="https://ipv6.social/tags/IPv6" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IPv6</span></a> . 😕</p><p>~1000 LIRs still begging for <a href="https://ipv6.social/tags/IPv4" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IPv4</span></a> addresses 🤔</p><p><a href="https://ipv6.social/tags/ripe" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ripe</span></a> region </p><p><a href="https://www.ripe.net/about-us/news/member-update-july-2025/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">ripe.net/about-us/news/member-</span><span class="invisible">update-july-2025/</span></a></p>
mkj<p>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.</p><p>I got annoyed one time too many.</p><p>Have a *proper* solution.</p><p>May or may not also work on for example the *BSDs, but should definitely work on any modern typical-userland Linux.</p><p><a href="https://michael.kjorling.se/blog/2025/ip-address-of-network-interface-linux/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">michael.kjorling.se/blog/2025/</span><span class="invisible">ip-address-of-network-interface-linux/</span></a></p><p><a href="https://social.mkj.earth/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Linux</span></a> <a href="https://social.mkj.earth/tags/BlogPost" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>BlogPost</span></a> <a href="https://social.mkj.earth/tags/blog" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>blog</span></a> <a href="https://social.mkj.earth/tags/PersonalWebSite" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>PersonalWebSite</span></a> <a href="https://social.mkj.earth/tags/indieweb" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>indieweb</span></a> <a href="https://social.mkj.earth/tags/networking" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>networking</span></a> <a href="https://social.mkj.earth/tags/IPv4" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IPv4</span></a> <a href="https://social.mkj.earth/tags/IPv6" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IPv6</span></a></p>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://oldbytes.space/@drscriptt" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>drscriptt</span></a></span> again: I'd see this as more error-prone than <a href="https://infosec.space/tags/DNSSEC" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DNSSEC</span></a> and only hindering the transition from <a href="https://infosec.space/tags/IPv4" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IPv4</span></a> to <a href="https://infosec.space/tags/IPv6" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IPv6</span></a> if not bricking <em>proper <a href="https://infosec.space/tags/DualStack" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>DualStack</span></a></em>…</p>
Peter N. M. Hansteen<p>Yes, The Book of PF, 4th Edition Is Coming Soon <a href="https://nxdomain.no/~peter/yes_the_book_of_pf_4th_ed_is_coming.html" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">nxdomain.no/~peter/yes_the_boo</span><span class="invisible">k_of_pf_4th_ed_is_coming.html</span></a> </p><p>Long rumored and eagerly anticipated by some, the fourth edition of The Book of PF is now available for preorder <a href="https://nostarch.com/book-of-pf-4th-edition" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">nostarch.com/book-of-pf-4th-ed</span><span class="invisible">ition</span></a> <a href="https://mastodon.social/tags/openbsd" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>openbsd</span></a> <a href="https://mastodon.social/tags/pf" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>pf</span></a> <a href="https://mastodon.social/tags/packetfilter" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>packetfilter</span></a> <a href="https://mastodon.social/tags/freebsd" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>freebsd</span></a> <a href="https://mastodon.social/tags/networking" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>networking</span></a> <a href="https://mastodon.social/tags/security" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>security</span></a> <a href="https://mastodon.social/tags/tcpip" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>tcpip</span></a> <a href="https://mastodon.social/tags/ipv6" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ipv6</span></a> <a href="https://mastodon.social/tags/ipv4" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ipv4</span></a> <a href="https://mastodon.social/tags/bookofpf" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>bookofpf</span></a></p><p>... 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"</p><p>That said, watch this space for further announcements!</p>
T_X<p>So, <a href="https://chaos.social/tags/OpenAI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OpenAI</span></a> thinks they are developing the next big thing that will replace everything else?<br>You know what they still can't even implement and replace? <a href="https://chaos.social/tags/IPv4" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IPv4</span></a> with <a href="https://chaos.social/tags/IPv6" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IPv6</span></a>, their website is still IPv4 only, lol.</p>
takt<p>When will we stop using <a href="https://infosec.exchange/tags/IPv4" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IPv4</span></a> on <a href="https://infosec.exchange/tags/Peering" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Peering</span></a> LANs and avoid the messy renumberings? <a href="https://infosec.exchange/tags/IPv6" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IPv6</span></a> <a href="https://infosec.exchange/tags/Extended" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Extended</span></a>-Nexthop <a href="https://infosec.exchange/tags/RFC5549" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>RFC5549</span></a></p>
sahilister<p>After going through <a href="https://bgp.tools/transfer-history/?org=Amazon.com%2c%20Inc" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">bgp.tools/transfer-history/?or</span><span class="invisible">g=Amazon.com%2c%20Inc</span></a>. , it feels like Amazon has always been buying all the larger IPv4 blocks.</p><p><a href="https://toots.sahilister.in/tags/amazon" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>amazon</span></a> <a href="https://toots.sahilister.in/tags/ipv4" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ipv4</span></a></p>
Thomas Schäfer<p><a href="https://ipv6.social/tags/ipv4" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ipv4</span></a> <br>nice rant</p><p><a href="https://abusix.com/blog/why-cgnat-is-a-cancer-on-the-internet/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">abusix.com/blog/why-cgnat-is-a</span><span class="invisible">-cancer-on-the-internet/</span></a></p>
Daniel Lakeland<p>Seriously people, if you're ipv6 enabled its only a matter of months before more than half your global traffic will be <a href="https://mastodon.sdf.org/tags/ipv6" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ipv6</span></a>. Stop writing software and documentation that assumes IP addresses are <a href="https://mastodon.sdf.org/tags/ipv4" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ipv4</span></a> only.</p><p>People are stuck in 2010 because they're just not paying attention and shit is happening fast.</p>
Thomas Schäfer<p><a href="https://ipv6.social/tags/ipv4" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ipv4</span></a><br><a href="https://ipv6.social/tags/rip" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>rip</span></a> <br><a href="https://labs.ripe.net/media/documents/The_State_of_IPv4_Report.pdf" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">labs.ripe.net/media/documents/</span><span class="invisible">The_State_of_IPv4_Report.pdf</span></a></p><p>"Participants in the interviews conducted by NEXOP<br>said they believed that IPv4 will remain the primary<br>protocol for Internet connectivity for the next<br>decade or two. This prevailing sentiment highlights<br>the perceived necessity of IPv4 for most Internet<br>users in the foreseeable future. Many operators<br>also thought that the complexity of deploying IPv6<br>in large networks was underestimated."</p><p>🤦</p>
Denny<p>Kennt ihr günstige <a href="https://bunt.social/tags/Hoster" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Hoster</span></a> für <a href="https://bunt.social/tags/colocation" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>colocation</span></a> in <a href="https://bunt.social/tags/frankfurt" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>frankfurt</span></a> ? Ich stelle immer wieder fest, dass <a href="https://bunt.social/tags/firstColo" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>firstColo</span></a> doch recht teuer ist und aktruell liegt die <a href="https://bunt.social/tags/Rechnung" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Rechnung</span></a> bei 136€/Monat. Ab August wird es zwar günstiger, weil ich ein ungenutzes <a href="https://bunt.social/tags/ipv4" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ipv4</span></a> Netz gekündigt habe, aber für 1HE ... suche ich etwas, dass günstiger ist.</p>
RIPE NCC<p>📉 IPv4 exhaustion is real. So how are networks coping?</p><p>Our latest IP report dives into the rise of IPv4 transfers, trends in pricing and availability, and what it all means for the Internet’s future.</p><p>🔗 Read the full report: <a href="https://labs.ripe.net/media/documents/The_State_of_IPv4_Report.pdf" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">labs.ripe.net/media/documents/</span><span class="invisible">The_State_of_IPv4_Report.pdf</span></a></p><p>Do you think IPv4 transfers have become a crucial lifeline in the wake of address space exhaustion? </p><p><a href="https://mastodon.social/tags/IPv4" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IPv4</span></a> <a href="https://mastodon.social/tags/IPtransfers" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IPtransfers</span></a> <a href="https://mastodon.social/tags/InternetInfrastructure" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>InternetInfrastructure</span></a></p>
gyptazy<p>More or less, I do the same but on IP level. Having my own /29 subnet (out of my /24) for <a href="https://mastodon.gyptazy.com/tags/IPv4" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IPv4</span></a> and /48 (out of my /32) for <a href="https://mastodon.gyptazy.com/tags/IPv6" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IPv6</span></a> 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.</p><p><span class="h-card" translate="no"><a href="https://social.wildeboer.net/@jwildeboer" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>jwildeboer</span></a></span></p>
hallunke23 🇺🇦:nona:<p>Jupp. Wobei mir das in Verbindung mit den sinkenden Preisen Hoffnung macht. Inzwischen werden <a href="https://troet.cafe/tags/IPv4" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IPv4</span></a>-Adressen wieder für nur 20$/Stück verkauft. Wenn das weiter runter geht, steht irgendwann wirklich <a href="https://troet.cafe/tags/IPv6only" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IPv6only</span></a> vor der Tür.</p><p><a href="https://auctions.ipv4.global/prior-sales" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">auctions.ipv4.global/prior-sal</span><span class="invisible">es</span></a></p><p><span class="h-card" translate="no"><a href="https://chaos.social/@quincy" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>quincy</span></a></span></p>
Quincytrumpisierung, depol