This top screen shot is from Mystic Pi A36 - USER and STATUS fields are empty Only SERVER and ORIGIN are filled.

Ú Messages ¿ Ú Connections ¿ Ú Events ¿ Ú Stats ¿ ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ
³ SERVER USER STATUS ORIGIN

³ ÄÄÄÄÄÄ ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ
³ TELNET Unknown 98.146.163.184


This is Windows Mystic A 37 fields are there. What gives?

Ú Messages ¿ Ú Connections ¿ Ú Events ¿ Ú Stats ¿ ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ
³ SERVER USER STATUS ORIGIN

³ ÄÄÄÄÄÄ ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ
³ TELNET tenser |07:-(|11 posting msg 23.30.150.137

²ß±ß° {tHE.pIRATE.kING} ÜßÛßÜ
ß²Ü°ß HOIST THE COLOURS ßÛÜÛß
þþþ NEVER SHALL WE DIE. ÝÝÞ

--- Mystic BBS v1.12 A37 2017/12/09 (Windows/32)
* Origin: ACiD Telnet HQ / blackflag.acid.org (21:1/112)

This top screen shot is from Mystic Pi A36 - USER and STATUS fields are empty Only SERVER and ORIGIN are filled.

In this particular case the user is unknown, so there isn't a user name or status yet. Its a user sitting at the login prompt or matrix most likely.

--- Mystic BBS v1.12 A37 2017/12/10 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

On 12/12/17, g00r00 said the following...

This top screen shot is from Mystic Pi A36 - USER and STATUS fields a empty Only SERVER and ORIGIN are filled.

In this particular case the user is unknown, so there isn't a user name
or status yet. Its a user sitting at the login prompt or matrix most likely.

That or zombie systems hammering your port. I pretty much constantly had
random systems from primarily Japan and Colombia connecting and disconnecting over and over again until I configured fail2ban to watch MIS.

--- Mystic BBS v1.12 A36 2017/12/03 (Linux/64)
* Origin: Subcarrier BBS (21:2/140)

In this particular case the user is unknown, so there isn't a user name
or status yet. Its a user sitting at the login prompt or matrix most likely.

Ok im on the board right now and no matter what menu i go to those fields are still blank on my Pi A36

TELNET Unknown 65.35.153.211
^^^^^^^^^^^^^
thats my ip

²ß±ß° {tHE.pIRATE.kING} ÜßÛßÜ
ß²Ü°ß HOIST THE COLOURS ßÛÜÛß
þþþ NEVER SHALL WE DIE. ÝÝÞ

--- Mystic BBS v1.12 A36 2017/12/04 (Raspberry Pi/32)
* Origin: ACiD Underworld // Victor Ludorum (21:1/188)

This top screen shot is from Mystic Pi A36 - USER and STATUS fields a empty Only SERVER and ORIGIN are filled.

In this particular case the user is unknown, so there isn't a user name
or status yet. Its a user sitting at the login prompt or matrix most likely.

Nope user was at the main menu

²ß±ß° {tHE.pIRATE.kING} ÜßÛßÜ
ß²Ü°ß HOIST THE COLOURS ßÛÜÛß
þþþ NEVER SHALL WE DIE. ÝÝÞ

--- Mystic BBS v1.12 A37 2017/12/09 (Windows/32)
* Origin: ACiD Telnet HQ / blackflag.acid.org (21:1/112)

That or zombie systems hammering your port. I pretty much constantly had random systems from primarily Japan and Colombia connecting and disconnecting over and over again until I configured fail2ban to watch MIS.

Just FYI Mystic can auto-block IP after a configured amount of connections and you can have it automatically add the IP to IPTables so they can't connect at all to anything (via Mystic IP event). You don't need fail2ban to get the
same effect.

--- Mystic BBS v1.12 A37 2017/12/10 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

On 12/12/17, g00r00 said the following...

Just FYI Mystic can auto-block IP after a configured amount of
connections and you can have it automatically add the IP to IPTables so they can't connect at all to anything (via Mystic IP event). You don't need fail2ban to get the same effect.

I'm actually using the MIS autoblock/ban logs to trigger fail2ban. I just wanted all the zombie boxes to stop hanging off my nodes and filling the
logs.

--- Mystic BBS v1.12 A36 2017/12/03 (Linux/64)
* Origin: Subcarrier BBS (21:2/140)

I'm actually using the MIS autoblock/ban logs to trigger fail2ban. I just wanted all the zombie boxes to stop hanging off my nodes and filling the logs.

Yep, I understand that. :)

What I am trying to explain is that Mystic can already do exactly what you're using fail2ban to do, but it does it more gracefully because it doesn't involve log monitoring or another piece of software.

fail2ban scans Mystic's log files and then turns around to create a firewall rule if it reads certain things in the log file. Mystic can also create the same firewall rules out of the box, without extra software.

--- Mystic BBS v1.12 A37 2017/12/10 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

On 12/12/17, g00r00 said the following...

fail2ban scans Mystic's log files and then turns around to create a firewall rule if it reads certain things in the log file. Mystic can
also create the same firewall rules out of the box, without extra software.

Oh I get that, but the setup here isn't conducive to that configuration. I should mention that I have Mystic running entirely unprivileged on a shared system. I can't feasibly give it access to iptables without breaking security policies. We're also using IPset hashes for blacklisting and not individual iptables rules.

--- Mystic BBS v1.12 A36 2017/12/03 (Linux/64)
* Origin: Subcarrier BBS (21:2/140)

On 12/12/17, Hawk Hubbard said the following...

In this particular case the user is unknown, so there isn't a user na or status yet. Its a user sitting at the login prompt or matrix most likely.

Ok im on the board right now and no matter what menu i go to those
fields are still blank on my Pi A36

TELNET Unknown 65.35.153.211

I can second this. I haven't checked on the pi system, but on Linux 64bit,
I'm online, and on the MIS screen, it shows:

TELNET Unknown 67.61.21.181 (my IP)


---

Black Panther
a.k.a. Dan Richter
Sysop - Castle Rock BBS (RCS)
The sparrows are flying again....

--- Mystic BBS v1.12 A37 2017/12/09 (Linux/64)
* Origin: Castle Rock BBS - castlerockbbs.com (21:1/186)

On 12/12/17, Hawk Hubbard said the following...

In this particular case the user is unknown, so there isn't a user na or status yet. Its a user sitting at the login prompt or matrix most likely.

Ok im on the board right now and no matter what menu i go to those
fields are still blank on my Pi A36

TELNET Unknown 65.35.153.211

Yup, same issue here on the pi version... :(


---

Black Panther
aka Dan Richter
Sysop - Castle Rock BBS
The sparrows are flying again...

--- Mystic BBS v1.12 A36 2017/12/04 (Raspberry Pi/32)
* Origin: CRBBS Pi Test System (21:1/186.1)

Ok im on the board right now and no matter what menu i go to those fields are still blank on my Pi A36
TELNET Unknown 65.35.153.211

Yup, same issue here on the pi version... :(
Black Panther

Thanks for confirming the problem.

²ß±ß° {tHE.pIRATE.kING} ÜßÛßÜ
ß²Ü°ß HOIST THE COLOURS ßÛÜÛß
þþþ NEVER SHALL WE DIE. ÝÝÞ

--- Mystic BBS v1.12 A37 2017/12/09 (Windows/32)
* Origin: ACiD Telnet HQ / blackflag.acid.org (21:1/112)