OS in considerations :
Windows Server 2008+
We are adding IPv6 support in a complex client-server network application. Server opens many ports for listening, and different types of clients connect to different ports.
We are considering multiple scenarios including :
- Server on pure IPv6, client on pure IPv6
- Server on pure IPv4, client on pure IPv4
- Server on pure Dual-stack, client on pure IPv6
- Server on pure Dual-stack, client on pure IPv4 (Tunneling we are yet to figure out)
Related to server machine my question is : Is it safe to assume that in production machines, which are
Pure IPv6 will still have
IPv4 working at OS level ? To rephrase, whether production machines which are
Pure IPv6, will still have
IPv4 loopback address working in the system ?
IPv6 I have found stated here that it's mandatory part of OS, and at least there is no way to disable
IPv6 loopback. But it's possible for
I have two concerns here :
My Server app is written in Java. And if I disable IPv4 at OS level by using
netsh interface ipv4 uninstall, most of Java's network apis stop working, as they don't support this configuration yet. Link.
In my server app, there are few ports listening on
127.0.0.1because they must be accessed from same machine. So should I be worried about those if I make sure that code connects to these sockets using
127.0.0.1only and not using