Hello,
If I run:
./stunserver --protocol --family 6
Then I'll only get a listener on all IPv6 interfaces, that still accept IPv4 connections through a tunnel (which seems automatic since I never configured one on my Debian 7).
As a result, when discovering my own IPv4 address (no IPv4 at home), the STUN server will send me my IPv4 with an IPv6 prefix, such as:
::ffff:2.2.210.249
Instead of:
2.2.210.249
In order to fix it, I tried to start stunserver both on all IPv4 interfaces and IPv6 interfaces, without any tunneling, but stunserver refuses to start in IPv4 if it is already launched on IPv6. Reverse is the same. Reason: "Address already in use".
That's weird since I have an XMPP server which is listening on both 0.0.0.0 and :: and servicing users without any tunnel in case they are IPv4.
My question: is that a bug or a feature? Is there any way to override this, and have stunserver running both on IPv4 and IPv6 interfaces, and serving users their appropriate IP address without tunneling?
Thanks in advance ;)
PS: powering stun.jappix.com
I reverted stunserver to IPv4 for now on this server, don't test there.