@lina@vt.social
# ip -6 route show
anycast 2604:5500:706b:: dev eth1 proto kernel metric 0 pref medium
2604:5500:706b::/64 dev eth1 proto ra metric 1005 expires 2591846sec mtu 1500 pref medium
anycast 2604:5500:706b:3e00:: dev eth0 proto kernel metric 0 pref medium
2604:5500:706b:3e00::/64 dev eth0 proto dhcp metric 1003 expires 21474836sec pref medium
unreachable 2604:5500:706b:3e00::/56 dev lo proto dhcp metric 1001 pref medium
@lina@vt.social
and of course default via the link-local address on the headend:
default via fe80::629c:9fff:feb4:2ca8 dev eth1 proto ra metric 1005 expires 1646sec mtu 1500 pref medium
why i have not done this already? my IPs are in various GeoIP databases as “content” IPs, so they will be treated as if I were using a VPN company.
holy fuck y'all, i decided to fuck around with things and it's so much worse than i thought initially.
after about an hour of fucking around, i discovered google fiber is handing out duplicate ipv6 prefix delegations... ones which are being actively used by other customers. 😱
here's the email i just sent to their tech support, which i am sure won't be read, but whatever.
https://distfiles.ariadne.space/grumpy-google-fiber-email.txt
this is what it looks like when your ISP gaslights you because they can’t be bothered to fix their DHCPv6-PD setup
why fix problems when you can gaslight instead?
i am very close to just deploying a virtualized headend at my colo which is 0.4ms ping from my house. seriously.
why i have not done this already? my IPs are in various GeoIP databases as “content” IPs, so they will be treated as if I were using a VPN company.
i really should not have to have the “look, i am a well-known security engineer, when i say i am not getting ipv6 traffic i mean it and will publish this interaction on my blog if you all don’t fix it” conversation with my ISP (google fiber)
this is what it looks like when your ISP gaslights you because they can’t be bothered to fix their DHCPv6-PD setup
why fix problems when you can gaslight instead?
i am very close to just deploying a virtualized headend at my colo which is 0.4ms ping from my house. seriously.
i really should not have to have the “look, i am a well-known security engineer, when i say i am not getting ipv6 traffic i mean it and will publish this interaction on my blog if you all don’t fix it” conversation with my ISP (google fiber)
i don’t know who needs to hear this but that LLM “girlfriend” you installed on your phone doesn’t actually love you back
“if jesus is real, why is your hairline receding?” and other things i ask street preachers
fuck SPD
anywho, if you happen to be on an instance that is shutting down, and you want an invite here, just DM me, and i'll make you an invite link so you can bypass screening.
Ariadne Conill 🐰
:therian: