| View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||
| ID | Project | Category | View Status | Date Submitted | Last Update | ||||
|---|---|---|---|---|---|---|---|---|---|
| 0004142 | Doomseeker | [All Projects] Suggestion | public | 2023-06-25 13:43 | 2025-11-08 19:57 | ||||
| Reporter | Zalewa | ||||||||
| Assigned To | Zalewa | ||||||||
| Priority | normal | Severity | minor | Reproducibility | N/A | ||||
| Status | resolved | Resolution | fixed | ||||||
| Product Version | |||||||||
| Target Version | 1.5.0 | Fixed in Version | 1.5.0 | ||||||
| Summary | 0004142: Support the Zandronum's segmented server query response | ||||||||
| Description | Zandroum is about to gain support for segmented server query response which should help with the response packets going into the jumbo category and getting dropped by the network equipment as a result. See: https://wiki.zandronum.com/Launcher_protocol#Segmented_challenge [b]Important:[/b] The default description points to a backward-incompatible query challenge that changes the packet tag to 200. [b]We don't want that[/b] because it will break all previous Zandronum versions and handling this properly would be too convoluted. Keep using the challenge packet with [b]tag 199[/b], but only append the segmentation byte as described further down on the page in the https://wiki.zandronum.com/Launcher_protocol#Old_protocol_challenge section. | ||||||||
| Additional Information | See 0004064 for details. | ||||||||
| Attached Files |
| ||||||||
 Relationships |
|||||||||||||
|
|||||||||||||
 Relationships |
| Notes |
|
Zalewa (developer) 2023-07-23 18:13 |
Implement the segmented server query in a backwards-compatible way: - https://bitbucket.org/Doomseeker/doomseeker/commits/ffda69dc439a4bcb539c0aee120968d75a4e9ded And add an opt-in option for it: - https://bitbucket.org/Doomseeker/doomseeker/commits/ec453de441bfe38f27c3b0c63506938c45968413 I have decided to make this an opt-in only for a short while. The option will stay for now, at most as long as Zandronum itself supports the single packet reply, but it needs to be made enabled by default sooner than that -- in the next release of Doomseeker (or even before that). I will open a separate ticket for making the option enabled by default. |
|
Zalewa (developer) 2023-07-23 18:17 |
Option default -> 0004147. |
|
Zalewa (developer) 2023-07-23 22:40 |
Fixes: 1. https://bitbucket.org/Doomseeker/doomseeker/commits/ae38a9552198243fd9b6e66cccba0bff59fcb882 2. https://bitbucket.org/Doomseeker/doomseeker/commits/c39aa329203fa6953d7e2acf65875f25d11134a0 3. https://bitbucket.org/Doomseeker/doomseeker/commits/5ee17c7d4252a9f0cc400b757c96cccaac976efc |
|
Zalewa (developer) 2023-07-25 19:29 |
Ready for testing: https://devbuilds.drdteam.org/doomseeker/doomseeker-1.4.1~beta-230723-2106_windows.zip |
|
Zalewa (developer) 2023-07-26 21:23 |
This issue is confirmed by Iko and Kaminsky on Discord as fixed. |
|
Zalewa (developer) 2024-07-26 14:20 |
The protocol was altered on 2024-07-21 to "segmented reply v2" and Doomseeker needs to be adapted. https://wiki.zandronum.com/w/index.php?title=Launcher_protocol&oldid=2119 |
|
Zalewa (developer) 2024-07-27 14:10 |
Segmented reply v2: https://bitbucket.org/Doomseeker/doomseeker/commits/7545e7cdd46c3b9bfaabe7c3d1119f045c9dde4d |
|
Zalewa (developer) 2024-07-27 15:02 |
Segmented reply v2 is available for testing in this beta build: https://devbuilds.drdteam.org/doomseeker/doomseeker-1.4.1~beta-240727-1427_windows.zip There's currently no Zandronum testing build that supports this, though. At the moment the latest ZandroDev is 3.2-240414-1910, while the segmented reply v2 was authored on 2024-05-19. |
| Notes |
| Issue History |
|||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2023-06-25 13:43 | Zalewa | New Issue | |
| 2023-06-25 13:43 | Zalewa | Relationship added | related to 0004064 |
| 2023-06-25 13:46 | Zalewa | Description Updated | View Revisions |
| 2023-06-25 13:46 | Zalewa | Status | new => confirmed |
| 2023-07-22 12:31 | Zalewa | Assigned To | => Zalewa |
| 2023-07-22 12:31 | Zalewa | Status | confirmed => assigned |
| 2023-07-23 18:13 | Zalewa | Note Added: 0022892 | |
| 2023-07-23 18:13 | Zalewa | Status | assigned => needs review |
| 2023-07-23 18:17 | Zalewa | Relationship added | parent of 0004147 |
| 2023-07-23 18:17 | Zalewa | Note Added: 0022893 | |
| 2023-07-23 22:40 | Zalewa | Note Added: 0022894 | |
| 2023-07-25 19:29 | Zalewa | Note Added: 0022895 | |
| 2023-07-25 19:29 | Zalewa | Status | needs review => needs testing |
| 2023-07-26 21:23 | Zalewa | Note Added: 0022896 | |
| 2023-07-26 21:23 | Zalewa | Status | needs testing => resolved |
| 2023-07-26 21:23 | Zalewa | Fixed in Version | => 1.5.0 |
| 2023-07-26 21:23 | Zalewa | Resolution | open => fixed |
| 2024-07-26 14:20 | Zalewa | Note Added: 0023819 | |
| 2024-07-26 14:20 | Zalewa | Status | resolved => assigned |
| 2024-07-27 14:10 | Zalewa | Note Added: 0023826 | |
| 2024-07-27 14:10 | Zalewa | Status | assigned => needs review |
| 2024-07-27 15:02 | Zalewa | Note Added: 0023831 | |
| 2024-07-27 15:02 | Zalewa | Status | needs review => needs testing |
| 2025-11-08 19:57 | Zalewa | Status | needs testing => resolved |
| Issue History |
