Technology

378 readers

1 users here now

This magazine is dedicated to discussions on the latest developments, trends, and innovations in the world of technology. Whether you are a tech enthusiast, a developer, or simply curious about the latest gadgets and software, this is the place for you. Here you can share your knowledge, ask questions, and engage in discussions on topics such as artificial intelligence, robotics, cloud computing, cybersecurity, and more. From the impact of technology on society to the ethical considerations of new technologies, this category covers a wide range of topics related to technology. Join the conversation and let's explore the ever-evolving world of technology together!

founded 2 years ago

So after reading many articles going 'Don't use NAT66', I'm experimenting deploying NAT66 to provide IPv6 internet access to some VLANs on my network. (kbin.social)

submitted 1 year ago by 0spkl@kbin.social to c/tech@kbin.social

2 comments fedilink hide all child comments

So after reading many articles going 'Don't use NAT66', I'm experimenting deploying NAT66 to provide IPv6 internet access to some VLANs on my network.

I've tried asking my ISP for anything better then a /64, but apparently they are either unwilling, or unable to provide that. And every. single. ISP. in my country (Malaysia) is giving out /64 prefix delegations.

So on my test network, which is a VLAN (w/ WiFi) routed by an OPNSense instance running on one of my proxmox hosts, I've been testing it and it seems to work well enough I suppose. Well, at least better then HE TunnelBroker, speed wise anyway.

Unless anyone knows of any other approaches I can use for this?

#tech

you are viewing a single comment's thread
view the rest of the comments

[–] 0spkl@kbin.social 1 points 1 year ago

@kronicd Unless android has implemented DHCPv6 and nobody is talking about it, no, no it's not. It would still need me to route the entire /64 to one network after all for SLAAC.

Unless you're suggesting I install more-specific routes on the other networks? maybe a /65 or /66 on them? But in that case, wouldn't the main network, with it's full /64 prefix, have issues reaching those other hosts... hmm. Unless I deploy it with ULA addresses too. And treat the GUA addresses as just for internet connectivity.

Might still have to NAT66 it for other networks that may see android devices...

Might experiment with it once my opnsense box arrives I guess. Don't want to muck around with that on openwrt.
I just wish I got like a /60 at least.

I suppose tunnelling to a VPS is one option, but I'd rather use NAT66 over that because it'd have better throughput/latency.