Do we still need #IPvLegacy / #IPv4 at #Chaos / #CCC Events?
Recent searches
Search options
#ipv4
1 post1 participant0 posts today
Just wanted to share some thoughts on #RFC9715 - an #RFC that defines standards on reducing the #DNS issue of IP fragmentation over #UDP. It's not a long read, but a good one for everyone who understands the issues of large UDP responses on the #Internet. A great leap forward to (hopefully) reduce the reflection/amplification #DDoS potential of DNS.
Just today I learned that #Google 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 #TCP.
Question to the network people out there:
Are there any ISPs that are IPv6 only (without providing a NAT/whatever)?
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?
It would be nice if infosec and IT tools provided better IPv6 support.
Weren't we supposed to run out of IPv4 addressees 10 years ago? What happened to the IPv6 revolution?
IPv4 and IPv6 addresses
Start: 15 April 2025 3:00 pm
End: 15 April 2025 5:00 pm
15th April 2025 at 3pm UK
This month we look at IP (Internet Protocol) addresses, including both IPv4 and IPv6. The talk includes a brief description of IPv4 addresses, problems with IPv4, IPv6 addresses and current IPv6 status.
Joining details will be emailed to subscribers nearer the time. If you aren’t a member, it’s free to join here https://u3acommunities.org/subscribe-to-computing-forum/.
Plenty of time is reserved for discussions.
TIL about lsd(1)
What an awsome addition to my lolcat arsenal!
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!
`man lsd `
An ls command with a lot of pretty colors and some other stuff.
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?
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.
@mikrotik just released #routeros v7.18 with FastTrack/FastPath for #ipv6.
FastTrack is a hardware acceleration for stateful packet inspection, as far as i understood, and brought me already a huge throughput improvement on #ipv4. Its like a dream which is becoming true, that this is now available for #ipv6.
1. ping localhost
2. ping 127.0.0.1
3. ping ::1
Fourty Five years ago I wrote 1
When I progressed further I wrote 2
Now I write 3
Pinging home just became simpler and simpler
https://en.wikipedia.org/wiki/Ping_%28networking_utility%29?wprov=sfla1
Which #HTTP status code do you expect, if you connect to a #IPv6 only Webserver via #IPv4.
Talking about the situation, where the Website only has an #AAAA record, but the Webserver is also addressable via IPv4 (for other Websites). So one could contact the Webserver via IPv4 and pass the the #DNS name of the IPv6 only Website as Host header, which is the scenario that i want to reject - but what status code is appropriate?
IPv4 and IPv6: Evolution, Key Differences, and the Engineers Behind the Protocols
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.
Read More: https://machaddr.substack.com/p/ipv4-and-ipv6-evolution-key-differences
Replied in thread
@EugeneMcParland Yep, I also noticed that. And: The issue mostly affects #ipv4|only networks. As a result of this, Russia now scores 60% in #ipv6 rollout statistics when actual figures should be much lower. https://www.aelius.com/njh/google-ipv6/ru.html
www.aelius.comGoogle IPv6 Country Adoption - Russia
Hey #homelab users!
You probably already know me by my free @BoxyBSD 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?
- Static single #IPv4 & #IPv6 /48 (so you can subnet your homelab to several /64 without breaking #slacc)
- Bigger subnets (IPv4: /29, /28, /27 | IPv6: /32)
- Full RIPE personalization (inc. abuse & Co)
- #OpenVPN, #Wireguard, #GRE Support
- Auto configure (e.g., you load the wireguard config on any client and the addresses Arena immediately bound to that interface)
- Split usage / multiple tunnels: Use different IPs from your subnets at different locations
- Integration into #BoxyBSD
- Location in Germany or Netherlands (selectable)
- Hosted on redundant #FreeBSD nodes
Pricing:
- The starter package probably around 10€/month (not more) + 15€ setup including 2T traffic
- Pricing for addiriinal/larger subnets not yet sure, probably higher setup fees to avoid hoppers and spamers to keep the addresses clean
- Optional traffic packages (when exceeding speed Limit of 10Mbit which should still be ok for most homelabs)
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.
Danmark er et velfærdssamfund, men vi skulle eftersigende også være et meget digitaliseret samfund. I mange år har mange råbt op om at der ikke er mange IPv4 adresser tilbage og derfor skal vi implementere afløseren IPv6.
Det er glædeligt at mstdn.dk understøtter IPv6, men hvor er resten af Danmark?
Test i en browser, på arbejdet og hjemmefra på: https://ipv6-test.com/
I was thinking recently about how /not/ deploying #IPv6, and making your services accessible via IPv6 was discriminatory
Public #IPv4 addresses are now a scarce commodity, and some old/large orgs have historical allocations of them such that they don’t *need* to deploy v6. But many developing and/or poorer nations don’t, and rely heavily on IPv6 for public internet access
If your service isn’t accessible via IPv6 you're effectively discriminating against those users who can't afford IPv4
The #BoxyBSD project is taking a pause from provisioning completely free #vps instances / #vserver. For further questions, reach out to @gyptazy or in our Matrix chat.
After publishing the new self-service portal and making it easier to use and get a free VPS instance, we got a lot more new users who requested an instance than usual. We’re not out of resources but we want to provide a great and reliable service and have a buffer for upcoming things.
We’re already restocking the resources and adding new nodes to the project but temporary stop provisioning new instances. In the meantime, we will provide new services that will make the overall experience for users much better and easier.
We already started this with the new #NAT64 gateways and the new free #loadbalancing service that allows you to serve your website also on #IPv4, even your box is #IPv6 only.
We’re addicted to the #BSD community and hope to provide your quickly more #FreeBSD, #NetBSD, #OpenBSD, #DragonflyBSD and all the other bsd based systems again. In the meantime - have fun and #RUNBSD
We just added a free #loadbalancing service to #BoxyBSD!
This new feature got added by @gyptazy in addition to the newly introduced #NAT64 gateways to make your life easier and is currently tested with a few users! This provides you the ability to make your website also reachable by #IPv4 even your box is only running on #IPv6. This feature can be managed from your self-service portal and simply requires you to add a DNS name that should be balanced and to point the DNS A record to a given IPv4.
Making the legacy internet life easier, we hope for a higher #BSD adaption where people might be more motivated to try #FreeBSD, #NetBSD, #OpenBSD or even #opensolaris with #illumos.
