NAT64 - Viewing IPv4 Websites Via IPv6 With Tayga
Вставка
- Опубліковано 7 тра 2023
- If you use an IPv6 only network, you will not be able to access servers that are IPv4 only. By using Tayga in a Raspberry Pi router, you can translate the IPv4 address of the server into an IPv6 address that your host can use. This video shows the setup and some packet captures of how it works.
- Наука та технологія
Perfect timing. I was searching for a 6 to 4 gateway this morning 🙏
I just use the hotspot on my phone through a travel router (mango) in repeater mode. I let the DNS server handle it's job. Back when I worked for an ISP, I used to deal with IP addresses and all that stuff. Good video. I use quad9 for DNS.
Awesome, thanks! I will definitely implement that too, when I've got the time... Now only a video 464XLAT is missing ^^ ;)
Maybe it is worth setting up your own DNS64 so you do not rely on someone else's service
Exactly what I was thinking. It's not like it's complicated, there must be a package you can install to do it and it must surely be a tiny package.
@@BrianG61UK bind9 does it out of the box - just a couple lines of config (or 1 if you like your configs compact) ... dns64 64:ff9b::/96 { clients { any; };};
@@JMannus65 Bind9 seems like it's rather a big lump of extra stuff to be installing and running on my little router.
@@BrianG61UK DNSProxy exists and does DNS64; and if you happen to be running Adguard Home (or any variation of the same principle) it may have either the version of BIND or DNSProxy that supports the DNS64 solution you're looking for..
@@FatherlyFox Looks like AdguardTeam have a dnsproxy server with DNS64
I believe OpenWRT uses Jool, which uses an in-kernel module instead of Tayga, I assume this is more efficient.
❤ same as my LAN
I might see if I can try this, mainly because I'm curious to see how much is breaks. Most obviously any devices, software or protocols I'm using that don't properly support IPv6 will fail.
Very little, but with exception of some applications like doing P2P calls where the application expects to have a local IPv4 address.
Well, there is a reason why almost nobody uses IPv6 atm. Or not willingly, most people try to avoid IPv6 as much as possible.
Providers just give you a shitty DS Lite connection, but at least here I often see problems with the CG-NAT AFTR-servers being often unstable, down or just unresponsive and people then complain that half of the internet is dead..
@@hermannschaefer4777 Quite a lot of people, including me, use dual stack. Many ISPs will give you dual stack by default.
could you please make a tut on acccesing an ipv6 only server from ipv4 client configuring Bind9 and tayga.
In TAYGA's conf: ipv4-addr 192.168.255.254, while nat64 interface gets 192.168.254.254. Is that on purpose?
As I understand it, this takes care of IPv4 for internal networks when visiting websites, etc., but doesn't allow an application on your clients to have an IPv4 address when it needs 1, you need something like 464XLAT on the client device for that. That's what T-Mobile US has started doing at scale in 2013.
No, what he shows is 464xlat.
The only difference to what T-Mobile is doing, is that his Router (CPE) is doing PLAT with Tayga instead of the ISP.
And yes you are right, you will not get an IPv4 address on the client with this. You still need dual-stack for that.
This looks good so far, but what if the WAN connection doesn't have an IPv4 address (which is the case for lot of fibre providers here in Germany). Would it be possible to run tayga on a VPS which has IPv4 and IPv6 and then tell the local router to use the VPS endpoint?
I also wonder if this would work with VPN connections like Wireguard from an IPv6 only host to an IPv4 only Wireguard server.
works with ds-lite too
Who needs twitter anyway?
I just had a strange experience with comcast. I called them to ask if there was an outage in the area. I was told no, but they said they wanted to send a refresh to the modem. Before she could do that, I got reconnected without that. Yet she said she wanted to send a 'permanent signal, so it would never happen again. I knew that sounded made up and strange. Then she wanted the mac address on the back of the modem. I didn't think I wanted to do whatever she was doing, but for some reason went with that. A few minutes later i reconnected and youtube worked. Soon after that I realized IPV4 Websites no longer work in win 7, but youtube does. Nothing works, including youtube if I boot to a drive with windows 10, which is weird. I was thinking, what in the world could she have done. She never told me and I lost the call. Do you have any ideas what she could have happened? I called ask them to just put it back, but for hours no one could help me. They said something about my modem being older. I had also called to ask them to downgrade my service after finding out I had been paying for 150 to 200 mbit service I never ask for. I asked why would I need a newer modem if my old one could go faster than the 75 I wanted. No answer. If you have any idea how or why I could lost the ability to use IPV4, I'd appreciate knowing if you know. thanks