Album

joined 1 year ago
[–] Album@lemmy.ca 10 points 5 months ago (13 children)

It's honestly super simple to set up. Outside of your ISP config it's almost all autoconfig. 100% of the complication (at least for me) comes from knowing ipv4 first for 20 years and then trying to incorrectly map those concepts to V6.

As soon as I "let go" it was fine.

There's not a huge net benefit you're right. I mostly wanted to learn and I hope to be at the front edge of disabling ipv4 in the near distant future.

[–] Album@lemmy.ca 3 points 5 months ago (2 children)

I agree with this but I would say the prefix is the only thing you should focus on.

It's important that ISPs don't regularly rotate your PD and it's part of the rfc recommendations that they don't. And the remainder of the prefix is your vlan space that is as important for VLAN routing as always.

[–] Album@lemmy.ca 27 points 5 months ago* (last edited 5 months ago) (18 children)

Ipv6 requires fundamental rethinking about how addressing is done. If you're trying to apply v4 concepts to V6 you likely end up running into something they intentionally designed out.

A unique local address is an address space where you could do that. It's the equivalent to RFC1918 eg. 172/192/10. So you could statically assign fd0::x, and that is expected, but not required generally.

I wouldn't give each device a static unique global address unless they need to be accessed via wan without domain consistently. You lose device privacy really quickly that way because every device gets a unique globally routable address. It's fine for internet facing services but most Linux, Windows, and mobile implementations are using ipv6 privacy extensions by default to ensure you get a random GUA every day.

My network is dual stack and I connect mostly over ipv6 to all my internal clients using internal DNS. If my internal DNS is ever down I can fall back to ipv4 or it's basically the one box on my network with an easy to remember ULA.

[–] Album@lemmy.ca 1 points 5 months ago

Super cool!!

[–] Album@lemmy.ca 1 points 5 months ago* (last edited 5 months ago)

They can do it all they want but it won't work...

If I "opt in" it falls back to non doh immediately because using doh on my network is not up to Chrome.

use-application-dns.net + nxdomain for any known doh provider

I don't use pihole but doh blocking works great on my network. It should work on a pihole tho it's pretty basic stuff.

If you can't resolve the domain you can't validate the TLS certificate.

[–] Album@lemmy.ca 11 points 5 months ago (3 children)

It's not up to Chrome.

[–] Album@lemmy.ca 5 points 5 months ago* (last edited 5 months ago)

Chmod +t

And then chown root

[–] Album@lemmy.ca 1 points 7 months ago

Create a shell script to launch the Python script but make it the last call.

Then before it add commands for whatever method you update with.

[–] Album@lemmy.ca 2 points 7 months ago (1 children)

Fwiw I'm not American.

[–] Album@lemmy.ca 19 points 7 months ago

If tiktok can be considered owned by the Chinese gov so can facebook https://en.m.wikipedia.org/wiki/PRISM theres tons of programs secret and public that shows american tech companies have to obey to the US government demands.

"In 2014, ByteDance established an internal Chinese Communist Party (CCP) committee.[47] The company's vice president, Zhang Fuping, serves as the company's CCP Committee Secretary.[48][49]"

This is not a defense of FB or american companies, but rather an indictment of tiktok and an acknowledgement that the degree of CCP involvement in tiktok is not the same as neolib involvement in FB.

[–] Album@lemmy.ca 91 points 7 months ago (13 children)

It's almost like making money is not the primary purpose of this website 🤔

view more: ‹ prev next ›