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

#ipv4

2 posts2 participants1 post today
Max Resing<p>Just wanted to share some thoughts on <a href="https://infosec.exchange/tags/RFC9715" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>RFC9715</span></a> - an <a href="https://infosec.exchange/tags/RFC" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>RFC</span></a> that defines standards on reducing the <a href="https://infosec.exchange/tags/DNS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>DNS</span></a> issue of IP fragmentation over <a href="https://infosec.exchange/tags/UDP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>UDP</span></a>. It's not a long read, but a good one for everyone who understands the issues of large UDP responses on the <a href="https://infosec.exchange/tags/Internet" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Internet</span></a>. A great leap forward to (hopefully) reduce the reflection/amplification <a href="https://infosec.exchange/tags/DDoS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>DDoS</span></a> potential of DNS.</p><p>Just today I learned that <a href="https://infosec.exchange/tags/Google" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Google</span></a> will configure their public DNS resolvers to limit to ~1400 bytes (smaller adjustments expected while figuring out the sweet spot in production). From now on, DNS responses which exceed this limit will have the truncated flag set instructing the client to resolve back to <a href="https://infosec.exchange/tags/TCP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>TCP</span></a>. </p><p><a href="https://infosec.exchange/tags/ipv4" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ipv4</span></a> <a href="https://infosec.exchange/tags/ipv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ipv6</span></a> <a href="https://infosec.exchange/tags/ietf" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ietf</span></a></p>
Yvan ー イボん 🗺️ :ferris: :go:<p><a href="https://hachyderm.io/tags/ipv4" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ipv4</span></a> is hell</p><p>So much easier to go <a href="https://hachyderm.io/tags/ipv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ipv6</span></a> only.</p>
asmw<p>Today, when looking into <a href="https://infosec.exchange/tags/ipv4" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ipv4</span></a>/#ipv6 issues, I learned about <a href="https://infosec.exchange/tags/happyeyeballs" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>happyeyeballs</span></a> (<a href="https://en.wikipedia.org/wiki/Happy_Eyeballs" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">en.wikipedia.org/wiki/Happy_Ey</span><span class="invisible">eballs</span></a>).</p><p>Such a pretty name for such an annoying problem.</p>
Michael<p>Question to the network people out there:</p><p>Are there any ISPs that are IPv6 only (without providing a NAT/whatever)?</p><p>Background: Having an argument with a provider that hasn't published any AAAA records, and whilst I think that's poor form, I'm wondering if this would actually negatively affect any actual users in practice?</p><p><a href="https://mstdn.thms.uk/tags/ip" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ip</span></a> <a href="https://mstdn.thms.uk/tags/ipv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ipv6</span></a> <a href="https://mstdn.thms.uk/tags/ipv4" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ipv4</span></a> <a href="https://mstdn.thms.uk/tags/isp" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>isp</span></a></p>
Quincy<p><a href="https://chaos.social/tags/IPv4" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IPv4</span></a>-Adressen als Wertanlage</p>
U3A Communities<p><strong>IPv4 and IPv6 addresses</strong></p> <p>🗓️ Start: 15 April 2025 3:00 pm<br>⏳ End: 15 April 2025 5:00 pm</p><p><strong>15th April 2025 at 3pm UK</strong></p><p>This month we look at IP (Internet Protocol) addresses, including both IPv4 and IPv6.&nbsp; The talk includes a brief description of IPv4 addresses, problems with IPv4, IPv6 addresses and current IPv6 status.</p><p>Joining details will be emailed to subscribers nearer the time.&nbsp; If you aren’t a member, it’s free to join here <a href="https://u3acommunities.org/subscribe-to-computing-forum/" rel="nofollow noopener noreferrer" target="_blank">https://u3acommunities.org/subscribe-to-computing-forum/</a>.</p><p>Plenty of time is reserved for discussions.</p> <p><a href="https://u3acommunities.org/event/ipv4-and-ipv6-addresses/" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">u3acommunities.org/event/ipv4-</span><span class="invisible">and-ipv6-addresses/</span></a></p>
Radio Azureus<p>TIL about lsd(1)</p><p>What an awsome addition to my lolcat arsenal!</p><p>The acronym is not correctly used by me in this case, because I **know** I used LSD in the 1990's (the command in a UNIX ENV:) and LSD is just as pretty as it was psychedelic in the last century!</p><p>`man lsd `</p><p>An ls command with a lot of pretty colors and some other stuff.</p><p><span class="h-card" translate="no"><a href="https://fuzzies.wtf/@altbot" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>altbot</span></a></span> </p><p>🖋️ <a href="https://mastodon.social/tags/bash" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>bash</span></a> <a href="https://mastodon.social/tags/sh" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>sh</span></a> <a href="https://mastodon.social/tags/zsh" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>zsh</span></a> <a href="https://mastodon.social/tags/ksh" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ksh</span></a> <a href="https://mastodon.social/tags/csh" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>csh</span></a> <a href="https://mastodon.social/tags/Networking" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Networking</span></a> <a href="https://mastodon.social/tags/IPv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IPv6</span></a> <a href="https://mastodon.social/tags/IPv4" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IPv4</span></a> <a href="https://mastodon.social/tags/ProxMox" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ProxMox</span></a> <a href="https://mastodon.social/tags/freeBSD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>freeBSD</span></a> <a href="https://mastodon.social/tags/Linux" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Linux</span></a> <a href="https://mastodon.social/tags/POSIX" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>POSIX</span></a> <a href="https://mastodon.social/tags/Programming" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Programming</span></a></p>
Will Pettersson<p>Is there a standardised (or vaguely common) hostname akin to localhost that either a) only resolves to the IPv4 127.0.0.1, or only resolves to the IPv6 [::1]? In my experience, whether localhost resolves to an IPv4 or IPv6 address seems to be somewhat OS-dependent (or even system-dependent), I am wondering if there's a standard way to specify that I do want either the IPv4 version or the IPv6 version?</p><p>Why, you ask? I have a service on localhost that only listens on IPv4, but today localhost resolved to [::1] and it broke. Now I fixed it easily by specifying 127.0.0.1 as the server address instead of localhost in the upstream proxy, but it did make me start wondering.</p><p><a href="https://toot.cat/tags/tcpip" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>tcpip</span></a> <a href="https://toot.cat/tags/ipv4" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ipv4</span></a> <a href="https://toot.cat/tags/ipv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ipv6</span></a> <a href="https://toot.cat/tags/localhost" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>localhost</span></a></p>
who<p><span class="h-card" translate="no"><a href="https://mikrotik.social/@mikrotik" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>mikrotik</span></a></span> just released <a href="https://social.tchncs.de/tags/routeros" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>routeros</span></a> v7.18 with FastTrack/FastPath for <a href="https://social.tchncs.de/tags/ipv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ipv6</span></a>.</p><p>FastTrack is a hardware acceleration for stateful packet inspection, as far as i understood, and brought me already a huge throughput improvement on <a href="https://social.tchncs.de/tags/ipv4" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ipv4</span></a>. Its like a dream which is becoming true, that this is now available for <a href="https://social.tchncs.de/tags/ipv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ipv6</span></a>.</p><p><a href="https://social.tchncs.de/tags/Mikrotik" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Mikrotik</span></a></p>
Radio Azureus<p>1. ping localhost</p><p>2. ping 127.0.0.1</p><p>3. ping ::1</p><p>Fourty Five years ago I wrote 1<br>When I progressed further I wrote 2<br>Now I write 3</p><p>Pinging home just became simpler and simpler</p><p><span class="h-card" translate="no"><a href="https://fuzzies.wtf/@altbot" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>altbot</span></a></span></p><p><a href="https://en.wikipedia.org/wiki/Ping_%28networking_utility%29?wprov=sfla1" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">en.wikipedia.org/wiki/Ping_%28</span><span class="invisible">networking_utility%29?wprov=sfla1</span></a></p><p><a href="https://mastodon.social/tags/Networking" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Networking</span></a> <a href="https://mastodon.social/tags/basics" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>basics</span></a> <a href="https://mastodon.social/tags/localhost" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>localhost</span></a> <a href="https://mastodon.social/tags/IPV4" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IPV4</span></a> <a href="https://mastodon.social/tags/IPV6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IPV6</span></a></p>
Tommi Nieminen<p>P*rseensuti kun elämänsä voi tehdä itselleen vaikeaksi… Hakkaan hyvän aikaa päätäni seinään miettien, miksei <a href="https://mastodontti.fi/tags/virtuaalikone" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>virtuaalikone</span></a> suostu yhdistämään <a href="https://mastodontti.fi/tags/NAS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>NAS</span></a>'sin <a href="https://mastodontti.fi/tags/NFS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>NFS</span></a>-jakoa, vaikka asetusten pitäisi olla kunnossa ja NASsia pystyy <a href="https://mastodontti.fi/tags/ping" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ping</span></a>'aamaankin. Myös <a href="https://mastodontti.fi/tags/SSH" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>SSH</span></a>:lla pääsee kaikkiin koneisiin paitsi NASsiin.</p><p>No äh, minähän asetin juuri eilen virtuaalikoneiden <a href="https://mastodontti.fi/tags/IPv4" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IPv4</span></a>-osoitteen viimeisen oktetin alkamaan 130:stä, ja NASsilla torpataan osoitteet, joissa se on ≥ 128! <a href="https://mastodontti.fi/tags/atkjuttuja" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>atkjuttuja</span></a> <a href="https://mastodontti.fi/tags/miehenel%C3%A4m%C3%A4%C3%A4" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>miehenelämää</span></a></p>
aaron<p><a href="https://mastodon.social/tags/TIL" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>TIL</span></a>: You can use a /31 network for a point-to-point connection to avoid wasting the, in this case, unneeded network and broadcast addresses.</p><p>And, as it turned out, both <a href="https://mastodon.social/tags/MikroTik" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>MikroTik</span></a> and <a href="https://mastodon.social/tags/AVM" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>AVM</span></a> support this. As of RouterOS 7.17, the configuration is a little unexpected, however, I read that this will change in RouterOS 7.18. 🎉</p><p><a href="https://mastodon.social/tags/IPv4" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IPv4</span></a> <a href="https://mastodon.social/tags/Networking" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Networking</span></a></p>
samurro<p>I am trying to configure <a href="https://fosstodon.org/tags/pfsense" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>pfsense</span></a> <a href="https://fosstodon.org/tags/openvpn" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>openvpn</span></a> through alias instead of single CIDR notations, as soon as I make the changes, clients from the outside can't connect, even after restarting the openvpn server. But testing with a machine I have here through a mobile provider hotspot the new openvpn settings work. *scratches head* <a href="https://fosstodon.org/tags/sysadmin" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>sysadmin</span></a> <a href="https://fosstodon.org/tags/IPV6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IPV6</span></a> <a href="https://fosstodon.org/tags/ipv4" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ipv4</span></a></p>
André Machado :debian:<p>IPv4 and IPv6: Evolution, Key Differences, and the Engineers Behind the Protocols</p><p>The Internet Protocol (IP) serves as the foundational communication system for the internet, dictating how data packets are addressed and transmitted across networks. The two primary versions in use today are IPv4 and IPv6, each with distinct characteristics, histories, and contributions from various engineers.</p><p>Read More: <a href="https://machaddr.substack.com/p/ipv4-and-ipv6-evolution-key-differences" rel="nofollow noopener noreferrer" target="_blank"><span class="invisible">https://</span><span class="ellipsis">machaddr.substack.com/p/ipv4-a</span><span class="invisible">nd-ipv6-evolution-key-differences</span></a></p><p><a href="https://mastodon.sdf.org/tags/IPv4" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IPv4</span></a> <a href="https://mastodon.sdf.org/tags/IPv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IPv6</span></a> <a href="https://mastodon.sdf.org/tags/Computer" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Computer</span></a> <a href="https://mastodon.sdf.org/tags/Science" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Science</span></a> <a href="https://mastodon.sdf.org/tags/Network" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Network</span></a> <a href="https://mastodon.sdf.org/tags/Protocol" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Protocol</span></a> <a href="https://mastodon.sdf.org/tags/Networking" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Networking</span></a></p>
hallunke23 🇺🇦<p><span class="h-card" translate="no"><a href="https://mastodon.ie/@EugeneMcParland" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>EugeneMcParland</span></a></span> Yep, I also noticed that. And: The issue mostly affects <a href="https://troet.cafe/tags/ipv4" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ipv4</span></a>|only networks. As a result of this, Russia now scores 60% in <a href="https://troet.cafe/tags/ipv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>ipv6</span></a> rollout statistics when actual figures should be much lower. <a href="https://www.aelius.com/njh/google-ipv6/ru.html" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">aelius.com/njh/google-ipv6/ru.</span><span class="invisible">html</span></a></p>
gyptazy<p>Hey <a href="https://mastodon.gyptazy.com/tags/homelab" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>homelab</span></a> users!</p><p>You probably already know me by my free <span class="h-card" translate="no"><a href="https://mastodon.bsd.cafe/@BoxyBSD" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>BoxyBSD</span></a></span> project and I often got asked about IPv4 addresses. Currebtly, I tinker with a new but also honestly not free service. The idea is creating a static IP service for homelab users. I'm aware that there're already some around, so what could be some benefits here?</p><p>- Static single <a href="https://mastodon.gyptazy.com/tags/IPv4" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IPv4</span></a> &amp; <a href="https://mastodon.gyptazy.com/tags/IPv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IPv6</span></a> /48 (so you can subnet your homelab to several /64 without breaking <a href="https://mastodon.gyptazy.com/tags/slacc" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>slacc</span></a>)<br>- Bigger subnets (IPv4: /29, /28, /27 | IPv6: /32)<br>- Full RIPE personalization (inc. abuse &amp; Co)<br>- <a href="https://mastodon.gyptazy.com/tags/OpenVPN" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>OpenVPN</span></a>, <a href="https://mastodon.gyptazy.com/tags/Wireguard" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Wireguard</span></a>, <a href="https://mastodon.gyptazy.com/tags/GRE" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>GRE</span></a> Support<br>- Auto configure (e.g., you load the wireguard config on any client and the addresses Arena immediately bound to that interface)<br>- Split usage / multiple tunnels: Use different IPs from your subnets at different locations<br>- Integration into <a href="https://mastodon.gyptazy.com/tags/BoxyBSD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>BoxyBSD</span></a> <br>- Location in Germany or Netherlands (selectable)<br>- Hosted on redundant <a href="https://mastodon.gyptazy.com/tags/FreeBSD" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>FreeBSD</span></a> nodes </p><p>Pricing:<br>- The starter package probably around 10€/month (not more) + 15€ setup including 2T traffic <br>- Pricing for addiriinal/larger subnets not yet sure, probably higher setup fees to avoid hoppers and spamers to keep the addresses clean <br>- Optional traffic packages (when exceeding speed Limit of 10Mbit which should still be ok for most homelabs)</p><p>World this be interesting? Im aware that many ones already do this by VPS themselves, so this might just be a bit easier and optionally offering whole networks including RIPE personalizations.</p><p><a href="https://mastodon.gyptazy.com/tags/hosting" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>hosting</span></a> <a href="https://mastodon.gyptazy.com/tags/Server" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Server</span></a> <a href="https://mastodon.gyptazy.com/tags/kubernetes" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>kubernetes</span></a> <a href="https://mastodon.gyptazy.com/tags/Lab" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Lab</span></a> <a href="https://mastodon.gyptazy.com/tags/homelab" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>homelab</span></a> <a href="https://mastodon.gyptazy.com/tags/home" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>home</span></a> <a href="https://mastodon.gyptazy.com/tags/homelabs" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>homelabs</span></a> <a href="https://mastodon.gyptazy.com/tags/homelabcommunity" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>homelabcommunity</span></a> <a href="https://mastodon.gyptazy.com/tags/homelabnetworking" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>homelabnetworking</span></a> <a href="https://mastodon.gyptazy.com/tags/network" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>network</span></a> <a href="https://mastodon.gyptazy.com/tags/networking" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>networking</span></a> <a href="https://mastodon.gyptazy.com/tags/tunnel" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>tunnel</span></a> <a href="https://mastodon.gyptazy.com/tags/tunnelbroker" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>tunnelbroker</span></a> <a href="https://mastodon.gyptazy.com/tags/proxmox" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>proxmox</span></a> <a href="https://mastodon.gyptazy.com/tags/XCPng" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>XCPng</span></a> <a href="https://mastodon.gyptazy.com/tags/Virtualisation" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Virtualisation</span></a> <a href="https://mastodon.gyptazy.com/tags/virtualization" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>virtualization</span></a> <a href="https://mastodon.gyptazy.com/tags/traffic" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>traffic</span></a> <a href="https://mastodon.gyptazy.com/tags/BGP" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>BGP</span></a></p>
Jima :Compromise_bi_flag:<p>Does anyone know if you can get glue records set for delegations under ip6.arpa / in-addr.arpa? It crosses my mind "can you host reverse DNS without the benefit of a domain that you also have to pay for?"</p><p>I've set nameservers in ARIN's web UI, but it's been years and I no longer have any IP space under my authority.</p><p>(Believe it or not, this WASN'T promoted by the fediverse instance running on an ip6.arpa domain — I've got ONE follower who DOES know what prompted it, though. 🤭)</p><p><a href="https://mspsocial.net/tags/IPv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IPv6</span></a> <a href="https://mspsocial.net/tags/IPv4" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IPv4</span></a></p>
Paco Hope #resist<p>I am totally here for things like sticking <a href="https://infosec.exchange/tags/IPv4" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IPv4</span></a> A records into <a href="https://infosec.exchange/tags/DNS" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>DNS</span></a> zones that are meant for <a href="https://infosec.exchange/tags/IPv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IPv6</span></a> reverse PTRs. As soon as I saw <span class="h-card" translate="no"><a href="https://1.6.0.0.8.0.0.b.e.d.0.a.2.ip6.arpa/@domi" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>domi</span></a></span> as a profile, I had to follow. That's just ingenious as hell. </p><p>It's not DNS<br>It can't be DNS<br>It was DNS</p>
Paco Hope #resist<p><span class="h-card" translate="no"><a href="https://hachyderm.io/@mikael" class="u-url mention" rel="nofollow noopener noreferrer" target="_blank">@<span>mikael</span></a></span> This has been my experience with <a href="https://infosec.exchange/tags/verizon" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>verizon</span></a>. If I had Verizon residential IPv4, I’d get residential IPv6 automatically. To get static <a href="https://infosec.exchange/tags/IPv4" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IPv4</span></a> I had to go to Verizon Business, and <a href="https://infosec.exchange/tags/IPv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IPv6</span></a> was not available so I had to get a hurricane electric tunnel. <a href="https://infosec.exchange/tags/homelan" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>homelan</span></a></p>
Mikael Hansson<p>Sometimes I just get tired. I thought getting a public <a href="https://hachyderm.io/tags/IPv4" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IPv4</span></a> address was as simple as contacting my ISP and paying them some more money per month (for a service I've had for free up until now, of course).</p><p>Apparently they have to switch me over to a different comms operator to be able to provide me with a public address, though. And _that_ provider apparently can't provide <a href="https://hachyderm.io/tags/IPv6" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>IPv6</span></a> addresses in my area.</p><p>Have only heard one side of the story still, but this means I have to call around to my local communications operator and to various ISPs to try to see on what level the problem actually lurks. So far I've spent several hours trying to restore something that has been working perfectly for years - on top of getting a higher monthly bill for a worse selection of ISPs and service. Yay for monopolies... <a href="https://hachyderm.io/tags/selfhosting" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>selfhosting</span></a> <a href="https://hachyderm.io/tags/homelab" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>homelab</span></a></p>