this avali will trap ur plasma (shellbyte)
zaki@plasmatrap.com
i swear, why are some people just so fucking stubborn in not wanting to use ipv6 whatsoever
4
2
2
/Cinny 
@zaki
It’s different and that’s scary, and didn’t you know it’s evil.
CGNAT is a totally reasonable idea, we are doing just fine™ with IPv4 <small>/s</small>
0
1
1
@zaki piss poor support. my modem still bootloops if I try using a real v4+v6 dual stack configuration (instead of 464XLAT which fragments IPv4 packets), and my mobile ISP doesn’t care enough to support it at all.
i’d love to switch as a home server admin, but it Just Doesn’t Work
1
0
1
this avali will trap ur plasma (shellbyte)
zaki@plasmatrap.compiss poor support
something which can be true for some things still, unfortunately.
of note is that a lot of devices with poor IPv6 support also tend to also not very well support IPv4, though not all are such. meanwhile, the remaining are most often developments made by people that are apathetic to IPv6, or otherwise do not take it seriously.
1
0
1
this avali will trap ur plasma (shellbyte)
zaki@plasmatrap.com@ayameow i genuinely wonder if whatever ISP you’re on actually only does IPv6 with 464XLAT, perchance? and maybe when you try setting dual-stack on your modem, it gets going with IPv6 and without a v4, which maybe it doesn’t like?
2
0
1
this avali will trap ur plasma (shellbyte)
zaki@plasmatrap.com464XLAT which fragments IPv4 packets
tangential, but everyone being lazy and just setting a standard assumed fragment size of 1500 was such a mistake
god bless path mtu discovery
1
0
1
1
0
1
this avali will trap ur plasma (shellbyte)
zaki@plasmatrap.com
1
0
1
1
0
1
this avali will trap ur plasma (shellbyte)
zaki@plasmatrap.com
0
0
1
⠀ ⠀ ⠀ ⠀ stg
stag@mk.absturztau.be@zaki github still doesnt have ipv6. github, the website for devs, of all places
0
0
0
@zaki of course I nearly forgot to reply to this
I actually have no idea what exactly they do, because the customer support guy just told me to “reset to factory settings and disable IPv6” when I told him v4 sites barely load (??) with the v6 APN enabled.
On my old modem it would show both addresses (presumably) assigned via DHCP: a standard /64 for IPv6 and a CG-NAT address for IPv4 that could only respond to pings and load basic HTTP websites, nothing more. Changing the MTU wouldn’t fix this problem.
Either way, enabling IPv6 only on the new modem keeps IPv4 working, so you may be right that it’s doing 464XLAT now. But why would the old modem get both addresses, and this one dies? 
1
0
0
this avali will trap ur plasma (shellbyte)
zaki@plasmatrap.coma CG-NAT address for IPv4 that could only respond to pings and load basic HTTP websites, nothing more
yeah there’s definitely something fucked up on the provider’s end for full dual-stack, no wonder it wouldn’t like it
well, given that it’s a cellular-based provider, they’re most likely actually just going for IPv6 with 464XLAT for their deployment. it’s the most common i’ve seen; atleast 2 of the 3 major cell providers here do that, forgot what the other one does
the customer support guy just told me to “reset to factory settings and disable IPv6”
customer support people truly never know shit for fuck nowadays, bweh
0
0
0