Server Portforwarding Unity Media

[Arbo]

Hallo liebe Leute,

ich bin UnityMedia Kunde und möchte gerne meinen eignen Server erstellen, um mit meinem Freunden online spielen zu können. Dazu muss ich laut OTTD-Wiki:
1) In meiner Firewall die Ports 3979, 3978 für TCP und UDP freigeben (check)
2) In meinem Router die Ports 3979, 3978 für TCP und UDP weiterleiten (the big problem)

Jetzt ist das Ding, dass die Connectbox von UnityMedia das sogenannte Portforwarding nicht unterstützt (siehe https://community.unitymedia.de/questio ... onnect-box und https://forum.feste-ip.net/viewtopic.php?t=104)

Nummer 1) hat super geklappt. Und meine Freunde und ich haben auch schon im Internet zusammen gespielt, allerdings eben nicht UNSERE Karte, sondern irgendeine Karte von irgendeinem der "angekündigten" Server. Wir würden aber gerne unsere eigene Karte erstellen und online spielen. Da Nummer 2) mit meiner Connectbox nicht möglich ist, habe ich also einfach Mal bei "Mulitplayer" auf "Server starten" geklickt und mit den Grundeinstellungen (angekündigt = ja) ein Spiel geöffnet. Aber leider können meine Freunde dieses Spiel nicht finden. Vor der Aktion haben natürlich alle Open TTD geupdated (1.7.2). NewGRFs haben wir auch alle die gleichen. (Wobei die letzten zwei Punkte keine wirklichen Fehlerquellen sind, selbst bei Versions- oder NewGRF-Konflikt, sollten die Leute meinen Server wenigstens sehen).

Kann ich vielleicht meinen open TTD server explizit als "IPv6-Server" definieren, um das mit dem Portforwarding zu umgehen? Muss ich mir wirklich eine alternative Firmware für meine Connectbox holen, die dann Portforwarding unterstützt? Aber wie sollte das überhaupt gehen, wenn ich keine eindeutige IPv4 Adresse habe (Stichwort DS-Lite)? Gibt es sonst noch Fehlerquellen, die dafür sorgen könnten, dass mein Server nicht gefunden wird? Kann ich das ganze vielleicht mit einem VPN Tunnel regeln?

Im Voraus vielen Dank für eure Hilfe!
Arbo

EDIT 22.01.2018:
Hello guys,

I just realized that I have written my post in german... so here we go in the language of the internet:

I want to advertise a server so that my friends and I can play our OWN maps. Concerning the OTTD Wiki you need to do two things in order to achieve that:
1) In your firewall create rules for ports 3979, 3978 for both TCP and UDP
2) In your router configuration forward those ports again for both TCP and UDP.

Now I am "buying" internet at a very famous german company called "Unity Media". Unity Media uses both IPv4 and IPv6: Some 60 customers share 1 IPv4 adress, but each of them has only one IPv6 (if I understand that correctly). Therefore the modem+router called "Unity Media Connect Box" does not even offer the possibility of port forwarding. Again, if I understand correctly, this is due to the non-uniqueness of Unity Media IPv4 adresses (and IPv6 is not compatible to the concept of port forwarding at all).

Now the question is, given that I cannot port forward in my router at all, how can I set up an advertised open TTD server, so that my friends and I can play our own maps? Is there a way to explicitly set the server to be an "IPv6 Server"? Can I use VPN tunnel as an alternative? Are there any other sources of errors, that I have not in mind (we all share the same version 1.7.2 and the same newGRFs)?

Thanks in advance
Arbo

EDIT 22.01.2018:
Here is the console output of 'openttd -d net=2' (as suggested by multiplayer.txt):

dbg: [net] [udp] initializing listeners
dbg: [net] [udp] listening on IPv4 port 0.0.0.0:0 (IPv4)
dbg: [net] [udp] listening on IPv6 port [::]:0 (IPv6)
dbg: [net] [udp] closed listeners
dbg: [net] [udp] initializing listeners
dbg: [net] [udp] closed listeners
dbg: [net] [udp] initializing listeners
dbg: [net] starting listeners for clients
dbg: [net] [tcp] listening on IPv6 port [::]:3979 (IPv6)
dbg: [net] [tcp] listening on IPv4 port 0.0.0.0:3979 (IPv4)
dbg: [net] starting listeners for incoming server queries
dbg: [net] [udp] listening on IPv6 port [::]:3979 (IPv6)
dbg: [net] [udp] listening on IPv4 port 0.0.0.0:3979 (IPv4)
dbg: [net] [udp] advertising to master server
dbg: [net\Opeu\Doccu\ ts\OpynTTT\contenrary\ load\ai\librdbg: [net] [udp] listenit\opengfx\ogfx1_base.grf Pv6)
dbg: [net] [udp] received new session key from master server (IPv4)
dbg: [net] [udp] received new session key from master server (IPv6)
dbg: [net] [udp] advertising to master server
dbg: [net] [udp] advertising to master server
dbg: [net] [udp] advertising to the master server is failing
dbg: [net] [udp] we are not receiving the acknowledgement from the server
dbg: [net] [udp] this usually means that the master server cannot reach us
dbg: [net] [udp] please allow udp and tcp packets to port 3979 to be delivered
dbg: [net] [udp] please allow udp and tcp packets from port 3979 to be delivered

EDIT 23.01.2018:
I just posted this question at a community page of my ISP (german page): https://community.unitymedia.de/questio ... ox-ds-lite.

[Arbo]

Hello again,

so I solved my Problem. I already had a contract at Unitymeida featuring a "normal" IPv4 adress. But then I upgraded the contract (more MBit/s) and DS-Lite came with this upgrade. Now I called Unitymedia and I will be reset to a normal IPv4 and DS-Lite will be gone!

For all of you guys who are stuck with DS-Lite: I'm sorry but setting up an advertised OpenTTD Server will be very hard for you. If you still want to do it, then you should google for "DynDNS" and "Portmapper". Those are the relevant tools to compensate that DS-Lite is restricted when something in your Local Are Network is to be accessed from the internet. This could be your smart home system that you want to access from your place of vaccation. This could also be an Open TTD Server that must be accessed by the master server (and all the other players). In my case the router does not even support DynDNS (although it uses DS-Lite!!!), so I would have had to pay for a portmapper to do the job. Noone seems to offer the service of portmapping for free...