Sign in to follow this  
Followers 0

Halo server use/management - Bash Linux -FIREWALL

Those running halo servers in Linux might fight this interesting. As you are aware the halo server console takes up the cli terminal while it's running. There are ways around this such as using Docker, screen, tmux, and more. And people running multiple halo servers in Linux have defintely run into this issue in the cli.

But there is another way, nohup :)

It's probably already in your debian, centos, other major distro if it's not a minimal build too :)

By using nohup and aliases we can not only get the terminal back, run multiple halos from one terminal without extra stuff, but we can even issue halo server commands *from the terminal*

Other uses include being able to tail the in game chat from the halo console output to look for cheat complaints, and possibly setting up an alert system:

At the bottom of the github README I've added an example remote setup to view the halo console from a web browser :)

*new update*

Rootless Docker nohup install:

Edited by AntiMomentum
Takka, Kavawuvi, mouseboyx and 1 other like this

Share this post

Link to post
Share on other sites


Updating this post to include the Rootless Docker version of nohup. Everything nohup for Wine could do now applies to rootless Docker containers! No need to even install privileged Wine to your vps or whatever (Ubuntu 20.04LTS only for now):

Also there's a new firewall. The firewall will finally allow connections the linux server initiates. This means things like apt update are now possible while the firewall is running! It's similar to what ufw does by automatically dropping non-initiated connections, but while still filtering halo packets! The firewall includes DoS protections, which includes Sappboom protection, but it is still recommended to update your halo server:

Yep. You can now have basic network functionality to the linux server beyond just for halo lmao. While having the security of an unprivileged account to run Wine. With the benefits nohup provides.

The catch is Docker no longer has privileges to assign its own ports. All port assignments you see in my start/nohup start examples for rootless Docker are to align the ports for Docker not with the host too. The kernel will pick a random port in the range shown by: cat /proc/sys/net/ipv4/ip_local_port_range

but as long as your ubuntu server can get packets from the natneg server (, included in the WHITELIST ipset of my firewall) and the master server (which haloceded.exe will automatically reach out to)  then your server should appear in the list and be joinable even if you haven't download the Docker images yet.

You can get the public facing port number(s) by doing:

lsof |grep vpnkit| grep UDP| grep ':' | sed 's/^.*://'

Docker-compose installation has been added to the bottom of the rootless readme:

Edited by AntiMomentum
Java and Takka like this

Share this post

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  
Followers 0
  • Recently Browsing   0 members

    No registered users viewing this page.