@quad @kura I have the same problem with #IPv4only Internet, but worse as using https://tunnelbroker.net will get me #geoblocked (despite choosing FRA as PoP since entire ASNs get geolocated!) and thus using a GIF-Tunnel to get #IPv6 is worse than having #noIPv6 and only #IPv4...
#IPv4only
@hallunke23 @q They do have AAAA RRs for the apex domain but no AAAA for the webserver www, where you are redirected.
Additionallysome of the secondary services and JS providers are not enabled. If you are a customer, the portal is #IPv4only. Sadly.
See also:
https://testmyconnection.net/#sipgate.de
https://testmyconnection.net/#www.sipgate.de
@tschaefer
@forwardingplane do you know the reason for being #IPv4only?
Launching service like this around 6th June makes me sad. #dns4eu #ipv4first #ipv4only
https://stat.ripe.net/widget/dns-chain#resource=protective.joindns4.eu
@destiny yes, but that deoends on your ISP, Internet Setup, Firewall and how shoved your NAT table is.
If you have proper Dual-Stack (static #IPv4 + #IPv6 /64 subnet) then you should be able to get that.
If you have #IPv4only and/or #CGNAT then this will throttle you just like when you have an #ISP that doesn't properly #peer or even acts as #racketeer towards other providers and sabotages #P2P like #KT from #SouthKorea.
I was able to max oit the wifi at my university for downloads in the past...
wurde, also zu einer Zeit, wo es bereits normalisiert ist, dass ca. 70% aller Jabber- und Mastodoninstanzen #IPv6 können.
Aber was machen die bei Bluesky?
Tja...
Die haben ernsthaft in ihre Spezifikationen reingeschrieben, dass jede AT-Instanz #IPv4 unterstützen muss. Und dann haben sie ihre eigene Infrastruktur als #IPv4only ausgerollt.
DAS ist Bluesky.
(5/5) @Sascha
Ach ja, ich hab das mit der Verweigereransprache schonmal bei der Mastodoninstanz der Bundesregierung (Deutschland) versucht.
Die haben sich ernsthaft hinter ihrem Hoster versteckt (T-Systems) und gemeint, dass es nicht ihr eigener Fehler wäre, dass sie sich einen Hoster ausgesucht haben, bei dem die Grundfunktionialität fehlt.
@landley @jschauma @ryanc @0xabad1dea yeah, the exhaustion problem would've been shoved back with a #64bit or sufficiently delayed by a 40bit number.
Unless we also hate #NAT and expect every device to have a unique static #IP (which is a #privacy nightmare at best that "#PrivacyExtensions" barely fixed.)
- I mean they could've also gone the #DECnet approach and use the #EUI48 / #MAC-Address (or #EUI64) as static addressing system, but that would've made #vendors and not #ISPs the powerful forces of allocation. (Similar to how technically the #ICCID dictates #GSM / #4G / #5G access and not the #IMEI unless places like Australia ban imported devices.
I guess using a #128bit address space was inspired by #ZFS doing the same before, as the folks who designed both wanted to design a solution that clearly will outlive them (way harder than COBOL has outlived Grace Hopper)...
- Personally I've only had headaches with #IPv6 because not only do I only have #IPv4only #Internet but my #ISP refuses to allocate even a singe /64 to me (but has no problem throwing in a free /29 of #IPv4's in with my contract!)and stuff like #HurricaneElectric / #HEnet's #Tunnelbroker fail face first due to #Geoblocking and the fact that #ASNs get geolocated, not their #PoPs...
If I was @BNetzA I would've mandated #DualStack and banned #CGNAT (or at least the use of CGNAT in #RFC1918 address spaces) as well as #DualStackLite!
@shoppingtonz @alternativeto @torproject also every #Tunneling - regardless if #SSH or #VPN or whatever - will inevitably introduce #latency (unless you happen to be customer of a shitty #ISP with horrible #peering and thus can cut down on hops needed, which is AFAIK only a theoretical scenario)...
- Outside of circumventing #Geoblocking and bypassing #IP-based #Banning (i.e. for #Cheating) I've not seen any use-cases.
In fact I stopped using #HEnet #Tunnelbroker and #IPv6-#GIF-Tunneling because it created more issued than it solved on my #IPv4only #Internet connection…
I do that with #pfSense & #OPNsense (depending on the exact network in question) and have it merge multiple sources that get cached.
In total, I do may out the 30 DNS servers and whilst I have #IPv4only, I have everything ready for #DualStack (#IPv4 + #IPv6) once my ISP stops keeing it's thumbs um their ass...
#WhatsMissing: A tool to check if #TorBridges are still available/online/reachable that one can use either #standalone (with #TorBrowser and/or #Tor Expert Bundle) or on @tails_live / @tails / #Tails.
- Cuz I do run into issues and kinda want to sort #Bridges by availability so I don't waste time on a #TorBridge that is down and also thin-out the list of bridges that ain't online anymore.
Whilst I do acknowledge that @torproject do disrecommend having a huge list of Tor Bridges on hand, I do regularly need them for contacts who are behind a #GreatFirewall and can't #SSH-Tunnel out of it.
- Sadly #BridgeDB doesn't offer good #filtering options so one can't just query types effectively like "I need #webtunnel on #IPv4" or "I can only use Ports 80 & 443 on #IPv6" which may work.
Espechally being able to filter for #IPv4only and not just #IPv6only is something I miss, alongside the filter for #PluggableTransports type as @guardianproject #Orbot seems to only handle #obfs4 and not webtunnel or #meek at all...
- I'm pretty certain that merely pinging a bridge at it's port isn't working as a shure-fire way to check for it's availability.
Client Info
Server: https://mastodon.social
Version: 2025.04
Repository: https://github.com/cyevgeniy/lmst