IP Masking: Difference between revisions
Level 2 header. Level 1 is title |
shameless self promotion |
||
| Line 8: | Line 8: | ||
==Other means== | ==Other means== | ||
On some clones, due to technical limitations like being behind a proxy, not having administrator access or not having a firewall capable of this, the operators may choose to provide IP masking via [https://github.com/vectrix-space/ignite/ Ignite] mods or server/proxy plugins. | On some clones, due to technical limitations like being behind a proxy, not having administrator access or not having a firewall capable of this, the operators may choose to provide IP masking via [https://github.com/vectrix-space/ignite/ Ignite] mods or server/proxy plugins. | ||
Some examples of such masking are [https://code.optmstc.dev/opt/ip-random opt/ip-random] and [https://code.hcesaropz.dev/hcesaropz/unibom-masker hcesaropz/unibom-masker]. | |||
[[Category:Kaboom]] | [[Category:Kaboom]] | ||
Latest revision as of 04:17, 31 August 2026
IP masking refers to the practice of replacing real IP addresses with psuedorandom addresses, with the same original address producing the same psuedorandom address. This practice allows for increased player privacy on Kaboom and clones while still allowing for the accounts of a single IP address to be identified.
SNAT[edit]
This is the most common method of IP masking, as it is the method employed by Kaboom. Usually, this is done via iptables, but similar programs like nftables are able to achieve similar results.
The script to setup this particular method is available in the kaboomserver/framework repo.
Other means[edit]
On some clones, due to technical limitations like being behind a proxy, not having administrator access or not having a firewall capable of this, the operators may choose to provide IP masking via Ignite mods or server/proxy plugins.
Some examples of such masking are opt/ip-random and hcesaropz/unibom-masker.
