Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
The subnet.conf system has been rewritten to offer greater flexibility, and to fix some issues that appeared with 838321a. It is now possible to enter, separately, LAN subnets: - `lan_subnets`: This is essentially the same feature present in the old subnet.conf. Each entry in this list defines a (LAN, private) subnet the server is in. Clients connecting from the same subnet, will be redirected to the LAN IP rather than the default public IP. The format has been simplified, and it only requires one IP and one subnet mask (as opposed to a character and a map server IP). - `allowed`: Allowed IPs are IP ranges a server (char to login or map to char) can connect from. Any attempt to connect as a server from an IP not included here, will fail. For convenience, a wildcard range (matching all possible IP addresses) has been provided (`0.0.0.0:0.0.0.0`), but it is very advisable to edit it to a more restrictive set. - `trusted`: Trusted IPs are IP ranges excluded from the IPban checks. This may be useful, for example, to exclude the server's own IP from ipbans, in case of false positives. Any IP ranges added to this list are also implicitly included in the allowed IP ranges.
- Loading branch information
1 parent
a8e54e5
commit e13f1f7
Showing
8 changed files
with
302 additions
and
184 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,37 @@ | ||
// Network configuration file | ||
|
||
/* | ||
* List here any LAN subnets this server is in. | ||
* Example: | ||
* - char- (or map-) server's IP in LAN is 192.168.0.10 | ||
* - Public IP is 198.51.100.37 | ||
* If the list contains "192.168.0.10:255.255.255.0", any clients connecting | ||
* from the same 192.168.0.0/24 network will be presented with the LAN IP | ||
* (192.168.0.10) in the server list, rather than the public IP (198.51.100.37). | ||
*/ | ||
lan_subnets: ( | ||
"127.0.0.1:255.0.0.0", | ||
// "192.168.1.1:255.255.255.0", | ||
) | ||
|
||
/* | ||
* List here any IP ranges a char- or map-server can connect from. | ||
* A wildcard of "0.0.0.0:0.0.0.0" means that server connections are allowed | ||
* from ANY IP. (not recommended). | ||
*/ | ||
allowed: ( | ||
"0.0.0.0:0.0.0.0", | ||
// "127.0.0.1:255.0.0.0", | ||
) | ||
|
||
/* | ||
* List here any IP ranges a char- or map-server can connect from. These ranges | ||
* will also be excluded from the automatic ipban in casee of password failure. | ||
* Any entry present in this list is also automatically included in the | ||
* allowed IP list. | ||
* Note: This may be a security threat. Only edit this list if you know what | ||
* you are doing. | ||
*/ | ||
trusted: ( | ||
"127.0.0.1:255.0.0.0", | ||
) |
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.