ejabberd IP logs

[elexis]

If some lobby player violates the Terms of Use and creates many lobby accounts again and again, the lobby moderators are forced to either check every suspicious account for the IP through the GUI (many clicks, copy & pastes) or grep the ejabberd logs.

Both methods are uncomfortable. The ejabberd logs don't have the username and IP address in the same line and there can be unrelated lines in between. Furthermore the ejabberd logs are verbose and contain uninteresting information.

We use the mod_muc_log ejabberd module to write more readable lobby chatlogs.

These should contain the IP address for every join message, specifically this one:

​https://github.com/processone/ejabberd/blob/master/src/mod_muc_log.erl#L370

The IP address of the player can be easily obtained as seen in our mod_ipstamp:

​https://trac.wildfiregames.com/browser/ps/trunk/source/tools/XpartaMuPP/mod_ipstamp.erl#L49

[elexis]

The alternative approach is to have a bot that saves the IP address when registering or joining to a custom database.