4 ms·
But no v4 devices support this "four socks requests wrapped like an onion" thing you're proposing, so how would they work with it?
by Dagger2 2y ago
But no v4 devices support this "four socks requests wrapped like an onion" thing you're proposing, so how would they work with it?
- GoblinSlayer 2y agoSocks goes on application layer, hardware sees it as normal tcp/ip4.
- Dagger2 2y agoApplications don't support it either, and if the hardware is seeing normal v4 then you're limited to sending to v4 destinations. How is this helping?
- GoblinSlayer 2y agoIt would help everything else, applications are not the only part of the network (and many already support socks), there are middle boxes, DHCP, NAT, firewalls, reverse proxies, LAN services and what not that don't need to be aware of new addressing scheme. Firewalls might benefit from it, but even they would still mostly work, even if with less than perfect precision. And even applications can benefit from simplification due to absence of dual mode sockets and no need for two sockets to listen on 0.0.0.0 and [::].
- Dagger2 2y agoMany already support SOCKS, but not this 4-layer thing you're suggesting. How can a device, application, whatever that doesn't have support for this use it to handle longer addresses? How can it communicate with a remote node that doesn't have support? How can that remote node communicate back? If you just want to transport v6 over an existing v4 network there are already approaches to do that in v6.