Oh snap!
https://doomlist.net/full just registered my ass server in public broadcast! Even my server window display is reading up on the broadcast user connections! And dis is on a router, which is fuckery. I FUCKING NEED TO WRITE DOWN FUCKING (offline) INSTRUCTIONS!!!
1. Mircosoft TCP/IP version 6, aka IPv6
IPv6 needs not to be disabled, or uninstalled.
2. Router's Network Access Translation (NAT) or Gaming page
You may need to create a custom service tuple value.
ZDoom Service Name be "ZDoom Host Port 5029 UDP for Linux (or any base host port #)".
Zandronum Service Name be "Zandronum Host Port 10666 UDP for Linux (or any base host port #)".
ZDoom's Global Port Range ranges from 5029 ~ 5029.
Zandronum's Global Port Range ranges from 10666 ~ 10700.
Base Host Port needs to be a single host port value (you must set your base host port into your hosted server application [DON'T EVEN LET YOUR SERVER HOST THE PORT!!! {for backup citation references, Youtube user Kes Gaming's "How to Host a Doom Server on Zandronum/Doomseeker! Ultimate Guide to Port Forwarding and Hosting!" page ((
https://www.youtube.com/watch?v=Rkid352uxhY))}]).
Port Protocol be in value TCP/UDP.
Make sure to active the custom service with the specified machine (VERY IMPORTANT!) in question.
3. ZDoom/Zandronum Server Network Connection to Router
Adjust the connection type to the following settings.
Set Cloned MAC Address options parameter to option value "Random". This option should provide some means of security to the UDP port type.
Set Link Negotiation options parameter to option value "Automatic".
There are other settings to configure, but the situation varies according to user preferences and ZDoom/Zandronum client/host configurations.
4. Firewall?
You don't need to add either Zandronum, Doomseeker, ZDoom, or UDP port, to the firewall exceptions list.
However, you will have notification pop-up windows for each host attempt.
Sometimes, it's just best to add the broadcaster and source port application/program to the firewall exceptions list.
Firewall exceptions may influence your hosted server display as LAN mode.
5. Doomseeker's Private/Public IP Address Server Setup (requires port forwarding information on the router's Network Access Translation (NAT) or Gaming page
You must set your base host port into your hosted server application (DON'T EVEN LET YOUR SERVER THE HOST PORT!!!).
The following code needs to be in custom string parameter.
Reference material be right here.
https://wiki.zandronum.com/Creating_a_Game_Serverhttps://wiki.zandronum.com/Personal_Gam ... Doomseekerhttps://wiki.zandronum.com/Game_Servers_Troubleshootinghttps://wiki.zandronum.com/Personal_Gam ... indows_CLIhttps://wiki.zandronum.com/Master_Serverhttps://zandronum.com/forum/viewtopic.php?t=1771#p21782https://zdoom.org/wiki/Command_line_parametershttps://zandronum.com/forum/viewtopic.php?t=6884#p92380Linux firewall-config configuration configuroos:
https://access.redhat.com/documentation ... all-confighttps://major.io/2019/01/04/allow-port- ... firewalld/If you use Flatpak's Linux/Wine version of Zandronum/Doomseeker/ZDoom, you can host and broadcast your game session to the broadcasting lobby server on Linux. However, the OS being Linux, it may have different firewall designs. From the firewall-config (yes, that one, from Red Hat!), follow up on the blocks of instructions typed after this sentence.
|
You may want to prepare configuration of firewall-config securely and correctly before sub-configuration of Zandronum/Doomseeker/ZDoom.
|
Apply ports/port ranges/protocols values of 10666-10700/UDP in the Configuration section's Zones breadcrumb navigation menu's Ports, Protocols, Source Ports sub-breadcrumb navigation menus. Check the "Masquerade zone" checkbox parameter value from the Configuration section's Zones breadcrumb navigation menu's Masquerading sub-breadcrumb navigation menu. Apply ports/port ranges/protocols/(private/public) IP addresses (private IPv4, private IPv6, public IPv4, and public IPv6 apply as values [public IPv4 and public IPv6 discoverable in URL
https://ip4.me/ and
https://ip6.me/]) values of 10666-10700/UDP/private_IPv4/private_IPv6/public_IPv4/public_IPv6 in the Configuration section's Zones breadcrumb navigation menu's Port Forwarding and Sources sub-breadcrumb navigation menus (I only found out after a while from unknowingly using the private IPv4 address, how stupid of me!; it only occurred after waking in the afternoon from a overnight of trying to configure firewall-config for the access of port 443 and https protocol [was trying to get my website/domain as secure https]; I only realized about the https protocol value as unchecked in the Configuration section's Zones breadcrumb navigation menu's Services sub-breadcrumb navigation menu [will put down that information in the appropriate Apache installation/configuration block]). For any whitelisting (although it has its risks), apply the command parameter value of any launched items that may peruse the configured services, ports, protocols, source ports, port forwardings, and sources from the Configuration section's Zones breadcrumb navigation menu's Services, Ports, Protocols, Source Ports, Port Forwarding and Sources sub-breadcrumb navigation menus to the Configuration section's Lockdown Whitelist breadcrumb navigation menu's Commandlines sub-breadcrumb navigation menu.
In the Configuration section's Zones breadcrumb navigation menu's Port Forward sub-breadcrumb navigation menu, include the instances or resemblances to the examples below.
e.g.
Port Protocol To Port Address
10666-10700 UDP 10666-10700 Private IPv4 IP address #.#.#.#
10666-10700 UDP 10666-10700 Public IPv4 IP address #.#.#.#
10666-10700 UDP 10666-10700 Public IPv6 IP address #.#.#.#
Remember to set runtime configuration to permanent configuration and reload firewalld.
|
You may want to save configuration of firewall-config securely and correctly after sub-configuration of Zandronum/Doomseeker/ZDoom.
Code:
https://ip4.me/https://ip6.me/From the Doomseeker program's Doomseeker Host Online window's Custom parameters breadcrumb navigation menu, type down the following.
-sv_cheats 1
+sv_broadcast 1
+sv_updatemaster 1
+sv_enforcemasterbanlist 1
+sv_showlauncherqueries 1
+masterhostname master.zandronum.com
-useip #.#.#.#:# (for Linux requirement of PRIVATE/PUBLIC IP address [private IPv4, private IPv6, public IPv4, and public IPv6 apply as values {public IPv4 and public IPv6 discoverable in URL
https://ip4.me/ and
https://ip6.me/}])
-upnp 10666 (also another Linux requirement of port number)
Application Server Porting Prerequisite for Zandronum/ZDoom Application Server Hosting:
For every uptime of the hosting device and/or router, you must perform the following task for port forwarding connection between router and device hosting Zandronum/ZDoom server.
https://www.cyberciti.biz/faq/howto-lin ... p-address/-terminal command# sudo dhclient -v (in order to find the router/modem IP address [which is usually found on the DHCPACK line of the information output]; enter the router/modem IP address value in a web browser's search bar, you should be able to see Apache's congratulations page)
On the router's configuration page, find and press a text/button link that redirects to the device list index page. Press the button that indicate clearing and scanning for currently connected devices to the router. I know it's annoying, but you must follow up on this task for every hosting device's or router's uptime. The router holds the port access to Zandronum/ZDoom; as a application/service port, it cannot automatically rescan for any changes to the hosting device, its OS, or its server. Devices change internet connection configuration often so it cannot catch up, since the router is technically its own device. Hey, that's how application server porting works (sometimes).
GUI Steps:
From morganm, it (the selected pinning of the deemed server) definitely allows direct join by client side. I tried joining from the ::ffff:#.#.#.# server, but it appears to be the borrowed source port for the server console program.
"
Last thing I had to do was Doomseeker > Options > Configure > Custom Servers
Click Add.
Make sure the port is same as your server.
In the IP field put in your Local LAN IP (not your public WAN IP!).
Click Apply.
Click OK.
Click Refresh.
*BOOM*
"
Iwad and additional pwads, wads, and files parameters are up to your discretion, but make sure they be the same files.
Maplist parameter must be noted, or something like that.
Maximum number of clients and players parameters, or something like that.
URL and email parameter values preferably "[redacted]", but it could be a download link.
Message of the Day (MOTD) parameter will print out messages upon joining.
All other (informational) checkbox, buttons, options, numeric, and string parameters are jah ba gah! They be up to you!
---
If the Zandronum server in question is not publicly broadcasting to the master/broadcasting lobby server and/or privately/locally advertising within the Local Area Network (LAN) (cited reference pages:
https://zdoom.org/wiki/Command_line_par ... m_Specific and
https://wiki.zandronum.com/Personal_Gam ... indows_CLI), then you have two methods to connect/join to this non-public and non-private Zandronum server, assuming that the Doomseeker did not receive the deemed Zandronum server information in its public/master/broadcasting/private/local lobby server data transmission.
Method One: Client connection to non-public and non-private Zandronum server with Doomseeker's GUI
On Doomseeker's 'Doomseeker - Configuration' window, select the 'Pinned servers' option label from the options section. From the 'Pinned servers' option label of Doomseeker's 'Doomseeker - Configuration' window, search for the 'Pinned servers' subsection label from the details section. This subsection allows the addition and removal of pinned Zandronum servers in its pinned Zandronum servers database. Paste the copied hosted non-public and non-private Zandronum server's IP address and port number in its own respective tuple and attribute. The buttons and table descriptions are quite self-explanatory in terms of user interface navigation. Congratulations, you have successfully connect/join to the non-public and non-private Zandronum server, assuming that the Doomseeker did not receive the deemed Zandronum server information in its public/master/broadcasting/private/local lobby server data transmission.
Method Two: Client connection to non-public and non-private Zandronum/ZDoom server with Zandronum's/ZDoom's console
For Zandronum source port
connect to #.#.#.#:# mentioned in the server's name or address.
For ZDoom source port
join to #.#.#.#:# mentioned in the server's name or address.
Congratulations, you have successfully connect/join to the non-public and non-private Zandronum/ZDoom server, assuming that the Doomseeker did not receive the deemed Zandronum/ZDoom server information in its public/master/broadcasting/private/local lobby server data transmission.
6.
https://doomlist.net/fullThis page will determine if your (temporary) custom Zandronum server be registered on the public broadcast.
If successful, you may not see your hosted server tuple in LAN display mode anymore.
While annoying to broadcasting efforts, LAN display mode can easily list your hosted server.
Do search and pin for your specified hosted server in case it is not listed as LAN display mode.
Please note not to give away your LAN or host IP address as it is sensitive personal information.
You will be vulnerable if you do.
Instead, use other informational parameters to broadcast your hosted Zandronum server.
Should you ever need to give out a IP address, use
https://doomlist.net/full 's custom cover public IP address for broadcast.
Remember that the broadcasted Zandronum server is dependent on the machine's operation, router configurations, and server application configurations.
Good luck, I guess.
That be all.
---
I have successfully circumvent Doomseeker's currently malfunctioning (found on the year 2023) broadcasting lobby server. Okay, I am not really sure if there is actually a malfunction. It might be a ban of some mysterious nature. That doesn't matter for now. What matters for now is that I managed to circumvent this error. Just visit
https://doomlist.net/full as the alternative broadcasting lobby server. I know it's a bit cumbersome to add in CPU usage from a web browser, but at least the solution works (at this moment, there are no [public] instructions to create a custom broadcasting lobby server at this time). On the website, hover the pointer over the Zandronum server list relational database parameter values for more value details noted in the HTML element/tag's title parameter. From the database, search for its 'Address [?]' attribute. Search for the specified server (as tuple) in question. Search for that specified server's 'Address [?]' attribute. Select the value of that 'Address [?]' attribute, which is a hosted Zandronum server's IP address and port number. Copy that hosted Zandronum server's IP address and port number.
On Doomseeker's 'Doomseeker - Configuration' window, select the 'Pinned servers' option label from the options section. From the 'Pinned servers' option label of Doomseeker's 'Doomseeker - Configuration' window, search for the 'Pinned servers' subsection label from the details section. This subsection allows the addition and removal of pinned Zandronum servers in its pinned Zandronum servers database. Paste the copied hosted Zandronum server's IP address and port number in its own respective tuple and attribute. The buttons and table descriptions are quite self-explanatory in terms of user interface navigation. Congratulations, you have successfully circumvent Doomseeker's currently malfunctioning broadcasting lobby server.
However, if you want to join/host a server with a testing release of Zandronum source port (and that's because a popular Zandronum host is currently using a testing release), there is a way. Just don't go get carried away just because a server has the latest 'state of the art' mod design. These mods are currently under testing procedures so expect a burden requiring effort and time. On Doomseeker's 'Doomseeker - Configuration' window, select the 'Zandronum' option label from the options section. From the 'Zandronum' option label of Doomseeker's 'Doomseeker - Configuration' window, search for the 'Game - Zandronum' subsection label from the details section. From the 'Game - Zandronum' subsection of Doomseeker's 'Doomseeker - Configuration' window's details section, check the 'Testing releases' check flag. And that be it, the rest of Doomseeker's functions should follow though with your join/host server command. Just remember to not get carried away with playing around with mods under testing.
7. Last tidbits
Any .zip files may not work with Zandronum or Doomseeker.
Any skin wad would interfere with the server and client side connection.
Those are the rules of Zandronum or Doomseeker.
The next step is just some reference for you to play on singleplayer mode, but I really think it's optional!
On your hosted server, right click to show a "show join command line" option.
Replace the IP address from the -connect command, with the value 127.0.0.1:(base host port).
---
Any other semi-mishap that deals with the game code itself will depend on the source port design and there's no way to fix that semi-error.
Like, for example, the dropitem for Zandronum, is too specific in its demand!
Or just can't read out from the default too well!
Decorate translation cannot interfere well enough!!!
This is true for health items.
Now, I have to go back and correct my mistakes again!!!No code compatibility fixes will cure this lugging error!!!
Some shit is just outdated...
If you do join in the server console on Linux platform, regardless of LAN or internet, make sure to use the following Zandronum source port command.
connect to #.#.#.#:# mentioned in the server's name or address.
If you do join in the server console on Linux platform, regardless of LAN or internet, make sure to use the following ZDoom source port command.
join to #.#.#.#:# mentioned in the server's name or address.
MAN, AM I TIRED!