#ipv4 is hell

So much easier to go #ipv6 only.

Hello le #fediverse ! J'envisage peut-être de passer mes instances #peertube, #friendica, #pixelfed et #mastodon vers des serveurs full #ipv6 (des tests sont en cours avec pixelfed), ce qui me permettrait d'avoir une ip publique différente par machine, ce qui n'est pas le cas avec #ipv4, tous mes services tournent sur une même machine (ça fonctionne mais ce n'est pas très safe). Êtes-vous prêts pour le 100 % #ipv6 ? Vos réponses m'aideront à prendre une décision

Проброс сайта, не имеющего глобального IP-а́дреса, из локальной сети на свой сервер в Интернете (обратный прокси) через сеть Yggdrasil
https://multed.com/2024/04/03/nginx-and-yggdrasill.html

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?

No way I can properly explain this in 500 characters, but the short version is this:

Don't use a shared IP address for your website/app and expect zero issues.

If your cloud hosted app/website happens to share an IP address with another app that scans the entire internet, don't be surprised if your app/website gets blocked and your customers can't reach you. :(

In this case, that IP address is 199.36.158.199. Take a look at the SSL cert for all the domains hosted there.

#networking #ipv4

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.

@altbot

#bash #sh #zsh #ksh #csh #Networking #IPv6 #IPv4 #ProxMox #freeBSD #Linux #POSIX #Programming

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

@altbot

https://en.wikipedia.org/wiki/Ping_%28networking_utility%29?wprov=sfla1

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.

Here's a networking problem that I came across today. An ISP has a /19 netblock. Is there any technical reason why they shouldn't give out the last address in that block (xxx.xxx.255.255) as a customer address? #networking #ipv4 #cidr

I am totally here for things like sticking #IPv4 A records into #DNS zones that are meant for #IPv6 reverse PTRs. As soon as I saw @domi as a profile, I had to follow. That's just ingenious as hell.

It's not DNS
It can't be DNS
It was DNS

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

Orange partage à son tour par défaut les IPv4 pour les abonnés ADSL et fibre http://dlvr.it/THVyRP #Orange #IPv4

I just updated a little hobby project of mine: https://testmyconnection.net/
It's a website to quickly see if you have #IPv4 and #IPv6 connectivity.
It also features a tool to check if a given website is on- or offline, something that has a lot more failure modes than you would expect. There are other tools out there that do the same, but honestly, they all fail one way or another when it comes to IPv6. (I have a table with details, go look!)

I will probably have to add a table of speed tests too?

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.

Build it and they will come.

Just another typical day on a dual stacked college campus.

#ipv4 traffic is typically well below #ipv6 traffic.

On this graph, the dark blue is incoming ipv4 traffic and the lighter blue is incoming ipv6 traffic.

I got asked if I could create a #howto for creating a (public) #NAT64 service - just like I did recently for #BoxyBSD. With #DNS64 and #NAT64 you can also reach resource in the legacy internet (#IPv4) on #IPv6 only systems.

While this is based on #unbound and #tayga, there’s also a solution by using the #OpenBSD's native way which is also running on the other gateway. I’ll share a second how to how to do this in OpenBSD and pf.

https://gyptazy.com/howto-create-a-public-dns64-nat64-gateway/