Zandronum Chat @ irc.zandronum.com
#zandronum
Get the latest version: 3.0
Source Code

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0003531Doomseeker[All Projects] Suggestionpublic2018-10-04 20:162018-10-13 23:55
ReporterMaster O 
Assigned To 
PrioritylowSeverityfeatureReproducibilityN/A
StatusconfirmedResolutionopen 
PlatformOSOS Version
Product Version 
Target Version1.3Fixed in Version 
Summary0003531: IPV6 Support for Doomseeker
DescriptionIn relation to the report below regarding IPv6 support for Zandronum:

https://zandronum.com/tracker/view.php?id=214 [^]

Doomseeker will also need IPv6 support accordingly.
Attached Files

- Relationships
related to 0000214acknowledged Zandronum IPV6 Support for Skulltag on All OSes it runs on 
parent of 0003287closedZalewa Doomseeker IRC: IRC network address hostname lookups use IPv4 when IPv6 connectivity is available 

-  Notes
User avatar (0019910)
WubTheCaptain (developer)
2018-10-05 05:45

What specifically?

  • Doomseeker's IRC client defaults to IPv6 hostname lookups since 0003287 (to be released with Doomseeker 1.2).
  • doomseeker.drdteam.org has no AAAA records in DNS (site issue), particularly IP2C autoupdates and software release downloads (automatic updates on Windows).
  • Game (engine) plugin architecture?
  • Master server support (software, server administration?)


Last two I'm not familiar with.
User avatar (0019911)
WubTheCaptain (developer)
2018-10-05 05:54

I'm actually more certain the server browser already supports IPv6, at least for Custom Servers (1.1) / Pinned Servers (1.2). Just tested.
User avatar (0019917)
Master O (reporter)
2018-10-05 12:36

WubTheCaptain, I was referring to Master Server support, which is why I referencedhttps://zandronum.com/tracker/view.php?id=214 [^] in the first place.

Torr also said in that particular thread that the master server protocol needs IPv6 support as well.
User avatar (0019918)
WubTheCaptain (developer)
2018-10-05 17:13

I took a quick look at the source.

  • Server refresher assumes IPv4.
  • IP2C's isLANAddress() and isLocalhostAddress() only support IPv4 so far.
  • Something odd in ServerListRowHandler::fillItem() assumes IPv4.
  • Master server querying (src/core/serverapi/masterclient.cpp) only works with IPv4 largely.


Perhaps Blzut3 or Zalewa can create the appropriate children of this ticket.
User avatar (0019920)
Blzut3 (administrator)
2018-10-05 22:36

Can confirm that IPv6 is not supported in the server browser. In fact I had to specifically write code to reject IPv6 from Chocolate Doom. This was a long time ago so while it might be simpler now though all the refresher rewrites back then there was an issue with Qt changing the socket type automatically and potentially needing to manage two sockets.

Addressing this is now feasible since I do have IPv6 with my ISP.

Outside of the server browser things should more or less just depend on Qt so should support IPv6 unless we made a mistake.
User avatar (0020111)
WubTheCaptain (developer)
2018-10-13 18:12

[18:10:11] New Zandronum LAN server detected: ::ffff:127.0.0.1:50666
[18:10:11] New Zandronum LAN server detected: ::ffff:127.0.0.1:50667


Lack of IPv6 support in Zandronum probably meant why I could never directly join servers I created at Create Game from the server browser.

Oh, and that address (instead of ::1) is deprecated by an RFC, I believe.
User avatar (0020120)
Blzut3 (administrator)
2018-10-13 23:55

That address is IPv4 mapped IPv6. Which is a kernel feature that allows IPv6 sockets to accept v4 connections transparently. So while unconventional notation it is not the same as ::1, it is however the same as 127.0.0.1. I think you're thinking of another similar range.

As for not being able to join games that you create through the server browser on v4. That's likely a NAT "problem." Just discovered that my router has this issue. In short the router is detecting that you're trying to connect to your external IP (i.e. it) and looping it back early. As a result the connection appears to be coming from your router's LAN IP instead of the external one and only L2 forwarding is applied. At least that's what I think is going on.

Issue Community Support
Only registered users can voice their support. Click here to register, or here to log in.
Supporters: WubTheCaptain
Opponents: No one explicitly opposes this issue yet.

- Issue History
Date Modified Username Field Change
2018-10-04 20:16 Master O New Issue
2018-10-05 00:36 Blzut3 Relationship added related to 0000214
2018-10-05 00:36 Blzut3 Status new => acknowledged
2018-10-05 00:37 Blzut3 Project Zandronum => Doomseeker
2018-10-05 05:45 WubTheCaptain Note Added: 0019910
2018-10-05 05:45 WubTheCaptain Status acknowledged => feedback
2018-10-05 05:45 WubTheCaptain OS All Applicable OS-es =>
2018-10-05 05:50 WubTheCaptain Relationship added child of 0003287
2018-10-05 05:50 WubTheCaptain Relationship replaced parent of 0003287
2018-10-05 05:54 WubTheCaptain Note Added: 0019911
2018-10-05 12:36 Master O Note Added: 0019917
2018-10-05 12:36 Master O Status feedback => new
2018-10-05 17:13 WubTheCaptain Note Added: 0019918
2018-10-05 17:13 WubTheCaptain Status new => acknowledged
2018-10-05 18:04 WubTheCaptain Priority normal => low
2018-10-05 22:36 Blzut3 Note Added: 0019920
2018-10-06 08:58 WubTheCaptain Status acknowledged => confirmed
2018-10-06 09:00 WubTheCaptain Target Version => 1.3
2018-10-13 18:12 WubTheCaptain Note Added: 0020111
2018-10-13 23:55 Blzut3 Note Added: 0020120






Questions or other issues? Contact Us.

Links


Copyright © 2000 - 2018 MantisBT Team
Powered by Mantis Bugtracker