mfsipmap.cfg
The file that says which Chunkserver address a client is given, where the same machines answer on unrelated addresses in each LAN. The file keeps the traffic of a client inside the network that client connects from: the Master Server hands out the address from the asking machine's own network instead of the address the Chunkserver registered with.
How the file is built
An entry is two lists: the client addresses a remapping applies to, and the mappings themselves. Each mapping list applies to the client list that precedes it in the file. The file holds as many pairs of lists as your network needs. Lines starting with # are comments.
Client addresses
| Form | Meaning |
|---|---|
n.n.n.n/m.m.m.m | An address class, written as a network address and a mask. |
n.n.n.n/b | An address class, written as a network address and a number of significant bits. |
f.f.f.f-t.t.t.t | An address range, both ends included. |
n.n.n.n | A single address. |
A shortened address stands for the same class: a.b.c/24 is a.b.c.0/24, and a.b/255.255.0.0 is a.b.0.0/255.255.0.0.
Mappings
| Form | Meaning |
|---|---|
n.n.n.n:r.r.r.r | A client of the preceding client list reaches the Chunkserver the Master Server knows as n.n.n.n under the address r.r.r.r. |
One Chunkserver may be given a different address for each client list.
A mapping whose left side is the address of a Master Server works the same way PRO (PRO Edition only): the address of the leading Master Server is substituted before it is given to a client, a Metalogger or a Chunkserver.
Example
Clients in the three groups reach the Chunkserver 10.10.10.3 under 10.20.30.7, and the Chunkserver 10.10.10.4 under 10.20.33.19:
192.168.1/24
192.168.2.1-192.168.2.24
192.168.3.20
10.10.10.3:10.20.30.7
10.10.10.4:10.20.33.19
Where the LANs number their machines alike
A machine that keeps the same suffix in every LAN needs no mapping file: MULTILAN_BITS and MULTILAN_CLASSES in mfsmaster.cfg translate such addresses on their own.