4 ms·
Accessing an IPv4-only website from IPv6 is not a major problem. A NAT64 gateway to access such legacy services works fine. IPv4-only clients is another issue.
by icebraining 7y ago
Accessing an IPv4-only website from IPv6 is not a major problem. A NAT64 gateway to access such legacy services works fine. IPv4-only clients is another issue.
- p1mrx 7y agoRunning an IPv4-only website becomes a problem as ISPs migrate their IPv4 traffic to NAT44/NAT64, and you can no longer tell users apart for abuse detection purposes.
- icebraining 7y agoIf you run a dual-stack site, the attackers can just use your IPv4 (if their ISP gives them a private one) or the equivalent NATed IPv6 (forcing the use of NAT64) instead of your real IPv6.
- p1mrx 7y agoSure, but you can block the attacking IPv4 addresses without affecting normal IPv6 users. This is why it's a good idea for ISPs to deploy IPv6 alongside NAT, and for browsers to prefer IPv6 by default.
- blotter_paper 7y ago> you can no longer tell users apart for abuse detection purposes s/abuse detection/tracking As a user, this sounds like a feature -- but really, there are a ton of other metrics to track most users by (assuming we're talking about abuse done via the actual website interface rather than just flooding ports with packets from a specific IP).
- fakename11 7y agoI doubt this website would even be up if they had no abuse detection.