(no title)
elsjaako | 3 months ago
Working for you != working for everyone
Basically functioning != Working as well as it could
There are more advantages to IPv6. We don't see all of the advantages because we can't use them, because we are still largely stuck in an IPv4 world. This is a problem caused by not enabling IPv6.
iso1631|3 months ago
I have to put firewall rules in anyway (as I don't want a random device on the internet to be able to talk to my bathroom speaker), so what's the difference?
I get an RTP stream pushed from a source, if I want it on my laptop I dst-nat it to my laptop, if I want it on my desktop I dst-nat it to my desktop, no need to change the destination on the source IP. How would I do that with ipv6 - DNS I guess, if the source supports DNS lookups (some do, most don't)
I also have the advantage of being able to steer outgoing traffic via either my DSL or via my 4g depending on various rules (including source IP, target IP, protocol, src/dest ports, DSCP tags etc). I believe I can do this with NPT on ipv6, same as on ipv4.
But sure, security through obscurity is useful.
In any case I still have to maintain an ipv4 network as some services still won't work on ipv6 only subnets (even with NAT64 and DNS64), so the choice is either having an ipv4 network, or having an ipv4 and ipv6 network.
The former is less work and more secure.
elsjaako|3 months ago
It's great that your ISP does that. Mine doesn't, maybe it would for an extra charge if I got some kind of business account. Which makes sense, as the IPv4 addresses your ISP own are a valuable resource.
At the hacker space I'm part of we need to use a reverse proxy to run all our services on a single IPv4 address we get from our ISP.
> I have to put firewall rules in anyway (as I don't want a random device on the internet to be able to talk to my bathroom speaker), so what's the difference?
If, for example, two friends want to play a FPS game with each other they could connect directly. They still need to "punch" out to get the firewall open, but you lose the step where you have to guess at which port the message may end up. Right now I hear that with some ISP's you don't even get a public IP on your router, so even NAT hole punching doesn't work.
Not a lot of games currently provide the option to connect directly, but that's because it often doesn't work well behind NAT on IPv4 networks.
> I get an RTP stream pushed from a source
This sounds like a pretty niche application, but sure. I don't have the immediate best Ipv6 solution for you. Maybe you could switch which device has the RTP-receive IPv6 address (one device can have multiple IPs), you could do NAT on IPv6 for this application.
Right now you're using the NAT as a kind of forwarder to send the data to different hosts, so if you have a router you can run software on you could just have it forward to both devices on the local network.
> I also have the advantage of being able to steer outgoing traffic via either my DSL or via my 4g depending on various rules
Aren't these features of your router, not of your IP stack?
> In any case I still have to maintain an ipv4 network as some services still won't work on ipv6 only subnets.
You're right, it doesn't always make sense for an individual to switch. That's why we're still stuck on old technology.
But prices for IPv4 addresses are going up. There are already VPS's that charge less if you don't need IPv4. Availability of IPv6 for consumers is going up; In India it's near 80%. At some point, some kind of service in India is going to not bother to get IPv4.
magicalhippo|3 months ago
Of course, once you figure out it's IPv6 related you can then work on figuring out what's actually going on.