Instabilities when using IPv6 with relay server
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
widelands |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
When recording my Youtube Videso, I found that there are some instability with the Relay Server:
* I started and Internat game "HasiTube" but when connecting the next time it still was active?
* I sent the computer to conserve power mode OSX, After that I had some trouble to reconect
* I had to swutch of IPV6 in the end to allow me to connect the normal way.
Some messages from the logs:
-- 1st try:
InternetGaming: Connecting to the metaserver.
Could not resolve network name: resolve: Host not found (authoritative)
[NetClient]: Trying to connect to 85.214.243.231:7395 ... success.
InternetGaming: Sending login request.
InternetGaming: Client Hasi50 logged in.
InternetGaming: Server time offset is 0 second(s).
InternetGaming: Client update on metaserver.
InternetGaming: Received a client list update with 14 items.
InternetGaming: Received a game list update with 2 items.
InternetGaming: Client opened a game with the name HasiTube3.
InternetGaming: Game update on metaserver.
InternetGaming: Received ips of the relay to host: 2a01:238:
InternetGaming: Client update on metaserver.
[Host]: starting up.
[NetRelayConnec
[NetRelayConnec
[NetRelayConnec
[NetRelayConnec
InternetGaming: logout(
[NetClient] Closing network socket connected to 85.214.
-- 2nd try:
InternetGaming: Connecting to the metaserver.
Could not resolve network name: resolve: Host not found (authoritative)
[NetClient]: Trying to connect to 85.214.243.231:7395 ... success.
InternetGaming: Received ips of the relay to host: 2a01:238:
InternetGaming: Client update on metaserver.
[Host]: starting up.
[NetRelayConnec
-- Switched to IPv4 only:
[NetRelayConnec
[NetRelayConnec
May that mix of IPv4/6 resulted in confusion, may the relay server
already had crashed on the IPv6 conection?
Can someone collect the server logs from today?
Changed in widelands: | |
assignee: | nobody → Notabilis (notabilis27) |
milestone: | none → build20-rc1 |
status: | New → Confirmed |
Changed in widelands: | |
assignee: | Notabilis (notabilis27) → nobody |
status: | Confirmed → Fix Committed |
Thanks for reporting and for the logs! I also got the ones from the server.
I guess (not sure) that the IPv6-problems and the old games might be separate bugs, but I have to look into it.
1) When you sent your computer to conserve power mode, was Widelands still connected to the metaserver when doing so?
2) Does IPv6 in Widelands normally work for you or is it always broken?
3) Does IPv6 work on your system for other servers?
4) If it never works for Widelands, does that mean that you always have to wait some time while the game tries to connect to the metaserver / the relay? It shouldn't hang for much more than a second.
If IPv6 normally works and was only behaving strange this time, you could try again. I restarted the meta-/relay-server so from the server side it should work as normal now.