PvPGN Firewall - DieTesseract

You have the virtual machine inside that VPS ?

b1n wrote:

Congratulations and thanks for the tutorial, I'm going to try it right now

I've heard that in tesseract d2gs it's possible to check the Patch_D2.mpq and don't let the user enter games with wrong patch, there's a way to do this ?

Thats not part of the versioncheck.conf ?

I've just modified the patch_d2.mpq and players use the d2gfx.dll that allows multiple screens, just that

There's a way to identify if the packets crashing my d2gs are attacks or patch problems?

Just the first ladder of my server has been without d2gs crashes, there's several months with d2gs crashes almost every day..
thanks

What's your experiences hosting a PVPGN?
https://forums.pvpgn.pro/viewtopic.php?id=1858

b1n wrote:

I've just modified the patch_d2.mpq and players use the d2gfx.dll that allows multiple screens, just that

There's a way to identify if the packets crashing my d2gs are attacks or patch problems?

Just the first ladder of my server has been without d2gs crashes, there's several months with d2gs crashes almost every day..
thanks

I also do not know an exact way to identify problems in d2gs

my experiences, when it is attack, a log is almost always generated in D2GS-Hack.txt, but not always..

if it is a patch problem, you can use the "d2txtanalyser" tool to find any possible failures in your *.TXT files

As we commented in another post, most of the attacks come from Argentina

What's your experiences hosting a PVPGN?
https://forums.pvpgn.pro/viewtopic.php?id=1858

b1n, if you are capturing and saving all your packet sends, then it should be easy.

I'd use something like PeerBlock to train what connections you have coming through and also manually track your logs. When it does get attacked and crashed, it'll be easy to line up the timestamps, nuke the IP, boom.

Is there a particular reason you want the exact packets? If it is being attached, it should be easy to see.  PM if you need any further help.

This is a different way to windows server users tested on Windows Server 2019
Hi i tried D2Gs Admin but it didnt work, didnt block the full package, only the first 2bytes of the code, i did another one
it autostarts the process of D2GS defined the location inside the source code, so i share it compiled and the source code

Copy and paste in your browser
prnt.sc/mu6JzZGmKJ-_

Cannot post 2 links, so
https://www.mediafire.com/file/zpexqsw1 … l.zip/file
Source Code:

import pydivert
import threading
import subprocess
import time
import psutil
import ctypes
import json

log_file = "blocked_packets.log"  # Specify the log file path
ban_duration = 300  # Ban duration in seconds
banned_ips_file = "banned_ips.json"  # File to store banned IPs

# Set the window title
ctypes.windll.kernel32.SetConsoleTitleW("Revenge Firewall")

# Load banned IPs from file
def load_banned_ips():
    try:
        with open(banned_ips_file, "r") as f:
            return json.load(f)
    except (FileNotFoundError, json.JSONDecodeError):
        return {}

# Save banned IPs to file
def save_banned_ips(banned_ips):
    with open(banned_ips_file, "w") as f:
        json.dump(banned_ips, f)

# Initialize banned IPs dictionary
banned_ips = load_banned_ips()

def block_packet(packet, w):
    payload = bytes(packet.tcp.payload)
    if packet.tcp.dst_port == 4000 and payload.startswith(b'\xff\x01'):
        source_ip = packet.src_addr
        if source_ip in banned_ips:
            ban_start_time = banned_ips[source_ip]
            ban_elapsed_time = time.time() - ban_start_time
            if ban_elapsed_time < ban_duration:
                # IP is still banned, don't send the packet
                print(f"IP {source_ip} is banned. Packet dropped.", flush=True)
                return
            else:
                # Ban duration has elapsed, remove the IP from the banned list
                del banned_ips[source_ip]
                save_banned_ips(banned_ips)

        # Log blocked packet and source IP
        log_message = f"Blocked packet: {payload}\nSource IP: {source_ip}\n"
        with open(log_file, "a") as f:
            f.write(log_message)

        # Display blocked packet and source IP
        print(log_message, flush=True)

        # Ban the source IP
        banned_ips[source_ip] = time.time()
        save_banned_ips(banned_ips)

        # Do not send the packet to effectively block it

    else:
        # Allow the packet to pass through
        w.send(packet)

def packet_capture():
    print("Starting packet capture...")
    with pydivert.WinDivert("tcp.DstPort == 4000") as w:
        for packet in w:
            block_packet(packet, w)

# Start packet capture in a separate thread
packet_capture_thread = threading.Thread(target=packet_capture)
packet_capture_thread.start()

print("Scanning packets on port 4000...")

# Continuously check if the process is running and restart if necessary
while True:
    process_name = "D2GS.exe"

    # Check if the process is running
    process_running = any(
        proc.name() == process_name for proc in psutil.process_iter()
    )

    if not process_running:
        # Restart the process
        process_path = r"C:\Users\Mantenimiento\Desktop\Server\D2GS\D2GS.exe"
        try:
            subprocess.Popen(
                process_path,
                shell=True,
                stdout=subprocess.PIPE,
                stderr=subprocess.PIPE,
                creationflags=subprocess.CREATE_NEW_CONSOLE,
            )
            print(f"Process '{process_name}' restarted.")
        except subprocess.CalledProcessError:
            print(f"Failed to restart process '{process_name}'.")

    # Wait for a few seconds before checking again
    time.sleep(5)

GecKoTDF wrote:

I see.

Well the .exe version in my personal experience with users, it's more simple and safe.
For example im using Windows Server 2016, and runs fine, without need to install nothing.
And because it's a .exe file I can add it into the Game Panel and start it with the server.

If the .exe dissapear will be need it detailed instructions for scratch to get Python installed, and how to install all the pre-requisites, because the 80% of the users don't know this.

About the config file, I think the most simple way it's a .cfg file, where you set the variables like
BAN_DURATION, BANNED_IPS_FILE, etc. To avoid edit the original .py file and destroy something in the process.
Add a variable to the Folder Path of the D2GS.exe.
The chance to enable or disable the process monitoring, because some people do it with another software.
And probably another .cfg file to set different payloads like:

\xFF\x01
\xFF\x02
\xFF\x03

Because some people have modded versions of the game, more custom and some Hex code can change.

Thanks for your time.

P.D: Igual te hablo en ingles para que el resto entienda, sino despues nos putean y nos comemos el bansito ahre.

Updated github with those changes you mentioned before, and updated Readme with the dependencies to run it from windows server 2019, should work for any windows S.o
config.json for basic configs, and payloads.json for the payload settings, also an example-payloads.json to add multiple payloads to block.

https://github.com/jcerutti/PythonFirewallD2GS

Saludos genio, no vi que tambien eras argentino jajaja.